Question 200
At the Redhaven customer support provider, following an unexpected peak in customer demand, a security patch for an older supported version accidentally ships unfinished new features from main. Which maintenance practice best addresses the continuing risk?
Explanation
Correct Answer
After the immediate fix, the priority is to review branch support windows and backport approvals after each product release. This reinforces the control against the original weakness: applying an unrelated development head can introduce changes outside a maintenance release. This directly addresses the reported issue at the Redhaven customer support provider.
Incorrect Answers
This routine applies to branch policy required reviewers, but it does not maintain the specific correction needed for the problem at the Redhaven customer support provider.
That practice helps control a different risk: untrusted pull request code can abuse secrets or privileged runner contexts if not separated. The recurring control here should be to review branch support windows and backport approvals after each product release. For the Redhaven customer support provider, the priority is to maintain controlled maintenance branches for supported releases and backport only verified fixes.
The alternative suggests that the team review sparse selection rules whenever project dependencies change; it would not directly prevent the observed issue from returning. For the Redhaven customer support provider, the priority is to maintain controlled maintenance branches for supported releases and backport only verified fixes.