State and real infrastructure mapping in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of Terraform state?

Terraform state keeps track of the resources it manages. It maps the configuration to real infrastructure so Terraform knows what exists and what needs to change.

beginner

How does Terraform use the state file during deployment?

Terraform reads the state file to understand current infrastructure. It compares this to the desired configuration to plan changes.

intermediate

What can happen if the Terraform state file is lost or corrupted?

Terraform may lose track of resources, causing it to try to recreate or delete resources incorrectly. This can lead to downtime or resource duplication.

intermediate

Why is remote state storage recommended in Terraform?

Remote state storage allows teams to share the state file safely. It prevents conflicts and keeps state backed up and secure.

beginner

What is the difference between Terraform configuration and Terraform state?

Configuration is the code describing desired infrastructure. State is the snapshot of what Terraform has created and manages in the real world.

What does Terraform state file primarily store?

A Cloud provider billing info

B User credentials

C Terraform configuration code

D Current infrastructure resource details

Terraform state stores details about the real infrastructure resources it manages.

Why should Terraform state be stored remotely in team environments?

A To allow multiple users to access and update state safely

B To speed up Terraform execution

C To reduce cloud costs

D To encrypt Terraform configuration files

Remote state storage prevents conflicts by allowing safe shared access to the state file.

What happens if Terraform state is out of sync with real infrastructure?

A Terraform may try to recreate or delete resources incorrectly

B Terraform automatically fixes the state file

C Terraform ignores the state and applies changes blindly

D Terraform deletes all resources

An out-of-sync state can cause Terraform to make wrong changes, risking resource loss or duplication.

Which command updates the Terraform state to match real infrastructure without making changes?

A terraform apply

B terraform refresh

C terraform init

D terraform plan

The 'terraform refresh' command updates the state file to reflect real infrastructure status.

What is stored in Terraform configuration files?

A Cloud provider API keys

B Current infrastructure state

C Desired infrastructure setup

D Terraform state file backup

Configuration files describe the desired infrastructure Terraform should create or manage.

Explain how Terraform state helps map configuration to real infrastructure.

Think about how Terraform knows what exists and what to change.

Describe best practices for managing Terraform state in a team environment.

Consider how teams avoid conflicts and data loss.

Practice

1. What is the main purpose of the Terraform state file?

easy

A. To keep track of real infrastructure resources Terraform manages

B. To store user credentials for cloud providers

C. To define the desired infrastructure configuration

D. To log errors during Terraform runs

Solution

1. Step 1: Understand Terraform state role

   The state file records what resources Terraform has created or manages in the real world.

2. Step 2: Differentiate state from config and logs

   The configuration defines desired setup, but state tracks actual deployed resources. Credentials and logs are separate concerns.

3. Final Answer:

   To keep track of real infrastructure resources Terraform manages -> Option A

4. Quick Check:

   State tracks real resources [OK]

Hint: State file = Terraform's memory of real resources [OK]

Common Mistakes:

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

2. Which Terraform command shows the current state of resources managed by Terraform?

easy

A. terraform init

B. terraform plan

C. terraform apply

D. terraform state list

Solution

1. Step 1: Identify command to inspect state

   "terraform state list" displays all resources tracked in the current state file.

2. Step 2: Differentiate from other commands

   "terraform plan" previews changes, "apply" makes changes, "init" sets up backend and providers.

3. Final Answer:

   terraform state list -> Option D

4. Quick Check:

   State inspection command = terraform state list [OK]

Hint: Use 'terraform state list' to see tracked resources [OK]

Common Mistakes:

• Using 'terraform plan' to check state directly
• Confusing 'terraform apply' with state inspection
• Thinking 'terraform init' shows state

3. Given this Terraform state snippet showing one AWS instance resource:

{
  "resources": [
    {
      "type": "aws_instance",
      "name": "web",
      "instances": [
        {"attributes": {"id": "i-1234567890abcdef0", "ami": "ami-0abc1234", "instance_type": "t2.micro"}}
      ]
    }
  ]
}

What is the instance type Terraform currently tracks for this resource?

medium

A. t2.micro

B. ami-0abc1234

C. i-1234567890abcdef0

D. aws_instance

Solution

1. Step 1: Locate instance_type attribute in state

   The attribute "instance_type" has value "t2.micro" in the resource's attributes.

2. Step 2: Understand attribute meanings

   "ami" is the image ID, "id" is the instance ID, "type" is resource type, so only "instance_type" matches the question.

3. Final Answer:

   t2.micro -> Option A

4. Quick Check:

   Instance type in state = t2.micro [OK]

Hint: Look for 'instance_type' attribute in state JSON [OK]

Common Mistakes:

• Confusing AMI ID with instance type
• Picking resource type as instance type
• Choosing instance ID instead of type

4. You ran terraform apply but your real infrastructure changed outside Terraform. What should you do to fix the state mismatch?

medium

A. Run terraform destroy to remove all resources

B. Run terraform refresh to update the state file with real resource data

C. Manually edit the state file to match real resources

D. Delete the state file and run terraform init again

Solution

1. Step 1: Understand state drift problem

   When real resources change outside Terraform, state file becomes outdated and causes mismatch.

2. Step 2: Use terraform refresh to sync state

   "terraform refresh" updates the state file to reflect current real infrastructure without changing resources.

3. Final Answer:

   Run terraform refresh to update the state file with real resource data -> Option B

4. Quick Check:

   Sync state with real infra = terraform refresh [OK]

Hint: Use 'terraform refresh' to sync state with real resources [OK]

Common Mistakes:

• Deleting state file causes loss of tracking
• Editing state file manually risks corruption
• Destroying resources is unnecessary for state fix

5. You want to share your Terraform state securely among your team using a remote backend. Which approach best ensures state consistency and safety?

hard

A. Email the state file to team members after each change

B. Store the state file on a shared network drive without locking

C. Use a remote backend like AWS S3 with state locking via DynamoDB

D. Keep the state file local on each developer's machine

Solution

1. Step 1: Identify remote backend with locking

   A remote backend like AWS S3 combined with DynamoDB locking prevents simultaneous edits and keeps state consistent.

2. Step 2: Evaluate other options for safety

   Shared drives without locking risk conflicts, emailing state causes version confusion, local files prevent collaboration.

3. Final Answer:

   Use a remote backend like AWS S3 with state locking via DynamoDB -> Option C

4. Quick Check:

   Remote backend + locking = safe shared state [OK]

Hint: Use remote backend with locking for team state safety [OK]

Common Mistakes:

• Ignoring state locking leads to conflicts
• Sharing state by email causes outdated copies
• Local state prevents team collaboration