Backend initialization and migration in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize the Terraform backend.

Terraform

terraform [1]

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

Ainit

Bapply

Cplan

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'terraform apply' before initializing the backend.

Confusing 'terraform plan' with initialization.

The terraform init command initializes the backend and prepares the working directory.

2fill in blank

medium

Complete the code to migrate the Terraform state to a new backend.

Terraform

terraform [1] -migrate-state

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

Aapply

Bplan

Crefresh

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to migrate state with 'terraform apply'.

Forgetting the '-migrate-state' flag.

The terraform init -migrate-state command migrates the state to the new backend configuration.

3fill in blank

hard

Fix the error in the backend configuration block by completing the missing backend type.

Terraform

terraform {
  backend "[1]" {
    bucket = "my-terraform-state"
    region = "us-west-2"
  }
}

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

Agcs

Blocal

Cs3

Dazurerm

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'local' backend when remote storage is intended.

Confusing 'gcs' (Google Cloud Storage) with AWS S3.

The backend type s3 is used for storing Terraform state in an AWS S3 bucket.

4fill in blank

hard

Fill both blanks to configure a remote backend with encryption and versioning enabled.

Terraform

terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    region         = "us-east-1"
    [1] = true
    [2] = true
  }
}

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

Aencrypt

Bversioning

Ckms_key_id

Dforce_destroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kms_key_id' instead of 'encrypt' for encryption flag.

Confusing 'force_destroy' with versioning.

The encrypt option enables encryption of the state file, and versioning enables versioning on the S3 bucket.

5fill in blank

hard

Fill all three blanks to write a backend block for Azure Blob Storage with container and key specified.

Terraform

terraform {
  backend "[1]" {
    storage_account_name = "mystorageaccount"
    container_name       = "[2]"
    key                  = "[3]"
  }
}

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

Aazurerm

Btfstate

Cterraform.tfstate

Dstatefiles

Attempts:

3 left

💡 Hint

Common Mistakes

Using 's3' instead of 'azurerm' for Azure backend.

Incorrect container or key names causing state file errors.

The backend type for Azure Blob Storage is azurerm. The container_name is typically a container like tfstate, and the key is the state file name, commonly terraform.tfstate.