State and real infrastructure mapping in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize Terraform state in the current directory.

Terraform

terraform [1]

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

Aapply

Bplan

Cdestroy

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' before initializing causes errors.

Confusing 'plan' with initialization.

Terraform uses init to initialize the working directory and set up the state backend.

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'

Ashow

Bstate list

Crefresh

Dapply

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'state list' only lists resource addresses, not full state details.

Using 'apply' changes infrastructure instead of showing state.

The terraform show command displays the current state or plan in a human-readable format.

3fill in blank

hard

Fix the error in the command to refresh Terraform state with real infrastructure.

Terraform

terraform [1]

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

Aplan

Bapply

Crefresh

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' changes infrastructure instead of just refreshing state.

Using 'plan' only shows changes but does not update state.

The terraform refresh command updates the state file to match the real infrastructure.

4fill in blank

hard

Fill both blanks to list all resources in the Terraform state and filter by resource type.

Terraform

terraform state [1] | grep [2]

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

Alist

Bshow

Caws_instance

Dplan

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'show' instead of 'list' does not list resource addresses.

Using 'plan' is unrelated to state listing.

terraform state list lists all resources in state. Using grep aws_instance filters to show only AWS instances.

5fill in blank

hard

Fill the blanks to remove a resource from Terraform state safely.

Terraform

terraform state [1] [2]

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

Arm

Baws_instance.example

C-force

Dshow

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'show' instead of 'rm' does not remove resources.

Confusing state 'rm' with 'destroy', which affects real infrastructure.

terraform state rm aws_instance.example removes the resource from state without affecting real infrastructure.

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