Tuple type definition in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Tuple Type Definition in Terraform

Which of the following Terraform type definitions correctly defines a tuple with a string, a number, and a boolean in that order?

A tuple([bool, string, number])

B tuple([string, bool, number])

C tuple([number, string, bool])

D tuple([string, number, bool])

💡 Hint

Remember that tuple types require the exact order of types as elements.

Tuple types in Terraform require the exact sequence of types. Option D correctly lists string, number, then bool.

❓ Configuration

intermediate

Tuple Type Validation in Terraform Variable

Given this Terraform variable declaration, which option correctly assigns a valid value to it?

variable "example" {
  type = tuple([string, number, bool])
}

A ["hello", 42, true]

B [true, 42, "hello"]

C ["hello", true, 42]

D [42, "hello", true]

💡 Hint

Match the order of types: string, number, bool.

The tuple type requires the first element to be a string, second a number, and third a boolean. Only option A matches this order.

❓ Architecture

advanced

Using Tuple Types for Module Inputs

You want to pass a tuple of a string and a number to a Terraform module input. Which type definition and input value pair is correct?

A type = tuple([string, number]) with value [3, "app"]

B type = tuple([number, string]) with value ["app", 3]

C type = tuple([string, number]) with value ["app", 3]

D type = tuple([bool, string]) with value [true, "app"]

💡 Hint

Check both the type order and the value order.

The tuple type and value must match in order and type. Option C correctly defines and assigns a tuple of string then number.

❓ security

advanced

Security Implications of Tuple Types in Terraform

Which statement about using tuple types for sensitive data in Terraform is true?

A Tuple types can mark individual elements as sensitive to prevent exposure.

B Terraform does not support marking tuple elements as sensitive; the whole tuple must be sensitive.

C Tuple types automatically encrypt sensitive elements at rest.

D Using tuple types for sensitive data disables Terraform state encryption.

💡 Hint

Consider how Terraform handles sensitivity at the type level.

Terraform currently does not support marking individual tuple elements as sensitive. Sensitivity applies to the entire variable or output.

❓ service_behavior

expert

Behavior of Tuple Type with Optional Elements in Terraform 1.5+

In Terraform 1.5+, you define a tuple type with an optional third element: tuple([string, number, optional(bool)]). What happens if you assign the value ["test", 10] to this variable?

A The assignment is valid; the optional bool element can be omitted.

B The assignment causes a type error because the tuple length is less than 3.

C Terraform treats the missing bool as false automatically.

D Terraform fills the missing bool with null and raises a warning.

💡 Hint

Think about how optional elements in tuple types work in Terraform 1.5 and later.

Terraform 1.5+ supports optional tuple elements. Omitting the optional bool element is valid and does not cause errors.

Practice

1. What is a tuple type in Terraform?

easy

A. A fixed list of values where each value has a specific type

B. A list of values all having the same type

C. A map with keys and values of any type

D. A variable that can hold any type of data

Solution

1. Step 1: Understand tuple definition

   A tuple in Terraform is a collection of values with a fixed number and specific types for each position.

2. Step 2: Compare with other types

   Unlike lists, tuples have fixed length and types per position, not all the same type.

3. Final Answer:

   A fixed list of values where each value has a specific type -> Option A

4. Quick Check:

   Tuple = fixed types and order [OK]

Hint: Remember: tuple = fixed order and types [OK]

Common Mistakes:

• Confusing tuple with list (all same type)
• Thinking tuple can have variable length
• Mixing tuple with map types

2. Which of the following is the correct syntax to define a tuple type with a string and a number in Terraform?

easy

A. tuple([string, number])

B. tuple[string, number]

C. list([string, number])

D. tuple(string, number)

Solution

1. Step 1: Recall tuple syntax

   Terraform tuple types are defined as tuple([type1, type2, ...]), using square brackets inside parentheses.

2. Step 2: Check options

   The correct syntax is tuple([string, number]). Options B and D are invalid syntax. list([string, number]) is a list, not a tuple.

3. Final Answer:

   tuple([string, number]) -> Option A

4. Quick Check:

   Tuple syntax = tuple([type1, type2]) [OK]

Hint: Use tuple([type1, type2]) syntax with square brackets inside parentheses [OK]

Common Mistakes:

• Using parentheses without square brackets
• Using square brackets without parentheses
• Confusing tuple syntax with list syntax

3. Given this variable definition in Terraform:

variable "example" {
  type = tuple([string, number, bool])
  default = ["hello", 42, true]
}

What will be the value of var.example[1]?

medium

A. "hello"

B. true

C. Error: invalid index

D. 42

Solution

1. Step 1: Understand tuple indexing

   Tuple elements are indexed starting at 0. The second element is at index 1.

2. Step 2: Identify value at index 1

   The tuple is ["hello", 42, true], so index 1 is 42.

3. Final Answer:

   42 -> Option D

4. Quick Check:

   Index 1 in tuple = 42 [OK]

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

Common Mistakes:

• Confusing index 1 with index 0
• Expecting string instead of number at index 1
• Thinking tuple elements are unordered

4. What is wrong with this Terraform tuple type definition?

variable "bad_tuple" {
  type = tuple([string, number])
  default = ["text", "not a number"]
}

medium

A. The tuple type syntax is incorrect

B. The default value does not match the tuple types

C. Tuple cannot have string and number types together

D. Default value must be a map, not a list

Solution

1. Step 1: Check tuple type syntax

   The syntax tuple([string, number]) is correct for a tuple with two elements.

2. Step 2: Validate default values

   The default is ["text", "not a number"]. The second element should be a number but is a string, causing a type mismatch.

3. Final Answer:

   The default value does not match the tuple types -> Option B

4. Quick Check:

   Tuple types must match default values [OK]

Hint: Check default values match tuple types exactly [OK]

Common Mistakes:

• Assuming tuple syntax is wrong
• Ignoring type mismatch in default values
• Thinking tuples can't mix types

5. You want to define a Terraform variable that holds a tuple with three elements: a string, a list of numbers, and a boolean. Which is the correct type definition?

hard

A. tuple(string, list[number], bool)

B. tuple(string, list, bool)

C. tuple([string, list(number), bool])

D. tuple[string, list(number), bool]

Solution

1. Step 1: Understand tuple element types

   The tuple has three elements: a string, a list of numbers, and a boolean.

2. Step 2: Use correct syntax for list of numbers

   In Terraform, list of numbers is written as list(number). So the tuple type is tuple([string, list(number), bool]).

3. Step 3: Check options

   tuple([string, list(number), bool]) matches the correct syntax. Others use invalid syntax like list[number] or brackets.

4. Final Answer:

   tuple([string, list(number), bool]) -> Option C

5. Quick Check:

   List type inside tuple uses list(type) [OK]

Hint: Use list(type) inside tuple for lists [OK]

Common Mistakes:

• Using square brackets instead of parentheses for list
• Omitting type inside list
• Using tuple with square brackets incorrectly