Examkin

Question

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

An organization is evaluating infrastructure as code (IaC) deployment methods for their Azure environment. They review the following statement regarding Bicep templates:

Statement: Azure Resource Manager (ARM) templates written in Bicep require a separate runtime engine to be installed in Azure before they can be executed.

Is this statement true or false?

Answer: Answer

Answer

False
The statement is false because Azure Bicep is a domain-specific language that compiles/transpiles to standard JSON Azure Resource Manager (ARM) templates. Azure Resource Manager natively interprets the JSON templates, so there is no Bicep runtime engine installed in Azure.

Step-by-Step Solution

1
Analyze Bicep's architecture and how Bicep files are processed.
Identify that Bicep is a domain-specific language (DSL) designed to simplify the authoring of Azure Resource Manager (ARM) templates.
Understanding the design goal of Bicep helps clarify how it interacts with the Azure platform.
2
Evaluate the deployment mechanism of Bicep files.
Note that Bicep files (.bicep) are compiled (transpiled) into standard JSON ARM templates (.json) before execution, and the native Azure Resource Manager handles the deployment.
This confirms that Azure does not run Bicep code directly and does not need a special engine to execute it.

Key Concept

Bicep transpilation to standard JSON ARM templates and execution via the native Azure Resource Manager engine
Rate this question

Topics

Azure Resource Manager (ARM) and ARM Templates/Bicep

More questions from this topic