Provider configuration block in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the cloud provider as AWS.

Terraform

provider "[1]" {}

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

Agoogle

Bdigitalocean

Cazure

Daws

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong provider name like 'google' when intending AWS.

Misspelling the provider name.

The provider block tells Terraform which cloud provider to use. Here, aws is the correct provider name for Amazon Web Services.

2fill in blank

medium

Complete the code to set the AWS region to us-west-2.

Terraform

provider "aws" {
  region = "[1]"
}

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

Aus-east-1

Beu-central-1

Cus-west-2

Dap-southeast-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a region code that does not exist.

Forgetting to put the region value in quotes.

The region attribute sets the AWS region where resources will be created. us-west-2 is the correct region code for Oregon.

3fill in blank

hard

Fix the error in the provider block by completing the missing attribute name.

Terraform

provider "aws" {
  [1] = "us-east-1"
}

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

Azone

Bregion

Clocation

Darea

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'zone' or 'location' instead of 'region'.

Misspelling the attribute name.

The correct attribute to specify the AWS location is region. Other options are invalid and cause errors.

4fill in blank

hard

Fill both blanks to configure the AWS provider with region us-east-1 and profile default.

Terraform

provider "aws" {
  [1] = "us-east-1"
  [2] = "default"
}

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

Aregion

Bprofile

Czone

Daccount

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'zone' or 'account' instead of 'region' or 'profile'.

Swapping the order of attributes.

The region attribute sets the AWS region, and profile specifies the AWS CLI profile to use for credentials.

5fill in blank

hard

Fill all three blanks to configure the AWS provider with region us-west-1, profile admin, and enable shared credentials file.

Terraform

provider "aws" {
  [1] = "us-west-1"
  [2] = "admin"
  [3] = true
}

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

Aregion

Bprofile

Cshared_credentials_file

Duse_shared_credentials_file

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'shared_credentials_file' as a boolean instead of a file path.

Confusing attribute names for enabling shared credentials.

region sets the AWS region, profile selects the AWS CLI profile, and use_shared_credentials_file enables using the shared credentials file for authentication.

Practice

1.

What is the main purpose of the provider block in a Terraform configuration?

easy

A. To specify which cloud or service Terraform will manage

B. To define the resources to be created

C. To write output values for the configuration

D. To declare variables used in the configuration

Solution

1. Step 1: Understand the role of the provider block

   The provider block tells Terraform which cloud or service to connect to and manage.

2. Step 2: Differentiate from other blocks

   Resource blocks define what to create, variables declare inputs, and outputs define results, but the provider sets the target platform.

3. Final Answer:

   To specify which cloud or service Terraform will manage -> Option A

4. Quick Check:

   Provider block = target cloud/service [OK]

Hint: Provider block sets the cloud or service to use [OK]

Common Mistakes:

• Confusing provider with resource blocks
• Thinking provider defines variables or outputs
• Assuming provider creates resources directly

2.

Which of the following is the correct syntax to configure the AWS provider with the region us-west-2?

?

easy

A. provider aws { region = us-west-2 }

B. provider "aws" region = "us-west-2"

C. provider "aws" { region = "us-west-2" }

D. provider "aws" { region: "us-west-2" }

Solution

1. Step 1: Check provider block syntax

   The provider block requires the provider name in quotes and curly braces enclosing settings.

2. Step 2: Validate region assignment

   Region must be assigned with equals and quotes around the string value.

3. Final Answer:

   provider "aws" { region = "us-west-2" } -> Option C

4. Quick Check:

   Correct provider block syntax uses braces and equals [OK]

Hint: Use quotes and braces with equals for provider config [OK]

Common Mistakes:

• Omitting quotes around provider name
• Using colon instead of equals for assignment
• Not quoting string values like region

3.

Given this provider block:

provider "google" {
  project = "my-project"
  region  = "us-central1"
}

What will Terraform use as the target region when creating resources?

medium

A. my-project

B. us-central1

C. google

D. default region

Solution

1. Step 1: Identify the region setting in the provider block

   The region is set explicitly to "us-central1" in the provider configuration.

2. Step 2: Understand the role of the project setting

   The project is a separate setting identifying the Google Cloud project, not the region.

3. Final Answer:

   us-central1 -> Option B

4. Quick Check:

   Region setting = us-central1 [OK]

Hint: Region is the value of region key in provider block [OK]

Common Mistakes:

• Confusing project with region
• Assuming default region if region is set
• Using provider name as region

4.

Identify the error in this provider block configuration:

provider "azurerm" {
  features = {}
  region = "eastus"
}

medium

A. The region value should not be in quotes

B. The features block must be empty

C. The provider name should be azure not azurerm

D. The region argument is invalid for azurerm provider

Solution

1. Step 1: Check azurerm provider required arguments

   AzureRM provider uses features block but does not accept a region argument.

2. Step 2: Understand region specification for Azure

   Region is specified inside resource blocks, not in provider block for azurerm.

3. Final Answer:

   The region argument is invalid for azurerm provider -> Option D

4. Quick Check:

   AzureRM provider does not use region in provider block [OK]

Hint: Check provider docs for valid arguments [OK]

Common Mistakes:

• Adding unsupported arguments to provider block
• Confusing provider name with resource names
• Misusing quotes around values

5.

You want to configure two AWS providers in the same Terraform configuration: one for us-east-1 and one for us-west-1. Which is the correct way to set this up?

hard

A. Use two provider "aws" blocks with different alias names and specify regions inside each

B. Use one provider "aws" block with a list of regions

C. Create two separate Terraform configurations for each region

D. Set region dynamically inside resource blocks without provider aliases

Solution

1. Step 1: Understand multiple provider usage

   Terraform supports multiple provider configurations by using alias to distinguish them.

2. Step 2: Configure each provider with its own region and alias

   Each provider "aws" block must have a unique alias and region setting.

3. Step 3: Reference providers in resources using the alias

   Resources specify which provider alias to use for deployment.

4. Final Answer:

   Use two provider "aws" blocks with different alias names and specify regions inside each -> Option A

5. Quick Check:

   Multiple providers = aliases + separate blocks [OK]

Hint: Use aliases to configure multiple providers [OK]

Common Mistakes:

• Trying to list multiple regions in one provider block
• Not using aliases for multiple providers
• Assuming one provider block covers all regions