Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Preview ARM Template Changes With What-If
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An administrator is preparing to deploy infrastructure using an Azure Resource Manager (ARM) template.
Before executing the deployment, the administrator needs to evaluate the template to preview which resources will be created, modified, or deleted, as well as detect syntax and preflight validation errors without making actual changes to the live environment.
Which operation should the administrator execute?
Explanations
Resource locks
Resource locks
What Resource Locks Are
Resource locks are governance safeguards applied to Azure subscriptions, resource groups, or individual resources to prevent unauthorized or accidental modifications and deletions.
Why It Doesn't Meet the Requirement
- Does not preview deployments: Resource locks do not simulate template deployments or display predicted configuration changes.
- Does not perform syntax validation: Locks have no functionality for inspecting JSON syntax or testing template parameters.
Key Characteristics and Limitations
- Lock levels: Supports
CanNotDelete(authorized users can read and modify, but not delete) andReadOnly(authorized users can only read resources). - Inheritance: Locks applied at a subscription or resource group level are automatically inherited by all child resources.
- Protection mechanism: They serve strictly as a protective guardrail rather than an infrastructure analysis tool.
This Answer Would Be Correct If
This option would be correct if the scenario required protecting critical production resources from being accidentally deleted or modified by administrators.
Additional Context
If a resource lock is in place, attempting to deploy a template that deletes or modifies that locked resource will fail, but the lock itself does not provide pre-deployment change previews.
Deployment scripts
Deployment scripts
What Deployment Scripts Are
Deployment scripts are custom Azure PowerShell or Azure CLI scripts embedded within or referenced by an ARM template to perform custom automation tasks during a deployment.
Why It Doesn't Meet the Requirement
- Executes custom logic rather than previewing changes: Deployment scripts perform actions (such as managing external data or executing setup steps) during the deployment lifecycle rather than simulating template outcomes.
- Does not analyze template impacts: They do not provide a comparative summary of planned infrastructure additions, modifications, or deletions.
Key Characteristics and Limitations
- Extends template capabilities: Allows running arbitrary scripts in containers during deployment to handle tasks not natively supported by ARM templates.
- Container execution: Scripts run within an Azure Container Instance created temporarily during template execution.
- Output capture: Can pass script output variables back into subsequent resources defined in the ARM template.
This Answer Would Be Correct If
This option would be correct if the scenario required executing custom administrative commands or data seeding scripts as part of an end-to-end ARM template deployment.
Additional Context
Deployment scripts execute during active deployment and cannot replace preflight simulation tools such as the what-if operation.
The what-if operation
The what-if operation
What the What-If Operation Is
The what-if operation in Azure Resource Manager allows administrators and engineers to preview the exact changes that will occur before executing an ARM template deployment. It compares the desired state described in the template against the current real-time state of the target environment.
How It Meets the Requirements
- Previewing resource impacts: It clearly identifies which resources will be created, modified, or deleted prior to deploying.
- Preflight validation and syntax checking: The operation evaluates the template syntax and verifies property configurations against Azure resource providers to detect potential errors before any changes are committed.
- Safe evaluation: It performs these checks non-destructively, ensuring that existing infrastructure remains untouched.
Key Advantages and Capabilities
- Eliminates state management: Azure Resource Manager directly checks the current state of resources in the cloud, avoiding the need to maintain external state files.
- Predictable deployments: It helps prevent unintended configuration overwrites or accidental resource deletions.
- Broad tooling support: The operation can be invoked directly through the Azure portal, Azure CLI (
az deployment group what-if), and Azure PowerShell (Get-AzResourceGroupDeploymentWhatIfResult). - Comprehensive change summary: It displays property-level modifications, highlighting added, ignored, or modified values.
Why This Is Optimal
The what-if operation is specifically designed for pre-deployment inspection and validation. It allows administrators to verify template logic, ensure expected outcomes, and identify configuration errors safely before initiating actual infrastructure modifications.
Template specs
Template specs
What Template Specs Are
Template specs are first-class Azure resource types used to store, version, and share ARM templates natively within an Azure subscription or resource group.
Why It Doesn't Meet the Requirement
- No preview capability: Storing a template as a template spec does not show what resources will be created, updated, or removed in an environment.
- Not an evaluation tool: A template spec is a packaging and sharing mechanism rather than a validation or simulation tool.
Key Characteristics and Limitations
- Role-based access control: Access to template specs can be managed using standard Azure RBAC permissions to ensure only authorized users deploy approved templates.
- Centralized library: It serves as an organizational catalog of standard, reusable templates.
- Versioning support: Multiple versions of the same template can be maintained within a single spec resource.
This Answer Would Be Correct If
This option would be correct if the requirement was to securely store and share verified ARM templates across teams within an organization while controlling access using Azure role-based access control (RBAC).
Additional Context
While a template spec contains the ARM template definition, evaluating its impact still requires running the what-if operation against the target scope prior to deployment.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
ARM Template Condition Element
Describe Azure Resource Manager (ARM) and ARM templates
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
ARM Template Parameters Section
Describe Azure Resource Manager (ARM) and ARM templates
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
ARM Template Secure Parameters
Describe Azure Resource Manager (ARM) and ARM templates
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Resource Manager Control Plane
Describe Azure Resource Manager (ARM) and ARM templates
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Management Groups
Describe management groups
AdvancedAZ-104 Microsoft Azure Administrator Exam
Availability Zones High Availability
Deploy virtual machines to availability zones and availability sets
Last updated Validated