Nested dynamic blocks in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Output of nested dynamic blocks in Terraform

Given the following Terraform configuration snippet using nested dynamic blocks, what will be the value of the resource's tags attribute after deployment?

Terraform

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

  dynamic "tags" {
    for_each = { env = "prod", team = "devops" }
    content {
      key   = tags.key
      value = tags.value

      dynamic "subtag" {
        for_each = { owner = "alice", project = "cloud" }
        content {
          key   = subtag.key
          value = subtag.value
        }
      }
    }
  }
}

A {"env": "prod", "team": "devops", "owner": "alice", "project": "cloud"}

B SyntaxError: Invalid nested dynamic block usage

C {"env": "prod", "team": "devops"}

D {"tags": [{"key": "env", "value": "prod", "subtag": [{"key": "owner", "value": "alice"}, {"key": "project", "value": "cloud"}]}, {"key": "team", "value": "devops", "subtag": [{"key": "owner", "value": "alice"}, {"key": "project", "value": "cloud"}]}]}

💡 Hint

Remember that nested dynamic blocks create nested lists or maps in the resource attributes.

The outer dynamic block iterates over two tags, each producing a map with key and value. The inner dynamic block adds a list of subtag maps inside each tag. This results in a list of tag objects, each containing a list of subtag objects.

❓ service_behavior

intermediate

Behavior of nested dynamic blocks with empty inner for_each

In Terraform, if the inner nested dynamic block's for_each is an empty map, what will be the effect on the resource attribute generated by the nested dynamic blocks?

Terraform

resource "aws_security_group" "example" {
  name = "example"

  dynamic "ingress" {
    for_each = { http = 80, https = 443 }
    content {
      from_port   = ingress.value
      to_port     = ingress.value
      protocol    = "tcp"

      dynamic "cidr_blocks" {
        for_each = {}
        content {
          cidr_block = cidr_blocks.value
        }
      }
    }
  }
}

A The ingress blocks will have empty cidr_blocks attributes (empty lists).

B Terraform will raise a runtime error due to empty inner for_each.

C The ingress blocks will not include the cidr_blocks attribute at all.

D Terraform will ignore the entire ingress block because inner for_each is empty.

💡 Hint

Empty for_each in a dynamic block results in no blocks generated for that level.

When the inner dynamic block's for_each is empty, no cidr_blocks blocks are created inside each ingress block. The ingress blocks still exist but without cidr_blocks attribute.

❓ Architecture

advanced

Designing nested dynamic blocks for multi-tier infrastructure

You want to use Terraform nested dynamic blocks to define a multi-tier AWS security group where each tier has multiple ingress rules and each ingress rule can have multiple CIDR blocks. Which structure best represents this nested dynamic block usage?

A One dynamic block for tiers, inside it a dynamic block for ingress rules, inside that a dynamic block for CIDR blocks.

B One dynamic block for ingress rules, inside it a dynamic block for tiers, inside that a dynamic block for CIDR blocks.

C Separate static blocks for tiers, ingress rules, and CIDR blocks without dynamic blocks.

D One dynamic block for CIDR blocks, inside it a dynamic block for ingress rules, inside that a dynamic block for tiers.

💡 Hint

Think about the hierarchy: tiers contain ingress rules, which contain CIDR blocks.

The correct nesting order is tiers > ingress rules > CIDR blocks, so nested dynamic blocks should follow this order to represent the hierarchy properly.

❓ security

advanced

Security implications of nested dynamic blocks in Terraform

What is a potential security risk when using nested dynamic blocks to generate AWS IAM policies dynamically from user input variables?

A Unintended broad permissions if user input is not validated, leading to privilege escalation.

B Terraform will block any dynamic block that uses user input variables for security reasons.

C Nested dynamic blocks cause IAM policies to be ignored by AWS, reducing security.

D There is no security risk because Terraform validates all IAM policy content automatically.

💡 Hint

Consider what happens if user input is not controlled or sanitized.

If user input variables are used directly in nested dynamic blocks to build IAM policies, malicious or incorrect input can create overly permissive policies, risking privilege escalation.

✅ Best Practice

expert

Optimizing nested dynamic blocks for maintainability and performance

Which practice is best to optimize Terraform configurations that use deeply nested dynamic blocks to manage complex resources?

A Write all nested dynamic blocks inline in a single resource block for clarity.

B Break down nested dynamic blocks into reusable modules and use locals to simplify expressions.

C Avoid using dynamic blocks altogether and write static blocks for every possible combination.

D Use nested dynamic blocks with complex for_each expressions directly referencing remote state outputs.

💡 Hint

Think about code reuse and readability in large Terraform projects.

Breaking complex nested dynamic blocks into smaller reusable modules and using locals to simplify expressions improves maintainability and reduces errors.