Why testing infrastructure matters in Terraform - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize Terraform before applying changes.

Terraform

terraform [1]

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

Ainit

Bapply

Cplan

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' before initialization causes errors.

Confusing 'plan' with 'init'.

Terraform must be initialized with terraform init to download providers and set up the working directory before applying any changes.

2fill in blank

medium

Complete the code to preview infrastructure changes without applying them.

Terraform

terraform [1]

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

Avalidate

Bplan

Cdestroy

Dapply

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' when only previewing changes.

Confusing 'validate' with planning.

terraform plan shows what changes Terraform will make without applying them. This helps catch mistakes early.

3fill in blank

hard

Fix the error in the Terraform configuration to ensure resource names are unique.

Terraform

resource "aws_instance" "[1]" {
  ami           = "ami-12345678"
  instance_type = "t2.micro"
}

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

Aaws_instance

Binstance

Cwebserver

Dresource

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'resource' as the resource name.

Using the provider name as the resource name.

The resource name must be a unique identifier like webserver. Using generic names like 'resource' or 'aws_instance' causes conflicts.

4fill in blank

hard

Fill both blanks to create a variable with a default value and use it in the resource.

Terraform

variable "[1]" {
  type    = string
  default = "t2.micro"
}

resource "aws_instance" "example" {
  ami           = "ami-12345678"
  instance_type = var.[2]
}

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

Ainstance_type

Bami_id

Dregion

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching variable name and usage.

Using unrelated variable names.

The variable name instance_type is declared and then referenced as var.instance_type in the resource to set the instance type.

5fill in blank

hard

Fill all three blanks to output the public IP of an AWS instance after deployment.

Terraform

output "[1]" {
  value = aws_instance.[2].[3]
}

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

Ainstance_ip

Bexample

Cpublic_ip

Dprivate_ip

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'private_ip' instead of 'public_ip'.

Mismatching resource names.

The output named instance_ip shows the public_ip attribute of the AWS instance named example.

Practice

1. Why is it important to test your Terraform infrastructure before applying changes?

easy

A. To make the code run faster

B. To automatically fix bugs in your cloud provider

C. To reduce the size of your Terraform files

D. To catch errors early and avoid breaking your cloud setup

Solution

1. Step 1: Understand the purpose of testing infrastructure

   Testing helps find mistakes before they affect your live cloud environment.

2. Step 2: Identify the benefit of early error detection

   Finding errors early saves time and prevents service disruptions.

3. Final Answer:

   To catch errors early and avoid breaking your cloud setup -> Option D

4. Quick Check:

   Testing prevents errors = B [OK]

Hint: Testing finds errors before they cause problems [OK]

Common Mistakes:

• Thinking testing makes code faster
• Believing testing reduces file size
• Assuming testing fixes bugs automatically

2. Which Terraform command checks if your configuration files are syntactically valid without applying changes?

easy

A. terraform destroy

B. terraform apply

C. terraform validate

D. terraform output

Solution

1. Step 1: Identify the command for syntax checking

   Terraform validate checks the syntax and structure of configuration files.

2. Step 2: Differentiate from other commands

   Apply changes resources, destroy deletes them, output shows values; only validate checks syntax without changes.

3. Final Answer:

   terraform validate -> Option C

4. Quick Check:

   Syntax check = terraform validate [OK]

Hint: Use 'terraform validate' to check syntax only [OK]

Common Mistakes:

• Using 'terraform apply' to check syntax
• Confusing 'terraform destroy' with validation
• Thinking 'terraform output' validates files

3. Given this Terraform command sequence:

terraform validate
terraform plan
terraform apply

What is the main purpose of running terraform plan before terraform apply?

medium

A. To preview changes without applying them

B. To execute changes immediately

C. To delete existing infrastructure

D. To generate output variables

Solution

1. Step 1: Understand the role of 'terraform plan'

   This command shows what changes Terraform will make without applying them.

2. Step 2: Compare with other commands

   Apply executes changes, destroy deletes resources, output shows values; plan previews changes.

3. Final Answer:

   To preview changes without applying them -> Option A

4. Quick Check:

   Plan previews changes = A [OK]

Hint: Plan shows changes before applying [OK]

Common Mistakes:

• Thinking plan applies changes
• Confusing plan with destroy
• Believing plan generates outputs

4. You run terraform validate and get an error about a missing required argument. What should you do to fix this?

medium

A. Add the missing argument to your Terraform configuration file

B. Run terraform apply to fix the error automatically

C. Delete the Terraform configuration file

D. Ignore the error and continue

Solution

1. Step 1: Understand the error cause

   The error means your config lacks a required setting Terraform needs.

2. Step 2: Correct the configuration

   Add the missing argument to fix the syntax and meet requirements.

3. Final Answer:

   Add the missing argument to your Terraform configuration file -> Option A

4. Quick Check:

   Fix config errors by adding missing parts = C [OK]

Hint: Fix errors by completing config, not skipping steps [OK]

Common Mistakes:

• Trying to apply without fixing errors
• Deleting config files instead of fixing
• Ignoring errors and hoping for the best

5. You want to ensure your Terraform changes won't cause downtime. Which testing approach helps you achieve this before applying changes?

hard

A. Delete all resources and recreate them

B. Run terraform plan to review changes and use a staging environment

C. Skip testing and monitor after deployment

D. Directly run terraform apply on production

Solution

1. Step 1: Identify safe testing practices

   Using terraform plan previews changes; staging environment tests safely without affecting production.

2. Step 2: Avoid risky actions

   Applying directly risks downtime; skipping tests or deleting resources causes outages.

3. Final Answer:

   Run terraform plan to review changes and use a staging environment -> Option B

4. Quick Check:

   Plan + staging = safe testing [OK]

Hint: Use plan and staging to avoid downtime [OK]

Common Mistakes:

• Applying changes directly to production
• Skipping tests before deployment
• Deleting resources instead of updating