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.