Question 190
During an operational security assessment at a public-sector technology agency, the team documents this issue: A shared source update breaks a consumer without any recorded dependency upgrade. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Select TWO: one corrective action and one test that confirms its effectiveness. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. The action targets the recorded failure (A shared source update breaks a consumer without any recorded dependency upgrade), and is intended to reduce the corresponding risk: Floating shared code references create nonreproducible builds and unexpected behavioral changes across consuming services.
Correct verification. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change. The measurement or controlled test provides evidence for the issue (A shared source update breaks a consumer without any recorded dependency upgrade) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. It is not the complementary risk control for git submodules and shared dependency versioning.
Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. The git submodules and shared dependency versioning implementation and safeguard are still missing.
Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The two-part git submodules and shared dependency versioning control remains unsatisfied.