Question 510
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 technical evidence should be required before closing this change?
Explanation
Correct Answer
GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces. This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. It checks the technical distinction: A deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Applied here, the relevant facts are: A deployment stage targets all routers at once despite an approved plan to canary one site before fleet rollout. The question asks what technical evidence should be required before closing this change.
Incorrect Answers
That test belongs to another control with this basis: This directly verifies the related correction: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. In the current case, the governing reason is: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The direct verification is “GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces”.
The alternative verifies a different condition: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. The current case instead depends on: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. Confirm that “GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces”.
That test belongs to another control with this basis: This directly verifies the related correction: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. In the current case, the governing reason is: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The direct verification is “GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces”.