File naming conventions (.tf files) in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name a Terraform configuration file correctly.

Terraform

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

# Save this configuration in a file named [1]

Drag options to blanks, or click blank then click option'

Aterraform.doc

Bconfig.txt

Cmain.tf

Dscript.sh

Attempts:

3 left

💡 Hint

Common Mistakes

Using file extensions like .txt or .doc which are not valid for Terraform.

Naming files with script extensions like .sh.

The correct file extension for Terraform configuration files is .tf. The common convention is to use main.tf as the primary file name.

2fill in blank

medium

Complete the code to name a Terraform variables file correctly.

Terraform

# Variables for Terraform
variable "region" {
  description = "AWS region"
  type        = string
}

# Save this in [1]

Drag options to blanks, or click blank then click option'

Avariables.tf

Bvars.txt

Cvariables.json

Dvars.sh

Attempts:

3 left

💡 Hint

Common Mistakes

Using .txt or .json extensions for variable files.

Naming variable files with shell script extensions.

Terraform variable definitions are conventionally stored in a file named variables.tf with the .tf extension.

3fill in blank

hard

Fix the error in the file naming for Terraform outputs.

Terraform

# Outputs configuration
output "instance_ip" {
  value = aws_instance.example.public_ip
}

# This should be saved as [1]

Drag options to blanks, or click blank then click option'

Aoutputs.txt

Boutput.sh

Coutput.json

Doutputs.tf

Attempts:

3 left

💡 Hint

Common Mistakes

Using .txt or .json extensions for output files.

Naming output files with shell script extensions.

Output definitions in Terraform are stored in files with the .tf extension. The common convention is outputs.tf.

4fill in blank

hard

Fill both blanks to correctly name Terraform files for provider and backend configuration.

Terraform

# Provider configuration
provider "aws" {
  region = "us-west-2"
}

# Save this in [1]

# Backend configuration
terraform {
  backend "s3" {
    bucket = "mybucket"
    key    = "path/to/my/key"
    region = "us-west-2"
  }
}

# Save this in [2]

Drag options to blanks, or click blank then click option'

Aprovider.tf

Bbackend.txt

Cbackend.tf

Dprovider.txt

Attempts:

3 left

💡 Hint

Common Mistakes

Using .txt extension for Terraform configuration files.

Mixing up provider and backend file names.

Provider configurations are usually saved in provider.tf and backend configurations in backend.tf, both using the .tf extension.

5fill in blank

hard

Fill all three blanks to correctly name Terraform files for main configuration, variables, and outputs.

Terraform

# Main configuration
resource "aws_s3_bucket" "bucket" {
  bucket = "my-tf-bucket"
  acl    = "private"
}

# Save this in [1]

# Variables
variable "bucket_name" {
  type = string
}

# Save this in [2]

# Outputs
output "bucket_id" {
  value = aws_s3_bucket.bucket.id
}

# Save this in [3]

Drag options to blanks, or click blank then click option'

Amain.tf

Bvariables.tf

Coutputs.tf

Dconfig.tf

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-.tf extensions for any Terraform files.

Confusing file names for variables and outputs.

The main Terraform configuration file is usually main.tf, variables are in variables.tf, and outputs in outputs.tf.

Practice

1. Which of the following is the most common file name used to define the main Terraform configuration?

easy

A. terraform.tf

B. config.tf

C. setup.tf

D. main.tf

Solution

1. Step 1: Understand common Terraform file names

   The main Terraform configuration is typically placed in a file named main.tf to keep it clear and standard.

2. Step 2: Compare options with common practice

   Among the options, only main.tf is widely recognized and recommended for the main configuration.

3. Final Answer:

   main.tf -> Option D

4. Quick Check:

   Main configuration file = main.tf [OK]

Hint: Main config file is usually named main.tf [OK]

Common Mistakes:

• Choosing uncommon names like config.tf
• Using generic names like terraform.tf
• Confusing setup files with main config

2. Which file name is conventionally used to declare input variables in Terraform?

easy

A. variables.tf

B. inputs.tf

C. vars.tf

D. params.tf

Solution

1. Step 1: Identify the standard file for input variables

   Terraform commonly uses variables.tf to declare input variables for clarity and consistency.

2. Step 2: Check other options for correctness

   Other names like inputs.tf, vars.tf, and params.tf are not standard and may confuse team members.

3. Final Answer:

   variables.tf -> Option A

4. Quick Check:

   Input variables file = variables.tf [OK]

Hint: Input variables go in variables.tf file [OK]

Common Mistakes:

• Using inputs.tf instead of variables.tf
• Shortening to vars.tf which is non-standard
• Naming it params.tf which is unclear

3. Given these files in a Terraform project: main.tf, variables.tf, and outputs.tf, what is the purpose of outputs.tf?

medium

A. To define the resources to create

B. To declare input variables

C. To specify values to show after apply

D. To configure backend storage

Solution

1. Step 1: Understand the role of outputs.tf

   The outputs.tf file is used to declare output values that Terraform will display after applying the configuration.

2. Step 2: Differentiate from other files

   main.tf defines resources, variables.tf declares inputs, and backend configuration is usually in backend.tf or inside main.tf.

3. Final Answer:

   To specify values to show after apply -> Option C

4. Quick Check:

   outputs.tf shows output values [OK]

Hint: Outputs.tf shows results after apply [OK]

Common Mistakes:

• Confusing outputs.tf with variables.tf
• Thinking outputs.tf defines resources
• Assuming outputs.tf configures backend

4. You have a Terraform project with files named main.tf, variables.tf, and output.tf. Why might this violate standard conventions?

medium

A. Because main.tf must contain outputs

B. Because the outputs file is misnamed; it should be outputs.tf

C. Because variables.tf is missing output declarations

D. Because Terraform requires outputs in a .json file

Solution

1. Step 1: Check file naming conventions for outputs

   The conventional file name for outputs is outputs.tf (plural). Naming it output.tf (singular) violates standard conventions.

2. Step 2: Understand Terraform file loading

   Terraform loads all .tf files regardless of name for functionality, but standard names improve clarity and teamwork.

3. Final Answer:

   Because the outputs file is misnamed; it should be outputs.tf -> Option B

4. Quick Check:

   outputs file = outputs.tf [OK]

Hint: Outputs file should be named outputs.tf [OK]

Common Mistakes:

• Assuming outputs can be in variables.tf
• Thinking main.tf must have outputs
• Expecting outputs in JSON files

5. You want to organize a large Terraform project by splitting configurations into multiple files. Which naming approach best supports teamwork and maintenance?

hard

A. Use descriptive names like network.tf, compute.tf, variables.tf, outputs.tf

B. Name all files config1.tf, config2.tf, config3.tf for simplicity

C. Put all code in main.tf to avoid confusion

D. Use random names to avoid predictable patterns

Solution

1. Step 1: Consider clarity and teamwork in file naming

   Descriptive file names like network.tf and compute.tf help team members quickly find and understand code sections.

2. Step 2: Evaluate other naming options

   Generic names like config1.tf or random names cause confusion and make maintenance harder. Putting all code in one file reduces clarity.

3. Final Answer:

   Use descriptive names like network.tf, compute.tf, variables.tf, outputs.tf -> Option A

4. Quick Check:

   Descriptive file names improve teamwork [OK]

Hint: Use clear, descriptive file names for easier teamwork [OK]

Common Mistakes:

• Using numbered or random file names
• Putting all code in one file
• Ignoring naming conventions for clarity