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

Question 19 — AB-620 Practice Exam 3

For each connection requirement, drag it to the appropriate box in the Correct Match column to match it with the supported connected-agent option.

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

Option Correct Match
Connect to an independently published agent that already exists in the same Copilot Studio environment [Gap 1]
Connect to an agent that uses Azure AI Foundry for specialized model selection and reasoning configuration [Gap 2]
Surface conversational analytics over OneLake data sources through an agent created for structured-data access [Gap 3]
Connect to an independently hosted agent created with the Microsoft 365 Agents SDK [Gap 4]
Communicate with a partner agent on a non-Microsoft platform through the open Agent2Agent standard [Gap 5]

  1. A2A protocol agent
  2. Microsoft Foundry agent
  3. Child agent
  4. Existing Copilot Studio agent
  5. Orchestrator/subagent pattern
  6. Microsoft 365 Agents SDK agent
  7. Microsoft Fabric Data agent

Correct answers

  1. Gap 1: Existing Copilot Studio agent
  2. Gap 2: Microsoft Foundry agent
  3. Gap 3: Microsoft Fabric Data agent
  4. Gap 4: Microsoft 365 Agents SDK agent
  5. Gap 5: A2A protocol agent

Explanations

Correct Matches

Existing Copilot Studio agent – This option connects an orchestrator to a separately published agent in the same Copilot Studio environment while preserving independent ownership and deployment.

Microsoft Foundry agent – This option connects to an agent built in Azure AI Foundry when specialized model or reasoning configuration is required.

Microsoft Fabric Data agent – This option provides conversational access to analytics capabilities built over OneLake data sources.

Microsoft 365 Agents SDK agent – This option connects to an agent built and hosted with the Microsoft 365 Agents SDK outside the Copilot Studio agent implementation.

A2A protocol agent – This option uses the open Agent2Agent protocol to communicate with agents on non-Microsoft platforms that maintain their own reasoning.

Unused Item(s)

Child agent – A child agent is built inside its parent agent and is not one of the connection options for independently deployed agents.

Orchestrator/subagent pattern – This is a coordination pattern that determines how work is delegated, not a connection mechanism based on where an external agent was built.