Question 130
At the Stonehaven digital retailer, release engineers squash unrelated fixes into one commit without retaining links to their individual work items. Which statement best identifies the control gap?
Explanation
Correct Answer
The issue is not simply a failed task; an overly compressed history can obscure which approvals and tests supported distinct changes. That is why the practical change is to use a reviewed merge strategy that preserves required change and work-item traceability. This directly addresses the reported issue at the Stonehaven digital retailer.
Incorrect Answers
That statement concerns merge queue validation; here the reported facts point to a different issue: an overly compressed history can obscure which approvals and tests supported distinct changes. For the Stonehaven digital retailer, the priority is to use a reviewed merge strategy that preserves required change and work-item traceability.
Uncontrolled ref rewrites can orphan changes and weaken forensic traceability. This can occur in other projects, but it is not the primary explanation at the Stonehaven digital retailer.
This explanation belongs to git lfs for binary assets. The immediate weakness in the question is that an overly compressed history can obscure which approvals and tests supported distinct changes. For the Stonehaven digital retailer, the priority is to use a reviewed merge strategy that preserves required change and work-item traceability.