Question 42 — AB-620 Practice Exam 2
For each Copilot Studio integration approach, drag it to the appropriate box in the Correct Match column to match it with its defining characteristic.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Uses an integration published by Microsoft or a partner to expose predefined actions for supported external services | [Gap 1] |
| Describes an organization's API through OpenAPI and creates a reusable integration for Copilot Studio, Power Automate, Power Apps, and Azure Logic Apps in the same environment | [Gap 2] |
| Connects an agent directly to an API through an OpenAPI v2 definition without first creating a connector | [Gap 3] |
| Is created and managed through the Power Apps maker portal | [Gap 4] |
| Is created through a guided experience in Copilot Studio and stored on the environment-level Tools page | [Gap 5] |
- Prebuilt connector
- Custom connector
- REST API tool
- Connector knowledge source
Correct answers
- Gap 1: Prebuilt connector
- Gap 2: Custom connector
- Gap 3: REST API tool
- Gap 4: Custom connector
- Gap 5: REST API tool
Explanations
Correct Matches
Prebuilt connector – A prebuilt connector is published by Microsoft or a partner and exposes ready-made actions for supported services. It is generally the quickest integration approach when an appropriate connector already exists.
Custom connector – A custom connector defines an organization's API through OpenAPI and makes the resulting integration reusable across Copilot Studio, Power Automate, Power Apps, and Azure Logic Apps within the same environment. Custom connectors are created and managed through the Power Apps maker portal.
REST API tool – A REST API tool connects Copilot Studio directly to a REST API through an OpenAPI v2 specification without requiring a connector to be created first. It is configured through Copilot Studio and stored on the environment-level Tools page, allowing it to be added to agents in that environment.
Unused Item
Connector knowledge source – A connector configured as a knowledge source retrieves live external data to ground an agent's responses. It represents a different connector role rather than an API integration creation approach such as a prebuilt connector, custom connector, or REST API tool.