Question 350
At fictional Seabright Learning, an acceptance review of a reproducible simulation finds: A deployment stage targets all routers at once despite an approved plan to canary one site before fleet rollout. What ongoing engineering assurance should follow the successful fix?
Explanation
Correct Answer
Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions. This prevents the recurrence because a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. A matching immediate correction is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.
Incorrect Answers
The suggested review tracks a different technical risk: deployment command success is not the same as verified service success; operational checks must follow state changes. Here the sustained control must address: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Choose “Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions”.
That safeguard is relevant to: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The current failure instead follows from: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Its prevention measure is “Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions”.
This routine guards against another mechanism: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The recurring exposure in the current case is: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The matching preventive check is “Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions”.