Why state is essential in Terraform - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize Terraform state.

Terraform

terraform [1]

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

Aapply

Binit

Cplan

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' before initializing causes errors.

Confusing 'plan' with initialization.

The terraform init command initializes the working directory and downloads necessary plugins, setting up the state file.

2fill in blank

medium

Complete the code to show the current Terraform state.

Terraform

terraform [1]

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

Aapply

Bplan

Cstate list

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' or 'plan' to view state.

Trying to read state without initializing.

The terraform state list command lists all resources tracked in the current state file.

3fill in blank

hard

Fix the error in the backend configuration to enable remote state storage.

Terraform

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

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

As3

Blocal

Cgcs

Dazurerm

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'local' backend when remote storage is needed.

Confusing cloud providers in backend names.

The s3 backend stores Terraform state files in an AWS S3 bucket, enabling remote state management.

4fill in blank

hard

Fill both blanks to configure Terraform to lock state during operations.

Terraform

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

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

Aencrypt

Block_table

Cdynamodb_table

Dlock

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect key names like 'lock_table' or 'lock'.

Forgetting to enable encryption.

Setting encrypt = true secures the state file, and dynamodb_table enables state locking using a DynamoDB table.

5fill in blank

hard

Fill all three blanks to output the current state file path and its format.

Terraform

output "state_info" {
  value = {
    path   = "[1]"
    format = "[2]"
    size   = [3]
  }
}

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

Aterraform.tfstate

Bjson

C1024

Dstate.tf

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect file names or formats.

Confusing size with string instead of number.

The default state file is terraform.tfstate, stored in JSON format. The size is an example number representing file size in bytes.

Practice

1. Why does Terraform use a state file when managing infrastructure?

easy

A. To keep track of resources it created and their current status

B. To store user credentials for cloud providers

C. To log errors during deployment

D. To save the Terraform configuration files

Solution

1. Step 1: Understand Terraform's resource tracking

   Terraform needs to know what resources it created and their current state to manage updates correctly.

2. Step 2: Identify the purpose of the state file

   The state file stores this information so Terraform can compare desired and actual infrastructure.

3. Final Answer:

   To keep track of resources it created and their current status -> Option A

4. Quick Check:

   State file tracks resources [OK]

Hint: State file tracks resources and status [OK]

Common Mistakes:

• Confusing state file with config files
• Thinking state stores credentials
• Assuming state logs errors

2. Which of the following is the correct way to specify the backend for storing Terraform state remotely?

easy

A. backend = s3 { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" }

B. backend: s3 { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" }

C. backend "s3" (bucket = "mybucket", key = "state.tfstate", region = "us-east-1")

D. backend "s3" { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" }

Solution

1. Step 1: Recall Terraform backend syntax

   The backend block uses the syntax: backend "type" { ... } with curly braces and key-value pairs.

2. Step 2: Match the correct syntax

   backend "s3" { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" } matches this format exactly, while others use incorrect symbols or assignment styles.

3. Final Answer:

   backend "s3" { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" } -> Option D

4. Quick Check:

   Backend block uses "backend \"type\" { ... }" syntax [OK]

Hint: Backend uses "backend \"type\" { ... }" syntax [OK]

Common Mistakes:

• Using equals sign instead of block
• Using parentheses instead of braces
• Incorrect colon usage

3. Given this Terraform state snippet showing two resources, what will happen if you run terraform apply after changing the resource name in the config but not updating the state file?

medium

A. Terraform will delete both resources

B. Terraform will update the existing resource with the new name

C. Terraform will create a new resource and keep the old one

D. Terraform will throw a syntax error

Solution

1. Step 1: Understand state and resource identity

   Terraform uses the state file to track resources by their IDs, not just names in config.

2. Step 2: Effect of changing resource name without state update

   Changing the resource name in config makes Terraform think it's a new resource, so it creates it and keeps the old one.

3. Final Answer:

   Terraform will create a new resource and keep the old one -> Option C

4. Quick Check:

   State tracks resource IDs, name change creates new resource [OK]

Hint: State tracks IDs, name change adds new resource [OK]

Common Mistakes:

• Assuming name change updates resource
• Expecting deletion of old resource
• Thinking syntax error occurs

4. You accidentally deleted your Terraform state file locally but still have your infrastructure running. What is the best way to fix this?

medium

A. Use terraform import to re-associate resources with a new state file

B. Manually recreate the state file by writing JSON

C. Run terraform init to recreate the state file from scratch

D. Delete all infrastructure and start over

Solution

1. Step 1: Understand state file importance

   The state file tracks existing resources; losing it means Terraform doesn't know what exists.

2. Step 2: Best recovery method

   Using terraform import lets you link existing resources back into a new state file safely.

3. Final Answer:

   Use terraform import to re-associate resources with a new state file -> Option A

4. Quick Check:

   Import existing resources to rebuild state [OK]

Hint: Use terraform import to rebuild lost state [OK]

Common Mistakes:

• Thinking terraform init recreates state automatically
• Trying to write state JSON manually
• Assuming infrastructure must be deleted

5. In a team environment, why is it important to share the Terraform state file remotely instead of each member using a local state file?

hard

A. To avoid using version control systems

B. To prevent conflicting changes and ensure everyone works with the latest infrastructure state

C. To speed up Terraform plan execution by caching locally

D. To allow each member to have a personal copy of infrastructure

Solution

1. Step 1: Understand teamwork challenges with local state

   If each member uses local state, changes can conflict and cause errors or resource duplication.

2. Step 2: Benefits of remote shared state

   Sharing state remotely ensures everyone sees the latest resource info and avoids conflicts.

3. Final Answer:

   To prevent conflicting changes and ensure everyone works with the latest infrastructure state -> Option B

4. Quick Check:

   Shared state prevents conflicts in teams [OK]

Hint: Share state remotely to avoid conflicts in teams [OK]

Common Mistakes:

• Thinking local state is fine for teams
• Believing remote state speeds up plans
• Confusing state sharing with version control