Terraform state rm for removing resources - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to remove a resource named 'aws_instance.example' from the Terraform state.

Terraform

terraform state rm [1]

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

Aaws_instance.example

Baws_instance.example.id

Cexample.aws_instance

Dterraform.aws_instance.example

Attempts:

3 left

💡 Hint

Common Mistakes

Adding '.id' to the resource address

Using incorrect resource address format

Including extra prefixes before the resource address

The correct command to remove a resource from Terraform state uses the exact resource address, such as aws_instance.example.

2fill in blank

medium

Complete the command to remove multiple resources at once from the Terraform state.

Terraform

terraform state rm [1]

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

Aaws_instance.example1,aws_instance.example2

Baws_instance.example1 aws_instance.example2

Caws_instance.example1;aws_instance.example2

Daws_instance.example1|aws_instance.example2

Attempts:

3 left

💡 Hint

Common Mistakes

Using commas or semicolons to separate resource addresses

Using pipes or other symbols instead of spaces

To remove multiple resources, list them separated by spaces without commas or other separators.

3fill in blank

hard

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

Terraform

terraform state rm [1]

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

Aaws_instance-example

Baws_instance.example id

Caws_instance.example/

Daws_instance.example

Attempts:

3 left

💡 Hint

Common Mistakes

Replacing dots with dashes

Adding trailing slashes

Adding spaces inside the resource address

The resource address must be exact and without extra characters or spaces. The correct format is aws_instance.example.

4fill in blank

hard

Fill both blanks to remove a resource from a specific module in Terraform state.

Terraform

terraform state rm [1].[2]

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

Amodule.webserver

Baws_instance

Cexample

Dresource

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'resource' instead of the resource name

Omitting the 'module.' prefix

Swapping the order of module and resource

When removing a resource inside a module, the address includes the module path and the resource name, like module.webserver.example.

5fill in blank

hard

Fill all three blanks to remove a resource from a nested module in Terraform state.

Terraform

terraform state rm [1].[2].[3]

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

Amodule.database

Bmodule.backend

Caws_db_instance

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Missing one of the module parts

Incorrect order of modules

Using resource name without module path

For nested modules, the resource address includes each module in the path followed by the resource name, e.g., module.backend.module.database.aws_db_instance.

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