Creation-time vs destruction-time in Terraform - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding creation-time and destruction-time in Terraform

Which statement best describes the difference between creation-time and destruction-time in Terraform?

A Creation-time refers to when resources are provisioned, and destruction-time is when resources are deleted during terraform destroy or resource replacement.

B Creation-time is when Terraform validates the configuration, and destruction-time is when Terraform applies changes.

C Creation-time is when Terraform runs the plan command, and destruction-time is when Terraform runs the apply command.

D Creation-time is when Terraform deletes resources, and destruction-time is when Terraform creates resources.

💡 Hint

Think about the lifecycle of a resource from start to end.

Creation-time is when Terraform provisions resources. Destruction-time happens when resources are removed, either by terraform destroy or when replaced.

❓ service_behavior

intermediate

Behavior of resource replacement in Terraform

When a resource attribute change requires replacement, what happens during Terraform apply?

A Terraform pauses and waits for manual approval before any action.

B Terraform creates the new resource first, then destroys the old resource.

C Terraform updates the resource in place without destruction.

D Terraform destroys the old resource first, then creates the new resource.

💡 Hint

What is the default order of operations for resource replacement in Terraform?

By default, Terraform destroys the old resource first, then creates the new resource. This may cause downtime unless create_before_destroy = true is set in the lifecycle block.

❓ Configuration

advanced

Predicting output of Terraform lifecycle block with create_before_destroy

Given the following Terraform resource snippet, what is the effect during resource replacement?

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

  lifecycle {
    create_before_destroy = true
  }
}

A Terraform destroys the old instance before creating the new one, causing downtime.

B Terraform updates the instance in place without replacement.

C Terraform creates the new instance before destroying the old one, ensuring no downtime.

D Terraform ignores the lifecycle block and uses default behavior.

💡 Hint

Check what create_before_destroy does in the lifecycle block.

The create_before_destroy flag tells Terraform to create the new resource before destroying the old one, preventing downtime.

❓ security

advanced

Security implications of destruction-time in Terraform

Which security risk is most relevant during destruction-time of cloud resources managed by Terraform?

A Destruction-time only affects resource billing, not security.

B Sensitive data might be exposed if resource state files are not securely handled during destruction.

C Terraform prevents any data loss during destruction by default.

D Resources are automatically encrypted during destruction, eliminating all risks.

💡 Hint

Think about what happens to resource data and state files when resources are destroyed.

During destruction, sensitive data may be exposed if state files or logs are not properly secured.

❓ Architecture

expert

Designing zero-downtime infrastructure updates with Terraform

You need to update a critical database server managed by Terraform without downtime. Which approach best uses creation-time and destruction-time concepts to achieve this?

A Use lifecycle create_before_destroy to provision a new database instance before destroying the old one, then switch traffic after creation.

B Destroy the old database instance first, then create the new one to ensure clean state.

C Manually delete the database outside Terraform, then run terraform apply to create a new one.

D Update the database instance in place without replacement, ignoring lifecycle settings.

💡 Hint

Consider how to avoid downtime during resource replacement.

Using create_before_destroy ensures the new database is ready before the old one is removed, enabling zero downtime.

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