Azure provider setup in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the location for an Azure resource group in Terraform.

Terraform

resource "azurerm_resource_group" "example" {
  name     = "example-resources"
  [1] = "eastus"
}

Drag options to blanks, or click blank then click option'

Azone

Bregion

Clocation

Darea

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'region' instead of 'location' causes Terraform to fail.

Using 'zone' or 'area' are not valid attributes for the azurerm_resource_group resource.

The correct attribute to specify the Azure region in the resource group block is location.

2fill in blank

medium

Complete the code to authenticate with Azure using a service principal.

Terraform

provider "azurerm" {
  features = {}
  client_id     = var.client_id
  client_secret = var.[1]
  tenant_id     = var.tenant_id
  subscription_id = var.subscription_id
}

Drag options to blanks, or click blank then click option'

Aclient_secret

Bpassword

Csecret_key

Daccess_token

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'password' or 'secret_key' instead of 'client_secret' causes authentication errors.

Using 'access_token' is not valid in this context.

The correct variable name for the service principal secret is client_secret.

3fill in blank

hard

Fix the error in the provider block to enable Azure Resource Manager features.

Terraform

provider "azurerm" {
  features = [1]
}

Drag options to blanks, or click blank then click option'

A[]

Bnull

Ctrue

D{}

Attempts:

3 left

💡 Hint

Common Mistakes

Using [] causes a type error.

Using true or null causes configuration errors.

The features argument must be set to an empty map {} to enable Azure RM features.

4fill in blank

hard

Fill both blanks to configure the Azure provider with environment variables.

Terraform

provider "azurerm" {
  features = [1]
  subscription_id = var.[2]
}

Drag options to blanks, or click blank then click option'

A{}

Bsubscription_id

Ctenant_id

Dclient_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using a list or boolean for features.

Using tenant_id or client_id instead of subscription_id for subscription.

The features argument must be an empty map {}. The subscription ID variable is named subscription_id.

5fill in blank

hard

Fill all three blanks to complete the Azure provider block with authentication details.

Terraform

provider "azurerm" {
  features = [1]
  client_id = var.[2]
  client_secret = var.[3]
}

Drag options to blanks, or click blank then click option'

A{}

Bclient_id

Cclient_secret

Dtenant_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using tenant_id instead of client_secret for the secret.

Omitting the features argument or setting it incorrectly.

The features argument is an empty map {}. The authentication uses client_id and client_secret variables.

Practice

1. What is the main purpose of the Azure provider in Terraform?

easy

A. To provide a user interface for Azure portal

B. To create virtual machines automatically without configuration

C. To connect Terraform with your Azure account for resource management

D. To backup Azure resources to local storage

Solution

1. Step 1: Understand the role of a provider in Terraform

   The provider acts as a bridge between Terraform and the cloud platform, enabling resource management.

2. Step 2: Identify the Azure provider's function

   The Azure provider specifically connects Terraform to Azure to create, update, or delete Azure resources.

3. Final Answer:

   To connect Terraform with your Azure account for resource management -> Option C

4. Quick Check:

   Azure provider connects Terraform to Azure [OK]

Hint: Provider connects Terraform to cloud platform [OK]

Common Mistakes:

• Thinking provider creates resources without config
• Confusing provider with Azure portal UI
• Assuming provider handles backups

2. Which of the following is the correct minimal syntax to declare the Azure provider in Terraform?

easy

A. provider "azure" { features {} }

B. provider azurerm { features {} }

C. provider "azurerm" {}

D. provider "azurerm" { features {} }

Solution

1. Step 1: Check the provider block syntax

   Terraform requires the provider name in quotes and a block with at least an empty features block for Azure.

2. Step 2: Validate the provider name and features block

   The correct provider name is "azurerm" and it must include features {} even if empty.

3. Final Answer:

   provider "azurerm" { features {} } -> Option D

4. Quick Check:

   Correct syntax includes "azurerm" and features block [OK]

Hint: Use quotes and include empty features block [OK]

Common Mistakes:

• Omitting quotes around provider name
• Using wrong provider name like "azure"
• Skipping the features block

3. Given this Terraform snippet, what will happen when you run terraform init?

provider "azurerm" {
  features {}
  subscription_id = "1234-5678-9012"
}

medium

A. Terraform ignores subscription_id and initializes provider

B. Terraform initializes Azure provider with given subscription ID

C. Terraform throws an error because subscription_id is not allowed here

D. Terraform requires a client_id and client_secret to initialize

Solution

1. Step 1: Understand provider initialization

   Terraform accepts subscription_id in the provider block to configure Azure provider authentication.

2. Step 2: Check if subscription_id is valid here

   subscription_id is a valid argument for azurerm provider and helps specify the Azure subscription.

3. Final Answer:

   Terraform initializes Azure provider with given subscription ID -> Option B

4. Quick Check:

   subscription_id configures provider initialization [OK]

Hint: subscription_id is valid in provider block [OK]

Common Mistakes:

• Thinking subscription_id causes error
• Assuming client_id/client_secret always required
• Believing Terraform ignores unknown keys silently

4. You wrote this provider block but get an error on terraform init. What is the likely cause?

provider "azurerm" {
  features {}
  client_id = "abc"
}

medium

A. Missing client_secret and tenant_id for authentication

B. features block should not be empty

C. client_id must be a number, not a string

D. provider name should be "azure" not "azurerm"

Solution

1. Step 1: Review required authentication parameters

   Azure provider requires client_id, client_secret, and tenant_id for service principal authentication.

2. Step 2: Identify missing parameters

   Only client_id is provided; client_secret and tenant_id are missing, causing authentication error.

3. Final Answer:

   Missing client_secret and tenant_id for authentication -> Option A

4. Quick Check:

   All auth params needed: client_id, client_secret, tenant_id [OK]

Hint: All three auth params must be set together [OK]

Common Mistakes:

• Leaving features block empty causes error
• Using wrong provider name
• Misunderstanding client_id data type

5. You want to configure Terraform to authenticate to Azure using environment variables instead of hardcoding credentials. Which provider block setup is correct?

hard

A. provider "azurerm" { features {} }

B. provider "azurerm" { features {} client_id = var.client_id }

C. provider "azurerm" { features {} subscription_id = var.sub_id }

D. provider "azurerm" { features {} client_secret = var.secret }

Solution

1. Step 1: Understand environment variable authentication

   Azure provider can use environment variables for authentication if no credentials are hardcoded in the provider block.

2. Step 2: Identify minimal provider block for env auth

   Providing only features {} allows Terraform to use environment variables automatically.

3. Final Answer:

   provider "azurerm" { features {} } -> Option A

4. Quick Check:

   Empty features block enables env var auth [OK]

Hint: Empty features block uses env vars for auth [OK]

Common Mistakes:

• Hardcoding credentials disables env var auth
• Omitting features block causes error
• Assuming subscription_id alone enables auth