AZ400-Q: enforce review on a release branch
A release branch must accept only reviewed changes that pass a build and cannot be deleted by ordinary contributors. Which configuration is appropriate?
- A) A README instruction asking contributors to be careful.
- B) A tag on the release branch.
- C) Branch protection/rules requiring pull requests and status checks, restricting direct push and deletion to authorized roles. ✓
- D) Contributor access at Azure subscription scope.
Answer: C. Branch rules enforce the source-control workflow at the branch boundary.
Why not the others: Documentation and tags do not enforce repository actions. Azure subscription access is unrelated to Git branch protection.