Your company uses Azure DevOps. You need to recommend a method to validate whether the code meets the company's quality standards and code review standards. What should you recommend implementing in…

Question

Options

• Abranch folders
• Bbranch permissions
• Cbranch policies
• Dbranch locking

• A
  6% (3)
• B
  2% (1)
• C
  90% (43)
• D
  2% (1)

Explanation

Branch policies (Option C) are the correct choice because they allow you to enforce quality gates directly on branches in Azure DevOps, including requiring pull request reviews, linking work items, enforcing minimum reviewer counts, and integrating build validation to ensure code meets quality standards before merging.

Why the distractors are wrong:

• Branch folders (A) are simply an organizational tool for grouping branches by naming convention (e.g., feature/, bugfix/) - they enforce nothing.
• Branch permissions (B) control who can perform actions on a branch (like push or delete), not whether code quality or review standards are met.
• Branch locking (D) prevents any changes to a branch entirely, which is too restrictive and does not facilitate a review or quality process.

Memory tip: Think of branch policies as the rules of the road - they define the standards traffic (code) must meet before it can merge onto the main highway. If you need to validate quality, you need policies, not permissions or locks.

No community discussion yet for this question.