Question 310
During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A GitLab deployment job compiles automation files on the production runner using a different dependency set than unit tests used. What technical evidence should be required before closing this change?
Explanation
Correct Answer
The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit. This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. It checks the technical distinction: A CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages.
Incorrect Answers
This observation would test a different technical dependency: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The current issue is governed by: This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Its decisive check is “The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit”.
The alternative verifies a different condition: This directly verifies the related correction: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The current case instead depends on: This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Confirm that “The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit”.
This observation would test a different technical dependency: This directly verifies the related correction: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. The current issue is governed by: This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Its decisive check is “The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit”.