Root module concept in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the root module in Terraform?

In Terraform, what does the term root module refer to?

A A module that is automatically created by Terraform for each provider.

B A special Terraform module that manages remote state storage.

C The directory where Terraform configuration files are loaded and executed by default.

D A module that contains only variables and no resources.

💡 Hint

Think about where Terraform starts reading your configuration files.

The root module is the main directory where Terraform loads configuration files to start the deployment process. It is the entry point for Terraform execution.

❓ Architecture

intermediate

How does Terraform handle nested modules called from the root module?

When a root module calls a child module, how does Terraform treat the child module?

A As a separate module with its own state, isolated from the root module.

B As part of the root module's configuration and state, but logically separated.

C As a completely independent Terraform project requiring separate initialization.

D As a provider plugin that manages resources automatically.

💡 Hint

Consider how Terraform manages state for modules called inside other modules.

Child modules are included in the root module's state but are logically separated to organize resources. They do not have independent state files.

❓ Configuration

advanced

What is the output of this Terraform root module configuration?

Given this root module code snippet, what will be the value of the output instance_name?

Terraform

module "web_server" {
  source = "./modules/server"
  name   = "app-server"
}

output "instance_name" {
  value = module.web_server.name
}

A "app-server"

B "web_server"

C null

D SyntaxError: output value must be a string

💡 Hint

Look at how the module input name is passed and then output is referencing it.

The module is called with name = "app-server". The output references module.web_server.name, so the output value is "app-server".

❓ security

advanced

Which practice improves security when using root modules in Terraform?

When managing sensitive data in a root module, which practice is best to keep secrets safe?

A Hardcoding secrets directly in the root module variables.tf file.

B Including secrets in output blocks to easily access them after deployment.

C Storing secrets in plain text files inside the root module directory.

D Using environment variables or secret management tools to inject sensitive values.

💡 Hint

Think about how to avoid exposing secrets in code or outputs.

Using environment variables or secret management tools keeps sensitive data out of code and state files, improving security.

❓ service_behavior

expert

What happens if the root module's Terraform state file is deleted accidentally?

If the Terraform state file for the root module is deleted, what is the expected behavior when running terraform apply again?

A Terraform will recreate all resources because it thinks none exist.

B Terraform will detect existing resources and import them automatically without changes.

C Terraform will fail with an error saying state file is missing and stop execution.

D Terraform will ignore the missing state and only update resources defined in child modules.

💡 Hint

Consider how Terraform uses the state file to track resources.

Terraform relies on the state file to know what resources exist. Without it, Terraform assumes no resources exist and tries to create them again.