Meta-arguments overview in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of Terraform meta-arguments

Which of the following best describes the purpose of Terraform meta-arguments?

A They control how Terraform manages resource creation, updates, and dependencies.

B They define the cloud provider credentials and authentication methods.

C They specify the exact hardware specifications for virtual machines.

D They are used to write conditional expressions inside resource blocks.

💡 Hint

Think about arguments that affect resource lifecycle and dependencies.

Terraform meta-arguments like depends_on, count, and lifecycle control resource management behavior, not credentials or hardware specs.

❓ Configuration

intermediate

Effect of count meta-argument on resource instances

Given the following Terraform resource snippet, how many instances of aws_instance will be created?

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

A 3 instances

B 0 instances

C 1 instance

D Depends on the number of availability zones

💡 Hint

The count meta-argument controls how many copies of the resource are created.

Setting count = 3 creates exactly 3 instances of the resource.

❓ Architecture

advanced

Using depends_on to control resource creation order

Consider two resources: aws_vpc.main and aws_subnet.subnet1. You want to ensure the subnet is created only after the VPC is fully created. Which meta-argument usage achieves this?

A Add <code>depends_on = [aws_subnet.subnet1]</code> inside <code>aws_vpc.main</code> resource block.

B Use <code>count = 0</code> in <code>aws_subnet.subnet1</code> until VPC is created.

C No need to specify; Terraform automatically orders resources alphabetically.

D Add <code>depends_on = [aws_vpc.main]</code> inside <code>aws_subnet.subnet1</code> resource block.

💡 Hint

Think about which resource depends on the other.

Using depends_on in the subnet resource pointing to the VPC ensures the subnet waits for the VPC creation.

❓ security

advanced

Impact of lifecycle meta-argument on resource deletion

What is the effect of setting lifecycle { prevent_destroy = true } in a Terraform resource block?

A Terraform will delete the resource immediately without confirmation.

B Terraform will refuse to delete the resource, preventing accidental destruction.

C Terraform will ignore changes to the resource's attributes during updates.

D Terraform will automatically recreate the resource if deleted outside Terraform.

💡 Hint

Consider what 'prevent_destroy' implies about resource safety.

Setting prevent_destroy = true stops Terraform from deleting the resource, protecting it from accidental removal.

❓ service_behavior

expert

Behavior of for_each meta-argument with map input

Given this Terraform resource snippet, what will be the keys of the created resources?

resource "aws_s3_bucket" "buckets" {
  for_each = {
    alpha = "us-east-1"
    beta  = "us-west-2"
  }
  bucket = "my-bucket-${each.key}"
  region = each.value
}

A No resources will be created due to syntax error

B [0, 1]

C ["alpha", "beta"]

D ["us-east-1", "us-west-2"]

💡 Hint

Recall how for_each uses map keys as resource instance keys.

When using a map with for_each, Terraform creates one resource per key, using the keys as instance identifiers.