Question 310
During an operational security assessment at a public-sector technology agency, the team documents this issue: An emergency rollback cannot reconstruct the library graph from the prior release. 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. Commit ecosystem lockfiles, authenticate feeds and enforce locked dependency restore in automated builds to control transitive package changes. The action targets the recorded failure (An emergency rollback cannot reconstruct the library graph from the prior release), and is intended to reduce the corresponding risk: Unpinned transitive dependencies and nondeterministic restores can change deployed binaries without a reviewed code change.
Correct verification. Two isolated builds of the tagged revision resolve identical dependency versions and produce traceable artifact provenance. The measurement or controlled test provides evidence for the issue (An emergency rollback cannot reconstruct the library graph from the prior release) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Use a documented calendar versioning scheme paired with commit SHA or build run provenance when release timing matters more than API compatibility. The paired controls concern supply chain lockfiles and reproducibility, not that measure.
A breaking contract change produces an appropriate major-version promotion and consumers remain pinned until tested. The supply chain lockfiles and reproducibility implementation and safeguard are still missing.
Publish versioned packages to GitHub Packages with repository-scoped workflow permissions and verified consuming-repository access. The two-part supply chain lockfiles and reproducibility control remains unsatisfied.