Type constraints in variables in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding type constraints in Terraform variables

Which Terraform variable declaration correctly restricts the variable to accept only a list of strings?

A variable "names" { type = string }

B variable "names" { type = map(string) }

C variable "names" { type = any }

D variable "names" { type = list(string) }

💡 Hint

Think about the data structure that holds multiple string values in order.

The list(string) type constraint ensures the variable only accepts a list where each item is a string. Other options either expect different data types or allow any type.

❓ Configuration

intermediate

Identifying invalid type constraint in Terraform variable

Which variable declaration will cause a Terraform configuration error due to an invalid type constraint?

A variable "enabled" { type = bool }

B variable "config" { type = map(any) }

C variable "settings" { type = list[object] }

D variable "count" { type = number }

💡 Hint

Check the syntax for declaring a list of objects in Terraform.

The correct syntax for a list of objects is list(object) with parentheses, not square brackets. Option C uses square brackets which is invalid.

❓ Architecture

advanced

Choosing the correct type constraint for complex variable

You want to define a Terraform variable that accepts a map where each key is a string and each value is an object with two attributes: id (string) and enabled (bool). Which type constraint is correct?

A variable "resources" { type = list(object({ id = string, enabled = bool })) }

B variable "resources" { type = map(object({ id = string, enabled = bool })) }

C variable "resources" { type = map(tuple([string, bool])) }

D variable "resources" { type = object({ id = string, enabled = bool }) }

💡 Hint

Think about the data structure: a map with string keys and object values.

Option B correctly defines a map with string keys and object values having the specified attributes. Option B uses a list instead of a map. Option B uses tuple which does not name attributes. Option B defines a single object, not a map.

❓ security

advanced

Preventing insecure input with type constraints

Which Terraform variable type constraint best prevents users from passing sensitive data as a plain string by enforcing a map with specific keys?

A variable "credentials" { type = object({ username = string, password = string }) }

B variable "credentials" { type = any }

C variable "credentials" { type = string }

D variable "credentials" { type = map(string) }

💡 Hint

Consider how to enforce structure and keys for sensitive data.

Using an object type with named attributes enforces that the variable must include both username and password keys as strings, preventing arbitrary or insecure input formats.

❓ service_behavior

expert

Effect of incorrect type constraint on Terraform plan

Given the variable declaration variable "ports" { type = list(number) }, what will happen if the user provides ["80", "443"] as input during terraform plan?

A Terraform plan will fail with a type mismatch error because strings are provided instead of numbers.

B Terraform plan will succeed and convert strings to numbers automatically.

C Terraform plan will ignore the variable and use default values.

D Terraform plan will succeed but treat the ports as strings.

💡 Hint

Think about how Terraform enforces variable types strictly during planning.

Terraform enforces type constraints strictly. Providing strings where numbers are expected causes a type mismatch error during plan, preventing deployment.

Practice

1. What is the main purpose of using type constraints in Terraform variables?

easy

A. To assign default values to variables

B. To make variables optional

C. To encrypt variable values

D. To ensure variables only accept specific kinds of data

Solution

1. Step 1: Understand variable type constraints

   Type constraints limit what kind of data a variable can accept, like strings or lists.

2. Step 2: Identify the purpose

   This helps catch errors early by preventing wrong data types from being used.

3. Final Answer:

   To ensure variables only accept specific kinds of data -> Option D

4. Quick Check:

   Type constraints = restrict data type [OK]

Hint: Type constraints restrict variable data types [OK]

Common Mistakes:

• Confusing type constraints with default values
• Thinking type constraints make variables optional
• Assuming type constraints encrypt data

2. Which of the following is the correct syntax to declare a variable with a list of strings type constraint in Terraform?

easy

A. variable "names" { type = list(string) }

B. variable "names" { type = "list of strings" }

C. variable "names" { type = [string] }

D. variable "names" { type = string[] }

Solution

1. Step 1: Recall Terraform type syntax

   Terraform uses list(string) to specify a list of strings as a type.

2. Step 2: Compare options

   variable "names" { type = list(string) } uses the correct syntax. Others use invalid or unsupported formats.

3. Final Answer:

   variable "names" { type = list(string) } -> Option A

4. Quick Check:

   List of strings = list(string) [OK]

Hint: Use list(string) for list of strings type [OK]

Common Mistakes:

• Using quotes around type names incorrectly
• Using array syntax like string[] which is invalid in Terraform
• Writing type as a plain string description

3. Given this variable declaration:

variable "ports" {
  type = set(number)
  default = [80, 443, 8080]
}

What will be the type and value of var.ports when accessed in Terraform?

medium

A. A list of numbers: [80, 443, 8080]

B. A set of numbers: {80, 443, 8080}

C. A map with keys 80, 443, 8080

D. A string containing "80,443,8080"

Solution

1. Step 1: Understand the declared type

   The variable type is set(number), which means a set of unique numbers.

2. Step 2: Check the default value

   The default is a list, but Terraform converts it to a set because of the type constraint.

3. Final Answer:

   A set of numbers: {80, 443, 8080} -> Option B

4. Quick Check:

   Type set(number) = set of numbers [OK]

Hint: set(number) converts list to unique number set [OK]

Common Mistakes:

• Confusing set with list type
• Expecting a map instead of a set
• Thinking default list stays a list despite type

4. Identify the error in this variable declaration:

variable "config" {
  type = map(string)
  default = ["a", "b", "c"]
}

medium

A. Default values must be numbers

B. Type map(string) is invalid syntax

C. Default value is a list, but type expects a map

D. Variable name cannot be "config"

Solution

1. Step 1: Analyze the type constraint

   The type map(string) expects a map with string values, like { key = "value" }.

2. Step 2: Check the default value

   The default is a list, which does not match the map type.

3. Final Answer:

   Default value is a list, but type expects a map -> Option C

4. Quick Check:

   Type map(string) needs map, not list [OK]

Hint: Match default value type to variable type [OK]

Common Mistakes:

• Using list as default for map type
• Thinking map(string) is invalid syntax
• Believing variable names are restricted

5. You want a variable that accepts either a string or a list of strings. Which type constraint correctly allows this in Terraform?

hard

A. type = string | list(string)

B. type = any

C. type = object({ string_or_list = string })

D. type = string, list(string)

Solution

1. Step 1: Understand union types in Terraform

   Terraform supports union types using the pipe symbol | to allow multiple types.

2. Step 2: Identify correct syntax

   type = string | list(string) uses string | list(string), which means the variable can be either a string or a list of strings.

3. Step 3: Check other options

   type = any allows any type, which is too broad. type = object({ string_or_list = string }) defines an object, not a union. type = string, list(string) is invalid syntax.

4. Final Answer:

   type = string | list(string) -> Option A

5. Quick Check:

   Union type uses | to combine types [OK]

Hint: Use | to combine types for union constraints [OK]

Common Mistakes:

• Using commas instead of | for union types
• Choosing any type instead of specific union
• Confusing object type with union type