Sign in to practice all 53 questions with progress tracking and AI explanations.
1. Which top-level sections must appear in a minimal ARM template to define inputs, reusable values, resources, and return values?
- A.A minimal ARM template should include Schema, Parameters, Variables, Resources, and Outputs to define structure, inputs, reusable values, deployments, and returned values.✓ Correct
- B.A minimal ARM template must include API version, Location, ResourceGroup, and Instance definitions to control the deployment and returned outputs.
- C.A minimal ARM template only needs Resources and Outputs; Parameters and Variables are optional and never used for real deployments.
- D.A minimal ARM template requires Schema, Providers, Subscriptions, and DeploymentScripts sections to be valid and executable by Azure.
Explanation
ARM templates use the top-level sections Schema, Parameters, Variables, Resources, and Outputs; other options list incorrect or non-required fields.
2. When should you use parameters instead of variables in an ARM template for virtual machine deployments?
- A.Use parameters when values must be supplied or changed at deployment time, such as adminUsername, VM size, or image SKU, while variables hold derived or reused values.✓ Correct
- B.Use variables when values must be supplied at deployment time by users, because parameters are only for internal template math and concatenation.
- C.Use parameters only for secrets and never for non-sensitive configurable options like VM size or network name in templates.
- D.Use variables instead of parameters when you want to allow end users to override values at deployment time for flexibility.
Explanation
Parameters are for values supplied at deployment time; variables store computed or reusable values. Other options reverse or misstate usage.
3. You run an ARM deployment in Complete mode against a resource group containing a VM and a storage account, but your template only contains the VM resource. What happens to the storage account?
- A.Complete mode removes resources not declared in the template, so the storage account will be deleted during deployment unless excluded by locks or policies.✓ Correct
- B.Complete mode leaves existing resources untouched and only adds or updates resources declared in the template, so the storage account remains.
- C.Complete mode moves the storage account to a temporary state until a later deployment reconciles it, preserving data automatically.
- D.Complete mode converts the storage account into a nested template resource and retains its configuration without deletion.
Explanation
Complete mode deletes resources not present in the template; incremental mode preserves them. Other options are incorrect about behavior.
4. Why might you prefer Incremental deployment mode when updating a production resource group that contains many unrelated resources?
- A.Incremental mode updates or adds only resources in the template and leaves unrelated existing resources intact, reducing risk of accidental deletions in production.✓ Correct
- B.Incremental mode deletes any resource not in the template, which is desirable to keep production tidy and remove stale resources automatically.
- C.Incremental mode prevents any changes to resource properties and only validates templates, so it's safest for production updates.
- D.Incremental mode checkpoints resource states and rolls back automatically if any resource in the resource group differs from the template.
Explanation
Incremental mode preserves unrelated resources and only changes declared ones, reducing deletion risk; other options misstate its behavior.
5. In an ARM template you define a virtual machine and a network interface; how do you ensure the NIC is created before the VM?
- A.Set a dependsOn property on the VM resource that references the NIC resource name so Azure deploys the NIC first and then the VM that uses it.✓ Correct
- B.Rely on Azure to automatically infer dependencies from the VM's networkProfile and no explicit dependsOn is ever necessary for NIC creation ordering.
- C.Place the NIC resource in a separate template with a different subscription to guarantee ordering across deployments.
- D.Create the VM first and then the NIC in the same template; Azure will pause VM provisioning until the NIC appears.
Explanation
Use dependsOn to guarantee order; Azure sometimes infers dependencies but explicit dependsOn ensures correct sequence. Other options are incorrect or unreliable.
Practice all 53+ questions in this domain
Start free practice →