AI-103 Practice Question 44: Cross Project Agent Handoff
Microsoft Azure AI Apps and Agents Developer Associate (AI-103) · Test 5 · question 4 of 10
A retailer's shopping-assistant prompt agent already carries a large toolbox for inventory lookup, order status, and recommendations. A separate fraud team owns and independently maintains its own specialized fraud-scoring agent in a different Foundry project. The shopping assistant needs to hand off suspicious-order checks to that agent for a small subset of orders, while staying in control of the conversation itself. The team wants to reuse the fraud team's existing agent as-is, not rebuild its logic, and avoid standing up a full multistep orchestration just for this one hand-off.
What should the team do?
Show answer and explanation
Answer:
Microsoft names this exact case for the agent-to-agent (A2A) pattern: "for lightweight scenarios where one agent just needs to call another (without a formal, multistep workflow) expose an agent as an A2A endpoint and call it directly. This approach keeps the calling agent in control while it delegates a task to a specialized agent." Enabling incoming A2A on the fraud-scoring agent, wiring an A2A connection from the shopping assistant's project, and attaching the A2A tool lets the shopping assistant delegate without rebuilding anything or crossing project boundaries.
- A is wrong because function calling requires the shopping assistant's own application to implement and own the scoring logic. That reimplements exactly the capability the fraud team already built and maintains, instead of reusing it. - C is wrong because a Foundry workflow is built for repeatable, branching, human-in-the-loop orchestration across several steps. Standing up and maintaining a workflow graph for a single conditional hand-off is precisely the overhead the team wants to avoid. - D is wrong because it duplicates the fraud team's specialist inside another team's project instead of calling their independently owned and maintained agent; the two copies would drift, and connected agents (classic) are the older mechanism for agents built together in one project, not for delegating to another team's separately published agent.
Reference: Enable incoming A2A on a Foundry agent