Question 160
An emergency change is proposed for: An orchestration token can read inventory but currently has organization-wide write permission with no justification. Which assumption would most directly undermine safe resolution of this exact problem?
Explanation
Correct Answer
The risky assumption is treating automation accounts as exempt from least-privilege governance because they are not humans. In this particular incident, an orchestration token can read inventory but currently has organization-wide write permission with no justification. The safer path is to inspect machine credential privileges, intended API calls and audit history for the integration and then, when verified, to issue a supported least-privilege token and restrict it to required read-only functions. The risk statement matters because it would obscure the true mechanism, broaden permissions, or falsely certify that the required outcome had been achieved.
Incorrect Answers
Blindly replacing the shared configuration with an older local copy during concurrent changes. The check concerns blindly replacing the shared configuration with an older local copy during concurrent changes, not confirming that treating automation accounts as exempt from least-privilege governance because they are not humans.
Assuming an automated API call is inherently safer than a human-operated change without governance. This assesses assuming an automated API call is inherently safer than a human-operated change without governance; it does not determine the reported condition—an orchestration token can read inventory but currently has organization-wide write permission with no justification.
Treating every scheduled run as a mandate to redeploy all NGFWs regardless of drift. The case-specific requirement is confirming that treating automation accounts as exempt from least-privilege governance because they are not humans, which that option does not establish.