Create_before_destroy lifecycle rule in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the create_before_destroy lifecycle rule do in Terraform?

It tells Terraform to create the new resource before destroying the old one, helping to avoid downtime during updates.

beginner

Why is create_before_destroy useful for resources like load balancers or instances?

Because it ensures the new resource is ready before the old one is removed, preventing service interruptions.

beginner

How do you enable create_before_destroy in a Terraform resource block?

By adding a lifecycle block with create_before_destroy = true inside the resource definition.

intermediate

What happens if create_before_destroy is not set and a resource needs replacement?

Terraform destroys the old resource first, which can cause downtime or service disruption.

intermediate

Can create_before_destroy be used with all Terraform resources?

No, some resources do not support it due to provider or resource limitations.

What is the main benefit of using create_before_destroy in Terraform?

A It creates the new resource before destroying the old one to avoid downtime.

B It destroys the resource immediately without creating a new one.

C It delays resource creation until after destruction.

D It disables resource replacement.

The create_before_destroy rule ensures the new resource is created first, preventing downtime.

Where do you place the create_before_destroy setting in Terraform?

A Inside the <code>output</code> block.

B Inside the <code>provider</code> block.

C Inside the <code>variable</code> block.

D Inside the <code>resource</code> block's <code>lifecycle</code> block.

It must be set inside the lifecycle block within a resource.

What might happen if you don't use create_before_destroy for a critical resource update?

A The old resource is destroyed before the new one is ready, causing downtime.

B Terraform will automatically enable <code>create_before_destroy</code>.

C Terraform will skip the update.

D Terraform will create two resources.

Without create_before_destroy, the old resource is removed first, which can cause downtime.

Is create_before_destroy always supported by all Terraform providers?

A Yes, all providers support it.

B Only for AWS resources.

C No, some providers or resources do not support it.

D Only for Google Cloud resources.

Support depends on the provider and resource capabilities.

Which of these is a correct example of enabling create_before_destroy?

A resource "aws_instance" "example" { create_before_destroy = true }

B resource "aws_instance" "example" { lifecycle { create_before_destroy = true } }

C provider "aws" { create_before_destroy = true }

D variable "create_before_destroy" { default = true }

The create_before_destroy setting must be inside the lifecycle block within the resource.

Explain how the create_before_destroy lifecycle rule helps prevent downtime during resource updates in Terraform.

Think about what happens when replacing a resource without this rule.

Describe where and how to configure the create_before_destroy rule in a Terraform resource.

Look for the lifecycle settings inside the resource.