Count vs for_each decision in Terraform - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Choosing between count and for_each for resource creation

You want to create multiple identical virtual machines in Terraform. You have a list of VM names. Which approach is best to create one resource per VM name?

A Use for_each with a map of VM names as keys to create one resource per name.

B Use for_each with the VM names list converted to a set to create one resource per name.

C Use count with a fixed number and hardcode VM names inside the resource.

D Use count with the length of the VM names list and index into the list inside the resource.

💡 Hint

Think about how Terraform uniquely identifies each resource instance.

Using for_each with a map of VM names as keys allows Terraform to track each resource by its key, making management easier and more stable. Count uses numeric indexes which can cause issues if the list changes.

❓ Configuration

intermediate

Terraform resource creation with count and for_each

Given the following Terraform snippet, what will be the number of resources created?

variable "servers" {
  default = ["app1", "app2", "app3"]
}

resource "aws_instance" "example" {
  count = length(var.servers)
  ami           = "ami-123456"
  instance_type = "t2.micro"
  tags = {
    Name = var.servers[count.index]
  }
}

A An error occurs due to invalid count usage.

B 3 resources, one for each server name in the list.

C 0 resources, because the variable is not referenced correctly.

D 1 resource, because count is not supported with lists.

💡 Hint

Count creates multiple instances based on the number provided.

Count uses the length of the servers list (3), so Terraform creates 3 aws_instance resources, each tagged with the corresponding server name.

❓ Architecture

advanced

Handling resource updates with count vs for_each

You have a Terraform configuration using count to create resources from a list. You remove one item from the list and apply changes. What happens to the resources?

A Terraform keeps all resources unchanged.

B Terraform destroys the resource corresponding to the removed item by matching its index.

C Terraform throws an error because count cannot handle list changes.

D Terraform destroys the last resource in the list regardless of which item was removed.

💡 Hint

Think about how count indexes resources and what happens when list length changes.

Count uses numeric indexes. Removing an item shifts indexes, so Terraform destroys the resource at the end of the list, which may not correspond to the removed item, causing unintended destruction.

❓ security

advanced

Security implications of using for_each with sensitive data

You use for_each to create multiple resources with sensitive variables as keys. What is a potential security risk?

A Terraform automatically encrypts all sensitive data in state files, so no risk exists.

B Using for_each disables sensitive variable masking in logs.

C Sensitive data may appear in Terraform state files as keys, exposing secrets.

D There is no difference in security between count and for_each.

💡 Hint

Consider how Terraform stores resource identifiers in state files.

When sensitive data is used as keys in for_each, those keys appear in plaintext in the state file, potentially exposing secrets. It's best to avoid using sensitive data as keys.

❓ service_behavior

expert

Impact on resource lifecycle when switching from count to for_each

You have a Terraform module using count to create resources. You switch to for_each with a map of resource names. After applying, what is the expected behavior regarding resource replacement?

A Terraform will replace all resources because the resource keys changed from indexes to names.

B Terraform will keep all resources unchanged because count and for_each are interchangeable.

C Terraform will throw an error due to incompatible resource identifiers.

D Terraform will only replace resources whose keys differ between count and for_each.

💡 Hint

Think about how Terraform tracks resources by keys and indexes.

Switching from count (numeric indexes) to for_each (named keys) changes resource identifiers, so Terraform treats them as new resources and replaces all existing ones.