Skip to main content
  1. Public practice questions
  2. AB-620 Practice Exams | AI Agent Builder Associate
  3. AB-620 Practice Exam 2

Question 39 — AB-620 Practice Exam 2

For each specialized-agent requirement, drag it to the appropriate box in the Correct Match column to match it with the supported Copilot Studio agent connection type.

Each item may be used once, more than once, or not at all.

Option Correct Match
Connect to a published agent in the same Copilot Studio environment that is configured to accept connections [Gap 1]
Connect to an agent created in Microsoft Azure AI Foundry by using a Foundry project endpoint [Gap 2]
Delegate reasoning over structured enterprise data maintained in Microsoft Fabric [Gap 3]
Connect to a code-built agent through the messaging endpoint provided by the Microsoft 365 Agents SDK [Gap 4]
Connect to an agent hosted on another platform through an endpoint that implements the open cross-platform A2A standard [Gap 5]

  1. Agent2Agent (A2A) protocol agents
  2. Bot Framework skills
  3. MCP servers
  4. Microsoft 365 Agents SDK agents (preview)
  5. Microsoft Fabric Data agents (preview)
  6. Microsoft Foundry agents (preview)
  7. Copilot Studio agents

Correct answers

  1. Gap 1: Copilot Studio agents
  2. Gap 2: Microsoft Foundry agents (preview)
  3. Gap 3: Microsoft Fabric Data agents (preview)
  4. Gap 4: Microsoft 365 Agents SDK agents (preview)
  5. Gap 5: Agent2Agent (A2A) protocol agents

Explanations

Correct Matches

Copilot Studio agents – A Copilot Studio agent can be connected when it is in the same environment, has been published, and is configured to accept connections.

Microsoft Foundry agents (preview) – Microsoft Foundry agents are created in Azure AI Foundry and are connected through a Foundry project endpoint.

Microsoft Fabric Data agents (preview) – Microsoft Fabric Data agents specialize in reasoning over structured enterprise data stored in Microsoft Fabric.

Microsoft 365 Agents SDK agents (preview) – These agents are implemented in code with the Microsoft 365 Agents SDK and are connected through their messaging endpoint.

Agent2Agent (A2A) protocol agents – A2A enables connections to agents on other platforms when they expose an endpoint compatible with the open Agent2Agent standard.

Unused Item(s)

Bot Framework skills – Bot Framework skills reuse existing Bot Framework SDK conversational components as tools; they are not one of the connected agent types represented by these requirements.

MCP servers – MCP servers centralize tool access to APIs for agents. They provide shared tool infrastructure rather than representing a delegated agent type.