Question 41 — AB-620 Practice Exam 3
For each Copilot Studio action-integration requirement, drag it to the appropriate box in the Correct Match column to match it with the most suitable integration pattern.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Integrate with a supported Microsoft or non-Microsoft service with no custom development | [Gap 1] |
| Create a reusable low-code OpenAPI wrapper for a proprietary REST API that multiple agents and flows will use | [Gap 2] |
| Connect a proprietary API for a single non-production use case without completing connector packaging | [Gap 3] |
| Centralize enterprise-managed tools so that many agents can consume the same server-managed definitions | [Gap 4] |
| Reuse an existing Bot Framework SDK conversational component that supports synchronous execution and private endpoints | [Gap 5] |
- Computer use
- Model Context Protocol
- REST API tool
- Prebuilt connector
- Bot Framework skill
- Custom connector
- HTTP request node
Correct answers
- Gap 1: Prebuilt connector
- Gap 2: Custom connector
- Gap 3: REST API tool
- Gap 4: Model Context Protocol
- Gap 5: Bot Framework skill
Explanations
Correct Matches
Prebuilt connector – A prebuilt connector provides a ready-made integration for supported Microsoft and non-Microsoft services and avoids custom development.
Custom connector – A custom connector wraps a REST API through an OpenAPI definition and is reusable across multiple agents and flows, making its setup investment suitable for shared integrations.
REST API tool (preview) – A REST API tool provides a direct route to a proprietary API when connector packaging is unnecessary for a limited, non-production use case.
Model Context Protocol (MCP) – MCP supports centrally managed tool servers that expose consistent tool definitions to multiple connected agents.
Bot Framework skill – Bot Framework skills allow existing conversational components built with the Bot Framework SDK to be reused in Copilot Studio, including components that require synchronous execution or private endpoints.
Unused Item(s)
HTTP request node – An HTTP request node configures a direct API call inline within a topic. It is designed for relatively simple one-off calls rather than the reusable or centrally managed requirements represented in the table.
Computer use – Computer use interacts with graphical interfaces when suitable APIs are unavailable. None of the listed requirements requires graphical-interface automation.