Why state operations are needed 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

Bplan

Cinit

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' before initializing state.

Confusing 'plan' with initialization.

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

2fill in blank

medium

Complete the code to show the current Terraform state.

Terraform

terraform [1] show

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

Aoutput

Bstate

Crefresh

Dvalidate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'output' which shows output variables, not state.

Using 'refresh' which updates state but does not show it.

The state show command displays detailed information about resources in the state.

3fill in blank

hard

Fix the error in the command to remove a resource from state.

Terraform

terraform state [1] aws_instance.example

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

Arm

Bdelete

Cremove

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' which is not a valid subcommand.

Using 'destroy' which deletes actual resources, not state entries.

The correct command to remove a resource from state is terraform state rm.

4fill in blank

hard

Fill the blank to correctly move a resource in Terraform state.

Terraform

terraform state [1] aws_instance.old_name aws_instance.new_name

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

Amv

Brm

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'rm' which removes resources instead of moving.

Using 'destroy' which deletes actual resources, not state entries.

The terraform state mv command moves a resource in the state file from one name to another.

5fill in blank

hard

Fill both blanks to correctly import an existing resource into Terraform state.

Terraform

terraform import [1] [2]

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

Aaws_instance.example

Bi-1234567890abcdef0

C-config=terraform.tf

D-var-file=prod.tfvars

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-config=terraform.tf' instead of resource address.

Mixing resource ID and address positions.

The terraform import command requires the resource address and the real resource ID.

Practice

1. Why does Terraform use a state file to track resources?

easy

A. To store user passwords securely

B. To backup cloud provider data automatically

C. To speed up internet connection

D. To know what resources exist and manage changes safely

Solution

1. Step 1: Understand Terraform's purpose

   Terraform manages cloud resources by tracking their current state to avoid conflicts and errors.

2. Step 2: Role of the state file

   The state file records what resources exist and their settings, so Terraform can plan updates safely.

3. Final Answer:

   To know what resources exist and manage changes safely -> Option D

4. Quick Check:

   State file tracks resources = B [OK]

Hint: State file tracks resources to manage changes safely [OK]

Common Mistakes:

• Thinking state stores passwords
• Confusing state with cloud backups
• Believing state speeds internet

2. Which Terraform command updates the state file after creating resources?

easy

A. terraform apply

B. terraform init

C. terraform plan

D. terraform destroy

Solution

1. Step 1: Identify command purpose

   terraform apply creates or updates resources and updates the state file accordingly.

2. Step 2: Compare other commands

   terraform plan only shows changes, terraform init sets up, and terraform destroy deletes resources.

3. Final Answer:

   terraform apply -> Option A

4. Quick Check:

   Apply updates state = C [OK]

Hint: Apply command updates state after changes [OK]

Common Mistakes:

• Choosing plan instead of apply
• Confusing init with apply
• Thinking destroy updates state positively

3. Given this Terraform output after terraform plan:

  # aws_instance.example will be created
  + resource "aws_instance" "example" {
      + id = (known after apply)
      + ami = "ami-123456"
      + instance_type = "t2.micro"
    }

What does this output tell you about the state?

medium

A. The instance will be created and added to the state

B. The instance will be destroyed

C. The state file is corrupted

D. The instance already exists in the state

Solution

1. Step 1: Analyze plan output symbols

   The plus sign (+) means Terraform plans to create this resource, not yet in state.

2. Step 2: Understand state update

   After apply, the new instance will be created and recorded in the state file.

3. Final Answer:

   The instance will be created and added to the state -> Option A

4. Quick Check:

   Plus sign means create and update state = D [OK]

Hint: Plus sign means resource creation and state update [OK]

Common Mistakes:

• Thinking plus means destroy
• Assuming resource exists already
• Believing state file is corrupted

4. You run terraform apply but get an error saying the state file is locked. What is the likely cause?

medium

A. The cloud provider is down

B. Your Terraform version is outdated

C. Another user or process is currently modifying the state

D. Your configuration file has syntax errors

Solution

1. Step 1: Understand state locking

   Terraform locks the state file during operations to prevent conflicts from multiple users or processes.

2. Step 2: Identify cause of lock error

   If you get a lock error, it means someone else or another process is currently using the state file.

3. Final Answer:

   Another user or process is currently modifying the state -> Option C

4. Quick Check:

   State lock means concurrent modification = A [OK]

Hint: State lock means another user/process is active [OK]

Common Mistakes:

• Blaming Terraform version
• Assuming cloud provider issue
• Thinking syntax error causes lock

5. Your team shares a Terraform project using a remote backend for state. One member applies changes without pulling the latest state, causing conflicts. What is the best practice to avoid this?

hard

A. Disable state locking to allow simultaneous changes

B. Always run terraform init before any operation to sync state

C. Manually edit the state file to merge changes

D. Use separate state files for each team member

Solution

1. Step 1: Understand remote state and teamwork

   Remote backends store shared state; syncing ensures everyone works on the latest version.

2. Step 2: Importance of terraform init

   Running terraform init refreshes backend config and downloads latest state to avoid conflicts.

3. Step 3: Why other options fail

   Disabling locking risks conflicts; manual edits are error-prone; separate states break shared management.

4. Final Answer:

   Always run terraform init before any operation to sync state -> Option B

5. Quick Check:

   Init syncs state for teamwork = A [OK]

Hint: Run terraform init first to sync shared state [OK]

Common Mistakes:

• Disabling locking causes conflicts
• Editing state manually risks errors
• Using separate states breaks collaboration