Why complex types matter in Terraform - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a variable with a complex type list of strings.

Terraform

variable "example_list" {
  type = [1]
}

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

Alist(string)

Bmap(string)

Cstring

Dnumber

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'string' instead of 'list(string)' for a list variable.

Using 'map(string)' which expects key-value pairs, not a list.

The variable type list(string) defines a list where each item is a string. This is a common complex type in Terraform.

2fill in blank

medium

Complete the code to define a variable with a map of numbers.

Terraform

variable "example_map" {
  type = [1]
}

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

Astring

Blist(number)

Cmap(number)

Dnumber

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'list(number)' which is a list, not a map.

Using 'number' which is a single number, not a map.

The type map(number) defines a map where each key maps to a number value.

3fill in blank

hard

Fix the error in the variable type definition for a set of strings.

Terraform

variable "example_set" {
  type = [1]
}

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

Aset(string)

Blist(string)

Cmap(string)

Dstring

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'list(string)' which allows duplicates and is ordered.

Using 'map(string)' which expects key-value pairs.

The correct type for a set of strings is set(string). It represents an unordered collection of unique strings.

4fill in blank

hard

Fill both blanks to define an object type with two attributes: name (string) and count (number).

Terraform

variable "example_object" {
  type = object({
    name = [1],
    count = [2]
  })
}

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

Astring

Bnumber

Cbool

Dlist(string)

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bool' or 'list(string)' for these attributes incorrectly.

Mixing up attribute types.

The object type requires attribute types. Here, name is a string and count is a number.

5fill in blank

hard

Fill all three blanks to define a complex variable: a list of objects with attributes id (number), enabled (bool), and tags (list of strings).

Terraform

variable "complex_var" {
  type = list(object({
    id = [1],
    enabled = [2],
    tags = [3]
  }))
}

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

Astring

Bbool

Clist(string)

Dnumber

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'bool' with 'string' or 'number'.

Using 'string' instead of 'list(string)' for tags.

The object attributes are: id as number, enabled as bool, and tags as list of strings.

Practice

1. Why are complex types like object or map useful in Terraform?

easy

A. They automatically fix syntax errors in your code.

B. They group related data together for better organization and clarity.

C. They make Terraform run faster by using less memory.

D. They replace the need for variables entirely.

Solution

1. Step 1: Understand the purpose of complex types

   Complex types like objects and maps group related pieces of data into one unit, making code clearer.

2. Step 2: Compare with other options

   They do not speed up Terraform or fix syntax errors automatically, nor do they replace variables.

3. Final Answer:

   They group related data together for better organization and clarity. -> Option B

4. Quick Check:

   Complex types = group related data [OK]

Hint: Think: complex types bundle related info neatly [OK]

Common Mistakes:

• Confusing complex types with performance improvements
• Believing complex types fix syntax errors
• Thinking complex types remove the need for variables

2. Which of the following is the correct syntax to define an object variable with attributes name (string) and age (number) in Terraform?

easy

A. variable "person" { type = object[name string, age number] }

B. variable "person" { type = map(string, number) }

C. variable "person" { type = list(object(name, age)) }

D. variable "person" { type = object({ name = string, age = number }) }

Solution

1. Step 1: Recall object type syntax

   Terraform defines object types with curly braces and attribute names with their types inside parentheses.

2. Step 2: Check each option

   variable "person" { type = object({ name = string, age = number }) } matches correct syntax: object({ name = string, age = number }). Others have wrong syntax or wrong type structures.

3. Final Answer:

   variable "person" { type = object({ name = string, age = number }) } -> Option D

4. Quick Check:

   Object type syntax = variable "person" { type = object({ name = string, age = number }) } [OK]

Hint: Remember object uses curly braces with attribute types inside [OK]

Common Mistakes:

• Using map instead of object for fixed attributes
• Incorrect brackets or parentheses
• Mixing list and object syntax

3. Given this Terraform variable declaration:

variable "server" {
  type = object({
    ip = string
    ports = list(number)
  })
  default = {
    ip = "10.0.0.1"
    ports = [80, 443]
  }
}

What is the value of var.server.ports[1]?

medium

A. "443"

B. 80

C. 443

D. Error: index out of range

Solution

1. Step 1: Understand the variable structure

   The variable "server" is an object with an IP string and a list of numbers called ports: [80, 443].

2. Step 2: Access the second port value

   Index 1 in the list is the second element, which is 443 (a number, not a string).

3. Final Answer:

   443 -> Option C

4. Quick Check:

   var.server.ports[1] = 443 [OK]

Hint: List index starts at 0, so 1 is second item [OK]

Common Mistakes:

• Confusing index 1 with index 0
• Thinking numbers are strings
• Assuming index out of range error

4. This Terraform code snippet causes an error:

variable "config" {
  type = object({
    region = string
    tags = map(string)
  })
}

output "region" {
  value = var.config.region
}

output "tag_value" {
  value = var.config.tags["env"]
}

What is the most likely cause of the error?

medium

A. The variable config is missing a default value or input.

B. The tags attribute should be a list, not a map.

C. Output blocks cannot access variable attributes directly.

D. The syntax for accessing map values is incorrect.

Solution

1. Step 1: Check variable declaration and usage

   The variable "config" is declared with no default, so it must be provided during apply.

2. Step 2: Identify error cause

   If no input is given, accessing var.config.region or var.config.tags["env"] causes an error because the variable is undefined.

3. Final Answer:

   The variable config is missing a default value or input. -> Option A

4. Quick Check:

   Missing input for variable = error [OK]

Hint: Variables without defaults need input to avoid errors [OK]

Common Mistakes:

• Assuming map access syntax is wrong
• Thinking outputs can't access variables
• Confusing map and list types

5. You want to pass a list of objects representing servers to a module. Each server has name (string), ip (string), and ports (list of numbers). Which variable type declaration correctly enforces this structure?

hard

A. variable "servers" { type = list(object({ name = string, ip = string, ports = list(number) })) }

B. variable "servers" { type = map(object({ name = string, ip = string, ports = list(string) })) }

C. variable "servers" { type = object({ name = list(string), ip = list(string), ports = list(number) }) }

D. variable "servers" { type = list(map(string)) }

Solution

1. Step 1: Understand the required structure

   The variable is a list of objects, each with name (string), ip (string), and ports (list of numbers).

2. Step 2: Match the correct type declaration

   variable "servers" { type = list(object({ name = string, ip = string, ports = list(number) })) } correctly declares a list of objects with the specified attributes and types.

3. Step 3: Eliminate incorrect options

   variable "servers" { type = map(object({ name = string, ip = string, ports = list(string) })) } uses map instead of list and ports as list of strings (wrong type). variable "servers" { type = object({ name = list(string), ip = list(string), ports = list(number) }) } is a single object with lists, not a list of objects. variable "servers" { type = list(map(string)) } is a list of maps with string values only, missing nested list of numbers.

4. Final Answer:

   variable "servers" { type = list(object({ name = string, ip = string, ports = list(number) })) } -> Option A

5. Quick Check:

   List of objects with correct attributes = variable "servers" { type = list(object({ name = string, ip = string, ports = list(number) })) } [OK]

Hint: List of objects means list(object({...})) [OK]

Common Mistakes:

• Confusing map and list types
• Using wrong attribute types inside objects
• Declaring a single object instead of list of objects