Terraform destroy for cleanup - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run the Terraform command that destroys all managed infrastructure.

Terraform

terraform [1]

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

Aapply

Bdestroy

Cplan

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'terraform apply' which creates or updates resources instead of destroying them.

Using 'terraform plan' which only shows changes without applying them.

The terraform destroy command removes all resources created by Terraform, cleaning up your infrastructure.

2fill in blank

medium

Complete the command to destroy infrastructure without asking for confirmation.

Terraform

terraform destroy [1]

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

A-skip-approve

B-force

C-auto-approve

D-no-confirm

Attempts:

3 left

💡 Hint

Common Mistakes

Using flags that do not exist like '-force' or '-no-confirm'.

Forgetting to add any flag and getting prompted for confirmation.

The -auto-approve flag skips the confirmation prompt and immediately destroys the resources.

3fill in blank

hard

Fix the error in the command to destroy resources in a specific workspace.

Terraform

terraform workspace select [1] && terraform destroy -auto-approve

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

Adefault

Bmain

Cproduction

Ddev

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting the wrong workspace name that does not exist.

Not selecting any workspace and destroying resources in the default workspace.

To destroy resources in the 'dev' workspace, you must select it first using terraform workspace select dev.

4fill in blank

hard

Fill both blanks to destroy resources using a specific Terraform state file and skip confirmation.

Terraform

terraform [1] -state=[2] -auto-approve

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

Adestroy

Bapply

Cterraform.tfstate

Dprod.tfstate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' instead of 'destroy' which creates or updates resources.

Using the wrong state file name or forgetting to specify it.

Use terraform destroy to remove resources and specify the state file with -state=prod.tfstate to target the correct infrastructure.

5fill in blank

hard

Fill all three blanks to destroy resources with a plan file and skip confirmation.

Terraform

terraform [1] [2] [3]

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

Aapply

B-auto-approve

Cdestroy.plan

D-state=terraform.tfstate

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the order of arguments or using incorrect flags.

Using 'destroy' instead of 'apply' when applying a destroy plan file.

Use terraform apply destroy.plan to destroy resources using the plan file (generated from terraform plan -destroy -out=destroy.plan) and skip confirmation with -auto-approve.

Practice

1. What does the terraform destroy command do?

easy

A. It updates existing resources without deleting them.

B. It deletes all resources created by Terraform in the current workspace.

C. It creates new resources defined in the configuration.

D. It shows the current state of resources without making changes.

Solution

1. Step 1: Understand the purpose of terraform destroy

   This command is designed to remove all resources that Terraform manages in the current workspace. Unlike terraform apply which creates or updates resources, terraform destroy deletes them. It does not just show state or update resources.

2. Final Answer:

   It deletes all resources created by Terraform in the current workspace. -> Option B

3. Quick Check:

   terraform destroy = deletes resources [OK]

Hint: Destroy means delete all created resources [OK]

Common Mistakes:

• Confusing destroy with apply
• Thinking destroy only shows resources
• Assuming destroy updates resources

2. Which of the following is the correct syntax to run terraform destroy without asking for confirmation?

easy

A. terraform destroy -force

B. terraform destroy --yes

C. terraform destroy --confirm

D. terraform destroy -auto-approve

Solution

1. Step 1: Recall the flag to skip confirmation

   The correct flag to skip the confirmation prompt is -auto-approve. -force, --yes, and --confirm are not valid flags for terraform destroy.

2. Final Answer:

   terraform destroy -auto-approve -> Option D

3. Quick Check:

   Skip confirmation = -auto-approve [OK]

Hint: Use -auto-approve to skip confirmation [OK]

Common Mistakes:

• Using -force instead of -auto-approve
• Typing --yes which is invalid
• Assuming --confirm works

3. Given the following Terraform commands run in order:
terraform apply -auto-approve
terraform destroy
What will happen after the second command?

medium

A. All resources created by the first command will be deleted after confirmation.

B. Resources will be updated but not deleted.

C. Nothing will happen because destroy requires -auto-approve.

D. Terraform will show an error because destroy must be run before apply.

Solution

1. Step 1: Understand the effect of terraform apply -auto-approve

   This command creates or updates resources without asking for confirmation. This command will prompt for confirmation before deleting all resources created by Terraform.

2. Final Answer:

   All resources created by the first command will be deleted after confirmation. -> Option A

3. Quick Check:

   Destroy deletes resources after confirmation [OK]

Hint: Destroy deletes resources after confirmation unless skipped [OK]

Common Mistakes:

• Thinking destroy needs -auto-approve to work
• Believing destroy updates resources
• Assuming destroy must run before apply

4. You ran terraform destroy but it failed with an error about a locked state file. What should you do to fix this?

medium

A. Run terraform init again to reset the state.

B. Manually delete the state file from your local machine.

C. Use terraform force-unlock with the lock ID to unlock the state.

D. Delete all resources manually in the cloud provider console.

Solution

1. Step 1: Understand state locking in Terraform

   Terraform locks the state file during operations to prevent conflicts. If locked, commands like destroy fail. terraform force-unlock with the lock ID safely removes the lock so you can continue.

2. Final Answer:

   Use terraform force-unlock with the lock ID to unlock the state. -> Option C

3. Quick Check:

   Unlock state with force-unlock command [OK]

Hint: Use terraform force-unlock to fix locked state errors [OK]

Common Mistakes:

• Deleting state file manually causing data loss
• Running terraform init which doesn't unlock state
• Manually deleting cloud resources instead of fixing state

5. You want to automate cleanup of your test environment using Terraform. Which approach safely destroys all resources without manual confirmation and logs the output to a file?

hard

A. Run terraform destroy -auto-approve > destroy.log to skip confirmation and save output.

B. Run terraform apply -destroy -auto-approve to destroy and log output automatically.

C. Run terraform destroy --force --log=destroy.log to force destroy and log output.

D. Run terraform delete -auto-approve > destroy.log to delete resources and log output.

Solution

1. Step 1: Identify correct command to destroy without confirmation

   terraform destroy -auto-approve skips confirmation safely. Using shell redirection with > destroy.log saves the command output to a log file.

2. Final Answer:

   Run terraform destroy -auto-approve > destroy.log to skip confirmation and save output. -> Option A

3. Quick Check:

   Destroy + auto-approve + output redirection = Run terraform destroy -auto-approve > destroy.log to skip confirmation and save output. [OK]

Hint: Use -auto-approve and > file to automate and log destroy [OK]

Common Mistakes:

• Using invalid flags like --force or --log
• Confusing apply with destroy for cleanup
• Using terraform delete which is not a valid command