Terraform validate for syntax check - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What does terraform validate check in a Terraform configuration?

Choose the correct description of what terraform validate does when run in a Terraform project directory.

A It checks the syntax and internal consistency of Terraform files without contacting any cloud provider.

B It applies the configuration and creates resources in the cloud to verify correctness.

C It only checks if the cloud provider credentials are valid and can be used.

D It runs a full plan and shows the changes that will be applied.

💡 Hint

Think about whether terraform validate needs to connect to the cloud or create resources.

terraform validate checks the syntax and internal consistency of the Terraform files locally. It does not contact any cloud provider or create resources. It helps catch syntax errors before planning or applying.

🧠 Conceptual

intermediate

Which error will terraform validate detect?

Given the following Terraform snippet, what error will terraform validate report?

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

A No error; configuration is valid.

B Error: Missing required provider configuration for AWS.

C Error: Invalid AMI ID format.

D Error: Unsupported argument 'invalid_attribute' for resource 'aws_instance'.

💡 Hint

Check if all attributes used are supported by the resource type.

terraform validate detects unsupported or misspelled attributes in resource blocks. Here, 'invalid_attribute' is not valid for 'aws_instance'.

❓ Configuration

advanced

What is the output of terraform validate for this configuration?

Consider this Terraform configuration snippet:

variable "region" {
  type = string
}

provider "aws" {
  region = var.region
}

Run terraform validate without setting any variable values. What will happen?

A Validation passes but warns about missing variable values.

B Validation passes because variables can be unset during validation.

C Validation fails with a syntax error in the provider block.

D Validation fails with an error about missing required variable 'region'.

💡 Hint

Think about whether terraform validate requires variable values to be set.

terraform validate checks syntax and internal consistency only. It does not require variable values to be set, so validation passes even if variables are unset.

❓ security

advanced

Which terraform validate limitation affects security checks?

Which security-related issue terraform validate cannot detect?

A Exposed secrets in variable default values.

B Syntax errors in Terraform files.

C Misconfigured resource attributes that violate security policies.

D Missing required provider blocks.

💡 Hint

Consider what terraform validate checks and what it does not.

terraform validate checks syntax and structure but does not enforce security policies or detect misconfigurations that violate security best practices.

❓ Architecture

expert

Why might terraform validate succeed but terraform plan fail?

Choose the best explanation for why terraform validate can pass but terraform plan fails with an error.

A <code>terraform validate</code> only checks syntax and does not verify cloud provider connectivity or resource existence, which <code>terraform plan</code> requires.

B <code>terraform validate</code> runs a full plan internally but ignores errors.

C <code>terraform plan</code> uses a different configuration file than <code>terraform validate</code>.

D <code>terraform validate</code> requires credentials but <code>terraform plan</code> does not.

💡 Hint

Think about the difference between syntax checking and planning.

terraform validate only checks syntax and internal consistency locally. terraform plan contacts cloud providers and checks resource states, so it can fail due to connectivity or configuration issues not caught by validation.

Practice

1. What is the main purpose of the terraform validate command?

easy

A. To destroy all existing Terraform-managed infrastructure

B. To check the syntax and internal consistency of Terraform configuration files

C. To deploy resources to the cloud provider

D. To update Terraform to the latest version

Solution

1. Step 1: Understand the role of terraform validate

   This command checks your Terraform files for syntax errors and logical mistakes without applying changes.

2. Step 2: Differentiate from other commands

   Unlike terraform apply or terraform destroy, it does not affect cloud resources.

3. Final Answer:

   To check the syntax and internal consistency of Terraform configuration files -> Option B

4. Quick Check:

   Validate = syntax check [OK]

Hint: Validate means check syntax only, no changes made [OK]

Common Mistakes:

• Confusing validate with apply or destroy
• Thinking validate deploys resources
• Assuming validate updates Terraform version

2. Which of the following is the correct way to run Terraform validation on your configuration files?

easy

A. terraform verify

B. terraform check

C. terraform syntax-check

D. terraform validate

Solution

1. Step 1: Recall the exact command name

   The official command to check syntax is terraform validate.

2. Step 2: Eliminate incorrect options

   Commands like terraform check, terraform syntax-check, and terraform verify do not exist in Terraform CLI.

3. Final Answer:

   terraform validate -> Option D

4. Quick Check:

   Correct command = terraform validate [OK]

Hint: Remember exact command: terraform validate [OK]

Common Mistakes:

• Using non-existent commands like terraform check
• Mixing validate with verify
• Assuming syntax-check is a valid command

3. Given this Terraform snippet, what will terraform validate report?

resource "aws_instance" "example" {
  ami           = "ami-12345678"
  instance_type = "t2.micro"
  tags = {
    Name = "ExampleInstance"
  }
  invalid_attribute = "value"
}

medium

A. Warning: Attribute "invalid_attribute" is deprecated

B. Validation successful, no errors found

C. Error: Unknown argument "invalid_attribute"

D. Error: Missing required attribute "subnet_id"

Solution

1. Step 1: Identify invalid attribute in resource block

   The attribute invalid_attribute is not recognized by the aws_instance resource.

2. Step 2: Understand Terraform validate behavior

   Terraform validate checks for unknown or unsupported arguments and reports errors for them.

3. Final Answer:

   Error: Unknown argument "invalid_attribute" -> Option C

4. Quick Check:

   Unknown attribute causes validation error [OK]

Hint: Unknown attributes cause validation errors [OK]

Common Mistakes:

• Assuming validate ignores unknown attributes
• Confusing warnings with errors
• Expecting missing subnet_id error without VPC context

4. You run terraform validate and get this error: Error: Missing required argument. What should you do to fix it?

medium

A. Add the missing required argument to the resource block

B. Ignore the error and run terraform apply anyway

C. Delete the resource block causing the error

D. Run terraform init to fix the error

Solution

1. Step 1: Understand the error meaning

   The error indicates a required argument is missing in your configuration.

2. Step 2: Correct the configuration

   To fix it, add the required argument with a valid value in the resource block.

3. Final Answer:

   Add the missing required argument to the resource block -> Option A

4. Quick Check:

   Fix missing argument by adding it [OK]

Hint: Add missing required arguments to fix validation errors [OK]

Common Mistakes:

• Ignoring validation errors and applying anyway
• Deleting resources instead of fixing config
• Thinking terraform init fixes syntax errors

5. You have multiple Terraform files in a directory. You want to ensure all files are syntactically correct before applying. Which approach is best?

hard

A. Run terraform validate in the directory containing all files

B. Run terraform apply directly to check for errors

C. Manually open each file and check for syntax errors

D. Run terraform plan without validating first

Solution

1. Step 1: Understand how terraform validate works

   This command checks all Terraform files in the current directory for syntax and internal consistency.

2. Step 2: Compare with other options

   Running terraform apply or terraform plan without validation risks applying broken configs. Manual checking is error-prone and inefficient.

3. Final Answer:

   Run terraform validate in the directory containing all files -> Option A

4. Quick Check:

   Validate all files together before apply [OK]

Hint: Validate entire directory before applying changes [OK]

Common Mistakes:

• Skipping validation and applying directly
• Manually checking files instead of automated validation
• Confusing plan with validation