Question 42 — AB-650 Practice Exam 1
For each Microsoft Entra Agent ID object description, drag the appropriate object to the corresponding box in the Correct Match column.
Each item may be used once, more than once or not at all.
| Option | Correct Match |
|---|---|
| Provides the authentication foundation for one or more agent identities, stores credentials, and can apply policies such as Conditional Access across those identities | [Gap 1] |
| Represents a blueprint inside a particular tenant, can acquire tokens, and appears in that tenant's audit logs | [Gap 2] |
| Represents the runtime identity of a specific AI agent, has no credentials of its own, and maintains its own downstream permissions | [Gap 3] |
| Provides an optional one-to-one user object for an agent that must use a resource requiring a user account | [Gap 4] |
- Agent identity blueprint principal
- Agent's user account
- Agent identity blueprint
- Standalone service principal
- Agent identity
Correct answers
- Gap 1: Agent identity blueprint
- Gap 2: Agent identity blueprint principal
- Gap 3: Agent identity
- Gap 4: Agent's user account
Explanations
Correct Matches
Agent identity blueprint – This object is the authentication foundation for agent identities created from it. It stores the credentials used to acquire tokens on behalf of those identities, and policies applied at the blueprint level can affect all associated agent identities.
Agent identity blueprint principal – This object represents the blueprint's presence in a specific tenant. Microsoft Entra creates it when the blueprint is added to that tenant, enabling token acquisition and tenant-level audit visibility.
Agent identity – This is the runtime identity for a specific agent. It is a specialized service principal that does not maintain its own credentials because authentication depends on the associated blueprint. Each agent identity can still have its own permissions to downstream resources.
Agent's user account – This optional account is paired one-to-one with an agent identity when a target system requires a user object, such as certain mailbox, Teams, or document-library interactions. The user account and agent identity remain separate objects with different functions.
Unused Item
Standalone service principal – A standalone service principal can authenticate application or tool activity, but it is not one of the four Agent ID object types used to represent the complete governed agent model.