Why modules enable reusability in Terraform - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How do Terraform modules improve code reusability?

Which statement best explains why Terraform modules enable reusability?

A Modules automatically update cloud resources without any input changes.

B Modules are only used for storing variables and do not affect resource creation.

C Modules package configuration into reusable units that can be called multiple times with different inputs.

D Modules prevent any changes to infrastructure once deployed.

💡 Hint

Think about how grouping code helps avoid repeating the same instructions.

Terraform modules group related configuration so you can reuse the same setup multiple times by changing inputs, avoiding duplication.

❓ Architecture

intermediate

Using modules to deploy multiple similar resources

You want to deploy three virtual machines with similar settings but different names and IPs. How can Terraform modules help?

A Modules cannot be used for multiple similar resources; use loops instead.

B Write three separate resource blocks without modules to keep it simple.

C Use a module only once and manually copy its output to create other VMs.

D Create one module defining a VM and call it three times with different input variables for name and IP.

💡 Hint

Think about how calling the same code with different inputs saves effort.

Modules let you define a VM once and reuse it multiple times by passing different variables, making your code cleaner and easier to maintain.

❓ Configuration

advanced

What output does this Terraform module call produce?

Given the module call below, what is the value of module.webserver.instance_count after applying?

Terraform

module "webserver" {
  source = "./modules/server"
  instance_count = 3
  server_name = "web-prod"
}

output "instance_count" {
  value = module.webserver.instance_count
}

A 0

B 3

C null

D Error: output not found

💡 Hint

Check how the input variable instance_count is passed and output is defined.

The module receives instance_count=3 and outputs it, so the value is 3.

❓ security

advanced

How do modules help improve security in Terraform projects?

Which option best describes how using modules can enhance security in Terraform infrastructure code?

A Modules allow centralizing sensitive configurations, reducing exposure and mistakes across multiple resources.

B Modules automatically encrypt all variables and outputs without extra configuration.

C Modules prevent unauthorized users from running Terraform commands.

D Modules disable logging to avoid exposing sensitive data.

💡 Hint

Think about how reusing code can reduce errors and improve control.

By centralizing sensitive settings in modules, you reduce duplication and risk of exposing secrets or misconfigurations.

❓ service_behavior

expert

What happens when a module is updated and re-applied?

You have a Terraform module used in multiple places. You update the module code to change a resource property. What is the expected behavior when you run terraform apply in a project using this module?

A Terraform detects the change and updates the affected resources accordingly during apply.

B Terraform ignores module changes unless you delete and re-add the module block.

C Terraform throws an error and refuses to apply changes from updated modules.

D Terraform automatically creates new resources but does not modify existing ones.

💡 Hint

Consider how Terraform tracks resource state and module code.

Terraform compares the current state with the updated module code and applies necessary changes to keep infrastructure in sync.