You need to design a solution that provides Fabrikam Inc.

Policy questions → Delegate to a knowledge-focused agent; Metric requirements → Delegate to a data-access agent; Transaction requirements → Delegate to a tools-first agent.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The architecture should separate responsibilities according to the kind of work each specialist performs. Policy and procedure questions depend on retrieval from curated, indexed content and therefore belong with a knowledge-focused agent. Operational measures such as backlog, SLA exposure, and parts shortages require governed, current business data; a data-access specialist, represented in this case by the Fabric Data Agent, is the correct destination. Creating a parts request or changing a service-case status is different from answering a question: it is an authenticated transaction and should be delegated to a tools-first agent that can invoke approved MCP operations. Putting all three responsibilities into one agent would increase the number of competing tools and knowledge sources, weaken routing precision, and duplicate logic already owned by specialist teams. The selected pattern also matches Fabrikam ' s requirement that capabilities evolve independently. Clear names, descriptions, inputs, and outputs remain essential because generative orchestration uses that metadata to decide which connected agent to invoke. This division gives the primary agent a coordination role while each specialist retains its own knowledge, privileges, release lifecycle, and audit boundary. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Design multi-agent solutions in Copilot Studio.

===============