Why expressions add logic in Terraform - Challenge Your Understanding

Challenge - 5 Problems

❓ service_behavior

intermediate

How does a Terraform 'count' expression affect resource creation?

Consider a Terraform resource with a count expression. What is the effect of setting count = var.create_resource ? 1 : 0?

Terraform

variable "create_resource" {
  type    = bool
  default = true
}

resource "aws_s3_bucket" "example" {
  count = var.create_resource ? 1 : 0
  bucket = "my-example-bucket"
  acl    = "private"
}

A The resource is always created once, ignoring the <code>count</code> expression.

B The resource is created only if <code>create_resource</code> is true; otherwise, no resource is created.

C Terraform creates multiple resources equal to the boolean value of <code>create_resource</code>.

D The resource is created twice if <code>create_resource</code> is false.

💡 Hint

Think about how count controls the number of resource instances.

The count expression controls how many instances of the resource Terraform creates. Using a conditional expression like var.create_resource ? 1 : 0 means the resource is created only when create_resource is true.

❓ Architecture

intermediate

Using 'for' expressions to create multiple resources dynamically

Given a list of subnet CIDRs, which Terraform expression correctly creates one subnet resource per CIDR?

Terraform

variable "subnet_cidrs" {
  type    = list(string)
  default = ["10.0.1.0/24", "10.0.2.0/24"]
}

resource "aws_subnet" "example" {
  count = length(var.subnet_cidrs)
  vpc_id     = aws_vpc.main.id
  cidr_block = ???
}

A cidr_block = var.subnet_cidrs[-1]

B cidr_block = var.subnet_cidrs[0]

C cidr_block = var.subnet_cidrs[count]

D cidr_block = var.subnet_cidrs[count.index]

💡 Hint

Remember that count.index gives the current resource index.

Using count.index accesses the current index in the list, so each subnet resource gets a unique CIDR block from the list.

❓ security

advanced

Conditional logic in Terraform to restrict security group rules

Which expression correctly adds an ingress rule only if var.enable_ingress is true?

Terraform

variable "enable_ingress" {
  type    = bool
  default = false
}

resource "aws_security_group" "example" {
  name = "example-sg"

  ingress = ???
}

A ingress = [{ from_port = 80, to_port = 80, protocol = "tcp", cidr_blocks = ["0.0.0.0/0"] }]

B ingress = var.enable_ingress or []

C ingress = var.enable_ingress ? [{ from_port = 80, to_port = 80, protocol = "tcp", cidr_blocks = ["0.0.0.0/0"] }] : []

D ingress = var.enable_ingress && [{ from_port = 80, to_port = 80, protocol = "tcp", cidr_blocks = ["0.0.0.0/0"] }]

💡 Hint

Think about how to use a conditional expression to choose between a list and an empty list.

The conditional expression returns the ingress rule list only if enable_ingress is true; otherwise, it returns an empty list, so no ingress rules are added.

❓ Configuration

advanced

Understanding 'lookup' function with conditional expressions

What is the output of this Terraform expression?

Terraform

variable "env" {
  type    = string
  default = "prod"
}

locals {
  config = {
    prod = "production-config"
    dev  = "development-config"
  }

  selected_config = lookup(local.config, var.env, "default-config")
}

A selected_config = "production-config"

B selected_config = "development-config"

C selected_config = "default-config"

D selected_config = null

💡 Hint

Check the value of var.env and the keys in local.config.

The lookup function returns the value for the key matching var.env. Since var.env is "prod", it returns "production-config".

🧠 Conceptual

expert

Why do Terraform expressions add logic to infrastructure as code?

Which statement best explains why Terraform expressions add logic to infrastructure definitions?

A They allow dynamic decisions and conditional resource creation based on variables and environment, making infrastructure flexible and reusable.

B They replace the need for any variables or modules in Terraform configurations.

C They automatically fix syntax errors in Terraform code during deployment.

D They prevent any changes to infrastructure once deployed, ensuring immutability.

💡 Hint

Think about how expressions influence resource behavior based on inputs.

Terraform expressions let you write logic that changes what resources are created or how they are configured depending on inputs, making your infrastructure code adaptable and reusable.