A municipal engineer asks what an ARM template is at Azure Fundamentals depth. Which description is correct?
Select an answer to reveal the explanation.
Short Explanation
An ARM template is a JSON shopping list that says what Azure should build — declare it, then deploy it. It is not a screenshot, a guest driver, or an identity policy file.
Full Explanation
At Azure Fundamentals depth, an ARM template is a JSON file that defines Azure resources declaratively for deployment. You declare what should exist—resource types, names, properties, dependencies—and Azure Resource Manager processes that definition to deploy or update the environment. That declarative shopping-list mental model is the exam-ready description.
An ARM template is not a screenshot of the portal used as a legally binding contract; pictures are not deployable desired state. It is not a binary hypervisor driver installed inside every VM guest; guest drivers are unrelated to subscription-level declarative deployment documents. It is not a Conditional Access policy written only in XML; Conditional Access is an Entra identity control with its own authoring surfaces, not an ARM template synonym.
Exam caveat: other IaC formats exist, and Bicep often compiles to ARM JSON—fundamentals still expect you to recognize ARM templates as the classic JSON declarative vehicle. Operational check: open a simple ARM template, identify resources declared in JSON, deploy to a sandbox resource group, and verify the deployed resources match the template’s declarations in the portal. Prefer validating a template in a non-production resource group first, then promoting the same definition through change control.