AZ400-Q: validate pipeline-as-code changes

A pull request changes a shared YAML pipeline template. What should the repository require before merge?

  • A) No validation because YAML is not application code.
  • B) A production deployment only.
  • C) Syntax/lint and representative pipeline validation/tests, followed by required review under protected-branch rules. ✓
  • D) A longer commit message.

Answer: C. Pipeline code can change production behavior and must be tested/reviewed as a high-impact software artifact.

Why not the others: No validation or immediate production deploy is unsafe; prose length is not validation.

pipeline-yaml · pipeline-templates · branch-protection