Examkin

Question

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

A systems administrator is reviewing a draft architecture document that outlines the deployment of a new environment using Azure Bicep templates. The draft makes the following assumptions:
1. A database resource group can be nested inside a virtual network resource group to consolidate management.
2. Every resource deployed by the template must share the same physical location as the containing resource group.
3. Bicep templates operate as imperative, step-by-step execution scripts that specify the order of resource creation.

Which of the following statements correctly evaluates the feasibility of these three assumptions in Azure?

  1. A
    Only the second assumption is feasible because resources are restricted to the same region as their containing resource group, while nesting is unsupported and Bicep templates are declarative.
  2. B
    Only the first and second assumptions are feasible because resource groups can be nested and resources must share their group's region, while Bicep templates must be declarative.
  3. None of the assumptions are feasible because resource groups cannot be nested, resources can reside in a different region than their resource group, and Bicep templates are declarative.Answer
  4. D
    Only the third assumption is feasible because Bicep templates must be written as imperative scripts, while nesting resource groups and region divergence are unsupported.

Answer

None of the assumptions are feasible because resource groups cannot be nested, resources can reside in a different region than their resource group, and Bicep templates are declarative.
None of the assumptions are feasible. In Azure, resource groups cannot be nested inside other resource groups. Furthermore, the location of a resource group only dictates where its metadata is stored, meaning resources inside it can reside in different geographical regions. Lastly, Bicep and ARM templates are declarative configurations defining the desired state of infrastructure, rather than imperative, step-by-step scripting tools.

Step-by-Step Solution

1
Evaluate the first assumption regarding resource group nesting.
Resource groups cannot be nested; they are flat logical containers directly under subscriptions.
Azure Resource Manager (ARM) does not support hierarchical nesting of resource groups.
2
Evaluate the second assumption regarding resource location requirements.
Resources do not need to match their resource group's location; they can be deployed to any supported region.
A resource group's location is only used to store metadata about the resources, not to restrict the deployment region of the resources themselves.
3
Evaluate the third assumption regarding the execution style of Bicep templates.
Bicep and ARM templates are declarative configurations that specify the target end-state, not imperative scripts.
Azure Resource Manager reads the declarative template and orchestrates the resource creation process automatically, making imperative scripting unnecessary.

Key Concept

Azure Resource Manager (ARM) template structure, deployment behaviors, and Resource Group properties.
Estimated Time:2m 0s
Rate this question

Topics

Azure Resource Manager (ARM) and ARM Templates/Bicep

More questions from this topic