Question 60
While checking a production data center change, the team finds: An automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure. Which deployment safeguard most directly reduces this failure risk?
Explanation
Correct Answer
This safeguard addresses rest api authorization status handling: The REST client does not distinguish insufficient authorization from retryable transport or server errors. The appropriate prevention is: Build explicit error classification and bounded retries into every infrastructure API client. Other subsystem controls would not address the specified recurring failure.
Incorrect Answers
The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. “Document shell boundaries and supported packages before on-box automation deployment” would address that alternative cause, not the condition in this question: the REST client does not distinguish insufficient authorization from retryable transport or server errors.
“Test rerun behavior and configuration diffs before scheduling on-box Python automation” responds to this separate finding: the script lacks an idempotent precheck to compare desired and current network device state. This question instead needs “Build explicit error classification and bounded retries into every infrastructure API client”, so the alternative does not meet the stated condition.
The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. “Audit scheduler job frequency and execution history after automation changes” applies to that separate problem. The observed case is an automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure; choosing this alternative would address the wrong failure mode.