Question 80
At the Greystone energy services group, a pull request closes an Azure Boards bug but no link exists between the work item and GitHub repository. How should the team reduce the chance of the issue recurring?
Explanation
Correct Answer
For the Greystone energy services group, the control should be maintained by having the team periodically test integration permissions and link behavior after repository transfers. It reduces the chance that disconnected planning and source platforms weaken evidence that a reported issue was fixed.
Incorrect Answers
This routine applies to release notes from git history, but it does not maintain the specific correction needed for the problem at the Greystone energy services group.
The alternative suggests that the team review overdue risk-based remediation intervals and recurring breaches; it would not directly prevent the observed issue from returning. For the Greystone energy services group, the priority is to configure supported Azure Boards–GitHub connection and require linked pull requests for status transitions.
This maintenance work is reasonable for release change lineage. The continuing exposure described here is that disconnected planning and source platforms weaken evidence that a reported issue was fixed. For the Greystone energy services group, the priority is to configure supported Azure Boards–GitHub connection and require linked pull requests for status transitions.