AZ-400 Question 15
Select 2You are a DevOps engineer at a software company that uses Azure DevOps for managing user stories, bugs, and code commits. Your team struggles to match existing bugs to the correct commits and verify that all test results are traceable to user stories. You need to design a solution that ensures source, bug, and quality traceability across the entire development lifecycle. Which two actions should you implement to achieve these goals?
- A
Enable 'Link work items to commits' in project settings and make it mandatory in pull request policies.
- B
Use specific mention of bug IDs in commit messages without linking them to Azure DevOps work items.
- C
Require all test results to be associated with bugs or user stories by publishing them to the corresponding work items in your build or release pipeline.
- D
Disable linking rules in the repository to avoid overhead and rely on manual references in the code review.
- E
Configure a branch naming convention that includes the related work item ID, ensuring a direct link from the branch name.
Show answer and explanation
Correct answers: A, C
Explanation
In Azure DevOps, traceability relies on linking work items, commits, and test results so that each bug or feature can be tracked from planning through to deployment. Configuring pull request policies to require a work item and publishing test results to those same work items are key steps in ensuring quality traceability. For more information, refer to Microsoft� official documentation on Azure Repos policies (https://docs.microsoft.com/azure/devops/repos) and Test Plans (https://docs.microsoft.com/azure/devops/test).
- A. Correct.
Correct. Enabling the link between commits and work items in Azure DevOps settings and enforcing it through pull request policies ensures that all code changes can be directly traced to relevant bugs or user stories. This is one of the most reliable methods to maintain source and bug traceability.
- B. Incorrect.
Incorrect. Merely mentioning bug IDs in commit messages without formally linking them to work items will not provide consistent traceability. Azure DevOps has built-in functionality for linking commits, which provides better tracking and reporting.
- C. Correct.
Correct. Publishing test results directly to associated bugs or user stories ensures that quality metrics can be traced from development to testing. By linking test results to work items, you can easily see which tests passed or failed for specific bugs or features.
- D. Incorrect.
Incorrect. Disabling linking rules runs counter to the goal of traceability. Relying solely on manual references in code reviews is error-prone and does not provide comprehensive visibility into changes, bugs, or test results.
- E. Incorrect.
Incorrect. Although a branch naming convention can aid developers in visually recognizing relevant work items, it does not guarantee full traceability within Azure DevOps. Formal linking from commits and test results to work items is still necessary for end-to-end visibility.