Prevent_destroy lifecycle rule in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the prevent_destroy lifecycle rule do in Terraform?

It stops Terraform from deleting a resource, even if you run terraform destroy or remove the resource from your configuration. This protects important resources from accidental deletion.

beginner

How do you enable the prevent_destroy rule in a Terraform resource?

Inside the resource block, add a lifecycle block with prevent_destroy = true. For example:

resource "aws_s3_bucket" "example" {
  lifecycle {
    prevent_destroy = true
  }
}

intermediate

Why is using prevent_destroy considered a best practice for critical resources?

Because it acts like a safety lock, preventing accidental deletion of resources that could cause downtime or data loss if removed unintentionally.

beginner

What happens if you try to delete a resource with prevent_destroy enabled?

Terraform will show an error and stop the deletion process. You must first remove or disable prevent_destroy to delete the resource.

intermediate

Can prevent_destroy protect resources from manual deletion outside Terraform?

No. It only protects resources managed by Terraform during Terraform operations. Manual deletion outside Terraform is not prevented by this rule.

What is the purpose of the prevent_destroy lifecycle rule in Terraform?

A To automatically recreate a resource if deleted

B To allow manual deletion of a resource

C To prevent Terraform from creating a resource

D To prevent a resource from being deleted by Terraform

The prevent_destroy rule stops Terraform from deleting a resource during destroy or update operations.

How do you enable prevent_destroy for a resource?

A Use <code>terraform protect</code> command

B Set <code>destroy_protection = true</code> at the provider level

C Add <code>prevent_destroy = true</code> inside a <code>lifecycle</code> block

D Add <code>prevent_delete = true</code> in the resource block

You enable it by adding prevent_destroy = true inside the resource's lifecycle block.

What happens if you try to delete a resource with prevent_destroy enabled?

A Terraform shows an error and stops deletion

B Terraform deletes it anyway

C Terraform ignores the resource

D Terraform recreates the resource automatically

Terraform will stop and show an error to prevent accidental deletion.

Does prevent_destroy protect resources from manual deletion outside Terraform?

A Yes, it blocks manual deletion

B No, it only protects Terraform operations

C Yes, but only for AWS resources

D No, it only protects during creation

It only prevents deletion during Terraform runs, not manual deletion outside Terraform.

Which of these is a good use case for prevent_destroy?

A Protecting a database instance from accidental deletion

B Automatically scaling resources

C Allowing quick resource replacement

D Ignoring resource changes

Critical resources like databases should be protected from accidental deletion using prevent_destroy.

Explain how the prevent_destroy lifecycle rule works in Terraform and why it is useful.

Think about how to keep important things safe from being removed by mistake.

Describe a scenario where using prevent_destroy would be important and how you would configure it.

Consider resources that hold valuable data or services.

Practice

1. What does the prevent_destroy lifecycle rule do in Terraform?

easy

A. Stops accidental deletion of a resource

B. Automatically recreates a resource if deleted

C. Prevents updates to a resource

D. Locks the resource to prevent any changes

Solution

1. Step 1: Understand the purpose of prevent_destroy

   The prevent_destroy rule is designed to stop Terraform from deleting a resource accidentally.

2. Step 2: Compare with other lifecycle rules

   Unlike update prevention or locking, it specifically blocks deletion unless the rule is removed.

3. Final Answer:

   Stops accidental deletion of a resource -> Option A

4. Quick Check:

   prevent_destroy stops deletion = A [OK]

Hint: Remember: prevent_destroy means no accidental deletes [OK]

Common Mistakes:

• Thinking it prevents updates instead of deletion
• Confusing it with resource locking
• Assuming it recreates deleted resources automatically

2. Which is the correct way to set the prevent_destroy rule in a Terraform resource?

easy

A. resource { prevent_destroy = true }

B. prevent_destroy = true

C. lifecycle { prevent_destroy = true }

D. lifecycle { prevent_delete = true }

Solution

1. Step 1: Identify correct syntax for lifecycle block

   The prevent_destroy must be inside a lifecycle block within the resource.

2. Step 2: Check option correctness

   lifecycle { prevent_destroy = true } correctly places prevent_destroy = true inside lifecycle { }. Others are either missing the block or have wrong keywords.

3. Final Answer:

   lifecycle { prevent_destroy = true } -> Option C

4. Quick Check:

   Correct lifecycle syntax = C [OK]

Hint: Always put prevent_destroy inside lifecycle block [OK]

Common Mistakes:

• Placing prevent_destroy outside lifecycle block
• Using wrong keyword like prevent_delete
• Adding prevent_destroy directly under resource

3. Given this Terraform resource snippet, what happens if you run terraform destroy?

resource "aws_s3_bucket" "example" {
  bucket = "my-bucket"
  lifecycle {
    prevent_destroy = true
  }
}

medium

A. Terraform will show an error and stop the destroy

B. Terraform will delete the S3 bucket without error

C. Terraform will ignore prevent_destroy and delete anyway

D. Terraform will update the bucket instead of deleting

Solution

1. Step 1: Understand prevent_destroy effect on destroy

   The prevent_destroy = true stops Terraform from deleting the resource during destroy.

2. Step 2: Predict Terraform behavior on destroy

   Terraform will detect the rule and raise an error, preventing the deletion.

3. Final Answer:

   Terraform will show an error and stop the destroy -> Option A

4. Quick Check:

   prevent_destroy blocks destroy = A [OK]

Hint: prevent_destroy causes destroy to error, not delete [OK]

Common Mistakes:

• Assuming resource deletes anyway
• Thinking it updates instead of blocking destroy
• Believing Terraform silently ignores the rule

4. You added prevent_destroy = true to a resource but now need to delete it. What is the correct way to fix the error during terraform destroy?

medium

A. Run terraform destroy with --force flag

B. Remove or comment out the prevent_destroy line and apply again

C. prevent_destroy = false

D. Delete the resource manually from the cloud console

Solution

1. Step 1: Understand how prevent_destroy blocks deletion

   The rule must be removed or disabled in Terraform code before deletion can proceed.

2. Step 2: Identify correct fix

   Removing or commenting out the line and applying changes allows Terraform to delete the resource safely.

3. Final Answer:

   Remove or comment out the prevent_destroy line and apply again -> Option B

4. Quick Check:

   Disable prevent_destroy before destroy = B [OK]

Hint: Disable prevent_destroy in code before deleting resource [OK]

Common Mistakes:

• Using unsupported --force flag
• Setting prevent_destroy directly under resource
• Deleting resource manually without Terraform sync

5. You have a Terraform resource with prevent_destroy = true. You want to replace this resource safely without downtime. Which approach is best?

hard

A. Temporarily remove prevent_destroy, apply destroy, then recreate resource

B. Manually delete resource in cloud console, then run terraform apply

C. Use terraform taint to mark resource for replacement without removing prevent_destroy

D. Set prevent_destroy to false and run terraform apply to replace resource

Solution

1. Step 1: Understand prevent_destroy blocks deletion

   Removing prevent_destroy allows deletion but risks downtime; manual deletion is unsafe.

2. Step 2: Disable prevent_destroy for safe replacement

   Setting prevent_destroy = false inside the lifecycle block disables the deletion block. Then terraform apply can replace the resource if config changes require recreation.

3. Step 3: Apply changes safely

   This triggers replacement using Terraform's logic (e.g., with create_before_destroy if set), avoiding manual steps.

4. Final Answer:

   Set prevent_destroy to false and run terraform apply to replace resource -> Option D

5. Quick Check:

   Set prevent_destroy = false allows replacement = C [OK]

Hint: Set prevent_destroy = false before terraform apply to replace [OK]

Common Mistakes:

• Using `terraform taint` without disabling prevent_destroy
• Manually deleting resource causing drift
• Running destroy separately, risking downtime