Question 100
At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A bad network automation change has already been pushed to a protected shared branch and teammates have based work on it. What technical evidence should be required before closing this change?
Explanation
Correct Answer
The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state. This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. It checks the technical distinction: Git revert records an inverse patch in new history rather than moving shared branch pointers backward.
Incorrect Answers
This observation would test a different technical dependency: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The current issue is governed by: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Its decisive check is “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.
The alternative verifies a different condition: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The current case instead depends on: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Confirm that “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.
That test belongs to another control with this basis: This directly verifies the related correction: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. In the current case, the governing reason is: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. The direct verification is “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.