AZ-400 Question 67
Select 3You are the lead developer for a team using Azure DevOps Repos with a 'develop' branch that serves as the primary integration branch. You plan to enforce a new pull request workflow with the following requirements: (1) at least two reviewers must approve any pull request, (2) all changes must pass a build before merging, and (3) merges are blocked if there are any active comments. You need to configure branch policies to satisfy these requirements. Which three actions should you take?
- A
A. Configure a Minimum number of reviewers policy and set the required approvals to 2
- B
B. Enable the 'Check for linked work items' branch policy
- C
C. Enable 'Require status checks to pass before merging' tied to a build pipeline
- D
D. Disable the auto-complete feature for the pull request
- E
E. Enable the 'Comment resolution' branch policy to block merging if comments are not resolved
Show answer and explanation
Correct answers: A, C, E
Explanation
To fulfill the stated requirements, you must first configure a minimum number of reviewers to mandate at least two approvals. Next, you link a build pipeline to the pull request and set 'Require status checks to pass before merging' so the build must succeed. Finally, enabling the comment resolution policy ensures no pull request with unresolved comments can be merged. For more information, refer to Microsoft Docs on Azure DevOps Branch Policies, which cover review requirements, build validation, and comment resolution in pull requests.
- A. Correct.
A. Correct. Configuring a Minimum number of reviewers policy with the threshold set to 2 ensures at least two people sign off on the changes before merging.
- B. Incorrect.
B. Incorrect. While linking work items is often considered a best practice for traceability, enabling 'Check for linked work items' does not enforce build success, reviewer count, or comment resolution.
- C. Correct.
C. Correct. Requiring status checks, such as a build pipeline to pass successfully, ensures the code compiles and tests run successfully before the pull request can be completed.
- D. Incorrect.
D. Incorrect. Disabling auto-complete is not directly tied to ensuring two approvals, a passing build, or blocking merges due to unresolved comments. Auto-complete is a convenience feature that automatically completes the pull request after all policies are met, but it does not enforce any of those policies itself.
- E. Correct.
E. Correct. Enabling the 'Comment resolution' policy means the pull request cannot merge unless all active comments have been resolved, preventing unresolved feedback from being overlooked.