Why dynamic blocks reduce repetition in Terraform - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding dynamic blocks in Terraform

Which statement best explains why dynamic blocks in Terraform reduce repetition?

A They allow you to write a single block that can generate multiple nested blocks based on a list or map, avoiding manual copy-pasting.

B They replace all variables with fixed values, so you only write blocks once.

C They automatically create resources without any configuration, so you don't need to write blocks at all.

D They remove the need for any loops or conditions in Terraform configurations.

💡 Hint

Think about how you can generate repeated blocks from data structures instead of copying code.

Dynamic blocks let you loop over collections to create multiple nested blocks from one template, reducing manual repetition and making configurations cleaner.

❓ Configuration

intermediate

Output count of nested blocks generated by dynamic block

Given this Terraform snippet using a dynamic block, how many ingress blocks will be created?

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

  dynamic "ingress" {
    for_each = var.rules
    content {
      from_port   = ingress.value.from_port
      to_port     = ingress.value.to_port
      protocol    = ingress.value.protocol
      cidr_blocks = ingress.value.cidr_blocks
    }
  }
}

Assuming var.rules is a list with 3 elements.

A 3

B 1

C 0

D Depends on the number of security groups

💡 Hint

Dynamic blocks create one nested block per item in the collection.

The dynamic block iterates over var.rules which has 3 elements, so it creates 3 ingress blocks.

❓ Architecture

advanced

Choosing dynamic blocks for modular Terraform design

You are designing a Terraform module to create firewall rules. You want to support any number of rules without repeating code. Which approach best uses dynamic blocks to achieve this?

A Use count on the resource itself to create multiple resources, each with a single rule block hardcoded.

B Manually write one block per rule and require users to copy the module multiple times.

C Use a dynamic block with for_each over a variable list of rules to generate nested rule blocks inside the resource.

D Use a static block with a fixed number of rules and ignore extra rules.

💡 Hint

Think about how to generate multiple nested blocks inside one resource dynamically.

Dynamic blocks with for_each allow the module to generate any number of nested rule blocks based on input, making the module flexible and reusable.

❓ service_behavior

advanced

Effect of dynamic blocks on resource behavior

When using dynamic blocks to create multiple nested blocks in a Terraform resource, what is the effect on the deployed infrastructure?

A Only the first nested block generated by the dynamic block will be applied to the infrastructure.

B The infrastructure will have multiple nested configurations applied as specified by the dynamic block iterations.

C Dynamic blocks only affect Terraform state but do not change the actual infrastructure.

D The resource will fail to deploy because dynamic blocks are not supported by providers.

💡 Hint

Consider how Terraform translates configuration into real infrastructure changes.

Dynamic blocks generate multiple nested blocks in the resource configuration, so the deployed infrastructure reflects all those nested configurations.

❓ security

expert

Security risks of improper dynamic block usage

What is a potential security risk when using dynamic blocks in Terraform to generate firewall rules from user input without validation?

A Dynamic blocks prevent any changes to firewall rules once applied.

B Dynamic blocks automatically encrypt all inputs, so no security risk exists.

C Terraform will reject any dynamic block with user input, preventing risks.

D Unvalidated input could create overly permissive firewall rules, exposing resources to unwanted access.

💡 Hint

Think about what happens if user data controls security settings without checks.

If user input is used directly in dynamic blocks for firewall rules without validation, it can create rules that allow unwanted traffic, risking security breaches.