Question 410
A containerized platform engineering team is working on GitLab-based infrastructure deployment pipeline. The team found that a squash merge hides the source of a critical network policy change in the resulting commit message. After remediation, which observation is the strongest evidence that this particular fault is resolved?
Explanation
Correct Answer
This evidence directly verifies the scoped correction, preserve traceable rationale and approval references in the squash commit and merge request, for the underlying issue: the merge description omits ticket links and constituent review context. It should be checked against actual device or pipeline output.
Incorrect Answers
This would confirm recovery from a topic branch cannot be merged because two authors edited the same ACL template lines, not necessarily from the reported incident. For the specified issue the relevant confirmation is: auditors can connect the consolidated change to underlying reviews and change approval.
This would confirm recovery from a change is rejected by server-side policy because a direct push targets protected main, not necessarily from the reported incident. For the specified issue the relevant confirmation is: auditors can connect the consolidated change to underlying reviews and change approval.
This would confirm recovery from a credential was committed and then deleted in a later revision, not necessarily from the reported incident. For the specified issue the relevant confirmation is: auditors can connect the consolidated change to underlying reviews and change approval.