What is the primary purpose of adding a REST API to an AI agent in Copilot Studio?

To manage user authentication within the agent

To enable the agent to exchange data with external systems

To improve the agent's ability to understand user intent

To customize the agent's visual appearance

An organization has an existing custom connector that calls an external CRM system. They want their Copilot Studio agent to use this connector to retrieve customer details. What is the required step to enable this?

Write a Power Automate flow to call the connector and expose it as a topic.

Add the custom connector as a tool in the agent's configuration and define the appropriate actions.

Publish the connector to the MCP catalog before using it.

Recreate the connector as a REST API in the agent's code.

An administrator is troubleshooting a Copilot Studio agent that uses a custom connector. The agent is failing intermittently with timeout errors. The administrator has already increased the timeout setting, but the issue persists. What should they do next?

Disable the connector and use a manual process.

Replace the custom connector with a REST API tool.

Increase the timeout further to 2 minutes.

Check the custom connector's performance analytics to see if the downstream API is slow.

A team wants to use an MCP tool that is not yet in their organization's catalog. They need to make it available for multiple agents. What should they do first?

Publish the MCP tool to the organization's catalog.

Create a custom connector for the MCP tool.

Add the MCP tool directly to each agent individually.

Write a REST API wrapper for the MCP tool.

What is the benefit of integrating a tool into an AI agent using an existing custom connector in Copilot Studio?

It allows the agent to call external APIs without writing custom code

It provides a visual designer for creating conversation flows

It improves the agent's natural language understanding

It automatically translates the agent's responses into multiple languages

Microsoft Certified:AI Agent Builder Associate

Domain 2Objective 2

Add Tools to Agents AB-620 Practice Questions (Page 4)

Part of the Integrate and extend agents in Copilot Studio domain, which accounts for 40–45% of the AB-620 exam. Microsoft does not publish an official question count, but from its 120-minute exam (~50–80 total, ~20–36 in this domain), expect 5–9 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

5concepts

40–45%of the exam

Questions 16–20

16foundation · easy
What is the primary purpose of adding a REST API to an AI agent in Copilot Studio?
Select an answer first
17application · medium
An organization has an existing custom connector that calls an external CRM system. They want their Copilot Studio agent to use this connector to retrieve customer details. What is the required step to enable this?
Select an answer first
18expert · hard
An administrator is troubleshooting a Copilot Studio agent that uses a custom connector. The agent is failing intermittently with timeout errors. The administrator has already increased the timeout setting, but the issue persists. What should they do next?
Select an answer first
19application · medium
A team wants to use an MCP tool that is not yet in their organization's catalog. They need to make it available for multiple agents. What should they do first?
Select an answer first
20foundation · easy
What is the benefit of integrating a tool into an AI agent using an existing custom connector in Copilot Studio?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AB-620

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “AB-620” is a trademark of its owner, used for identification only.