Object type definition in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Identify the correct Terraform object type definition

Which option correctly defines a Terraform object type with a string field name and a number field count?

A object({ name: string, count: number })

B object({ name = string, count = number })

C object([name = string, count = number])

D object({ "name" = string, "count" = number })

💡 Hint

Terraform object types use curly braces with key = type pairs.

Terraform object type syntax requires curly braces with keys and types separated by =. Colons or brackets are invalid.

❓ service_behavior

intermediate

What happens if a Terraform object type is missing a required attribute?

Given a Terraform object type object({ name = string, count = number }), what error occurs if you provide an object missing the count attribute?

A Terraform plan throws a syntax error.

B Terraform plan succeeds but sets 'count' to zero by default.

C Terraform plan ignores the missing attribute and continues.

D Terraform plan fails with a validation error about missing attribute 'count'.

💡 Hint

Terraform enforces required attributes in object types strictly.

Terraform requires all attributes defined in an object type to be present; missing attributes cause validation errors during plan.

❓ Architecture

advanced

Choose the correct nested object type definition in Terraform

Which option correctly defines a Terraform object type with a string name and a nested object settings containing a boolean enabled and a list of strings tags?

A object({ name = string, settings = object({ enabled = bool, tags = list(string) }) })

B object({ name = string, settings = object([ enabled = bool, tags = list(string) ]) })

C object({ name = string, settings = { enabled = bool, tags = list(string) } })

D object({ name = string, settings = map({ enabled = bool, tags = list(string) }) })

💡 Hint

Nested objects use object() with curly braces inside the parent object definition.

Terraform nested object types require object() with curly braces for the nested attributes. Square brackets or map() are invalid here.

❓ security

advanced

What is the security implication of using any type instead of a strict object type in Terraform?

If you replace a strict object type with any in Terraform variable definitions, what is the main security risk?

A It allows any data structure, potentially leading to unexpected or unsafe configurations.

B It encrypts all data automatically, increasing security.

C It causes Terraform to ignore the variable during plan.

D It restricts input to only strings, reducing flexibility.

💡 Hint

Using any disables type checking.

Using any disables strict type checking, which can allow unsafe or unexpected data to be passed, risking misconfiguration or security issues.

✅ Best Practice

expert

Which Terraform object type definition best enforces immutability of a configuration block?

You want to define a Terraform object type for a configuration block that should not allow extra attributes beyond id (string) and enabled (bool). Which option enforces this strictly?

A map(any)

B object({ id = string, enabled = bool, optional = true })

C object({ id = string, enabled = bool })

D object({ id = string, enabled = bool, additional_properties = false })

💡 Hint

Terraform object types do not support additional properties by default.

Terraform object types only allow the attributes defined. Options A and C allow extra attributes or are invalid syntax. Option C is not valid Terraform syntax.

Practice

1. What is the main purpose of defining an object type in Terraform?

easy

A. To group related values with specific names and types

B. To create a list of strings

C. To define a single integer value

D. To write shell scripts inside Terraform

Solution

1. Step 1: Understand object type concept

   An object type groups multiple related values, each with a name and a type.

2. Step 2: Compare with other types

   Unlike lists or single values, objects organize structured data clearly.

3. Final Answer:

   To group related values with specific names and types -> Option A

4. Quick Check:

   Object type = group related named values [OK]

Hint: Objects group named values, not single or list values [OK]

Common Mistakes:

• Confusing object with list or map types
• Thinking object holds only one value
• Assuming object is for scripting

2. Which of the following is the correct syntax to define an object type with a string field name and a number field age in Terraform?

easy

A. object({ name string, age number })

B. object({ name: string, age: number })

C. object({ "name" = string, "age" = number })

D. object({ name = string, age = number })

Solution

1. Step 1: Recall object type syntax

   Terraform object types use curly braces with unquoted identifier keys and equal signs: object({ key = type, ... })

2. Step 2: Check each option

   object({ name = string, age = number }) correctly uses unquoted keys and equal signs. Others use invalid syntax like colons, quoted keys for simple identifiers, or missing equals.

3. Final Answer:

   object({ name = string, age = number }) -> Option D

4. Quick Check:

   Object keys unquoted with = sign [OK]

Hint: Object keys use unquoted identifiers with = type [OK]

Common Mistakes:

• Using colons instead of equal signs
• Quoting keys in object type
• Omitting commas or using wrong separators

3. Given this variable definition in Terraform:

variable "person" {
  type = object({
    name = string
    age  = number
  })
  default = {
    name = "Alice"
    age  = 30
  }
}

What will be the value of var.person.age?

medium

A. "30"

B. 30

C. null

D. Error: type mismatch

Solution

1. Step 1: Analyze variable type and default

   The variable is an object with fields name (string) and age (number). Default sets age to 30 (number).

2. Step 2: Determine var.person.age value

   Accessing var.person.age returns the number 30 as defined.

3. Final Answer:

   30 -> Option B

4. Quick Check:

   Object field age = 30 number [OK]

Hint: Object fields keep their defined types and values [OK]

Common Mistakes:

• Thinking number becomes string automatically
• Expecting null if not accessed
• Confusing default with no value

4. Identify the error in this Terraform object type definition:

variable "config" {
  type = object({
    "enabled" = bool
    "count" = int
  })
  default = {
    enabled = true
    count = 3
  }
}

medium

A. The type int is invalid; should be number

B. Keys in object type should not be quoted

C. Default values must be strings

D. Boolean values cannot be used in objects

Solution

1. Step 1: Check type names in object

   Terraform uses number for numeric types, not int.

2. Step 2: Validate other syntax

   Quoted keys are allowed, default values match types, booleans are valid.

3. Final Answer:

   The type int is invalid; should be number -> Option A

4. Quick Check:

   Use number, not int, for numeric types [OK]

Hint: Use 'number' type, not 'int' in Terraform objects [OK]

Common Mistakes:

• Using 'int' instead of 'number'
• Thinking keys cannot be quoted
• Believing booleans are invalid in objects

5. You want to define a Terraform variable that accepts an object with a name (string), tags (map of strings), and an optional count (number). Which is the correct way to define this object type?

hard

A. object({ name = string, tags = map(string), count = number })

B. object({ "name" = string, "tags" = map(string), "count" = optional(number) })

C. object({ name = string, tags = map(string), count = optional(number) })

D. object({ name = string, tags = map(string), count = optional number })

Solution

1. Step 1: Recall optional attribute syntax

   Terraform uses optional(type) without quotes for optional fields inside object types.

2. Step 2: Check key quoting rules

   Keys in object type definitions use unquoted identifiers for standard names; quoting simple keys is incorrect.

3. Step 3: Evaluate options

   object({ name = string, tags = map(string), count = optional(number) }) correctly uses unquoted keys and optional(number) syntax. object({ "name" = string, "tags" = map(string), "count" = optional(number) }) quotes keys incorrectly. object({ name = string, tags = map(string), count = number }) misses optional. object({ name = string, tags = map(string), count = optional number }) has invalid syntax.

4. Final Answer:

   object({ name = string, tags = map(string), count = optional(number) }) -> Option C

5. Quick Check:

   Optional fields use optional(type) with unquoted keys [OK]

Hint: Use optional(type) without quotes and unquoted keys [OK]

Common Mistakes:

• Quoting keys in object type
• Missing optional() for optional fields
• Using invalid syntax like 'optional number'