You have a project in Azure DevOps. You need to implement a new branching solution. The solution must ensure that all pull requests meet the following requirements: - Include linked work items. - Pass

Question

Options

• Abranch policies
• Bpull request templates
• Cbranch security
• Dpull request permissions

• A
  83% (33)
• B
  3% (1)
• C
  5% (2)
• D
  10% (4)

Explanation

Branch policies in Azure DevOps are the correct tool because they allow you to enforce specific rules directly on a branch, including requiring linked work items, passing build validation checks, and mandating a minimum number of reviewers before a pull request can be completed - all three requirements in this scenario.

Pull request templates (B) only provide a pre-filled description format for pull requests; they cannot enforce or validate any conditions. Branch security (C) controls who has permissions to perform actions on a branch (e.g., push, delete), but does not govern the quality gates a PR must pass. Pull request permissions (D) manage what actions users can take on pull requests, not what conditions must be met before merging.

Memory tip: Think of branch policies as gatekeepers - they block a PR from merging unless all configured rules are satisfied. Whenever a question mentions "requiring" or "enforcing" conditions on pull requests, branch policies are almost always the answer.

No community discussion yet for this question.