Question 670
During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A merge introduces a network policy defect and a developer tries to revert the merge without identifying its mainline parent. What technical evidence should be required before closing this change?
Explanation
Correct Answer
The revert removes only the intended merge effect and network automation tests pass against the protected mainline. This directly verifies the related correction: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. It checks the technical distinction: Reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. Applied here, the relevant facts are: A merge introduces a network policy defect and a developer tries to revert the merge without identifying its mainline parent. The question asks what technical evidence should be required before closing this change.
Incorrect Answers
This observation would test a different technical dependency: This directly verifies the related correction: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. The current issue is governed by: This directly verifies the related correction: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. Its decisive check is “The revert removes only the intended merge effect and network automation tests pass against the protected mainline”.
That test belongs to another control with this basis: This directly verifies the related correction: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. In the current case, the governing reason is: This directly verifies the related correction: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. The direct verification is “The revert removes only the intended merge effect and network automation tests pass against the protected mainline”.
This observation would test a different technical dependency: This directly verifies the related correction: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. The current issue is governed by: This directly verifies the related correction: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. Its decisive check is “The revert removes only the intended merge effect and network automation tests pass against the protected mainline”.