Configure Multi-Agent Collaboration from Copilot Studio AB-620 Practice Questions (Page 3)

Questions 11–15

1. 11expert · hard

   A company is designing a multi-agent solution in Copilot Studio. They have a Foundry agent for technical support, a Fabric data agent for analytics, and an external agent that supports A2A for inventory management. The main agent must route requests to the appropriate agent based on the user's intent. The company wants to minimize the number of topics and prefer a centralized routing mechanism. What should the architect do?

   • ACreate a single topic that uses conditions to check the user's intent and then invokes the appropriate agent using the correct integration method (plugin, plugin, or A2A).
   • BUse the A2A protocol to connect all three agents to the main agent, using the same integration method for all.
   • CCreate custom connectors for all three agents to ensure a uniform integration method.
   • DCreate separate topics for each agent, each with its own trigger and integration method.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   When designing a multi-agent solution in Copilot Studio, what is a key consideration for how agents should interact with each other?

   • AAgents should always be independent and never communicate with each other
   • BAgents should be designed to hand off to each other when a user request falls outside their expertise
   • CAgents should only interact with the user, never with other agents
   • DAgents should all be configured with identical instructions to ensure consistency
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A global logistics company is designing a multi-agent solution. They have three agents: one for shipment tracking, one for customs documentation, and one for customer billing. The agents need to work together to resolve a customer inquiry that spans all three domains. The solution must be flexible so that agents can be added or removed without disrupting the overall system. What is the most important design consideration?

   • ADefine a clear orchestration pattern that determines how agents communicate and hand off work.
   • BMake all agents use the same programming language to simplify integration.
   • CEnsure each agent has its own dedicated database to avoid data conflicts.
   • DCombine all three agents into a single, larger agent to simplify the architecture.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A company is designing a multi-agent solution in Copilot Studio. The main agent must hand off a customer request to a specialized billing agent, but the billing agent must first receive the customer's account ID and the reason for the inquiry. The company wants the handoff to be managed entirely within Copilot Studio without custom code. What should the architect configure?

   • ACreate a topic in the main agent that triggers on the billing intent, then use the 'Redirect to another agent' action and pass the account ID and reason as input variables.
   • BCreate a new topic in the billing agent that asks for the account ID and reason, and instruct the main agent to simply transfer the conversation without any data.
   • CUse the A2A protocol to send a message to the billing agent's endpoint, embedding the account ID and reason in the message payload.
   • DConfigure the billing agent as a plugin in the main agent and call it from a topic using the 'Send a message' action.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A multinational corporation is building a multi-agent system. They have a Copilot Studio agent for HR, a Foundry agent for legal compliance, and a third-party agent for payroll. The legal compliance agent must be integrated, but it is only available in a specific region. The solution must ensure data residency requirements are met. What is the most important consideration?

   • AEnsure the A2A protocol is used for all communications to maintain a standardized interface.
   • BEnsure the Foundry agent is deployed in a region that meets the data residency requirements.
   • CRecreate the legal compliance agent's logic in Copilot Studio to avoid regional issues.
   • DIntegrate the Foundry agent using the native integration to simplify the setup.
   Reveal Solution Discussion Select an answer first