Question 770
During an operational security assessment at a public-sector technology agency, the team documents this issue: A shared cache makes builds faster but prevents auditors from recreating the approved release. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which TWO responses form a sound implementation-and-verification pair for this issue? (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Optimize pipelines without losing immutable release manifests, approvals, test outcomes or traceability required for incident investigation. The action targets the recorded failure (A shared cache makes builds faster but prevents auditors from recreating the approved release), and is intended to reduce the corresponding risk: Speed-driven changes can remove the records needed to prove what code, tests and approvals reached production.
Correct verification. A faster run still retains the deployed commit, package digest, linked approvals and test evidence for a sampled incident. The measurement or controlled test provides evidence for the issue (A shared cache makes builds faster but prevents auditors from recreating the approved release) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Monitor build and deployment failure rates and execution duration by pipeline stage, separating flaky tests from deterministic failures. This does not supply the required release pipeline retention and auditability optimization action-and-control pair.
Apply retention policies that preserve approved release binaries, deployment evidence and audit logs while expiring temporary build data. The release pipeline retention and auditability optimization implementation and safeguard are still missing.
Measured queue wait falls within the agreed threshold after tuning parallelism without a disproportionate increase in idle capacity. The two-part release pipeline retention and auditability optimization control remains unsatisfied.