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

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a resource that creates an AWS S3 bucket.

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = "[1]"
  acl    = "private"
}

Drag options to blanks, or click blank then click option'

Abucket_name

Baws_s3_bucket

Cmy-unique-bucket-123

Dprivate

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource type name instead of bucket name

Using ACL value in bucket name field

The bucket attribute requires the unique name of the S3 bucket to create at creation-time.

2fill in blank

medium

Complete the code to add a lifecycle rule that prevents deletion of the S3 bucket during destruction-time.

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-unique-bucket-123"
  acl    = "private"

  lifecycle {
    [1] = true
  }
}

Drag options to blanks, or click blank then click option'

Aprevent_destroy

Bcreate_before_destroy

Cignore_changes

Dreplace_triggered_by

Attempts:

3 left

💡 Hint

Common Mistakes

Using lifecycle arguments unrelated to destruction protection

Setting the wrong lifecycle argument name

The prevent_destroy lifecycle argument tells Terraform to block destruction of the resource, protecting it during destruction-time.

3fill in blank

hard

Fix the error in the code that tries to reference a resource attribute at destruction-time, which is not allowed.

Terraform

output "bucket_name" {
  value = aws_s3_bucket.my_bucket.[1]
}

Drag options to blanks, or click blank then click option'

Atags

Barn

Cid

Dbucket

Attempts:

3 left

💡 Hint

Common Mistakes

Referencing attributes that only exist after creation

Using resource IDs that may be null during destruction

The bucket attribute is the bucket name known at creation-time and can be safely referenced. Other attributes like id or arn may not be available during destruction-time.

4fill in blank

hard

Fill both blanks to create a resource with a creation-time computed attribute and a destruction-time lifecycle rule.

Terraform

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

  [1] = true

  lifecycle {
    [2] = true
  }
}

Drag options to blanks, or click blank then click option'

Aassociate_public_ip_address

Bprevent_destroy

Cdisable_api_termination

Dcreate_before_destroy

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing lifecycle arguments with resource arguments

Using wrong lifecycle argument names

disable_api_termination is a creation-time attribute that prevents instance termination via API. prevent_destroy is a lifecycle rule that prevents Terraform from destroying the resource.

5fill in blank

hard

Fill all three blanks to define an output that depends on a creation-time attribute, uses a destruction-time lifecycle ignore change, and references the correct attribute.

Terraform

resource "aws_security_group" "sg" {
  name        = "example-sg"
  description = "Example security group"

  lifecycle {
    [1] = ["ingress"]
  }
}

output "sg_id" {
  value = aws_security_group.sg.[2]
  description = "Security group ID"
  depends_on = [aws_security_group.sg]
  [3] = true
}

Drag options to blanks, or click blank then click option'

Aignore_changes

Bid

Csensitive

Dprevent_destroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using prevent_destroy in output block

Referencing attributes not available at creation-time

Not marking sensitive outputs when needed

ignore_changes lifecycle argument tells Terraform to ignore changes to ingress rules during destruction-time. The output references the id attribute, which is known at creation-time. The output is marked sensitive to hide its value in logs.