Microsoft AZ-104 ARM Templates and Bicep Practice Test

 

Topic 09 focuses on ARM Templates and Bicep Deployments for the Microsoft Certified: Azure Administrator Associate certification and the AZ-104 exam, using Microsoft Azure administration scenarios. For broader exam preparation, review the Microsoft Azure Administrator AZ-104 Exam Dumps page. Each question includes a concise explanation of the correct answer and the technical reason the other choices are incorrect.

Question 1

To deploy infrastructure consistently without scripting every imperative step, which Azure configuration should be selected?

1. Incremental deployment
2. Export template
3. Declarative infrastructure deployment
4. What-if operation

Correct Answer: C

 

Correct Answer

Answer C is correct because Declarative infrastructure deployment is a model in which the desired end state is described and Azure Resource Manager determines how to create or update resources. It directly supports the requirement to deploy infrastructure consistently without scripting every imperative step.

Incorrect Answers

Answer A is incorrect because Incremental deployment is used to apply desired changes while leaving resources not represented in the deployment untouched; it does not provide the capability described in the scenario.

Answer B is incorrect because Export template is used to use an existing deployment as a starting point for infrastructure as code; it does not provide the capability described in the scenario.

Answer D is incorrect because What-if operation is used to review planned infrastructure changes before committing them; it does not provide the capability described in the scenario.

 

Question 2

For Declarative infrastructure deployment, which administrative outcome is expected?

1. Break complex infrastructure into reusable, maintainable deployment components
2. Apply desired changes while leaving resources not represented in the deployment untouched
3. Author Azure infrastructure as code with simpler syntax than raw JSON templates
4. Deploy infrastructure consistently without scripting every imperative step

Correct Answer: D

 

Correct Answer

Answer D is correct because Declarative infrastructure deployment is a model in which the desired end state is described and Azure Resource Manager determines how to create or update resources. Its intended administrative use is to deploy infrastructure consistently without scripting every imperative step.

Incorrect Answers

Answer A is incorrect because that outcome belongs to Bicep module, which is used to break complex infrastructure into reusable, maintainable deployment components; it is not the primary purpose of Declarative infrastructure deployment.

Answer B is incorrect because that outcome belongs to Incremental deployment, which is used to apply desired changes while leaving resources not represented in the deployment untouched; it is not the primary purpose of Declarative infrastructure deployment.

Answer C is incorrect because that outcome belongs to Bicep file, which is used to author Azure infrastructure as code with simpler syntax than raw JSON templates; it is not the primary purpose of Declarative infrastructure deployment.

 

Question 3

To define repeatable Azure infrastructure in native Resource Manager JSON, which Azure configuration should be selected?

1. Deployment history
2. Bicep decompile
3. ARM template
4. Bicep module

Correct Answer: C

 

Correct Answer

Answer C is correct because ARM template is a JSON document that declares Azure resources, parameters, variables, functions, and outputs for Resource Manager deployment. It directly supports the requirement to define repeatable Azure infrastructure in native Resource Manager JSON.

Incorrect Answers

Answer A is incorrect because Deployment history is used to troubleshoot failed deployments and review what Resource Manager changed; it does not provide the capability described in the scenario.

Answer B is incorrect because Bicep decompile is used to accelerate migration from ARM JSON authoring to Bicep; it does not provide the capability described in the scenario.

Answer D is incorrect because Bicep module is used to break complex infrastructure into reusable, maintainable deployment components; it does not provide the capability described in the scenario.

 

Question 4

For ARM template, which administrative outcome is expected?

1. Accelerate migration from ARM JSON authoring to Bicep
2. Deploy infrastructure consistently without scripting every imperative step
3. Define repeatable Azure infrastructure in native Resource Manager JSON
4. Author Azure infrastructure as code with simpler syntax than raw JSON templates

Correct Answer: C

 

Correct Answer

Answer C is correct because ARM template is a JSON document that declares Azure resources, parameters, variables, functions, and outputs for Resource Manager deployment. Its intended administrative use is to define repeatable Azure infrastructure in native Resource Manager JSON.

Incorrect Answers

Answer A is incorrect because that outcome belongs to Bicep decompile, which is used to accelerate migration from ARM JSON authoring to Bicep; it is not the primary purpose of ARM template.

Answer B is incorrect because that outcome belongs to Declarative infrastructure deployment, which is used to deploy infrastructure consistently without scripting every imperative step; it is not the primary purpose of ARM template.

Answer D is incorrect because that outcome belongs to Bicep file, which is used to author Azure infrastructure as code with simpler syntax than raw JSON templates; it is not the primary purpose of ARM template.

 

Question 5

To author Azure infrastructure as code with simpler syntax than raw JSON templates, which Azure configuration should be selected?

1. Resource dependency
2. Declarative infrastructure deployment
3. Export template
4. Bicep file

Correct Answer: D

 

Correct Answer

Answer D is correct because Bicep file is a concise domain-specific language that compiles to an ARM template for Azure Resource Manager deployment. It directly supports the requirement to author Azure infrastructure as code with simpler syntax than raw JSON templates.

Incorrect Answers

Answer A is incorrect because Resource dependency is used to control deployment ordering when Azure cannot infer the dependency automatically; it does not provide the capability described in the scenario.

Answer B is incorrect because Declarative infrastructure deployment is used to deploy infrastructure consistently without scripting every imperative step; it does not provide the capability described in the scenario.

Answer C is incorrect because Export template is used to use an existing deployment as a starting point for infrastructure as code; it does not provide the capability described in the scenario.

 

Question 6

For Bicep file, which administrative outcome is expected?

1. Review planned infrastructure changes before committing them
2. Troubleshoot failed deployments and review what Resource Manager changed
3. Author Azure infrastructure as code with simpler syntax than raw JSON templates
4. Accelerate migration from ARM JSON authoring to Bicep

Correct Answer: C

 

Correct Answer

Answer C is correct because Bicep file is a concise domain-specific language that compiles to an ARM template for Azure Resource Manager deployment. Its intended administrative use is to author Azure infrastructure as code with simpler syntax than raw JSON templates.

Incorrect Answers

Answer A is incorrect because that outcome belongs to What-if operation, which is used to review planned infrastructure changes before committing them; it is not the primary purpose of Bicep file.

Answer B is incorrect because that outcome belongs to Deployment history, which is used to troubleshoot failed deployments and review what Resource Manager changed; it is not the primary purpose of Bicep file.

Answer D is incorrect because that outcome belongs to Bicep decompile, which is used to accelerate migration from ARM JSON authoring to Bicep; it is not the primary purpose of Bicep file.

 

Question 7

To reuse the same infrastructure definition across environments with different values, which Azure configuration should be selected?

1. Bicep file
2. Bicep module
3. Incremental deployment
4. Template parameter

Correct Answer: D

 

Correct Answer

Answer D is correct because Template parameter is an input whose value can be supplied at deployment time. It directly supports the requirement to reuse the same infrastructure definition across environments with different values.

Incorrect Answers

Answer A is incorrect because Bicep file is used to author Azure infrastructure as code with simpler syntax than raw JSON templates; it does not provide the capability described in the scenario.

Answer B is incorrect because Bicep module is used to break complex infrastructure into reusable, maintainable deployment components; it does not provide the capability described in the scenario.

Answer C is incorrect because Incremental deployment is used to apply desired changes while leaving resources not represented in the deployment untouched; it does not provide the capability described in the scenario.

 

Question 8

For Template parameter, which administrative outcome is expected?

1. Apply desired changes while leaving resources not represented in the deployment untouched
2. Reuse the same infrastructure definition across environments with different values
3. Troubleshoot failed deployments and review what Resource Manager changed
4. Control deployment ordering when Azure cannot infer the dependency automatically

Correct Answer: B

 

Correct Answer

Answer B is correct because Template parameter is an input whose value can be supplied at deployment time. Its intended administrative use is to reuse the same infrastructure definition across environments with different values.

Incorrect Answers

Answer A is incorrect because that outcome belongs to Incremental deployment, which is used to apply desired changes while leaving resources not represented in the deployment untouched; it is not the primary purpose of Template parameter.

Answer C is incorrect because that outcome belongs to Deployment history, which is used to troubleshoot failed deployments and review what Resource Manager changed; it is not the primary purpose of Template parameter.

Answer D is incorrect because that outcome belongs to Resource dependency, which is used to control deployment ordering when Azure cannot infer the dependency automatically; it is not the primary purpose of Template parameter.

 

Question 9

To simplify repeated expressions without requiring the deployer to provide the value, which Azure configuration should be selected?

1. Bicep decompile
2. Deployment history
3. Bicep module
4. Template variable

Correct Answer: D

 

Correct Answer

Answer D is correct because Template variable is a reusable value calculated or declared inside a template or Bicep file. It directly supports the requirement to simplify repeated expressions without requiring the deployer to provide the value.

Incorrect Answers

Answer A is incorrect because Bicep decompile is used to accelerate migration from ARM JSON authoring to Bicep; it does not provide the capability described in the scenario.

Answer B is incorrect because Deployment history is used to troubleshoot failed deployments and review what Resource Manager changed; it does not provide the capability described in the scenario.

Answer C is incorrect because Bicep module is used to break complex infrastructure into reusable, maintainable deployment components; it does not provide the capability described in the scenario.

 

Question 10

For Template variable, which administrative outcome is expected?

1. Create readable references between Bicep declarations without using deployment-time resource names as code identifiers
2. Simplify repeated expressions without requiring the deployer to provide the value
3. Expose resource identifiers, endpoints, or other deployment results for later use
4. Define repeatable Azure infrastructure in native Resource Manager JSON

Correct Answer: B

 

Correct Answer

Answer B is correct because Template variable is a reusable value calculated or declared inside a template or Bicep file. Its intended administrative use is to simplify repeated expressions without requiring the deployer to provide the value.

Incorrect Answers

Answer A is incorrect because that outcome belongs to Bicep symbolic name, which is used to create readable references between Bicep declarations without using deployment-time resource names as code identifiers; it is not the primary purpose of Template variable.

Answer C is incorrect because that outcome belongs to Template output, which is used to expose resource identifiers, endpoints, or other deployment results for later use; it is not the primary purpose of Template variable.

Answer D is incorrect because that outcome belongs to ARM template, which is used to define repeatable Azure infrastructure in native Resource Manager JSON; it is not the primary purpose of Template variable.

 

Question 11

To expose resource identifiers, endpoints, or other deployment results for later use, which Azure configuration should be selected?

1. Template output
2. Deployment history
3. Template parameter
4. Bicep decompile

Correct Answer: A

 

Correct Answer

Answer A is correct because Template output is a value returned after a deployment completes. It directly supports the requirement to expose resource identifiers, endpoints, or other deployment results for later use.

Incorrect Answers

Answer B is incorrect because Deployment history is used to troubleshoot failed deployments and review what Resource Manager changed; it does not provide the capability described in the scenario.

Answer C is incorrect because Template parameter is used to reuse the same infrastructure definition across environments with different values; it does not provide the capability described in the scenario.

Answer D is incorrect because Bicep decompile is used to accelerate migration from ARM JSON authoring to Bicep; it does not provide the capability described in the scenario.

 

Question 12

For Template output, which administrative outcome is expected?

1. Expose resource identifiers, endpoints, or other deployment results for later use
2. Break complex infrastructure into reusable, maintainable deployment components
3. Author Azure infrastructure as code with simpler syntax than raw JSON templates
4. Create readable references between Bicep declarations without using deployment-time resource names as code identifiers

Correct Answer: A

 

Correct Answer

Answer A is correct because Template output is a value returned after a deployment completes. Its intended administrative use is to expose resource identifiers, endpoints, or other deployment results for later use.

Incorrect Answers

Answer B is incorrect because that outcome belongs to Bicep module, which is used to break complex infrastructure into reusable, maintainable deployment components; it is not the primary purpose of Template output.

Answer C is incorrect because that outcome belongs to Bicep file, which is used to author Azure infrastructure as code with simpler syntax than raw JSON templates; it is not the primary purpose of Template output.

Answer D is incorrect because that outcome belongs to Bicep symbolic name, which is used to create readable references between Bicep declarations without using deployment-time resource names as code identifiers; it is not the primary purpose of Template output.

 

Question 13

To control deployment ordering when Azure cannot infer the dependency automatically, which Azure configuration should be selected?

1. Deployment history
2. Template parameter
3. Resource dependency
4. Bicep symbolic name

Correct Answer: C

 

Correct Answer

Answer C is correct because Resource dependency is a deployment relationship that ensures one resource is provisioned before another resource that depends on it. It directly supports the requirement to control deployment ordering when Azure cannot infer the dependency automatically.

Incorrect Answers

Answer A is incorrect because Deployment history is used to troubleshoot failed deployments and review what Resource Manager changed; it does not provide the capability described in the scenario.

Answer B is incorrect because Template parameter is used to reuse the same infrastructure definition across environments with different values; it does not provide the capability described in the scenario.

Answer D is incorrect because Bicep symbolic name is used to create readable references between Bicep declarations without using deployment-time resource names as code identifiers; it does not provide the capability described in the scenario.

 

Question 14

For Resource dependency, which administrative outcome is expected?

1. Review planned infrastructure changes before committing them
2. Control deployment ordering when Azure cannot infer the dependency automatically
3. Expose resource identifiers, endpoints, or other deployment results for later use
4. Break complex infrastructure into reusable, maintainable deployment components

Correct Answer: B

 

Correct Answer

Answer B is correct because Resource dependency is a deployment relationship that ensures one resource is provisioned before another resource that depends on it. Its intended administrative use is to control deployment ordering when Azure cannot infer the dependency automatically.

Incorrect Answers

Answer A is incorrect because that outcome belongs to What-if operation, which is used to review planned infrastructure changes before committing them; it is not the primary purpose of Resource dependency.

Answer C is incorrect because that outcome belongs to Template output, which is used to expose resource identifiers, endpoints, or other deployment results for later use; it is not the primary purpose of Resource dependency.

Answer D is incorrect because that outcome belongs to Bicep module, which is used to break complex infrastructure into reusable, maintainable deployment components; it is not the primary purpose of Resource dependency.

 

Question 15

To create readable references between Bicep declarations without using deployment-time resource names as code identifiers, which Azure configuration should be selected?

1. Bicep symbolic name
2. What-if operation
3. Template output
4. Resource dependency

Correct Answer: A

 

Correct Answer

Answer A is correct because Bicep symbolic name is the local identifier used to reference a Bicep resource or module elsewhere in the file. It directly supports the requirement to create readable references between Bicep declarations without using deployment-time resource names as code identifiers.

Incorrect Answers

Answer B is incorrect because What-if operation is used to review planned infrastructure changes before committing them; it does not provide the capability described in the scenario.

Answer C is incorrect because Template output is used to expose resource identifiers, endpoints, or other deployment results for later use; it does not provide the capability described in the scenario.

Answer D is incorrect because Resource dependency is used to control deployment ordering when Azure cannot infer the dependency automatically; it does not provide the capability described in the scenario.

 

Question 16

For Bicep symbolic name, which administrative outcome is expected?

1. Review planned infrastructure changes before committing them
2. Create readable references between Bicep declarations without using deployment-time resource names as code identifiers
3. Define repeatable Azure infrastructure in native Resource Manager JSON
4. Author Azure infrastructure as code with simpler syntax than raw JSON templates

Correct Answer: B

 

Correct Answer

Answer B is correct because Bicep symbolic name is the local identifier used to reference a Bicep resource or module elsewhere in the file. Its intended administrative use is to create readable references between Bicep declarations without using deployment-time resource names as code identifiers.

Incorrect Answers

Answer A is incorrect because that outcome belongs to What-if operation, which is used to review planned infrastructure changes before committing them; it is not the primary purpose of Bicep symbolic name.

Answer C is incorrect because that outcome belongs to ARM template, which is used to define repeatable Azure infrastructure in native Resource Manager JSON; it is not the primary purpose of Bicep symbolic name.

Answer D is incorrect because that outcome belongs to Bicep file, which is used to author Azure infrastructure as code with simpler syntax than raw JSON templates; it is not the primary purpose of Bicep symbolic name.

 

Question 17

To break complex infrastructure into reusable, maintainable deployment components, which Azure configuration should be selected?

1. Bicep module
2. Deployment history
3. Bicep symbolic name
4. Bicep file

Correct Answer: A

 

Correct Answer

Answer A is correct because Bicep module is a reusable Bicep file referenced from another Bicep deployment. It directly supports the requirement to break complex infrastructure into reusable, maintainable deployment components.

Incorrect Answers

Answer B is incorrect because Deployment history is used to troubleshoot failed deployments and review what Resource Manager changed; it does not provide the capability described in the scenario.

Answer C is incorrect because Bicep symbolic name is used to create readable references between Bicep declarations without using deployment-time resource names as code identifiers; it does not provide the capability described in the scenario.

Answer D is incorrect because Bicep file is used to author Azure infrastructure as code with simpler syntax than raw JSON templates; it does not provide the capability described in the scenario.

 

Question 18

For Bicep module, which administrative outcome is expected?

1. Break complex infrastructure into reusable, maintainable deployment components
2. Deploy resources or governance objects at the Azure hierarchy level they require
3. Define repeatable Azure infrastructure in native Resource Manager JSON
4. Accelerate migration from ARM JSON authoring to Bicep

Correct Answer: A

 

Correct Answer

Answer A is correct because Bicep module is a reusable Bicep file referenced from another Bicep deployment. Its intended administrative use is to break complex infrastructure into reusable, maintainable deployment components.

Incorrect Answers

Answer B is incorrect because that outcome belongs to Deployment scope, which is used to deploy resources or governance objects at the Azure hierarchy level they require; it is not the primary purpose of Bicep module.

Answer C is incorrect because that outcome belongs to ARM template, which is used to define repeatable Azure infrastructure in native Resource Manager JSON; it is not the primary purpose of Bicep module.

Answer D is incorrect because that outcome belongs to Bicep decompile, which is used to accelerate migration from ARM JSON authoring to Bicep; it is not the primary purpose of Bicep module.

 

Question 19

To review planned infrastructure changes before committing them, which Azure configuration should be selected?

1. Bicep symbolic name
2. Deployment history
3. What-if operation
4. Resource dependency

Correct Answer: C

 

Correct Answer

Answer C is correct because What-if operation is a Resource Manager preview that shows expected changes before a template or Bicep deployment is applied. It directly supports the requirement to review planned infrastructure changes before committing them.

Incorrect Answers

Answer A is incorrect because Bicep symbolic name is used to create readable references between Bicep declarations without using deployment-time resource names as code identifiers; it does not provide the capability described in the scenario.

Answer B is incorrect because Deployment history is used to troubleshoot failed deployments and review what Resource Manager changed; it does not provide the capability described in the scenario.

Answer D is incorrect because Resource dependency is used to control deployment ordering when Azure cannot infer the dependency automatically; it does not provide the capability described in the scenario.

 

Question 20

For What-if operation, which administrative outcome is expected?

1. Define repeatable Azure infrastructure in native Resource Manager JSON
2. Review planned infrastructure changes before committing them
3. Author Azure infrastructure as code with simpler syntax than raw JSON templates
4. Troubleshoot failed deployments and review what Resource Manager changed

Correct Answer: B

 

Correct Answer

Answer B is correct because What-if operation is a Resource Manager preview that shows expected changes before a template or Bicep deployment is applied. Its intended administrative use is to review planned infrastructure changes before committing them.

Incorrect Answers

Answer A is incorrect because that outcome belongs to ARM template, which is used to define repeatable Azure infrastructure in native Resource Manager JSON; it is not the primary purpose of What-if operation.

Answer C is incorrect because that outcome belongs to Bicep file, which is used to author Azure infrastructure as code with simpler syntax than raw JSON templates; it is not the primary purpose of What-if operation.

Answer D is incorrect because that outcome belongs to Deployment history, which is used to troubleshoot failed deployments and review what Resource Manager changed; it is not the primary purpose of What-if operation.

 

Question 21

To apply desired changes while leaving resources not represented in the deployment untouched, which Azure configuration should be selected?

1. Bicep decompile
2. ARM template
3. Incremental deployment
4. Template variable

Correct Answer: C

 

Correct Answer

Answer C is correct because Incremental deployment is the common Resource Manager deployment behavior that adds or updates resources declared in the template without automatically deleting unrelated resources in the target scope. It directly supports the requirement to apply desired changes while leaving resources not represented in the deployment untouched.

Incorrect Answers

Answer A is incorrect because Bicep decompile is used to accelerate migration from ARM JSON authoring to Bicep; it does not provide the capability described in the scenario.

Answer B is incorrect because ARM template is used to define repeatable Azure infrastructure in native Resource Manager JSON; it does not provide the capability described in the scenario.

Answer D is incorrect because Template variable is used to simplify repeated expressions without requiring the deployer to provide the value; it does not provide the capability described in the scenario.

 

Question 22

For Incremental deployment, which administrative outcome is expected?

1. Apply desired changes while leaving resources not represented in the deployment untouched
2. Deploy infrastructure consistently without scripting every imperative step
3. Break complex infrastructure into reusable, maintainable deployment components
4. Deploy resources or governance objects at the Azure hierarchy level they require

Correct Answer: A

 

Correct Answer

Answer A is correct because Incremental deployment is the common Resource Manager deployment behavior that adds or updates resources declared in the template without automatically deleting unrelated resources in the target scope. Its intended administrative use is to apply desired changes while leaving resources not represented in the deployment untouched.

Incorrect Answers

Answer B is incorrect because that outcome belongs to Declarative infrastructure deployment, which is used to deploy infrastructure consistently without scripting every imperative step; it is not the primary purpose of Incremental deployment.

Answer C is incorrect because that outcome belongs to Bicep module, which is used to break complex infrastructure into reusable, maintainable deployment components; it is not the primary purpose of Incremental deployment.

Answer D is incorrect because that outcome belongs to Deployment scope, which is used to deploy resources or governance objects at the Azure hierarchy level they require; it is not the primary purpose of Incremental deployment.

 

Question 23

To deploy resources or governance objects at the Azure hierarchy level they require, which Azure configuration should be selected?

1. Template parameter
2. Deployment scope
3. Template output
4. ARM template

Correct Answer: B

 

Correct Answer

Answer B is correct because Deployment scope is the target level such as resource group, subscription, management group, or tenant at which a Resource Manager or Bicep deployment runs. It directly supports the requirement to deploy resources or governance objects at the Azure hierarchy level they require.

Incorrect Answers

Answer A is incorrect because Template parameter is used to reuse the same infrastructure definition across environments with different values; it does not provide the capability described in the scenario.

Answer C is incorrect because Template output is used to expose resource identifiers, endpoints, or other deployment results for later use; it does not provide the capability described in the scenario.

Answer D is incorrect because ARM template is used to define repeatable Azure infrastructure in native Resource Manager JSON; it does not provide the capability described in the scenario.

 

Question 24

For Deployment scope, which administrative outcome is expected?

1. Deploy infrastructure consistently without scripting every imperative step
2. Deploy resources or governance objects at the Azure hierarchy level they require
3. Define repeatable Azure infrastructure in native Resource Manager JSON
4. Control deployment ordering when Azure cannot infer the dependency automatically

Correct Answer: B

 

Correct Answer

Answer B is correct because Deployment scope is the target level such as resource group, subscription, management group, or tenant at which a Resource Manager or Bicep deployment runs. Its intended administrative use is to deploy resources or governance objects at the Azure hierarchy level they require.

Incorrect Answers

Answer A is incorrect because that outcome belongs to Declarative infrastructure deployment, which is used to deploy infrastructure consistently without scripting every imperative step; it is not the primary purpose of Deployment scope.

Answer C is incorrect because that outcome belongs to ARM template, which is used to define repeatable Azure infrastructure in native Resource Manager JSON; it is not the primary purpose of Deployment scope.

Answer D is incorrect because that outcome belongs to Resource dependency, which is used to control deployment ordering when Azure cannot infer the dependency automatically; it is not the primary purpose of Deployment scope.

 

Question 25

To use an existing deployment as a starting point for infrastructure as code, which Azure configuration should be selected?

1. Deployment history
2. Incremental deployment
3. Bicep decompile
4. Export template

Correct Answer: D

 

Correct Answer

Answer D is correct because Export template is the Azure capability that generates an ARM-template representation from existing resources where supported. It directly supports the requirement to use an existing deployment as a starting point for infrastructure as code.

Incorrect Answers

Answer A is incorrect because Deployment history is used to troubleshoot failed deployments and review what Resource Manager changed; it does not provide the capability described in the scenario.

Answer B is incorrect because Incremental deployment is used to apply desired changes while leaving resources not represented in the deployment untouched; it does not provide the capability described in the scenario.

Answer C is incorrect because Bicep decompile is used to accelerate migration from ARM JSON authoring to Bicep; it does not provide the capability described in the scenario.

 

Question 26

For Export template, which administrative outcome is expected?

1. Review planned infrastructure changes before committing them
2. Deploy infrastructure consistently without scripting every imperative step
3. Create readable references between Bicep declarations without using deployment-time resource names as code identifiers
4. Use an existing deployment as a starting point for infrastructure as code

Correct Answer: D

 

Correct Answer

Answer D is correct because Export template is the Azure capability that generates an ARM-template representation from existing resources where supported. Its intended administrative use is to use an existing deployment as a starting point for infrastructure as code.

Incorrect Answers

Answer A is incorrect because that outcome belongs to What-if operation, which is used to review planned infrastructure changes before committing them; it is not the primary purpose of Export template.

Answer B is incorrect because that outcome belongs to Declarative infrastructure deployment, which is used to deploy infrastructure consistently without scripting every imperative step; it is not the primary purpose of Export template.

Answer C is incorrect because that outcome belongs to Bicep symbolic name, which is used to create readable references between Bicep declarations without using deployment-time resource names as code identifiers; it is not the primary purpose of Export template.

 

Question 27

To accelerate migration from ARM JSON authoring to Bicep, which Azure configuration should be selected?

1. What-if operation
2. Bicep decompile
3. Bicep symbolic name
4. Template variable

Correct Answer: B

 

Correct Answer

Answer B is correct because Bicep decompile is the Bicep CLI capability that converts an ARM JSON template into a best-effort Bicep representation. It directly supports the requirement to accelerate migration from ARM JSON authoring to Bicep.

Incorrect Answers

Answer A is incorrect because What-if operation is used to review planned infrastructure changes before committing them; it does not provide the capability described in the scenario.

Answer C is incorrect because Bicep symbolic name is used to create readable references between Bicep declarations without using deployment-time resource names as code identifiers; it does not provide the capability described in the scenario.

Answer D is incorrect because Template variable is used to simplify repeated expressions without requiring the deployer to provide the value; it does not provide the capability described in the scenario.

 

Question 28

For Bicep decompile, which administrative outcome is expected?

1. Accelerate migration from ARM JSON authoring to Bicep
2. Author Azure infrastructure as code with simpler syntax than raw JSON templates
3. Create readable references between Bicep declarations without using deployment-time resource names as code identifiers
4. Deploy infrastructure consistently without scripting every imperative step

Correct Answer: A

 

Correct Answer

Answer A is correct because Bicep decompile is the Bicep CLI capability that converts an ARM JSON template into a best-effort Bicep representation. Its intended administrative use is to accelerate migration from ARM JSON authoring to Bicep.

Incorrect Answers

Answer B is incorrect because that outcome belongs to Bicep file, which is used to author Azure infrastructure as code with simpler syntax than raw JSON templates; it is not the primary purpose of Bicep decompile.

Answer C is incorrect because that outcome belongs to Bicep symbolic name, which is used to create readable references between Bicep declarations without using deployment-time resource names as code identifiers; it is not the primary purpose of Bicep decompile.

Answer D is incorrect because that outcome belongs to Declarative infrastructure deployment, which is used to deploy infrastructure consistently without scripting every imperative step; it is not the primary purpose of Bicep decompile.

 

Question 29

To troubleshoot failed deployments and review what Resource Manager changed, which Azure configuration should be selected?

1. Deployment history
2. Declarative infrastructure deployment
3. Bicep module
4. ARM template

Correct Answer: A

 

Correct Answer

Answer A is correct because Deployment history is the Resource Manager record of deployments made to a scope, including status and operation details. It directly supports the requirement to troubleshoot failed deployments and review what Resource Manager changed.

Incorrect Answers

Answer B is incorrect because Declarative infrastructure deployment is used to deploy infrastructure consistently without scripting every imperative step; it does not provide the capability described in the scenario.

Answer C is incorrect because Bicep module is used to break complex infrastructure into reusable, maintainable deployment components; it does not provide the capability described in the scenario.

Answer D is incorrect because ARM template is used to define repeatable Azure infrastructure in native Resource Manager JSON; it does not provide the capability described in the scenario.

 

Question 30

For Deployment history, which administrative outcome is expected?

1. Reuse the same infrastructure definition across environments with different values
2. Deploy infrastructure consistently without scripting every imperative step
3. Control deployment ordering when Azure cannot infer the dependency automatically
4. Troubleshoot failed deployments and review what Resource Manager changed

Correct Answer: D

 

Correct Answer

Answer D is correct because Deployment history is the Resource Manager record of deployments made to a scope, including status and operation details. Its intended administrative use is to troubleshoot failed deployments and review what Resource Manager changed.

Incorrect Answers

Answer A is incorrect because that outcome belongs to Template parameter, which is used to reuse the same infrastructure definition across environments with different values; it is not the primary purpose of Deployment history.

Answer B is incorrect because that outcome belongs to Declarative infrastructure deployment, which is used to deploy infrastructure consistently without scripting every imperative step; it is not the primary purpose of Deployment history.

Answer C is incorrect because that outcome belongs to Resource dependency, which is used to control deployment ordering when Azure cannot infer the dependency automatically; it is not the primary purpose of Deployment history.