Question 57 — AB-620 Practice Exam 3
For each MCP server authentication requirement, drag the appropriate authentication type to the Correct Match column.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Connects without credentials when network-level controls provide sufficient protection for a fully trusted or internal server | [Gap 1] |
| Uses a secret supplied independently by each user rather than embedding one shared credential in the agent configuration | [Gap 2] |
| Delegates authentication to an identity provider and provides the agent with a user-scoped token after authorization | [Gap 3] |
| Provides the stronger choice for production access to sensitive data when the server and identity provider support it | [Gap 4] |
- OAuth 2.0
- None
- Shared password
- API key
Correct answers
- Gap 1: None
- Gap 2: API key
- Gap 3: OAuth 2.0
- Gap 4: OAuth 2.0
Explanations
Correct Matches
None – This authentication type sends MCP requests without credentials. It is suitable when a fully trusted or internal server relies on network-level protections and does not expose data requiring stronger credential-based controls.
API key – API key authentication uses a secret associated with each individual user. The credential value is supplied by the user rather than stored as a single shared key in the MCP server configuration.
OAuth 2.0 – OAuth 2.0 delegates identity verification to an identity provider and gives the agent a user-scoped token after the authorization flow. It provides stronger identity guarantees for production workloads involving sensitive data when the required infrastructure supports it.
Unused Item(s)
Shared password – Shared password authentication is not one of the MCP server authentication types available in Copilot Studio.