Topic 07 Practice Test 1 covers ARM Templates and Bicep Deployments for Microsoft Azure Administrator AZ-104 and maps to the objective: Automate deployment of resources by using ARM templates or Bicep files. For broader exam preparation, review the Microsoft AZ-104 Exam Dumps. Every option includes focused technical reasoning explaining both the Azure concept and its fit to the scenario.
Question 1
Contoso uses the same Bicep file for development and production, but each environment needs a different VM size. What should the author define for the size? Choose ONE.
- Define a parameter for the value
- Define a variable for the computed internal value
- Add an output to the deployment
- Declare the Azure resource in the template or Bicep file
Correct Answer: A
Correct Answer
Answer A is correct because The required outcome for Contoso is: the value must be supplied or overridden at deployment time without editing the infrastructure definition. Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. This option provides that capability.
Incorrect Answers
Answer B is incorrect because Variables hold reusable expressions or derived values inside a template, which avoids repeating complex expressions when the value does not need to be supplied by the deployer. For Contoso, however, that does not meet the stated requirement: the value must be supplied or overridden at deployment time without editing the infrastructure definition.
Answer C is incorrect because Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. It misses the key condition in the Contoso case: the value must be supplied or overridden at deployment time without editing the infrastructure definition.
Answer D is incorrect because Contoso must satisfy this condition: the value must be supplied or overridden at deployment time without editing the infrastructure definition. Resource declarations describe the desired Azure resources and their properties; deploying the file asks Resource Manager to reconcile those declarations at the selected scope. This option is aimed at another design goal.
Question 2
Fabrikam wants an ARM template to accept a location from the deployer each time it runs. Which template construct should be used? Choose ONE.
- Define a variable for the computed internal value
- Define a parameter for the value
- Add an output to the deployment
- Declare the Azure resource in the template or Bicep file
Correct Answer: B
Correct Answer
Answer B is correct because Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. The deciding condition in The Fabrikam scenario is: the value must be supplied or overridden at deployment time without editing the infrastructure definition. This option fits that condition.
Incorrect Answers
Answer A is incorrect because The required outcome for Fabrikam is: the value must be supplied or overridden at deployment time without editing the infrastructure definition. Variables hold reusable expressions or derived values inside a template, which avoids repeating complex expressions when the value does not need to be supplied by the deployer. This capability does not satisfy that condition.
Answer C is incorrect because The requirement for Fabrikam is: the value must be supplied or overridden at deployment time without editing the infrastructure definition. Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. The option therefore targets a different Azure capability.
Answer D is incorrect because Resource declarations describe the desired Azure resources and their properties; deploying the file asks Resource Manager to reconcile those declarations at the selected scope. The mismatch for Fabrikam is the stated requirement: the value must be supplied or overridden at deployment time without editing the infrastructure definition.
Question 3
Northwind Traders needs a reusable storage deployment where the SKU can be selected during deployment. What should be added to the template? Choose ONE.
- Define a variable for the computed internal value
- Add an output to the deployment
- Define a parameter for the value
- Declare the Azure resource in the template or Bicep file
Correct Answer: C
Correct Answer
Answer C is correct because The key requirement for Northwind Traders is: the value must be supplied or overridden at deployment time without editing the infrastructure definition. Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment.
Incorrect Answers
Answer A is incorrect because Variables hold reusable expressions or derived values inside a template, which avoids repeating complex expressions when the value does not need to be supplied by the deployer. The Northwind Traders scenario instead calls for this outcome: the value must be supplied or overridden at deployment time without editing the infrastructure definition.
Answer B is incorrect because Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. This would not resolve the stated requirement for Northwind Traders: the value must be supplied or overridden at deployment time without editing the infrastructure definition.
Answer D is incorrect because In the Northwind Traders case, the required result is: the value must be supplied or overridden at deployment time without editing the infrastructure definition. Resource declarations describe the desired Azure resources and their properties; deploying the file asks Resource Manager to reconcile those declarations at the selected scope. Selecting this would solve a neighboring problem instead.
Question 4
Adventure Works wants one template file to deploy different resource names in multiple environments without changing the resource block. Which construct is appropriate? Choose ONE.
- Define a variable for the computed internal value
- Add an output to the deployment
- Declare the Azure resource in the template or Bicep file
- Define a parameter for the value
Correct Answer: D
Correct Answer
Answer D is correct because Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. This aligns with The Adventure Works scenario, whose requirement is: the value must be supplied or overridden at deployment time without editing the infrastructure definition.
Incorrect Answers
Answer A is incorrect because Variables hold reusable expressions or derived values inside a template, which avoids repeating complex expressions when the value does not need to be supplied by the deployer. That feature is valid Azure functionality, but The requirement for Adventure Works is: the value must be supplied or overridden at deployment time without editing the infrastructure definition.
Answer B is incorrect because For Adventure Works, the required behavior is: the value must be supplied or overridden at deployment time without editing the infrastructure definition. Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. That is not the behavior this scenario calls for.
Answer C is incorrect because Resource declarations describe the desired Azure resources and their properties; deploying the file asks Resource Manager to reconcile those declarations at the selected scope. That does not line up with the stated constraint for Adventure Works: the value must be supplied or overridden at deployment time without editing the infrastructure definition.
Question 5
Wingtip Toys needs its deployment pipeline to receive the newly created storage account resource ID after an ARM deployment. What should the template include? Choose ONE.
- Add an output to the deployment
- Define a parameter for the value
- Define a variable for the computed internal value
- Declare the Azure resource in the template or Bicep file
Correct Answer: A
Correct Answer
Answer A is correct because For Wingtip Toys, the technical constraint is: the deployment must return a useful value after resources are created so later automation can consume it. Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result.
Incorrect Answers
Answer B is incorrect because For Wingtip Toys, the deciding constraint is: the deployment must return a useful value after resources are created so later automation can consume it. Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. This solves a different operational need.
Answer C is incorrect because Variables hold reusable expressions or derived values inside a template, which avoids repeating complex expressions when the value does not need to be supplied by the deployer. Even though the feature can be useful, it does not provide The required outcome for Wingtip Toys: the deployment must return a useful value after resources are created so later automation can consume it.
Answer D is incorrect because The Wingtip Toys scenario is testing this requirement: the deployment must return a useful value after resources are created so later automation can consume it. Resource declarations describe the desired Azure resources and their properties; deploying the file asks Resource Manager to reconcile those declarations at the selected scope. This option does not provide that result.
Question 6
- Datum wants a Bicep deployment to display the public endpoint of a resource after creation. Which construct should be added? Choose ONE.
- Define a parameter for the value
- Add an output to the deployment
- Define a variable for the computed internal value
- Declare the Azure resource in the template or Bicep file
Correct Answer: B
Correct Answer
Answer B is correct because The A. Datum scenario turns on this requirement: the deployment must return a useful value after resources are created so later automation can consume it. Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. That makes this the appropriate choice.
Incorrect Answers
Answer A is incorrect because Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. It misses the key condition in the A. Datum case: the deployment must return a useful value after resources are created so later automation can consume it.
Answer C is incorrect because A. Datum must satisfy this condition: the deployment must return a useful value after resources are created so later automation can consume it. Variables hold reusable expressions or derived values inside a template, which avoids repeating complex expressions when the value does not need to be supplied by the deployer. This option is aimed at another design goal.
Answer D is incorrect because Resource declarations describe the desired Azure resources and their properties; deploying the file asks Resource Manager to reconcile those declarations at the selected scope. A. Datum needs a different capability; the required result is: the deployment must return a useful value after resources are created so later automation can consume it.
Question 7
Fourth Coffee has a parent automation workflow that needs a subnet ID produced by a deployment. What is the correct template mechanism? Choose ONE.
- Define a parameter for the value
- Define a variable for the computed internal value
- Add an output to the deployment
- Declare the Azure resource in the template or Bicep file
Correct Answer: C
Correct Answer
Answer C is correct because Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. The capability is relevant to Fourth Coffee because the required outcome is: the deployment must return a useful value after resources are created so later automation can consume it.
Incorrect Answers
Answer A is incorrect because The requirement for Fourth Coffee is: the deployment must return a useful value after resources are created so later automation can consume it. Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. The option therefore targets a different Azure capability.
Answer B is incorrect because Variables hold reusable expressions or derived values inside a template, which avoids repeating complex expressions when the value does not need to be supplied by the deployer. The mismatch for Fourth Coffee is the stated requirement: the deployment must return a useful value after resources are created so later automation can consume it.
Answer D is incorrect because The Fourth Coffee design calls for this outcome: the deployment must return a useful value after resources are created so later automation can consume it. Resource declarations describe the desired Azure resources and their properties; deploying the file asks Resource Manager to reconcile those declarations at the selected scope. This choice addresses another concern.
Question 8
Lucerne Publishing wants an ARM deployment to expose the generated resource name to a later pipeline stage. Which template element should it use? Choose ONE.
- Define a parameter for the value
- Define a variable for the computed internal value
- Declare the Azure resource in the template or Bicep file
- Add an output to the deployment
Correct Answer: D
Correct Answer
Answer D is correct because The scenario for Lucerne Publishing requires this result: the deployment must return a useful value after resources are created so later automation can consume it. Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. This directly addresses it.
Incorrect Answers
Answer A is incorrect because Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. This would not resolve the stated requirement for Lucerne Publishing: the deployment must return a useful value after resources are created so later automation can consume it.
Answer B is incorrect because In the Lucerne Publishing case, the required result is: the deployment must return a useful value after resources are created so later automation can consume it. Variables hold reusable expressions or derived values inside a template, which avoids repeating complex expressions when the value does not need to be supplied by the deployer. Selecting this would solve a neighboring problem instead.
Answer C is incorrect because Resource declarations describe the desired Azure resources and their properties; deploying the file asks Resource Manager to reconcile those declarations at the selected scope. It is not the appropriate selection for Lucerne Publishing; the scenario requires: the deployment must return a useful value after resources are created so later automation can consume it.
Question 9
Contoso has a Bicep resource that sets a property to another resource symbolic name. The author wants deployment ordering to follow that relationship automatically. What should be relied on? Choose ONE.
- Reference the other resource symbolically so Bicep infers the dependency
- Add an explicit dependsOn only when the dependency cannot be inferred
- Define a parameter for the value
- Run the Resource Manager what-if operation
Correct Answer: A
Correct Answer
Answer A is correct because Bicep creates an implicit dependency when one resource references another resource symbol, reducing the need for an explicit dependsOn entry for that relationship. It is the suitable choice for Contoso; the deciding requirement is: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Incorrect Answers
Answer B is incorrect because For Contoso, the required behavior is: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list. An explicit dependsOn is useful when Resource Manager must enforce ordering and the relationship is not already represented through a symbolic or expression-based resource reference. That is not the behavior this scenario calls for.
Answer C is incorrect because Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. That does not line up with the stated constraint for Contoso: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Answer D is incorrect because The what-if operation previews expected resource changes before deployment, helping an administrator detect unintended creates, deletes, or property modifications without applying them. For Contoso, however, that does not meet the stated requirement: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Question 10
Fabrikam is simplifying a Bicep file where one resource directly references the ID of another declared resource. How should the dependency normally be represented? Choose ONE.
- Add an explicit dependsOn only when the dependency cannot be inferred
- Reference the other resource symbolically so Bicep infers the dependency
- Define a parameter for the value
- Run the Resource Manager what-if operation
Correct Answer: B
Correct Answer
Answer B is correct because For Fabrikam, the required behavior is: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list. Bicep creates an implicit dependency when one resource references another resource symbol, reducing the need for an explicit dependsOn entry for that relationship. That is why this option fits.
Incorrect Answers
Answer A is incorrect because An explicit dependsOn is useful when Resource Manager must enforce ordering and the relationship is not already represented through a symbolic or expression-based resource reference. Even though the feature can be useful, it does not provide The required outcome for Fabrikam: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Answer C is incorrect because The Fabrikam scenario is testing this requirement: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list. Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. This option does not provide that result.
Answer D is incorrect because The required outcome for Fabrikam is: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list. The what-if operation previews expected resource changes before deployment, helping an administrator detect unintended creates, deletes, or property modifications without applying them. This capability does not satisfy that condition.
Question 11
Northwind Traders wants to avoid an unnecessary explicit dependsOn because a child resource already references its parent symbolically. What should it use? Choose ONE.
- Add an explicit dependsOn only when the dependency cannot be inferred
- Define a parameter for the value
- Reference the other resource symbolically so Bicep infers the dependency
- Run the Resource Manager what-if operation
Correct Answer: C
Correct Answer
Answer C is correct because Bicep creates an implicit dependency when one resource references another resource symbol, reducing the need for an explicit dependsOn entry for that relationship. The technical fit for Northwind Traders is direct because the requirement is: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Incorrect Answers
Answer A is incorrect because Northwind Traders must satisfy this condition: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list. An explicit dependsOn is useful when Resource Manager must enforce ordering and the relationship is not already represented through a symbolic or expression-based resource reference. This option is aimed at another design goal.
Answer B is incorrect because Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. Northwind Traders needs a different capability; the required result is: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Answer D is incorrect because The what-if operation previews expected resource changes before deployment, helping an administrator detect unintended creates, deletes, or property modifications without applying them. The Northwind Traders scenario instead calls for this outcome: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Question 12
Adventure Works has two Bicep resources with a direct symbolic reference between them and needs correct deployment order. Which dependency approach is preferred? Choose ONE.
- Add an explicit dependsOn only when the dependency cannot be inferred
- Define a parameter for the value
- Run the Resource Manager what-if operation
- Reference the other resource symbolically so Bicep infers the dependency
Correct Answer: D
Correct Answer
Answer D is correct because Bicep creates an implicit dependency when one resource references another resource symbol, reducing the need for an explicit dependsOn entry for that relationship. For Adventure Works, that directly matches the stated requirement: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Incorrect Answers
Answer A is incorrect because An explicit dependsOn is useful when Resource Manager must enforce ordering and the relationship is not already represented through a symbolic or expression-based resource reference. The mismatch for Adventure Works is the stated requirement: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Answer B is incorrect because The Adventure Works design calls for this outcome: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list. Template parameters accept values at deployment time and make ARM or Bicep deployments reusable across environments without editing the resource definition for every deployment. This choice addresses another concern.
Answer C is incorrect because The what-if operation previews expected resource changes before deployment, helping an administrator detect unintended creates, deletes, or property modifications without applying them. That feature is valid Azure functionality, but The requirement for Adventure Works is: Bicep should derive resource deployment ordering from a direct symbolic reference instead of a manually maintained dependency list.
Question 13
Tailspin Toys has main.bicep on a build agent and must deploy it to resource group rg-app. Which deployment type should the automation run? Choose ONE.
- Run a resource-group-scope deployment
- Export a template from the current resource group or selected resources
- Run az bicep decompile against the ARM JSON template
- Add an output to the deployment
Correct Answer: A
Correct Answer
Answer A is correct because The required outcome for Tailspin Toys is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group. A resource-group deployment targets resources to a specific resource group and can be executed with commands such as az deployment group create using the template or Bicep file. This option provides that capability.
Incorrect Answers
Answer B is incorrect because In the Tailspin Toys case, the required result is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group. Exporting from existing resources produces an autogenerated snapshot of current resource state, including changes made after the original deployment, and usually needs cleanup before reuse. Selecting this would solve a neighboring problem instead.
Answer C is incorrect because The Bicep decompile command converts an ARM JSON template into a Bicep starting point; the generated Bicep should be reviewed because decompilation is not guaranteed to reproduce ideal source code. It is not the appropriate selection for Tailspin Toys; the scenario requires: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group.
Answer D is incorrect because For Tailspin Toys, the deciding constraint is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group. Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. This solves a different operational need.
Question 14
Woodgrove Bank needs Azure CLI to apply an ARM JSON template to an existing resource group. Which scope of deployment is appropriate? Choose ONE.
- Export a template from the current resource group or selected resources
- Run a resource-group-scope deployment
- Run az bicep decompile against the ARM JSON template
- Add an output to the deployment
Correct Answer: B
Correct Answer
Answer B is correct because A resource-group deployment targets resources to a specific resource group and can be executed with commands such as az deployment group create using the template or Bicep file. The deciding condition in The Woodgrove Bank scenario is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group. This option fits that condition.
Incorrect Answers
Answer A is incorrect because Exporting from existing resources produces an autogenerated snapshot of current resource state, including changes made after the original deployment, and usually needs cleanup before reuse. That does not line up with the stated constraint for Woodgrove Bank: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group.
Answer C is incorrect because The Bicep decompile command converts an ARM JSON template into a Bicep starting point; the generated Bicep should be reviewed because decompilation is not guaranteed to reproduce ideal source code. For Woodgrove Bank, however, that does not meet the stated requirement: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group.
Answer D is incorrect because Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. It misses the key condition in the Woodgrove Bank case: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group.
Question 15
Proseware is deploying a storage account and virtual network defined in Bicep into one resource group. What Resource Manager deployment scope should it use? Choose ONE.
- Export a template from the current resource group or selected resources
- Run az bicep decompile against the ARM JSON template
- Run a resource-group-scope deployment
- Add an output to the deployment
Correct Answer: C
Correct Answer
Answer C is correct because The key requirement for Proseware is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group. A resource-group deployment targets resources to a specific resource group and can be executed with commands such as az deployment group create using the template or Bicep file.
Incorrect Answers
Answer A is incorrect because The Proseware scenario is testing this requirement: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group. Exporting from existing resources produces an autogenerated snapshot of current resource state, including changes made after the original deployment, and usually needs cleanup before reuse. This option does not provide that result.
Answer B is incorrect because The required outcome for Proseware is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group. The Bicep decompile command converts an ARM JSON template into a Bicep starting point; the generated Bicep should be reviewed because decompilation is not guaranteed to reproduce ideal source code. This capability does not satisfy that condition.
Answer D is incorrect because The requirement for Proseware is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group. Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. The option therefore targets a different Azure capability.
Question 16
Litware wants to apply a template to resources in rg-prod by using az deployment group create. What kind of deployment is this? Choose ONE.
- Export a template from the current resource group or selected resources
- Run az bicep decompile against the ARM JSON template
- Add an output to the deployment
- Run a resource-group-scope deployment
Correct Answer: D
Correct Answer
Answer D is correct because A resource-group deployment targets resources to a specific resource group and can be executed with commands such as az deployment group create using the template or Bicep file. This aligns with The Litware scenario, whose requirement is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group.
Incorrect Answers
Answer A is incorrect because Exporting from existing resources produces an autogenerated snapshot of current resource state, including changes made after the original deployment, and usually needs cleanup before reuse. Litware needs a different capability; the required result is: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group.
Answer B is incorrect because The Bicep decompile command converts an ARM JSON template into a Bicep starting point; the generated Bicep should be reviewed because decompilation is not guaranteed to reproduce ideal source code. The Litware scenario instead calls for this outcome: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group.
Answer C is incorrect because Outputs return selected values after deployment, such as a resource ID, endpoint, or generated name, so downstream automation or an operator can consume the result. This would not resolve the stated requirement for Litware: the infrastructure file must be deployed at resource-group scope to create or update resources in the selected resource group.
Question 17
Wingtip Toys wants to review the effect of a Bicep change in production before executing the deployment. Which Resource Manager feature should it run? Choose ONE.
- Run the Resource Manager what-if operation
- Use incremental deployment behavior
- Export a template from the current resource group or selected resources
- Run az bicep decompile against the ARM JSON template
Correct Answer: A
Correct Answer
Answer A is correct because For Wingtip Toys, the technical constraint is: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. The what-if operation previews expected resource changes before deployment, helping an administrator detect unintended creates, deletes, or property modifications without applying them.
Incorrect Answers
Answer B is incorrect because The Wingtip Toys design calls for this outcome: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. Incremental deployment updates resources declared in the template while leaving unrelated existing resources in the target scope, making it the safer general deployment behavior. This choice addresses another concern.
Answer C is incorrect because Exporting from existing resources produces an autogenerated snapshot of current resource state, including changes made after the original deployment, and usually needs cleanup before reuse. That feature is valid Azure functionality, but The requirement for Wingtip Toys is: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources.
Answer D is incorrect because For Wingtip Toys, the required behavior is: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. The Bicep decompile command converts an ARM JSON template into a Bicep starting point; the generated Bicep should be reviewed because decompilation is not guaranteed to reproduce ideal source code. That is not the behavior this scenario calls for.
Question 18
- Datum changed several ARM template properties and needs a predeployment preview showing the expected resource changes. What should be used? Choose ONE.
- Use incremental deployment behavior
- Run the Resource Manager what-if operation
- Export a template from the current resource group or selected resources
- Run az bicep decompile against the ARM JSON template
Correct Answer: B
Correct Answer
Answer B is correct because The A. Datum scenario turns on this requirement: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. The what-if operation previews expected resource changes before deployment, helping an administrator detect unintended creates, deletes, or property modifications without applying them. That makes this the appropriate choice.
Incorrect Answers
Answer A is incorrect because Incremental deployment updates resources declared in the template while leaving unrelated existing resources in the target scope, making it the safer general deployment behavior. It is not the appropriate selection for A. Datum; the scenario requires: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources.
Answer C is incorrect because For A. Datum, the deciding constraint is: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. Exporting from existing resources produces an autogenerated snapshot of current resource state, including changes made after the original deployment, and usually needs cleanup before reuse. This solves a different operational need.
Answer D is incorrect because The Bicep decompile command converts an ARM JSON template into a Bicep starting point; the generated Bicep should be reviewed because decompilation is not guaranteed to reproduce ideal source code. Even though the feature can be useful, it does not provide The required outcome for A. Datum: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources.
Question 19
Fourth Coffee wants a pipeline gate that reports infrastructure changes without actually applying them. Which operation should the pipeline execute? Choose ONE.
- Use incremental deployment behavior
- Export a template from the current resource group or selected resources
- Run the Resource Manager what-if operation
- Run az bicep decompile against the ARM JSON template
Correct Answer: C
Correct Answer
Answer C is correct because The what-if operation previews expected resource changes before deployment, helping an administrator detect unintended creates, deletes, or property modifications without applying them. The capability is relevant to Fourth Coffee because the required outcome is: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources.
Incorrect Answers
Answer A is incorrect because Incremental deployment updates resources declared in the template while leaving unrelated existing resources in the target scope, making it the safer general deployment behavior. For Fourth Coffee, however, that does not meet the stated requirement: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources.
Answer B is incorrect because Exporting from existing resources produces an autogenerated snapshot of current resource state, including changes made after the original deployment, and usually needs cleanup before reuse. It misses the key condition in the Fourth Coffee case: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources.
Answer D is incorrect because Fourth Coffee must satisfy this condition: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. The Bicep decompile command converts an ARM JSON template into a Bicep starting point; the generated Bicep should be reviewed because decompilation is not guaranteed to reproduce ideal source code. This option is aimed at another design goal.
Question 20
Lucerne Publishing is concerned a template edit might remove a resource and wants to inspect the predicted change set first. What should it run? Choose ONE.
- Use incremental deployment behavior
- Export a template from the current resource group or selected resources
- Run az bicep decompile against the ARM JSON template
- Run the Resource Manager what-if operation
Correct Answer: D
Correct Answer
Answer D is correct because The scenario for Lucerne Publishing requires this result: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. The what-if operation previews expected resource changes before deployment, helping an administrator detect unintended creates, deletes, or property modifications without applying them. This directly addresses it.
Incorrect Answers
Answer A is incorrect because The required outcome for Lucerne Publishing is: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. Incremental deployment updates resources declared in the template while leaving unrelated existing resources in the target scope, making it the safer general deployment behavior. This capability does not satisfy that condition.
Answer B is incorrect because The requirement for Lucerne Publishing is: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources. Exporting from existing resources produces an autogenerated snapshot of current resource state, including changes made after the original deployment, and usually needs cleanup before reuse. The option therefore targets a different Azure capability.
Answer C is incorrect because The Bicep decompile command converts an ARM JSON template into a Bicep starting point; the generated Bicep should be reviewed because decompilation is not guaranteed to reproduce ideal source code. The mismatch for Lucerne Publishing is the stated requirement: the administrator must preview expected creates, deletes, and modifications before changing any Azure resources.
