Creation-time vs destruction-time in Terraform - When to Use Which

The Big Idea

What if your cloud resources could build themselves up and clean themselves away without you lifting a finger?

The Scenario

Imagine you are setting up a new cloud server by manually clicking buttons to create it, and later you have to remember to delete it by clicking again when it's no longer needed.

The Problem

This manual way is slow and easy to forget. You might leave unused servers running, wasting money, or accidentally delete the wrong one because you lost track of what was created.

The Solution

Using creation-time vs destruction-time in Terraform means you define what happens when resources are made and what happens when they are removed, all in one place. Terraform handles these steps automatically and safely.

Before vs After

✗ Before

Click 'Create Server' in cloud console
Remember to click 'Delete Server' later

✓ After

resource "aws_instance" "example" {
  # creation-time setup
}

# destruction-time handled automatically by Terraform

What It Enables

This lets you manage cloud resources reliably and automatically, avoiding mistakes and saving time.

Real Life Example

When launching a website, Terraform creates the servers and databases at creation-time, and when you no longer need the site, it safely removes all resources at destruction-time without extra clicks.

Key Takeaways

Manual cloud setup is slow and error-prone.

Creation-time vs destruction-time automates setup and cleanup.

Terraform manages resource lifecycle safely and efficiently.

Practice

1. What does creation-time mean in Terraform?

easy

A. The moment when resources are first set up or created

B. The moment when resources are deleted or removed

C. The time when Terraform runs a plan without changes

D. The time when Terraform refreshes the state

Solution

1. Step 1: Understand creation-time meaning

   Creation-time refers to when Terraform sets up resources for the first time.

2. Step 2: Differentiate from destruction-time

   Destruction-time is when resources are removed, not created.

3. Final Answer:

   The moment when resources are first set up or created -> Option A

4. Quick Check:

   Creation-time = resource setup [OK]

Hint: Creation-time means resource setup, destruction-time means removal [OK]

Common Mistakes:

• Confusing creation-time with destruction-time
• Thinking creation-time is when resources are deleted
• Mixing creation-time with Terraform plan execution

2. Which Terraform lifecycle argument controls actions at destruction-time?

easy

A. create_before_destroy

B. depends_on

C. ignore_changes

D. prevent_destroy

Solution

1. Step 1: Identify destruction-time control arguments

   The prevent_destroy argument stops Terraform from deleting a resource.

2. Step 2: Compare other lifecycle arguments

   create_before_destroy affects creation and replacement order, not destruction prevention.

3. Final Answer:

   prevent_destroy -> Option D

4. Quick Check:

   Destruction-time control = prevent_destroy [OK]

Hint: Use prevent_destroy to block resource deletion at destruction-time [OK]

Common Mistakes:

• Choosing create_before_destroy which affects creation order
• Confusing ignore_changes with destruction control
• Using depends_on which manages resource dependencies

3. Given this Terraform snippet:

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"

  lifecycle {
    create_before_destroy = true
  }
}

What happens when you change instance_type from t2.micro to t2.small?

medium

A. Terraform destroys the old instance first, then creates the new one

B. Terraform updates the instance in place without destruction

C. Terraform creates the new instance first, then destroys the old one

D. Terraform throws an error due to lifecycle conflict

Solution

1. Step 1: Understand create_before_destroy effect

   This setting makes Terraform create the new resource before destroying the old one.

2. Step 2: Apply to instance_type change

   Changing instance_type forces replacement, so new instance is created first, then old destroyed.

3. Final Answer:

   Terraform creates the new instance first, then destroys the old one -> Option C

4. Quick Check:

   create_before_destroy = new before old [OK]

Hint: create_before_destroy means new resource before old is removed [OK]

Common Mistakes:

• Assuming in-place update without replacement
• Thinking old resource is destroyed before new is created
• Believing lifecycle causes errors on changes

4. You added prevent_destroy = true to a resource but Terraform still deletes it on terraform destroy. What is the likely cause?

medium

A. You ran terraform destroy which ignores prevent_destroy

B. The prevent_destroy argument is misspelled or misplaced

C. The resource is referenced by another resource with depends_on

D. Terraform does not support prevent_destroy for that resource type

Solution

1. Step 1: Check prevent_destroy usage

   It must be inside the lifecycle block and spelled correctly.

2. Step 2: Understand terraform destroy behavior

   terraform destroy respects prevent_destroy and will error if deletion is blocked.

3. Final Answer:

   The prevent_destroy argument is misspelled or misplaced -> Option B

4. Quick Check:

   Misplaced prevent_destroy causes deletion despite protection [OK]

Hint: Ensure prevent_destroy is inside lifecycle block and spelled right [OK]

Common Mistakes:

• Assuming terraform destroy ignores prevent_destroy
• Placing prevent_destroy outside lifecycle block
• Thinking depends_on affects prevent_destroy behavior

5. You want to replace a resource safely without downtime. Which lifecycle settings should you use to ensure the new resource is created before the old one is destroyed, and prevent accidental deletion?

hard

A. Set create_before_destroy = true and prevent_destroy = true

B. Set create_before_destroy = false and prevent_destroy = true

C. Set create_before_destroy = true and ignore_changes = [all]

D. Set prevent_destroy = false and ignore_changes = [all]

Solution

1. Step 1: Use create_before_destroy for safe replacement

   This ensures the new resource is ready before the old one is removed, avoiding downtime.

2. Step 2: Use prevent_destroy to block accidental deletion

   This stops Terraform from deleting the resource unless explicitly allowed, adding safety.

3. Final Answer:

   Set create_before_destroy = true and prevent_destroy = true -> Option A

4. Quick Check:

   Safe replacement = create_before_destroy + prevent_destroy [OK]

Hint: Combine create_before_destroy and prevent_destroy for safe updates [OK]

Common Mistakes:

• Setting prevent_destroy without create_before_destroy causes downtime
• Using ignore_changes to avoid destruction which doesn't prevent deletion
• Disabling prevent_destroy risks accidental resource loss