Question 27 — AB-620 Practice Exam 1
For each connected agent type, drag it to the appropriate box in the Correct Match column to match it with its integration role.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Connects to an independently published agent that exists in the same Power Platform environment | [Gap 1] |
| Provides access to an agent built and hosted in Microsoft Foundry | [Gap 2] |
| Enables natural-language interaction with organizational data stored through Microsoft Fabric and OneLake | [Gap 3] |
| Connects heterogeneous agents through an open cross-platform interoperability standard | [Gap 4] |
| Integrates a developer-built agent created for Microsoft 365 scenarios | [Gap 5] |
- Microsoft 365 Agents SDK agents
- Agent2Agent protocol agents
- Microsoft Foundry agents
- Microsoft Fabric Data agents
- Power Automate desktop flows
- Copilot Studio agents
Correct answers
- Gap 1: Copilot Studio agents
- Gap 2: Microsoft Foundry agents
- Gap 3: Microsoft Fabric Data agents
- Gap 4: Agent2Agent protocol agents
- Gap 5: Microsoft 365 Agents SDK agents
Explanations
Correct Matches
Copilot Studio agents – This connection type is used for existing Copilot Studio agents published in the same Power Platform environment, including agents maintained by other organizational teams.
Microsoft Foundry agents – These connections allow Copilot Studio to invoke agents hosted in Microsoft Foundry, including agents that use advanced models and reasoning capabilities.
Microsoft Fabric Data agents – These agents support conversational access to data managed in Microsoft Fabric by translating natural-language requests into queries over OneLake-connected data sources.
Agent2Agent (A2A) protocol agents – A2A provides an open protocol for connecting agents across heterogeneous platforms rather than limiting integration to one vendor's agent technology.
Microsoft 365 Agents SDK agents – These are developer-built agents created with the Microsoft 365 Agents SDK for Microsoft 365-oriented scenarios.
Unused Item(s)
Power Automate desktop flows – Desktop flows automate desktop processes and are not one of the connected-agent integration types represented by these mappings.