A platform team deploys the same three-tier environment repeatedly. They want deployments to be declarative, repeatable, version-controlled, and idempotent — the same template always produces the same environment. Which approach BEST fits?
- A. Infrastructure as code using ARM templates (or Bicep)✓ Correct
- B. Clicking through the Azure portal using a documented checklist
- C. Manually running individual CLI commands from memory
- D. Emailing configuration screenshots between engineers
Explanation
ARM templates (and Bicep) are Azure's infrastructure-as-code: declarative JSON/Bicep definitions that are idempotent, repeatable, and storable in source control. Portal checklists (B) and ad-hoc CLI (C) are imperative, error-prone, and drift over time. Option D isn't a deployment method at all — it's how configuration knowledge gets lost.