Question 220
During an operational security assessment at a public-sector technology agency, the team documents this issue: An audit requires a clear record of who reversed a problematic change. 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 non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The action targets the recorded failure (An audit requires a clear record of who reversed a problematic change), and is intended to reduce the corresponding risk: Resetting shared history disrupts collaborators and can erase the audit trail of a production correction.
Correct verification. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. The measurement or controlled test provides evidence for the issue (An audit requires a clear record of who reversed a problematic change) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The git revert versus reset incident recovery implementation and safeguard are still missing.
Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. It is not the complementary risk control for git revert versus reset incident recovery.
A new developer checks out a targeted component with required history while repository transfer and disk use are reduced. This does not supply the required git revert versus reset incident recovery action-and-control pair.