AZ400-Q: reuse a secure deployment pattern
Five services use the same approved deployment steps, but each has a different name and target environment. The platform team must update the steps centrally without allowing application teams to copy and change them. What should it use?
- A) Duplicate the steps in each repository and document the preferred version.
- B) Put the steps in a wiki and ask teams to copy them when needed.
- C) Store a reviewed YAML template in a controlled repository and pass only approved parameters from each pipeline. ✓
- D) Put all deployment commands in a variable group.
Answer: C. YAML templates centralize reusable pipeline logic while parameters make permitted variation explicit. Protect the template repository and review changes because it becomes a supply-chain dependency.
Why not the others: Duplicated YAML drifts. A wiki is not executable version-controlled policy. Variable groups provide values, not structured job/stage behavior.