Question 340
At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A pipeline declares success when configuration API calls return 200 despite OSPF sessions remaining down on edge routers. What should the engineer change first to resolve this specific issue?
Explanation
Correct Answer
Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. This addresses the problem because deployment command success is not the same as verified service success; operational checks must follow state changes. Confirm success using: The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence.
Incorrect Answers
This alternative is a response to another technical cause: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The reported case instead depends on: deployment command success is not the same as verified service success; operational checks must follow state changes. The action that directly addresses it is “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent”.
The offered action targets: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The case facts point instead to: deployment command success is not the same as verified service success; operational checks must follow state changes. Implement “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent” to address that specific condition.
This alternative is a response to another technical cause: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The reported case instead depends on: deployment command success is not the same as verified service success; operational checks must follow state changes. The action that directly addresses it is “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent”.