Terraform state rm for removing resources - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What happens when you run terraform state rm on a resource?

You have a resource managed by Terraform. You run terraform state rm <resource_name>. What is the immediate effect on Terraform's behavior?

A Terraform deletes the actual resource from the cloud provider immediately.

B Terraform marks the resource as tainted and plans to recreate it on next apply.

C Terraform locks the state file to prevent changes to the resource.

D Terraform removes the resource from its state file but does not delete the actual resource.

💡 Hint

Think about what the state file represents versus the real resource.

The terraform state rm command removes the resource from Terraform's state file. This means Terraform no longer tracks it, but the actual resource in the cloud remains untouched. Terraform will not manage or delete it unless you import it back or manually delete it.

❓ Configuration

intermediate

Which command correctly removes a resource named aws_instance.example from Terraform state?

You want to remove the resource aws_instance.example from Terraform's state without deleting the actual instance. Which command should you run?

A terraform destroy -target=aws_instance.example

B terraform state rm aws_instance.example

C terraform apply -replace=aws_instance.example

D terraform import aws_instance.example

💡 Hint

Focus on the command that only affects the state file.

terraform state rm aws_instance.example removes the resource from the state file only. The other commands either destroy, replace, or import resources, which is not what is asked.

❓ service_behavior

advanced

After running terraform state rm on a resource, what will happen if you run terraform apply without changing configuration?

You removed a resource from Terraform state using terraform state rm. You did not change your Terraform configuration files. What will Terraform do when you run terraform apply next?

A Terraform will recreate the resource because it is missing from the state but present in configuration.

B Terraform will do nothing because the resource is removed from state and configuration.

C Terraform will show an error about missing resource in state.

D Terraform will delete the resource from the cloud provider automatically.

💡 Hint

Think about how Terraform compares state and configuration.

When a resource is removed from state but still exists in configuration, Terraform treats it as needing creation. So on terraform apply, it will try to create it again.

❓ security

advanced

What is a potential risk of using terraform state rm on sensitive resources?

You use terraform state rm to remove a sensitive resource like a database instance from Terraform state. What risk does this pose?

A Terraform will automatically delete the resource after state removal.

B Terraform will encrypt the resource data in the state file.

C Terraform will lose track of the resource, so accidental manual changes may go unnoticed.

D Terraform will expose sensitive data in logs after removal.

💡 Hint

Consider what happens when Terraform no longer manages a resource.

Removing a resource from state means Terraform no longer tracks it. Manual changes or drift can happen without Terraform detecting them, which is risky for sensitive resources.

❓ Architecture

expert

You want to remove a resource from Terraform state but keep it managed by another Terraform workspace. What is the best approach?

You have a resource managed in Terraform workspace dev. You want to remove it from dev state but keep managing it in workspace prod. How should you proceed?

A Run <code>terraform state rm</code> in <code>dev</code> workspace and import the resource into <code>prod</code> workspace.

B Delete the resource manually and recreate it in <code>prod</code> workspace.

C Run <code>terraform destroy</code> in <code>dev</code> workspace and then create in <code>prod</code>.

D Copy the state file from <code>dev</code> to <code>prod</code> and run <code>terraform apply</code>.

💡 Hint

Think about how Terraform tracks resources across workspaces.

Each workspace has its own state. To stop managing a resource in one workspace but keep it in another, remove it from the first workspace's state and import it into the second workspace's state.

Practice

1. What does the terraform state rm command do?

easy

A. Deletes the resource from the cloud provider and Terraform state

B. Removes a resource from Terraform's state without deleting the actual resource

C. Updates the resource configuration in Terraform files

D. Creates a new resource and adds it to the state

Solution

1. Step 1: Understand the purpose of terraform state rm

   This command tells Terraform to stop tracking a resource by removing it from the state file.

2. Step 2: Recognize it does not delete the actual resource

   The real resource remains intact in the cloud; only Terraform forgets it.

3. Final Answer:

   Removes a resource from Terraform's state without deleting the actual resource -> Option B

4. Quick Check:

   State removal only forgets resource [OK]

Hint: Remember: state rm forgets resource, does not delete it [OK]

Common Mistakes:

• Thinking it deletes the actual resource
• Confusing it with terraform destroy
• Assuming it updates resource configuration

2. Which of the following is the correct syntax to remove a resource named aws_instance.example from Terraform state?

easy

A. terraform rm state aws_instance.example

B. terraform remove aws_instance.example

C. terraform state rm aws_instance.example

D. terraform state delete aws_instance.example

Solution

1. Step 1: Recall the correct command structure

   The command to remove a resource from state is terraform state rm <resource_name>.

2. Step 2: Match the resource name format

   The resource name is aws_instance.example, so the full command is terraform state rm aws_instance.example.

3. Final Answer:

   terraform state rm aws_instance.example -> Option C

4. Quick Check:

   Correct command syntax [OK]

Hint: Use 'terraform state rm' followed by resource name [OK]

Common Mistakes:

• Swapping 'rm' and 'state' keywords
• Using 'remove' or 'delete' instead of 'rm'
• Incorrect command order

3. Given the following Terraform state command:

terraform state rm aws_s3_bucket.my_bucket

What will happen after running this command?

medium

A. Terraform will remove the S3 bucket from state but the bucket remains in AWS

B. Terraform will update the S3 bucket configuration in the state

C. Terraform will delete the S3 bucket from AWS and remove it from state

D. Terraform will show an error because the command is incomplete

Solution

1. Step 1: Understand the effect of terraform state rm

   This command removes the resource from Terraform's state file only.

2. Step 2: Recognize the real resource remains untouched

   The actual S3 bucket in AWS is not deleted or changed by this command.

3. Final Answer:

   Terraform will remove the S3 bucket from state but the bucket remains in AWS -> Option A

4. Quick Check:

   State removal keeps resource intact [OK]

Hint: State rm forgets resource, does not delete it in cloud [OK]

Common Mistakes:

• Assuming the resource is deleted from AWS
• Thinking the state file is updated with new config
• Believing the command is incomplete

4. You ran terraform state rm aws_instance.web but later realized you still want Terraform to manage this instance. What is the best way to fix this?

medium

A. Run terraform import aws_instance.web <instance_id> to re-add it to state

B. Run terraform state add aws_instance.web to add it back

C. Run terraform state rm aws_instance.web again to undo

D. Delete the instance manually and recreate it

Solution

1. Step 1: Understand that terraform state rm only removes from state

   Once removed, Terraform no longer tracks the resource.

2. Step 2: Use terraform import to re-add the existing resource to state

   This command links the real resource back to Terraform's state file.

3. Final Answer:

   Run terraform import aws_instance.web <instance_id> to re-add it to state -> Option A

4. Quick Check:

   Import command restores resource to state [OK]

Hint: Use terraform import to re-add removed resources [OK]

Common Mistakes:

• Trying to use a non-existent 'state add' command
• Running state rm again expecting undo
• Deleting resource unnecessarily

5. You want to stop managing a resource google_compute_instance.vm1 with Terraform but keep it running in your cloud. Which sequence of commands achieves this safely?

hard

A. Run terraform state rm google_compute_instance.vm1 then manually delete the resource

B. Run terraform destroy -target=google_compute_instance.vm1 to remove it from cloud and state

C. Remove the resource block from Terraform files and run terraform apply

D. Run terraform state rm google_compute_instance.vm1 only to remove it from state and keep it running

Solution

1. Step 1: Use terraform state rm to remove resource from state

   This stops Terraform from managing the resource but does not delete it.

2. Step 2: Avoid deleting the resource or removing config to keep it running

   Deleting or removing config and applying would delete or recreate the resource.

3. Final Answer:

   Run terraform state rm google_compute_instance.vm1 only to remove it from state and keep it running -> Option D

4. Quick Check:

   State rm forgets resource, keeps it running [OK]

Hint: State rm removes from Terraform control, resource stays alive [OK]

Common Mistakes:

• Deleting resource after state rm
• Using terraform destroy which deletes resource
• Removing config without state rm causes resource deletion