File naming conventions (.tf files) in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use multiple .tf files in a Terraform project?

In Terraform, you can split your infrastructure code into multiple .tf files. What is the main reason for doing this?

A Because Terraform requires each resource to be in a separate file to work correctly.

B To organize code logically by resource type or purpose, making it easier to manage and understand.

C To speed up Terraform plan and apply commands by parallel processing files.

D To avoid using variables and outputs in the configuration.

💡 Hint

Think about how organizing files helps when your project grows.

Using multiple .tf files helps keep your code organized by grouping related resources or configurations. Terraform automatically loads all .tf files in a directory, so splitting files is for clarity and maintainability, not a requirement or performance boost.

✅ Best Practice

intermediate

Which file name is best for defining variables in Terraform?

You want to define input variables for your Terraform project. Which file name follows common naming conventions?

A terraform_variables.tf

B input.tfvars

C vars.txt

D variables.tf

💡 Hint

Look for the standard file name used in most Terraform projects.

The file variables.tf is the common convention to define input variables. Files ending with .tfvars are used to provide values, not definitions. Using .txt or long descriptive names is not standard.

❓ Configuration

advanced

What happens if you have two files defining the same resource name?

Consider these two files in the same Terraform directory:

file1.tf:
resource "aws_s3_bucket" "mybucket" {
  bucket = "bucket-one"
}

file2.tf:
resource "aws_s3_bucket" "mybucket" {
  bucket = "bucket-two"
}

What will Terraform do when you run terraform plan?

A Terraform will raise an error about duplicate resource names and stop.

B Terraform will ignore the second resource and use only the first.

C Terraform will merge both resources into one with combined settings.

D Terraform will create two separate buckets with the same name.

💡 Hint

Think about how Terraform identifies resources uniquely.

Terraform requires resource names to be unique within a module. Defining two resources with the same type and name causes a conflict error during plan or apply.

❓ Architecture

advanced

How should you name files to separate environment configurations?

You manage multiple environments like dev and prod in the same Terraform project. Which file naming approach is best to keep environment configs separate?

A Use files named <code>dev.tfvars</code> and <code>prod.tfvars</code> to hold environment-specific values.

B Put all environment configs in one file named <code>environment.tf</code> with comments.

C Create separate directories named <code>dev</code> and <code>prod</code> with identical file names inside.

D Use a single file named <code>main.tf</code> and switch values manually before each run.

💡 Hint

Think about how Terraform loads variable values from files.

Using separate .tfvars files for each environment is a common practice. You keep the main configuration files the same and pass different variable values per environment by specifying the appropriate .tfvars file during commands.

❓ service_behavior

expert

What is the effect of naming a file terraform.tfstate in your working directory?

You accidentally create a file named terraform.tfstate manually in your Terraform directory before running any commands. What will happen when you run terraform apply?

A Terraform will overwrite the file without warning and proceed normally.

B Terraform will ignore the file and create its own state file elsewhere.

C Terraform will treat the file as the state file and may cause conflicts or errors if its content is invalid.

D Terraform will rename the file automatically to avoid conflicts.

💡 Hint

Think about how Terraform uses the state file to track resources.

The terraform.tfstate file is where Terraform stores the current state of managed infrastructure. If you create this file manually with invalid content, Terraform will try to read it and may fail or behave unexpectedly.