Optional attributes in objects in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an object type with an optional attribute.

Terraform

variable "config" {
  type = object({
    name = string
    age  = number
    city = [1] # optional attribute
  })
}

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

Astring

Boptional(string)

Coptional(number)

Dbool

Attempts:

3 left

💡 Hint

Common Mistakes

Using just 'string' makes the attribute required.

Using 'optional(number)' for a string attribute causes type mismatch.

The optional(string) marks the city attribute as optional in the object type.

2fill in blank

medium

Complete the code to assign a value to the optional attribute in a variable.

Terraform

variable "config" {
  default = {
    name = "Alice"
    age  = 30
    city = [1]
  }
}

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

A30

Bnull

C"New York"

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Assigning a number or boolean to a string attribute.

Using null when a string is expected.

Assigning a string value like "New York" to the optional city attribute is valid.

3fill in blank

hard

Fix the error in the object type definition by correctly marking the optional attribute.

Terraform

variable "config" {
  type = object({
    name = string
    age  = number
    city = [1]
  })
}

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

Astring

Bbool

Cnumber

Doptional(string)

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving the attribute as just 'string' causes errors if the attribute is missing.

Using wrong types like 'number' or 'bool' for a string attribute.

The city attribute must be marked as optional(string) to avoid errors when it is not provided.

4fill in blank

hard

Fill both blanks to define an object with one required and one optional attribute.

Terraform

variable "user" {
  type = object({
    username = [1]
    email    = [2]
  })
}

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

Astring

Boptional(string)

Cnumber

Dbool

Attempts:

3 left

💡 Hint

Common Mistakes

Marking required attributes as optional.

Using wrong types for attributes.

username is required as string, and email is optional as optional(string).

5fill in blank

hard

Fill all three blanks to create an object with two optional and one required attribute.

Terraform

variable "settings" {
  type = object({
    region   = [1]
    timeout  = [2]
    retries  = [3]
  })
}

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

Astring

Boptional(number)

Coptional(string)

Dnumber

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up optional and required attributes.

Using wrong types for attributes.

region is required string, timeout is optional string, and retries is optional number.

Practice

1. What does the optional(type, default) function do in a Terraform object type?

easy

A. It allows an attribute to be skipped and provides a default value if missing.

B. It makes an attribute required and enforces a value.

C. It deletes the attribute from the object.

D. It converts the attribute to a list type.

Solution

1. Step 1: Understand optional attribute purpose

   Optional attributes let you omit some fields safely without errors.

2. Step 2: Role of default value

   The default value is used when the attribute is not provided, ensuring smooth operation.

3. Final Answer:

   It allows an attribute to be skipped and provides a default value if missing. -> Option A

4. Quick Check:

   optional(type, default) = skip with default [OK]

Hint: Optional means skip allowed with default value [OK]

Common Mistakes:

• Thinking optional means required
• Assuming it deletes attributes
• Confusing optional with type conversion

2. Which of the following is the correct syntax to define an optional string attribute named region with default "us-west-1" in a Terraform object type?

easy

A. object({ optional(region, string, "us-west-1") })

B. object({ region = optional(string, "us-west-1") })

C. object({ region = string.optional("us-west-1") })

D. object({ region: optional(string, "us-west-1") })

Solution

1. Step 1: Recall correct optional attribute syntax

   The correct syntax is attribute = optional(type, default) inside object.

2. Step 2: Match syntax with options

   object({ region = optional(string, "us-west-1") }) matches this pattern exactly with attribute name and default value.

3. Final Answer:

   object({ region = optional(string, "us-west-1") }) -> Option B

4. Quick Check:

   Correct optional attribute syntax = object({ region = optional(string, "us-west-1") }) [OK]

Hint: Use attribute = optional(type, default) inside object [OK]

Common Mistakes:

• Placing optional outside attribute name
• Using colon instead of equals
• Wrong order of parameters

3. Given this Terraform variable type declaration:

variable "config" {
  type = object({
    name = string
    description = optional(string, "No description")
  })
}

What will be the value of var.config.description if the input is { name = "App" }?

medium

A. "No description"

B. null

C. Error: missing required attribute

D. "App"

Solution

1. Step 1: Identify optional attribute with default

   The description attribute is optional with default "No description".

2. Step 2: Check input for description

   The input does not provide description, so default applies.

3. Final Answer:

   "No description" -> Option A

4. Quick Check:

   Missing optional attribute uses default [OK]

Hint: Missing optional attribute uses default value [OK]

Common Mistakes:

• Expecting null instead of default
• Thinking missing optional causes error
• Confusing attribute values

4. You wrote this object type in Terraform:

object({
  id = string
  tags = optional(map(string))
})

But when you apply, Terraform shows an error about tags. What is the likely cause?

medium

A. Optional attributes cannot be maps

B. Missing default value for optional attribute tags

C. Syntax error: missing comma after id

D. The attribute id should be optional

Solution

1. Step 1: Check object type syntax

   In Terraform object types, attributes must be separated by commas.

2. Step 2: Identify missing comma

   After id = string there is no comma before tags, causing a syntax error often reported at tags.

3. Final Answer:

   Syntax error: missing comma after id -> Option C

4. Quick Check:

   Missing comma in object type causes syntax error [OK]

Hint: Object attributes need commas between them [OK]

Common Mistakes:

• Forgetting commas between attributes
• Thinking optional(map) requires explicit default
• Assuming maps can't be optional

5. You want to define a Terraform object type for a server configuration with these rules:
- hostname is required string
- port is optional number, default 80
- tags is optional map of strings, default empty map

Which of these is the correct type declaration?

hard

A. object({ hostname = string, port = optional(number), tags = map(string) })

B. object({ hostname = optional(string), port = number, tags = optional(map(string)) })

C. object({ hostname = string, port = number, tags = optional(map(string), null) })

D. object({ hostname = string, port = optional(number, 80), tags = optional(map(string), {}) })

Solution

1. Step 1: Identify required and optional attributes

   hostname is required string, port optional number with default 80, tags optional map with default empty map.

2. Step 2: Match syntax with rules

   object({ hostname = string, port = optional(number, 80), tags = optional(map(string), {}) }) correctly uses optional(type, default) for port and tags, and required string for hostname.

3. Final Answer:

   object({ hostname = string, port = optional(number, 80), tags = optional(map(string), {}) }) -> Option D

4. Quick Check:

   Required and optional with defaults correctly declared [OK]

Hint: Use optional(type, default) for optional with defaults [OK]

Common Mistakes:

• Missing default for optional attributes
• Marking required attributes as optional
• Using null instead of empty map as default