Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
ARM Template Parameters for Environment Reuse
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 IT department is creating an Azure Resource Manager (ARM) template in JSON format to deploy cloud infrastructure across development, testing, and production environments.
The deployment team must be able to supply custom input values—such as environment-specific SKUs, resource prefixes, and locations—at the time of deployment so that the exact same template file can be reused across all environments.
Which section of the ARM template should be configured to accept these custom input values during deployment?
Explanations
outputs
outputs
What the outputs section does
The outputs section of an ARM template specifies the values and data that the deployment returns after successfully provisioning the defined resources. It is used to surface information generated during deployment, such as provisioned endpoint URLs, public IP addresses, or fully qualified domain names.
Why it doesn't meet the requirement
The outputs section sends data out of the template after execution has finished. It cannot be used to accept or ingest input values from users or deployment scripts at the beginning of the deployment process.
Key characteristics and limitations
- Post-deployment return: Emits calculated or assigned properties back to the user, CLI console, or orchestrating deployment pipeline.
- Inter-template communication: Commonly used to pass runtime values (such as connection strings or resource IDs) from a parent template to a child template.
- Read-only nature: Displays deployment results and does not configure input behavior.
This answer would be correct if
This option would be correct if the requirement were to return generated resource properties—such as the default host name of a web app or the primary endpoint of a storage account—back to the administrator upon deployment completion.
parameters
parameters
What the parameters section is
The parameters section in an Azure Resource Manager (ARM) template defines configurable input values that can be passed into the template during deployment execution. Parameters enable templates to be dynamic, generic, and reusable across multiple environments (such as development, staging, and production) without modifying the underlying template code.
How it meets the requirement
By declaring entries in the parameters block, administrators can specify variables like resource names, region locations, or pricing tiers at runtime. The deployment team can supply these values using parameter files, command-line arguments, or continuous integration/continuous deployment (CI/CD) pipelines. This ensures the template remains flexible and environment-agnostic.
Key advantages and capabilities
- Runtime customization: Accepts dynamic values when deployment starts rather than hardcoding static configuration.
- Validation rules: Supports constraints such as
allowedValues,defaultValue,minLength,maxLength, and data types (string,int,bool,object,array). - Secure inputs: Supports
securestringandsecureObjecttypes to securely handle sensitive data like passwords or connection strings without exposing them in logs. - Template reusability: Promotes Infrastructure as Code (IaC) best practices by allowing a single template definition to serve multiple distinct environments.
Why this is optimal
The parameters section is specifically engineered in the ARM JSON schema to capture external inputs provided during deployment. Without parameters, separate templates with hardcoded values would have to be maintained for every environment, increasing administrative overhead and introducing deployment drift.
variables
variables
What the variables section does
The variables section of an ARM template defines internal values, expressions, and string operations that are constructed and used within the template lifecycle itself. Variables help simplify complex expressions and eliminate repetitive values across resource definitions.
Why it doesn't meet the requirement
Values defined in the variables section cannot be passed into the template directly at deployment time by an external user or pipeline. Instead, variables are static internal declarations or calculated dynamically from parameters and template functions (such as concat() or uniqueString()).
Key characteristics and limitations
- Internal scope: Variables are computed internally during template processing and cannot accept user-supplied inputs at execution time.
- Complexity reduction: Used to store constructed values (e.g., combining a prefix parameter with a unique hash) to keep resource definitions clean.
- Not runtime configurable: Changing a variable directly requires modifying and saving the template JSON file.
This answer would be correct if
This option would be correct if the team needed to define internal helper values or complex string concatenations (like combining a naming prefix with a unique subscription ID) inside the template to simplify resource properties.
resources
resources
What the resources section does
The resources section is the core component of an ARM template that lists and defines all Azure infrastructure components to be provisioned or updated, such as virtual networks, virtual machines, App Service plans, and storage accounts.
Why it doesn't meet the requirement
The resources block defines what infrastructure to deploy and configures properties, API versions, and dependencies between services. It does not define input interfaces or accept dynamic values supplied at the start of deployment.
Key characteristics and limitations
- Infrastructure declarations: Contains the actual Azure resource definitions, types (e.g.,
Microsoft.Web/serverfarms), and property configurations. - Dependency management: Uses the
dependsOnproperty to enforce deployment order and parallelism across resources. - Consumes inputs: References parameters and variables rather than defining the external inputs themselves.
This answer would be correct if
This option would be correct if the scenario asked where to declare the actual Azure services, infrastructure components, or resource types that need to be created or configured in the target subscription or resource group.
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 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
ARM Template What-If Operation
Describe Azure Resource Manager (ARM) and ARM templates
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
ARM Template Condition Element
Describe Azure Resource Manager (ARM) and ARM templates
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Service Health
Describe Azure Service Health
IntermediateAZ-800 Administering Windows Server Hybrid Core Infrastructure Exam
Azure File Sync Event Logs and Azure Monitor
Configure and manage Azure File Sync
Last updated Validated