Examkin

Question

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

A company wants to ensure that its infrastructure deployments are consistent and repeatable across different environments. Instead of writing step-by-step scripts that specify how to create each resource, the administrator wants to define the final configuration of the resources. Which feature of Azure Resource Manager (ARM) templates directly supports this deployment method?

  1. A
    Imperative scripting, which defines the exact sequence of commands to execute
  2. B
    Resource group nesting, which permits resource groups to contain other resource groups
  3. Declarative syntax, which defines the desired end-state configuration of the resourcesAnswer
  4. D
    Location inheritance, which forces all deployed resources to reside in the resource group's region

Answer

Declarative syntax, which defines the desired end-state configuration of the resources
The correct answer is the option focusing on declarative syntax. Azure Resource Manager (ARM) templates and Bicep files use declarative syntax, meaning you describe the desired resources and their properties without specifying the exact programming commands or step-by-step sequence to create them.

Step-by-Step Solution

1
Analyze the scenario requirement
The scenario requires defining the final configuration (end-state) of resources rather than writing step-by-step scripts.
This requirement points directly to the core difference between declarative and imperative deployment models.
2
Identify the ARM template mechanism that enables this behavior
ARM templates use declarative syntax (JSON or Bicep) to specify what resources to create and their properties.
Declaring the final state instead of execution steps is the definition of declarative syntax.

Key Concept

ARM templates use declarative syntax to define the desired end-state of Azure infrastructure.
Rate this question

Topics

Azure Resource Manager (ARM) and ARM Templates/Bicep

More questions from this topic