Question 58 — AB-650 Practice Exam 5
An autonomous AI agent continues operating after the employee who originally understood and managed it leaves the organization. The agent currently relies only on standalone service principals for the tools it calls. An administrator wants governance controls that make the agent accountable, distinguish its activity during investigations, and manage its identity as the agent changes over time. Which three capabilities does Microsoft Entra Agent ID add to address these requirements? (Select three answers)
Give every agent a paired user account regardless of the systems it accesses
Require human sponsorship so accountability can be assigned to the agent
Treat unrelated service principals used by individual tools as the complete identity of the agent
Generate agent-aware audit activity that can be reviewed as activity of a distinct agent identity
Use a blueprint-managed lifecycle to govern creation, renewal, and retirement of agent identities
Correct answers
Require human sponsorship so accountability can be assigned to the agent
Generate agent-aware audit activity that can be reviewed as activity of a distinct agent identity
Use a blueprint-managed lifecycle to govern creation, renewal, and retirement of agent identities
Explanations
Correct:
Require human sponsorship so accountability can be assigned to the agent
Sponsorship establishes human accountability for an agent. This helps prevent an agent from remaining operational indefinitely without a responsible person associated with it.
Generate agent-aware audit activity that can be reviewed as activity of a distinct agent identity
Agent-aware auditing makes the agent recognizable as a governed identity instead of allowing its actions to blend into generic application activity.
Use a blueprint-managed lifecycle to govern creation, renewal, and retirement of agent identities
Blueprint-managed lifecycle controls provide a governance structure for maintaining agent identities as agents are created, changed, renewed, or retired.
Wrong:
Give every agent a paired user account regardless of the systems it accesses
An agent's user account is optional. It is required when the agent must interact with a system that requires a user object, rather than as a general accountability mechanism for every agent.
Treat unrelated service principals used by individual tools as the complete identity of the agent
Separate service principals can authenticate individual tools, but they do not provide one governed identity representing the agent as a whole or supply the sponsorship, agent-aware auditing, and blueprint lifecycle controls required here.