Lifecycle customization in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Effect of lifecycle ignore_changes on resource updates

Given the following Terraform resource configuration, what will happen if the tags attribute is changed outside Terraform and then Terraform applies a change to instance_type?

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
  tags = {
    Environment = "dev"
  }

  lifecycle {
    ignore_changes = [tags]
  }
}

A Terraform will update the instance_type but will NOT revert the external changes to tags.

B Terraform will update the instance_type and revert the tags to the declared values.

C Terraform will ignore all changes and not update instance_type or tags.

D Terraform will fail to apply changes due to conflict in tags.

💡 Hint

Consider what ignore_changes does to attributes changed outside Terraform.

The lifecycle block with ignore_changes on tags tells Terraform to ignore any changes to tags made outside Terraform. Therefore, when instance_type changes, Terraform updates it but leaves tags as they are, not reverting external changes.

❓ Architecture

intermediate

Using lifecycle prevent_destroy to protect critical resources

You have a Terraform-managed database instance that must never be destroyed accidentally. Which lifecycle configuration ensures Terraform will refuse to destroy this resource even if you run terraform destroy or remove it from the configuration?

A lifecycle { create_before_destroy = true }

B lifecycle { ignore_changes = [all] }

C lifecycle { prevent_destroy = true }

D lifecycle { replace_triggered_by = ["aws_security_group.db"] }

💡 Hint

Which lifecycle setting blocks resource destruction?

The prevent_destroy setting in lifecycle blocks Terraform from destroying the resource, causing an error if a destroy is attempted.

❓ service_behavior

advanced

Impact of create_before_destroy on resource replacement

Consider a Terraform resource with the lifecycle block:

lifecycle {
  create_before_destroy = true
}

What is the behavior when a change requires resource replacement?

A Terraform creates the new resource first, then destroys the old one after the new is ready.

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

C Terraform updates the resource in place without replacement.

D Terraform fails with an error because create_before_destroy is incompatible with replacement.

💡 Hint

Think about how create_before_destroy affects resource replacement order.

With create_before_destroy, Terraform creates the replacement resource before destroying the original, minimizing downtime.

❓ security

advanced

Risks of ignoring changes on sensitive attributes

If you configure lifecycle ignore_changes on a sensitive attribute like password in a database resource, what is a potential risk?

A Terraform will expose the password in logs, causing a security leak.

B Terraform will never update the password even if changed in configuration, causing drift and security risk.

C Terraform will delete the resource when password changes.

D Terraform will prompt for password on every apply.

💡 Hint

Consider what ignoring changes means for sensitive data updates.

Ignoring changes on sensitive attributes means Terraform won't apply updates to them, so if the password changes in config, it won't be updated in the real resource, causing drift and potential security issues.

✅ Best Practice

expert

Combining lifecycle blocks for zero-downtime deployment

You want to update an AWS autoscaling group with zero downtime. Which lifecycle configuration combination best supports this goal?

A lifecycle { ignore_changes = [all] }

B lifecycle { prevent_destroy = true; ignore_changes = [launch_configuration] }

C lifecycle { create_before_destroy = true; prevent_destroy = true }

D lifecycle { create_before_destroy = true; ignore_changes = [desired_capacity] }

💡 Hint

Think about how to replace resources safely and avoid scaling interruptions.

create_before_destroy ensures new resources are ready before old ones are removed, and ignoring desired_capacity changes prevents Terraform from resetting scaling during updates, supporting zero downtime.

Practice

1. What does the create_before_destroy lifecycle setting do in Terraform?

easy

A. It ignores changes to specific resource attributes during updates.

B. It prevents the resource from being destroyed under any circumstances.

C. It forces Terraform to destroy the resource before creating a new one.

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

Solution

1. Step 1: Understand the purpose of create_before_destroy

   This setting ensures Terraform creates the replacement resource first.

2. Step 2: Avoid downtime during resource replacement

   By creating the new resource before destroying the old, service interruptions are minimized.

3. Final Answer:

   It creates a new resource before destroying the old one to avoid downtime. -> Option D

4. Quick Check:

   create_before_destroy = create new before delete [OK]

Hint: Remember: create_before_destroy means new first, then old removed [OK]

Common Mistakes:

• Confusing create_before_destroy with prevent_destroy
• Thinking it deletes first then creates
• Assuming it ignores changes

2. Which of the following is the correct syntax to prevent a resource from being destroyed in Terraform?

easy

A. lifecycle { ignore_changes = true }

B. lifecycle { prevent_destroy = true }

C. lifecycle { create_before_destroy = true }

D. lifecycle { destroy_protection = true }

Solution

1. Step 1: Identify the correct lifecycle argument to prevent destruction

   The argument is prevent_destroy set to true.

2. Step 2: Verify syntax correctness

   The syntax is lifecycle { prevent_destroy = true }, which is valid Terraform code.

3. Final Answer:

   lifecycle { prevent_destroy = true } -> Option B

4. Quick Check:

   prevent_destroy = true prevents deletion [OK]

Hint: Use prevent_destroy = true to block resource deletion [OK]

Common Mistakes:

• Using ignore_changes instead of prevent_destroy
• Using a non-existent destroy_protection argument
• Confusing create_before_destroy with prevent_destroy

3. Given this Terraform resource snippet:

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

  lifecycle {
    ignore_changes = ["tags"]
  }
}

What happens if you manually change the tags of this instance outside Terraform and then run terraform apply?

medium

A. Terraform will ignore the tag changes and keep the manual tags as is.

B. Terraform will destroy and recreate the instance to sync tags.

C. Terraform will throw an error due to tag mismatch.

D. Terraform will overwrite the manual tag changes with the configuration tags.

Solution

1. Step 1: Understand the effect of ignore_changes on tags

   The lifecycle setting ignore_changes = ["tags"] tells Terraform to ignore any changes to tags made outside Terraform.

2. Step 2: Predict Terraform behavior on apply

   Terraform will not attempt to update tags, so manual changes remain intact without error or replacement.

3. Final Answer:

   Terraform will ignore the tag changes and keep the manual tags as is. -> Option A

4. Quick Check:

   ignore_changes on tags means manual tag changes stay [OK]

Hint: ignore_changes = ["tags"] means Terraform skips tag updates [OK]

Common Mistakes:

• Assuming Terraform overwrites manual tag changes
• Expecting an error on tag mismatch
• Thinking resource will be recreated

4. You have this Terraform lifecycle block:

lifecycle {
  create_before_destroy = true
  prevent_destroy = true
}

What problem will occur if you try to update this resource that requires replacement?

medium

A. Terraform will create the new resource and destroy the old one successfully.

B. Terraform will ignore prevent_destroy and destroy the resource anyway.

C. Terraform will fail because it cannot destroy the old resource due to prevent_destroy.

D. Terraform will skip the update and keep the old resource unchanged.

Solution

1. Step 1: Analyze interaction of create_before_destroy and prevent_destroy

   create_before_destroy tries to create new resource before deleting old one, but prevent_destroy forbids deletion.

2. Step 2: Understand Terraform behavior on replacement

   Terraform cannot destroy the old resource due to prevent_destroy, so replacement fails.

3. Final Answer:

   Terraform will fail because it cannot destroy the old resource due to prevent_destroy. -> Option C

4. Quick Check:

   prevent_destroy blocks deletion, causing failure with create_before_destroy [OK]

Hint: prevent_destroy blocks deletion, so replacement fails [OK]

Common Mistakes:

• Assuming Terraform ignores prevent_destroy
• Thinking resource updates without replacement
• Believing create_before_destroy overrides prevent_destroy

5. You want to update an AWS S3 bucket's tags without triggering bucket replacement or downtime. Which lifecycle customization should you apply in Terraform to achieve this?

hard

A. Use ignore_changes = ["tags"] to skip tag updates.

B. Use prevent_destroy = true to block bucket deletion.

C. Use create_before_destroy = true to create new bucket first.

D. Use ignore_changes = ["versioning"] to skip versioning changes.

Solution

1. Step 1: Identify the goal to update tags without replacement

   Tags often cause resource updates; ignoring changes to tags avoids replacement.

2. Step 2: Choose lifecycle setting to ignore tag changes

   Setting ignore_changes = ["tags"] tells Terraform not to replace the bucket when tags change.

3. Final Answer:

   Use ignore_changes = ["tags"] to skip tag updates. -> Option A

4. Quick Check:

   ignore_changes on tags prevents replacement on tag updates [OK]

Hint: Ignore tag changes to update tags without replacement [OK]

Common Mistakes:

• Using prevent_destroy which blocks deletion but not replacement
• Using create_before_destroy which affects replacement order
• Ignoring unrelated attributes like versioning