Why meta-arguments control resource behavior in Terraform - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the resource count.

Terraform

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
  count         = [1]
}

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

Acount

B1

Ctrue

Dfor_each

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'count' as a value instead of a number.

Confusing 'count' with 'for_each'.

The count meta-argument controls how many instances of the resource are created. Here, setting count = 1 creates one instance.

2fill in blank

medium

Complete the code to use the 'depends_on' meta-argument correctly.

Terraform

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
  depends_on    = [[1]]
}

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

A"sg"

Baws_security_group.sg

C"aws_security_group.sg"

Dsg

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around the resource address.

Using variable names instead of resource addresses.

The depends_on meta-argument requires a list of resource addresses as strings. So, the correct format is ["aws_security_group.sg"].

3fill in blank

hard

Fix the error in the 'lifecycle' meta-argument to prevent resource destruction.

Terraform

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
  lifecycle     = {
    [1] = true
  }
}

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

Aprevent_destroy

Bignore_changes

Ccreate_before_destroy

Dreplace_triggered_by

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create_before_destroy' which controls replacement order, not destruction prevention.

Confusing 'ignore_changes' with destruction protection.

The prevent_destroy lifecycle argument set to true stops Terraform from destroying the resource unless manually overridden.

4fill in blank

hard

Fill both blanks to create multiple resources with unique names using 'for_each'.

Terraform

resource "aws_s3_bucket" "example" {
  for_each = [1]
  bucket   = "my-bucket-$[2]"
  acl      = "private"
}

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

Atoset(["one", "two", "three"])

Beach.key

Ceach.value

D["one", "two", "three"]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a list directly without converting to set for for_each.

Using each.value instead of each.key for naming.

The for_each meta-argument requires a set or map. Using toset([...]) converts the list to a set. The each.key is used to access the current key for naming.

5fill in blank

hard

Fill all three blanks to ignore changes to the 'tags' attribute and create the resource with a count.

Terraform

resource "aws_instance" "example" {
  count     = [1]
  ami       = "ami-123456"
  instance_type = "t2.micro"
  lifecycle = {
    ignore_changes = [[2]]
  }
  tags = {
    Name = "example-instance"
  }
  depends_on = [[3]]
}

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

A2

B"tags"

C"aws_security_group.sg"

D"instance_type"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a number as a string for count.

Not quoting the attribute name in ignore_changes.

Using variable names instead of resource addresses in depends_on.

Setting count = 2 creates two instances. The ignore_changes meta-argument with "tags" tells Terraform to ignore tag changes. The depends_on list must contain resource addresses as strings, here "aws_security_group.sg".