ARM vs Bicep vs Terraform decision in Azure - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Choosing the right tool for Azure infrastructure as code

You want to deploy Azure resources using infrastructure as code. Which tool is best if you want native Azure support with simple syntax and no external dependencies?

A Azure CLI scripts, because they are easy to write and run commands directly.

B Terraform, because it supports multiple clouds and has a large community.

C Bicep, because it is a domain-specific language that compiles to ARM templates and offers simpler syntax.

D ARM templates, because they are native JSON templates directly supported by Azure.

💡 Hint

Think about which tool is directly supported by Azure without extra layers.

ARM templates are native JSON files supported directly by Azure. They require no extra tools to deploy and are the base for other tools like Bicep.

❓ Architecture

intermediate

Selecting a tool for multi-cloud infrastructure management

Your company manages infrastructure across Azure, AWS, and Google Cloud. Which tool is best suited to manage all clouds with a single configuration language?

A Terraform, because it supports multiple cloud providers with one language.

B Bicep, because it simplifies ARM templates for Azure but does not support other clouds.

C ARM templates, because they are designed for Azure resources only.

D Azure Resource Manager portal, because it provides a graphical interface for all clouds.

💡 Hint

Consider which tool supports multiple cloud providers natively.

Terraform supports many cloud providers including Azure, AWS, and Google Cloud, allowing unified management with one language.

❓ security

advanced

Handling secrets securely in infrastructure as code

You need to deploy Azure resources and include sensitive data like passwords. Which approach best secures secrets when using Bicep or ARM templates?

A Embed secrets directly in the ARM or Bicep files as parameters.

B Use Azure Key Vault references in the templates to fetch secrets at deployment time.

C Store secrets in plain text files alongside the templates.

D Hardcode secrets in the deployment scripts that call the templates.

💡 Hint

Think about how to avoid storing secrets in code files.

Using Azure Key Vault references allows templates to securely retrieve secrets during deployment without exposing them in code.

✅ Best Practice

advanced

Maintaining infrastructure code readability and reuse

Which practice improves readability and reuse when writing infrastructure as code for Azure using Bicep?

A Use Bicep modules to break down infrastructure into smaller reusable parts.

B Write all resources in one large Bicep file without modules.

C Copy and paste resource definitions across multiple Bicep files.

D Avoid comments and documentation to keep files short.

💡 Hint

Think about how to organize code for reuse and clarity.

Bicep modules allow splitting infrastructure into smaller, reusable components, improving maintainability and readability.

❓ service_behavior

expert

Understanding deployment behavior differences between ARM and Terraform

You deploy the same Azure resource using ARM template and Terraform. After deployment, you update the resource outside the tools. What happens when you redeploy with each tool?

A Both ARM and Terraform detect external changes and update the resource accordingly.

B ARM redeploys and overwrites changes; Terraform ignores external changes and does not update the resource.

C ARM redeploys and overwrites changes; Terraform detects drift and can update the resource to match the configuration.

D Terraform redeploys and overwrites changes; ARM ignores external changes and does not update the resource.

💡 Hint

Consider how each tool tracks resource state and handles drift.

ARM templates redeploy resources as defined, overwriting changes. Terraform tracks state and can detect drift, allowing updates to restore desired state.