Why HCL matters as Terraform's language - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Terraform provider block using HCL.

Terraform

provider "aws" {
  region = [1]
}

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

A"us-west-2"

Bus-west-2

C"aws-region"

Dregion

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to put quotes around the region name

Using an undefined variable name without quotes

The region value must be a string in quotes in HCL, so "us-west-2" is correct.

2fill in blank

medium

Complete the code to declare a Terraform variable with a default value in HCL.

Terraform

variable "instance_type" {
  type    = string
  default = [1]
}

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

At2.micro

Bt2_micro

Cmicro

D"t2.micro"

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around the default string value

Using underscores instead of dots in instance type

Default values for variables in HCL must be strings enclosed in quotes, so "t2.micro" is correct.

3fill in blank

hard

Fix the error in the Terraform resource block by completing the missing attribute value.

Terraform

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

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

A"ami-123456"

Bami-123456

Cami_123456

D123456

Attempts:

3 left

💡 Hint

Common Mistakes

Using AMI ID without quotes

Replacing dashes with underscores

The AMI ID must be a string in quotes in HCL, so "ami-123456" is correct.

4fill in blank

hard

Fill both blanks to create a Terraform output that shows the instance's public IP.

Terraform

output "instance_ip" {
  value = [1].[2]
}

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

Aaws_instance.example

Bpublic_ip

Cprivate_ip

Dinstance_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using private_ip instead of public_ip

Omitting the resource name before the attribute

The output value must reference the resource name and the attribute public_ip to show the instance's public IP.

5fill in blank

hard

Fill all three blanks to define a Terraform resource with tags using HCL.

Terraform

resource "aws_s3_bucket" "bucket" {
  bucket = [1]
  acl    = [2]
  tags = {
    Name        = [3]
  }
}

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

A"my-bucket"

B"private"

C"MyBucket"

D"public-read"

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around string values

Using incorrect ACL values

The bucket name, ACL, and tag values must be strings in quotes. The bucket is named "my-bucket", ACL is "private", and tag Name is "MyBucket".

Practice

1. Why is HCL (HashiCorp Configuration Language) important for Terraform users?

easy

A. It makes cloud infrastructure code easy to read and write.

B. It is a programming language for building mobile apps.

C. It replaces the need for cloud providers.

D. It is used only for monitoring cloud resources.

Solution

1. Step 1: Understand HCL's purpose

   HCL is designed to be simple and clear for writing infrastructure code.

2. Step 2: Compare options

   Options A, B, and C describe unrelated uses or incorrect roles of HCL.

3. Final Answer:

   It makes cloud infrastructure code easy to read and write. -> Option A

4. Quick Check:

   HCL simplifies infrastructure code = D [OK]

Hint: HCL is for clear cloud setup code, not app or monitoring [OK]

Common Mistakes:

• Confusing HCL with general programming languages
• Thinking HCL replaces cloud providers
• Assuming HCL is for monitoring only

2. Which of the following is the correct way to define a variable in HCL for Terraform?

easy

A. var region = "us-west-1"

B. define region = "us-west-1"

C. variable "region" { default = "us-west-1" }

D. set variable region to "us-west-1"

Solution

1. Step 1: Recall HCL variable syntax

   In HCL, variables are declared using the keyword 'variable' followed by the name in quotes and a block with attributes.

2. Step 2: Check each option

   variable "region" { default = "us-west-1" } matches the correct HCL syntax. Options A, C, and D use invalid or non-HCL syntax.

3. Final Answer:

   variable "region" { default = "us-west-1" } -> Option C

4. Quick Check:

   HCL variable uses 'variable' block = B [OK]

Hint: HCL variables use 'variable' blocks with quoted names [OK]

Common Mistakes:

• Using programming language variable syntax
• Omitting quotes around variable names
• Writing variables as simple assignments

3. Given this HCL snippet:

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

What does this code do when applied with Terraform?

medium

A. Updates the AWS CLI configuration.

B. Creates an AWS EC2 instance with the specified AMI and type.

C. Deletes an existing AWS EC2 instance.

D. Creates a storage bucket in AWS.

Solution

1. Step 1: Identify resource type and name

   The code defines a resource of type 'aws_instance' named 'web', which means an EC2 instance.

2. Step 2: Understand resource attributes

   The 'ami' and 'instance_type' specify the machine image and size for the EC2 instance.

3. Final Answer:

   Creates an AWS EC2 instance with the specified AMI and type. -> Option B

4. Quick Check:

   Resource block creates EC2 instance = C [OK]

Hint: Resource blocks define cloud resources to create [OK]

Common Mistakes:

• Confusing resource creation with deletion
• Mixing resource types (instance vs bucket)
• Assuming it changes CLI settings

4. Identify the error in this HCL snippet:

resource "aws_s3_bucket" "mybucket" {
  bucket = my-bucket-name
  acl    = "private"
}

medium

A. The bucket name should be in quotes.

B. The resource type is incorrect.

C. The acl value must be a number.

D. The resource name cannot have uppercase letters.

Solution

1. Step 1: Check bucket attribute syntax

   In HCL, string values must be enclosed in quotes. 'my-bucket-name' is missing quotes.

2. Step 2: Verify other attributes

   The resource type and acl value are correct; acl is a string and resource name is valid.

3. Final Answer:

   The bucket name should be in quotes. -> Option A

4. Quick Check:

   String values need quotes = A [OK]

Hint: Always quote string values in HCL [OK]

Common Mistakes:

• Forgetting quotes around strings
• Assuming acl needs a number
• Thinking resource names have case restrictions

5. You want to share your Terraform cloud setup with your team so everyone can understand and update it easily. Why is using HCL beneficial in this case?

hard

A. HCL runs Terraform commands faster than other languages.

B. HCL automatically fixes errors without user input.

C. HCL encrypts your cloud credentials for security.

D. HCL is human-readable and structured, making collaboration simple.

Solution

1. Step 1: Understand collaboration needs

   Teams need clear, easy-to-read code to share and update cloud setups without confusion.

2. Step 2: Evaluate HCL features

   HCL is designed to be human-readable and structured, which helps teams understand and maintain code together.

3. Step 3: Eliminate incorrect options

   HCL does not auto-fix errors, encrypt credentials, or affect command speed directly.

4. Final Answer:

   HCL is human-readable and structured, making collaboration simple. -> Option D

5. Quick Check:

   Readable code helps team collaboration = A [OK]

Hint: Readable code means easier team work [OK]

Common Mistakes:

• Thinking HCL auto-corrects errors
• Confusing HCL with security tools
• Assuming HCL affects Terraform speed