During training, staff mix up “infrastructure as code” with “ARM templates.” How should the instructor separate the two ideas?
Select an answer to reveal the explanation.
Short Explanation
IaC is the habit — describe infra in code. ARM templates are one Azure way to do that habit. Practice versus tool: keep those labels straight and the class stays unconfused.
Full Explanation
Infrastructure as code is the practice of defining infrastructure in code or templates for consistent, repeatable deployment. ARM templates are one Azure implementation vehicle: JSON documents that declaratively describe Azure resources for Azure Resource Manager to deploy. Practice versus tool—keep those labels straight. Staff can use ARM templates, and other IaC approaches, in service of the same practice.
Saying ARM templates are the only possible meaning of IaC and banning all other tools collapses the practice into a single file format. Calling IaC a Microsoft billing SKU while calling ARM templates availability zones mixes commercial/geography concepts with deployment methods. Claiming IaC and ARM templates are unrelated marketing phrases denies the real technical link: ARM templates are a concrete way to do IaC on Azure.
Exam caveat: AZ-900 expects conceptual separation (practice vs example tool), not expertise in every alternative IaC stack. Operational check: show learners a simple ARM template side by side with the sentence “this file is one IaC artifact,” deploy it to a lab resource group, then ask them to label which term is the practice and which is the vehicle. Prefer one classroom slide that labels practice on top and ARM template under example tools to lock the mental model.