Question

Difficulty: EasyAzure Resource Manager (ARM) and ARM Templates/Bicep

A development team wants to ensure that all their testing environments are deployed consistently across different Azure subscriptions. They decide to use Bicep templates to define the infrastructure. What is a key benefit of using this declarative approach for their deployments?

  1. A
    They allow the team to write step-by-step command scripts that execute sequentially to build the environment.
  2. B
    They allow the team to create nested resource groups within other resource groups to organize resources hierarchically.
  3. They allow the team to define the desired end-state of the infrastructure, leaving Azure to determine how to deploy it.Answer
  4. D
    They force all deployed resources to inherit and use the exact same geographic region as the resource group.

Answer

They allow the team to define the desired end-state of the infrastructure, leaving Azure to determine how to deploy it.
Using declarative templates allows developers to specify what infrastructure they want (the desired end-state) rather than detailing the step-by-step instructions to create it. Azure Resource Manager handles the deployment logic, dependency ordering, and parallel execution automatically.

Step-by-Step Solution

1
Analyze the definition of a declarative approach in the context of infrastructure deployment.
A declarative approach defines 'what' the target environment should look like (the desired end-state) rather than 'how' to build it step-by-step.
This matches the core benefit and purpose of Bicep and ARM templates.
2
Evaluate the other options against Azure governance and architecture rules.
Eliminated options regarding step-by-step imperative scripting, nested resource groups, and forced location inheritance.
These options describe behaviors that are either incorrect or represent structural limitations in Azure.

Key Concept

Declarative infrastructure deployment using ARM templates and Bicep
Estimated Time:45s
Rate this question