Question 250
At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A GitLab job is marked failed after a network policy unit test, but the operator reruns deployment without inspecting the failing assertion. What acceptance check would prove the intended behavior was restored?
Explanation
Correct Answer
A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates. 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. It checks the technical distinction: A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.
Incorrect Answers
The alternative verifies a different condition: 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 case instead depends on: 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. Confirm that “A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates”.
That test belongs to another control with this basis: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. In the current case, the governing reason is: 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 direct verification is “A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates”.
This observation would test a different technical dependency: This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The current issue is governed by: 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. Its decisive check is “A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates”.