Question 210
During an operational security assessment at a public-sector technology agency, the team documents this issue: A release rollback retrieves different source because the tag target was rewritten. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Choose TWO statements that provide both the appropriate correction and a meaningful test of its success. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The action targets the recorded failure (A release rollback retrieves different source because the tag target was rewritten), and is intended to reduce the corresponding risk: Moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence.
Correct verification. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. The measurement or controlled test provides evidence for the issue (A release rollback retrieves different source because the tag target was rewritten) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. It is not the complementary risk control for git tags and immutable releases.
Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. This does not supply the required git tags and immutable releases action-and-control pair.
A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. The paired controls concern git tags and immutable releases, not that measure.