Why variables make configurations reusable in Terraform - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use variables in Terraform configurations?

Which statement best explains why variables make Terraform configurations reusable?

A Variables automatically create new resources without any input from the user.

B Variables store the output of Terraform commands for later use.

C Variables prevent any changes to the configuration once it is deployed.

D Variables allow you to change values without editing the main configuration, so the same code can deploy different resources.

💡 Hint

Think about how you can use the same recipe but change ingredients easily.

Variables let you customize values like names or sizes without changing the main code, making it reusable for different setups.

❓ Architecture

intermediate

How do variables improve Terraform module reuse?

You have a Terraform module that creates a virtual machine. How do variables help you reuse this module for different projects?

A By locking the module to a single fixed configuration.

B By forcing you to copy and edit the module code for each project.

C By allowing you to pass different VM names, sizes, and networks to the module without changing its code.

D By automatically detecting the best VM size for each project.

💡 Hint

Think about how you can use the same tool but adjust settings for each use.

Variables let you customize inputs like VM name and size, so the same module works for many projects without code changes.

❓ Configuration

advanced

What is the output of this Terraform variable usage?

Given this Terraform snippet, what will be the value of resource_name after applying?

Terraform

variable "env" {
  default = "prod"
}

variable "app" {
  default = "web"
}

output "resource_name" {
  value = "${var.app}-${var.env}-01"
}

A "web-prod-01"

B "prod-web-01"

C "web-01-prod"

D "01-web-prod"

💡 Hint

Look at how the variables are combined in the output value.

The output concatenates var.app, var.env, and "01" in that order, so the result is "web-prod-01".

❓ security

advanced

Why should sensitive variables be used in Terraform?

Which reason best explains why marking variables as sensitive improves security in Terraform?

A Sensitive variables hide their values in logs and output to prevent accidental exposure of secrets.

B Sensitive variables encrypt the values automatically in the cloud provider.

C Sensitive variables prevent Terraform from using the values in resource creation.

D Sensitive variables make the configuration run faster.

💡 Hint

Think about how you keep passwords hidden when sharing information.

Marking variables as sensitive stops Terraform from showing their values in logs or outputs, protecting secrets like passwords.

❓ service_behavior

expert

What happens if a required variable is not provided in Terraform?

Consider a Terraform configuration with a variable declared without a default value. What will Terraform do if you run terraform apply without providing this variable?

A Terraform will fail with a syntax error before applying.

B Terraform will prompt you to enter a value for the variable before proceeding.

C Terraform will skip creating resources that depend on the variable.

D Terraform will use an empty string as the variable value automatically.

💡 Hint

Think about how Terraform handles missing required inputs interactively.

Terraform asks the user to input a value for any variable without a default before it can continue applying changes.