Question 600
At the Westwick professional services firm, a complex classic release contains undocumented manual settings that teams want to move into a repository. What continuing safeguard is most appropriate?
Explanation
Correct Answer
After the immediate fix, the priority is to run side-by-side tests and formally retire classic definitions after verification. This reinforces the control against the original weakness: a format conversion without behavioral comparison can unintentionally remove release safeguards. This directly addresses the reported issue at the Westwick professional services firm.
Incorrect Answers
This routine applies to flaky pipeline trend, but it does not maintain the specific correction needed for the problem at the Westwick professional services firm.
That practice helps control a different risk: initial deployment compliance does not guarantee continuing host configuration consistency. The recurring control here should be to run side-by-side tests and formally retire classic definitions after verification. For the Westwick professional services firm, the priority is to migrate stages carefully to reviewed YAML while validating equivalent triggers, variables and approvals.
The alternative suggests that the team require pull request checks for production pipeline definition updates; it would not directly prevent the observed issue from returning. For the Westwick professional services firm, the priority is to migrate stages carefully to reviewed YAML while validating equivalent triggers, variables and approvals.