Why should automation use a purpose-created token rather than an administrator's personal token?
Select an answer to reveal the explanation.
Short Explanation
Use a purpose-created token so you can scope it to just what the automation needs, revoke it without breaking a person's access, and see it in audit logs as the automation instead of you.
Full Explanation
Purpose-created tokens are the right choice because they can carry minimal permissions, be revoked or rotated without affecting anyone's day-to-day work, and produce audit entries that identify the automation. The administrator's personal token loses all three benefits. The claim that personal tokens expire faster than automation tokens by design is incorrect because expiry is a configuration matter rather than an inherent difference between token types. The claim that personal tokens cannot be used by scripts at all is incorrect because personal tokens work technically; the objection is governance, not capability. The claim that personal tokens are rate limited more aggressively than other tokens is incorrect because rate limiting is not what distinguishes them. For the exam, tie dedicated tokens to scoping, independent revocation, and clean auditing.