AZ400-Q: protect the main branch

A team wants every production change reviewed and validated before merge. What should it configure?

  • A) Allow direct pushes for senior developers.
  • B) Require pull requests with required checks and review rules on the protected branch. ✓
  • C) Use tags instead of branches.
  • D) Grant repository owners permanent bypasses by default. Answer: B. Branch protection puts the review and validation policy at the merge boundary. Why not the others: Direct pushes and broad bypasses evade the control; tags do not replace review.

branch-protection · github-flow