Why should an automation script hold its own scoped API token rather than use an administrator's interactive session?
Select an answer to reveal the explanation.
Short Explanation
You want least privilege plus independent revocation. A person's session gives away far more than the script needs and disappears when they leave.
Full Explanation
The correct answer is the scoped-token option. A dedicated token can be limited to the operations the automation actually needs and revoked without disturbing anyone's access, whereas borrowing an administrator's session grants everything that administrator can do and breaks when their account changes. The interactive-session REST limitation option is incorrect because the objection is governance, not technical capability. The performance option is incorrect because performance is not the reason. The audit option is incorrect because administrative activity is recorded in the audit log regardless. For the exam, tie automation credentials to least privilege and independent revocation.