Null values handling in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Handling null values in Terraform variables

Given the following Terraform variable declaration and usage, what will be the value of resource_name after applying the configuration if var.name is null?

Terraform

variable "name" {
  type    = string
  default = null
}

locals {
  resource_name = var.name != null ? var.name : "default-name"
}

A null

B "default-name"

C ""

D Error: variable "name" must not be null

💡 Hint

Check how the ternary operator handles null values in Terraform.

The local variable resource_name uses a conditional expression to check if var.name is not null. If it is null, it assigns "default-name". Since var.name is null, the result is "default-name".

❓ Configuration

intermediate

Null value in Terraform map lookup

What will be the output of the following Terraform expression if var.settings is {} (an empty map)?

Terraform

variable "settings" {
  type = map(string)
  default = {}
}

output "region" {
  value = lookup(var.settings, "region", null)
}

A null

B "region"

C Error: key "region" not found

D ""

💡 Hint

The lookup function returns the default value if the key is missing.

The lookup function returns the value for the key if it exists. If not, it returns the default value provided, which is null here. Since the map is empty, the output is null.

❓ Architecture

advanced

Impact of null values on resource count in Terraform

Consider the following Terraform snippet. What will be the number of aws_instance resources created if var.instance_count is null?

Terraform

variable "instance_count" {
  type    = number
  default = null
}

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

A 1

B 0

C null

D Error: count must be a non-negative integer

💡 Hint

Look at how the count argument handles null values with a conditional expression.

The count argument uses a conditional expression to assign 1 if var.instance_count is null. Since it is null, count becomes 1, so one instance is created.

❓ security

advanced

Null values in sensitive Terraform variables

If a sensitive Terraform variable is set to null, what is the behavior when it is used in a resource attribute expecting a string?

Terraform

variable "db_password" {
  type      = string
  sensitive = true
  default   = null
}

resource "aws_db_instance" "default" {
  password = var.db_password
  # other required attributes
}

A Terraform ignores the password attribute

B Terraform applies with an empty string as password

C Terraform replaces null with a default password automatically

D Terraform throws an error due to null value in a required attribute

💡 Hint

Consider how Terraform treats null values for required resource attributes.

Terraform does not automatically convert null to empty string or default values for required attributes. Passing null to a required string attribute causes an error.

✅ Best Practice

expert

Best practice for handling optional null values in Terraform modules

You are designing a Terraform module with an optional variable that can be null. Which approach below correctly handles the null value to provide a default inside the module without causing errors?

Terraform

variable "environment" {
  type    = string
  default = null
}

locals {
  env = ???
}

A env = var.environment != null ? var.environment : "production"

B env = var.environment || "production"

C env = coalesce(var.environment, "production")

D env = var.environment ?? "production"

💡 Hint

Terraform has a built-in function to handle null and fallback values.

The coalesce function returns the first non-null argument. It is the recommended way to handle optional null variables with defaults in Terraform.

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