Question 240
At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A Terraform linting job suddenly fails after a GitLab base image pulls an incompatible provider and Python library combination. Which engineering principle explains the described system behavior?
Explanation
Correct Answer
Unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. Acceptance should show: The runner resolves the reviewed versions and integration tests pass consistently across repeated clean builds.
Incorrect Answers
The offered statement is true for this other mechanism: The corresponding repair is: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. It does not explain the facts described here, which follow from: The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.
This principle describes a separate cause: The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The reported condition is governed by: The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. The two mechanisms should not be conflated.
The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.