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.