AZ400-Q: govern a shared pipeline template
A shared deployment template is used by dozens of repositories. An accidental template change could affect every production deployment. What governance is required?
- A) Allow direct pushes to the template’s default branch for speed.
- B) Protect the template repository/branch, require review and validation, version or pin consumers appropriately, and communicate controlled changes. ✓
- C) Copy the template into each repository every week.
- D) Hide the template name from developers.
Answer: B. Central templates are high-impact dependencies and need change control, compatibility, and traceable rollout.
Why not the others: Direct push is unsafe, periodic copies drift, and obscurity is not a control.