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

Question 56 — AB-620 Practice Exam 5

For each OAuth 2.0 server capability, drag the appropriate Copilot Studio OAuth 2.0 sub-type to the Correct Match column.

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

Option Correct Match
The server supports Dynamic Client Registration (DCR) and exposes a discovery endpoint that can be used to locate the authorization and token endpoints automatically [Gap 1]
The server supports DCR without a discovery endpoint, so the maker supplies the Authorization URL and Token URL template [Gap 2]
The identity provider doesn't support DCR, so the maker supplies application credentials and OAuth endpoint information obtained through administrator coordination [Gap 3]

  1. API key
  2. Dynamic discovery
  3. Dynamic
  4. Manual

Correct answers

  1. Gap 1: Dynamic discovery
  2. Gap 2: Dynamic
  3. Gap 3: Manual

Explanations

Correct Matches

Dynamic discovery – This sub-type applies when the MCP server supports OAuth 2.0 Dynamic Client Registration and provides a discovery endpoint. Copilot Studio can locate the required OAuth endpoints and register the client automatically, reducing manual configuration.

Dynamic – This sub-type applies when DCR is supported but no discovery endpoint is available. The maker manually supplies the Authorization URL and Token URL template. After creation, a callback URL may be generated; when it appears, it must be supplied to the identity provider administrator for registration.

Manual – This sub-type is required when the identity provider does not support DCR. The maker provides the Client ID, Client secret, Authorization URL, Token URL template, Refresh URL, and optional Scopes. The identity provider administrator must register the application and provide the required credentials and endpoint information. The callback URL generated after creation must also be registered so the authorization flow can complete.

Unused Item(s)

API key – API key is a separate MCP authentication type and is not an OAuth 2.0 sub-type.