Null values handling in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to assign a default value if the variable is null.

Terraform

variable "instance_type" {
  type    = string
  default = [1]
}

resource "aws_instance" "example" {
  instance_type = var.instance_type != null ? var.instance_type : "t2.micro"
  ami           = "ami-123456"
}

Drag options to blanks, or click blank then click option'

A"t2.micro"

B"m5.large"

Cnull

D""

Attempts:

3 left

💡 Hint

Common Mistakes

Setting default to an empty string instead of null

Not handling null in the resource block

The variable default is set to null to allow overriding. The resource uses a conditional to assign t2.micro if the variable is null.

2fill in blank

medium

Complete the code to use the coalesce function to handle null values.

Terraform

resource "aws_s3_bucket" "example" {
  bucket = coalesce(var.bucket_name, [1])
  acl    = "private"
}

Drag options to blanks, or click blank then click option'

A"default-bucket"

Bnull

C""

D"public-bucket"

Attempts:

3 left

💡 Hint

Common Mistakes

Using null as fallback which causes errors

Using empty string which is invalid bucket name

The coalesce function returns the first non-null argument. If var.bucket_name is null, it uses "default-bucket".

3fill in blank

hard

Fix the error in the code to correctly handle null values in a list variable.

Terraform

variable "subnets" {
  type    = list(string)
  default = [1]
}

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

Drag options to blanks, or click blank then click option'

A[]

B[""]

C[null]

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Setting default to null instead of empty list

Using list with null element which causes index errors

The default should be an empty list [] so length(var.subnets) returns 0 and count = 0, preventing index access errors. Null causes plan-time errors on length(null).

4fill in blank

hard

Fill both blanks to create a map that excludes null values using the compact function.

Terraform

locals {
  raw_tags = {
    Name        = var.name
    Environment = var.environment
    Owner       = [1]
  }

  filtered_tags = zipmap(keys([2]), compact(values([2])))
}

Drag options to blanks, or click blank then click option'

Avar.owner

Blocal.raw_tags

Cvar.tags

Dvar.owner != null ? var.owner : "unknown"

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the wrong variable to compact

Using a conditional expression inside the map instead of compact

The raw_tags map includes var.owner which may be null. values(local.raw_tags) produces a list, compact removes nulls, and zipmap(keys(local.raw_tags), ...) reconstructs the map without null-value entries.

5fill in blank

hard

Fill all three blanks to safely access nested attributes that may be null using the lookup function.

Terraform

resource "aws_instance" "example" {
  ami           = lookup(var.ami_map, [1], [2])
  instance_type = lookup(var.instance_types, [3], "t2.micro")
}

Drag options to blanks, or click blank then click option'

A"us-east-1"

B"ami-123456"

C"us-west-2"

D"m5.large"

Attempts:

3 left

💡 Hint

Common Mistakes

Using values instead of keys in lookup

Not providing a default value causing errors

The lookup function safely retrieves values from maps. It uses a key and a default if the key is missing or null. Here, "us-east-1" and "us-west-2" are keys, and "ami-123456" is the default AMI.

Practice

1. What does a null value represent in Terraform configuration?

easy

A. A zero number

B. An empty string

C. An absence of a value or an intentional skip

D. A syntax error

Solution

1. Step 1: Understand the meaning of null in Terraform

   In Terraform, null means no value is set or the value is intentionally skipped.

2. Step 2: Differentiate null from other values

   Zero and empty string are actual values, while null means absence of any value.

3. Final Answer:

   An absence of a value or an intentional skip -> Option C

4. Quick Check:

   Null means no value set = B [OK]

Hint: Null means no value, not zero or empty string [OK]

Common Mistakes:

• Confusing null with zero
• Thinking null is an empty string
• Assuming null causes syntax error

2. Which of the following is the correct way to assign a null value to a variable in Terraform?

easy

A. variable "example" { default = null }

B. variable "example" { default = "null" }

C. variable "example" { default = '' }

D. variable "example" { default = 0 }

Solution

1. Step 1: Review Terraform syntax for null assignment

   In Terraform, null is a keyword without quotes to represent no value.

2. Step 2: Identify incorrect options

   variable "example" { default = "null" } uses quotes making it a string, C is empty string, D is zero number.

3. Final Answer:

   variable "example" { default = null } -> Option A

4. Quick Check:

   Null keyword without quotes = A [OK]

Hint: Use null without quotes to assign null value [OK]

Common Mistakes:

• Using "null" as a string instead of null keyword
• Confusing empty string with null
• Assigning zero instead of null

3. Given this Terraform expression:

var.input != null ? var.input : "default_value"

What will be the result if var.input is null?

medium

A. null

B. "default_value"

C. var.input

D. Error: invalid expression

Solution

1. Step 1: Understand the conditional expression

   The expression checks if var.input is not null; if true, returns var.input, else returns "default_value".

2. Step 2: Apply the condition when var.input is null

   Since var.input is null, the condition is false, so the expression returns "default_value".

3. Final Answer:

   "default_value" -> Option B

4. Quick Check:

   Null input returns default = A [OK]

Hint: If input is null, conditional returns default value [OK]

Common Mistakes:

• Assuming null is returned instead of default
• Thinking expression causes error
• Confusing var.input with string "var.input"

4. Identify the error in this Terraform snippet handling null values:

output "example" {
  value = var.optional_value != null ? var.optional_value : null
}

medium

A. The output block must not use variables

B. The conditional operator syntax is incorrect

C. Using null as fallback causes output to be invalid

D. No error; this is valid Terraform code

Solution

1. Step 1: Analyze the conditional expression

   The expression returns var.optional_value if not null, else returns null.

2. Step 2: Understand output block behavior with null

   Terraform outputs can have null values; it is valid and will display as null when using terraform output.

3. Final Answer:

   No error; this is valid Terraform code -> Option D

4. Quick Check:

   Outputs can accept null = D [OK]

Hint: Outputs can safely return null values [OK]

Common Mistakes:

• Believing outputs cannot accept null values
• Misreading the conditional syntax as incorrect
• Thinking variables cannot be used in output blocks

5. You want to create a resource only if a variable enable_feature is not null and true. Which Terraform expression correctly handles null values to achieve this?

hard

A. count = var.enable_feature != null && var.enable_feature == true ? 1 : 0

B. count = var.enable_feature != false ? 1 : 0

C. count = var.enable_feature ? 1 : 0

D. count = var.enable_feature != null ? 1 : 0

Solution

1. Step 1: Understand the requirement

   The resource should be created only if enable_feature is not null and true.

2. Step 2: Evaluate each option

   count = var.enable_feature != null ? 1 : 0: count = var.enable_feature != null ? 1 : 0 creates the resource if not null, regardless of true or false.
   count = var.enable_feature != false ? 1 : 0: count = var.enable_feature != false ? 1 : 0 creates for true and null (null != false).
   count = var.enable_feature ? 1 : 0: count = var.enable_feature ? 1 : 0 errors if null (invalid boolean condition).
   count = var.enable_feature != null && var.enable_feature == true ? 1 : 0: count = var.enable_feature != null && var.enable_feature == true ? 1 : 0 checks both conditions explicitly.

3. Final Answer:

   count = var.enable_feature != null && var.enable_feature == true ? 1 : 0 -> Option A

4. Quick Check:

   Check null and true explicitly = D [OK]

Hint: Check both not null and true explicitly for safe resource creation [OK]

Common Mistakes:

• Ignoring null check causing errors
• Assuming null is false automatically
• Using only one condition without null check