ARM Templates & Bicep
Declarative Azure deployments: read, modify, deploy and export ARM templates and Bicep files with repeatable parameters and dependencies.
Readiness
0%
2h baseline
Exam memorization points
- Bicep is a declarative language that compiles to ARM JSON and supports modules, parameters, variables, outputs and resource dependencies.
- ARM deployments are idempotent: Azure Resource Manager converges resources toward the declared state rather than executing an imperative script step by step.
- Use what-if before deployment to preview resource changes, especially deletes and replacements.
- Parameters hold environment-specific input; outputs expose deployment results; symbolic names and modules improve reuse.
- The current AZ-104 blueprint explicitly expects interpreting, modifying and deploying ARM/Bicep plus exporting or converting templates.
Traps & distractors
- Putting secrets directly in a template or parameter file instead of using secure parameters and a secret store.
- Assuming Bicep state is stored like Terraform state; Azure Resource Manager is the control plane and no separate Bicep state file is required.
- Skipping what-if and deploying a destructive change directly to production.
- Confusing complete deployment mode with incremental behavior; destructive semantics must be understood before use.
Suggested lab
Deploy and modify a small Bicep template
Practise the exact blueprint workflow: interpret, change, preview and deploy declarative Azure resources.
- 1Create a dedicated throwaway resource group for the lab.
- 2Write a Bicep file that deploys a storage account with parameters for name, location and tags.
- 3Run a what-if deployment and explain every proposed change before applying it.
- 4Modify redundancy or tags, run what-if again, then deploy the update.
- 5Export the deployed resource template and compare ARM JSON with the Bicep source.
- 6Cleanup: delete the dedicated resource group and verify that no lab resource remains billable.
Cleanup / cost guard
Use a dedicated throwaway resource group whenever possible. At the end, delete disposable lab resources and verify in Cost Management/resource lists that no billable VM, gateway, public IP, private endpoint, disk, database or other paid resource remains.
Microsoft Learn
Direct Microsoft Learn links are also used by the live AI tutor retrieval layer when available. Search links remain a discovery fallback and are not presented as retrieved evidence.
Status
No time invested yet. Baseline assumptions only.
Self-assessed mastery
0%
High priority
Strong exam value. Schedule this week.
- Exam importance80% × 30% = 24.0
Learner-agnostic frequency on the real exam (4/5).
- Blueprint weight100% × 25% = 25.0
This topic's domain carries 22.5% of the exam objectives.
- Dependency leverage0% × 20% = 0.0
Nothing else in the graph depends on this topic.
- Current gap100% × 25% = 25.0
Readiness is 0%, so 100% of the topic is still uncovered.
Exam Priority Score = 30% importance + 25% blueprint + 20% dependency + 25% gap. Importance is exam frequency, blueprint is the domain's official exam weight, dependency is how many later topics this one unlocks, and gap is how far you currently are from ready.
Unlocks next
Leaf topic - nothing depends on it.
Baseline study time
2h
Complexity
3 / 5
Remaining to target
1h 42m
Status weight
0%
Topics: bicep, arm, template, what-if, deployment, parameters, modules
AI tutor · Microsoft Learn grounded
Live DeepSeek tutor using the official Microsoft Learn links attached to this topic. It can explain and test you; it does not mark mastery or claim that a lab was completed.
Weak neighbours in Compute