Terraform file organization - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Identify the correct Terraform file organization for a multi-environment setup

You have a Terraform project that manages infrastructure for two environments: production and staging. Which file organization below best separates environment-specific configurations while reusing common modules?

A Separate folders for each environment (prod/, staging/) each containing main.tf, variables.tf, and backend.tf files, plus a modules/ folder for reusable modules.

B A single main.tf file with all resources and variables for both environments mixed together.

C One folder with main.tf and variables.tf files, and environment variables set externally to switch environments.

D Multiple .tf files in the root folder named prod.tf, staging.tf, and modules.tf without folders.

💡 Hint

Think about how to isolate environment settings while sharing common code.

Option A is best because it uses separate folders per environment to isolate configs and a modules folder for shared code. This keeps environments clean and reusable.

✅ Best Practice

intermediate

Choose the best practice for Terraform state file management

Which Terraform file organization practice helps prevent state file conflicts when multiple team members work on the same infrastructure?

A Store the state file locally on each developer's machine.

B Use a remote backend like S3 or Terraform Cloud with locking enabled, and organize state files per environment.

C Keep all environment states in a single shared state file in the root folder.

D Commit the state file to the version control system along with .tf files.

💡 Hint

Think about collaboration and avoiding overwriting each other's work.

Option B is best because remote backends with locking prevent conflicts and organizing state per environment keeps states isolated.

❓ service_behavior

advanced

What happens if you mix provider configurations in multiple Terraform files without explicit aliasing?

Consider a Terraform project with two .tf files: one configures AWS provider with region us-east-1, and another configures AWS provider with region us-west-2, both without aliases. What is the expected behavior when running terraform apply?

A Terraform will merge both provider configurations and apply resources in both regions automatically.

B Terraform will use the last declared provider configuration and ignore the first one.

C Terraform will throw a configuration error due to multiple provider blocks without aliases.

D Terraform will create duplicate resources in both regions without error.

💡 Hint

Think about how Terraform handles multiple provider blocks of the same type.

Terraform requires multiple provider configurations of the same type to use aliases. Without aliases, it throws an error to avoid ambiguity.

❓ security

advanced

Identify the security risk in Terraform file organization

Which Terraform file organization practice can lead to accidental exposure of sensitive data like secrets or passwords?

A Using <code>terraform.tfvars</code> files committed to version control containing secrets in plain text.

B Storing sensitive variables in a separate <code>variables.tf</code> file with no special handling.

C Referencing sensitive data from environment variables during Terraform runs.

D Using remote state backends with encryption enabled.

💡 Hint

Consider what happens if secret values are stored in files tracked by Git.

Committing terraform.tfvars files with secrets in plain text to version control risks exposing sensitive data publicly or to unauthorized users.

🧠 Conceptual

expert

Determine the number of Terraform state files in a recommended multi-module, multi-environment setup

You have a Terraform project organized with a modules/ folder containing reusable modules, and separate folders for dev/, qa/, and prod/ environments. Each environment folder has its own Terraform configuration files and remote backend configured. How many distinct Terraform state files will exist after applying all environments?

A One state file per module per environment.

B One state file per module, shared across all environments.

C One single state file for all environments and modules combined.

D One state file per environment, encompassing all modules used in that environment.

💡 Hint

Think about how Terraform state files track resources per configuration and environment.

Each environment folder has its own configuration and backend, so each environment has one state file that includes all modules used in that environment.