Infrastructure as code
CoreARM templates
JSON declarative resource definition, parameters, variables, and outputs.
Key points
- JSON documents declare parameters, variables, resources, properties, dependencies, and outputs.
- Deploy through Resource Manager at a supported target scope.
- API versions and resource types determine the accepted property schema.
Best-known use cases
- Deploy the same infrastructure with different parameter values.
- Interpret the effect of an existing JSON deployment file.
What candidates often confuse it with
- ARM template vs Bicep: native JSON document vs concise language compiled to ARM JSON.
- Parameter vs variable: deployment input vs internally derived reusable value.
Key takeaway
Use ARM templates for declarative Azure deployment and read them by tracing inputs, resource identities, dependencies, and outputs.
Related services
- Azure Resource Manager
- Bicep
Relevant exam tasks
- D3.1.S1 — Interpret an Azure Resource Manager template or a Bicep file
- D3.1.S2 — Modify an existing Azure Resource Manager template
- D3.1.S3 — Modify an existing Bicep file
- D3.1.S4 — Deploy resources by using an Azure Resource Manager template or a Bicep file
- D3.1.S5 — Export a deployment as an Azure Resource Manager template or convert an Azure Resource Manager template to a Bicep file