Question 360
While checking a production data center change, the team finds: A Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script. What is the primary technical reason the deployment fails?
Explanation
Correct Answer
The technical cause is The automation credential is stored insecurely and grants broader privileges than the script requires. The appropriate response is: Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests. Confirm successful repair: The job retrieves the required device data without exposing secrets in the repository or task logs.
Incorrect Answers
The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. “Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources” would address that alternative cause, not the condition in this question: the automation credential is stored insecurely and grants broader privileges than the script requires.
“Use stable approved resource IDs and validate organization scope before assigning Intersight policies” responds to this separate finding: the API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. This question instead needs “Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests”, so the alternative does not meet the stated condition.
The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. “Deploy the script in the approved supported shell environment with required dependencies and bounded permissions” applies to that separate problem. The observed case is a Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script; choosing this alternative would address the wrong failure mode.