Question 420
At the Jasperfield insurance software group, a build references shared infrastructure code without pinning the exact external repository revision. What continuing safeguard is most appropriate?
Explanation
Correct Answer
The continuing risk is that an unpinned external repository can change the build input without local source updates. To sustain the correction, require dependency revision review during pipeline configuration changes. This directly addresses the reported issue at the Jasperfield insurance software group.
Incorrect Answers
That practice helps control a different risk: overly broad cache keys reuse incompatible compiled or restored content. The recurring control here should be to require dependency revision review during pipeline configuration changes. For the Jasperfield insurance software group, the priority is to configure repository resources with approved references and traceable checkout identities.
The alternative suggests that the team update canary success metrics with changing user flows; it would not directly prevent the observed issue from returning. For the Jasperfield insurance software group, the priority is to configure repository resources with approved references and traceable checkout identities.
This maintenance work is reasonable for pipeline reliability ownership. The continuing exposure described here is that an unpinned external repository can change the build input without local source updates. For the Jasperfield insurance software group, the priority is to configure repository resources with approved references and traceable checkout identities.