Question 39 — AB-620 Practice Exam 4
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 tool mechanism.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Use an existing ready-made connection to a supported Microsoft or non-Microsoft service | [Gap 1] |
| Wrap an organization-owned REST API by using a low-code integration definition | [Gap 2] |
| Implement a deterministic multi-step automation with designed error-handling paths | [Gap 3] |
| Connect directly to an OpenAPI-described endpoint without creating a full connector | [Gap 4] |
| Centralize access to shared APIs that must be available to multiple agents | [Gap 5] |
| Operate a system that provides a graphical interface but no usable API | [Gap 6] |
| Reuse existing conversational components developed with the Bot Framework SDK | [Gap 7] |
- Computer use
- Prebuilt connectors
- Bot Framework skills
- Model Context Protocol servers
- REST API tools
- Agent flows
- Custom connectors
- Knowledge sources
- Agent connections
Correct answers
- Gap 1: Prebuilt connectors
- Gap 2: Custom connectors
- Gap 3: Agent flows
- Gap 4: REST API tools
- Gap 5: Model Context Protocol servers
- Gap 6: Computer use
- Gap 7: Bot Framework skills
Explanations
Correct Matches
Prebuilt connectors – A prebuilt connector is appropriate when a supported service already has a ready-made connection that the agent can use.
Custom connectors – Custom connectors provide a low-code method for exposing an organization's existing REST API to Copilot Studio.
Agent flows – Agent flows support deterministic multi-step automation and allow explicit error-handling paths to be designed into the process.
REST API tools (preview) – REST API tools provide direct OpenAPI integration without requiring the API to be packaged as a complete connector.
Model Context Protocol (MCP) servers – MCP servers are suited to scenarios in which several agents need shared API access and centralized tool management is preferable to configuring each agent separately.
Computer use – Computer use enables interaction through a graphical user interface when the target application does not provide an API suitable for direct integration.
Bot Framework skills – Bot Framework skills enable organizations to reuse existing pro-code conversational components created with the Bot Framework SDK.
Unused Item(s)
Knowledge sources – Knowledge sources ground answers in configured data; they are not action-execution mechanisms for these requirements.
Agent connections – Agent connections delegate work to specialized agents rather than directly implementing the action mechanisms described in the table.