Terraform provider ecosystem - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Terraform provider for AWS.

Terraform

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

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

Aus-west-2

Baws-region

Cdefault

Dregion-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid region names like 'aws-region' or 'default'.

Leaving the region blank.

The region attribute specifies the AWS region where resources will be created. us-west-2 is a valid AWS region.

2fill in blank

medium

Complete the code to declare the Terraform provider version constraint.

Terraform

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "[1]"
    }
  }
}

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

A>= 2.0.0

B= latest

C< 1.0

D~> 4.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using '= latest' which is not a valid version constraint.

Using '< 1.0' which restricts to very old versions.

The version constraint ~> 4.0 means any version from 4.0 up to but not including 5.0, which is a common best practice to allow minor updates.

3fill in blank

hard

Fix the error in the provider block to correctly configure the AWS provider with a profile.

Terraform

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

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

A"default"

Bdefault

Cprofile1

D"profile1"

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around the profile name.

Using single quotes instead of double quotes.

The profile attribute requires a string value, so it must be enclosed in quotes.

4fill in blank

hard

Fill both blanks to configure the Terraform provider for Google Cloud with a project and region.

Terraform

provider "google" {
  project = "[1]"
  region  = "[2]"
}

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

Amy-gcp-project

Bus-central1

Cdefault-project

Deurope-west1

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid project names or regions.

Mixing up project and region values.

The project should be your Google Cloud project ID, and region should be a valid GCP region like us-central1.

5fill in blank

hard

Fill all three blanks to configure the Azure provider with subscription ID, tenant ID, and client ID.

Terraform

provider "azurerm" {
  subscription_id = "[1]"
  tenant_id       = "[2]"
  client_id       = "[3]"
  features        = {}
}

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

A12345678-1234-1234-1234-123456789abc

B87654321-4321-4321-4321-cba987654321

Cabcdef12-3456-7890-abcd-ef1234567890

Dfedcba98-7654-3210-fedc-ba9876543210

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted IDs.

Mixing up the order of IDs.

These are example GUIDs for subscription ID, tenant ID, and client ID. They must be strings enclosed in quotes.

Practice

1. What is the main purpose of a Terraform provider?

easy

A. To write custom Terraform modules

B. To connect Terraform with cloud services and tools

C. To store Terraform state files remotely

D. To manage user permissions in Terraform

Solution

1. Step 1: Understand Terraform provider role

   Providers act as bridges between Terraform and external services like clouds or APIs.

2. Step 2: Identify the correct purpose

   Connecting Terraform to cloud services enables resource management through Terraform configurations.

3. Final Answer:

   To connect Terraform with cloud services and tools -> Option B

4. Quick Check:

   Provider = Connect Terraform to services [OK]

Hint: Providers link Terraform to services, not modules or state [OK]

Common Mistakes:

• Confusing providers with modules
• Thinking providers manage state files
• Assuming providers control user permissions

2. Which block is used to declare the providers your Terraform configuration requires?

easy

A. terraform_providers

B. provider

C. required_providers

D. provider_config

Solution

1. Step 1: Recall Terraform syntax for provider declaration

   The required_providers block declares which providers Terraform needs to download and use.

2. Step 2: Differentiate from provider block

   The provider block configures a provider, but required_providers declares them.

3. Final Answer:

   <code>required_providers</code> -> Option C

4. Quick Check:

   Declare providers with required_providers [OK]

Hint: Use required_providers to declare, provider to configure [OK]

Common Mistakes:

• Using provider block to declare providers
• Confusing required_providers with terraform_providers
• Using incorrect block names like provider_config

3. Given this Terraform snippet, what provider version will Terraform use?

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 4.0, < 5.0"
    }
  }
}

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

medium

A. Any AWS provider version 4.x

B. Exactly AWS provider version 5.0

C. Any AWS provider version 3.x

D. Any AWS provider version 5.x

Solution

1. Step 1: Analyze version constraint in required_providers

   The version constraint ">= 4.0, < 5.0" means any version starting at 4.0 up to but not including 5.0.

2. Step 2: Match options with version range

   Only Any AWS provider version 4.x matches this range, meaning any 4.x version is valid.

3. Final Answer:

   Any AWS provider version 4.x -> Option A

4. Quick Check:

   Version >=4.0 and <5.0 means 4.x [OK]

Hint: Version constraints use >= and < for ranges [OK]

Common Mistakes:

• Choosing versions outside the specified range
• Confusing exact version with range
• Ignoring the upper bound < 5.0

4. You wrote this Terraform configuration but get an error: "Provider configuration not found for provider aws". What is the likely cause?

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 4.0"
    }
  }
}

# Missing provider block here

resource "aws_s3_bucket" "bucket" {
  bucket = "my-bucket"
  acl    = "private"
}

medium

A. You forgot to add a provider block to configure AWS

B. The required_providers block has wrong syntax

C. The resource block is missing a name

D. Terraform does not support AWS provider version 4.0

Solution

1. Step 1: Identify error cause from message

   The error says "Provider configuration not found", meaning Terraform knows the provider but lacks configuration.

2. Step 2: Check configuration blocks

   The configuration has required_providers but no provider "aws" {} block to set region or credentials.

3. Final Answer:

   You forgot to add a provider block to configure AWS -> Option A

4. Quick Check:

   Missing provider block causes configuration error [OK]

Hint: Declare required_providers, then configure with provider block [OK]

Common Mistakes:

• Assuming required_providers configures provider fully
• Ignoring missing provider block
• Blaming resource block or version support

5. You want to manage resources in two AWS regions using Terraform. How should you configure providers to achieve this?

hard

A. Use a single provider block and specify regions in resource tags

B. Use one provider block and change region dynamically in resources

C. Declare two required_providers blocks with different versions

D. Declare two provider blocks with different aliases and region settings

Solution

1. Step 1: Understand multi-region provider setup

   Terraform supports multiple provider configurations using aliases to distinguish them.

2. Step 2: Apply correct configuration method

   Declare two provider "aws" blocks with different alias and region values, then reference aliases in resources.

3. Final Answer:

   Declare two provider blocks with different aliases and region settings -> Option D

4. Quick Check:

   Multiple regions need aliased provider blocks [OK]

Hint: Use provider aliases for multiple regions [OK]

Common Mistakes:

• Trying to change region inside resource without provider alias
• Declaring multiple required_providers blocks incorrectly
• Using resource tags to set region instead of provider config