Resource block syntax in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare an AWS S3 bucket resource.

Terraform

resource "aws_s3_bucket" [1] {
  bucket = "my-bucket"
  acl    = "private"
}

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

Amy_bucket_name

Bmy_bucket_resource

Cmy_bucket_id

Dmy_bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using the bucket name as the resource name directly.

Using invalid characters in the resource name.

The resource block requires a resource name identifier after the resource type. This name is a local name used within Terraform configuration.

2fill in blank

medium

Complete the code to specify the resource type for an AWS EC2 instance.

Terraform

resource [1] "web_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
}

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

Aaws_instance

Baws_vm

Cec2_instance

Daws_ec2

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect resource type names like aws_ec2 or aws_vm.

Confusing resource type with resource name.

The correct resource type for an EC2 instance in Terraform AWS provider is aws_instance.

3fill in blank

hard

Fix the error in the resource block by completing the missing keyword.

Terraform

resource "aws_s3_bucket" "my_bucket" [1] 
  bucket = "my-bucket"
  acl    = "private"
}

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

Abegin

B{

C(

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses or other keywords instead of curly braces.

Omitting the opening brace entirely.

The resource block must start with an opening curly brace { after the resource name.

4fill in blank

hard

Fill both blanks to complete the resource block for an AWS security group.

Terraform

resource [1] [2] {
  name        = "allow_ssh"
  description = "Allow SSH inbound traffic"
  vpc_id      = var.vpc_id
}

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

Aaws_security_group

Baws_sg

Callow_ssh

Dsecurity_group

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect resource types like aws_sg.

Using resource type as the resource name.

The resource type is aws_security_group and the resource name is a local identifier like allow_ssh.

5fill in blank

hard

Fill both blanks to complete the resource block for an AWS IAM role.

Terraform

resource [1] [2] {
  name = "example_role"
  assume_role_policy = data.aws_iam_policy_document.assume_role_policy.json
}

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

Aaws_iam_role

Bexample_role

C{

Daws_role

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect resource types like aws_role.

Omitting the opening brace or using wrong symbols.

The resource type is aws_iam_role, the resource name is example_role, and the block starts with {.

Practice

1. What is the correct way to start a resource block in Terraform?

easy

A. resource "aws_instance" { example }

B. resource aws_instance example { }

C. resource "example" "aws_instance" { }

D. resource "aws_instance" "example" { }

Solution

1. Step 1: Understand resource block syntax

   A resource block starts with the keyword resource, followed by the resource type in quotes, then the resource name in quotes.

2. Step 2: Match the correct syntax

   resource "aws_instance" "example" { } correctly uses resource "aws_instance" "example" { }, which matches the required syntax.

3. Final Answer:

   resource "aws_instance" "example" { } -> Option D

4. Quick Check:

   Resource block syntax = resource "type" "name" { } [OK]

Hint: Resource block always uses resource "type" "name" [OK]

Common Mistakes:

• Omitting quotes around type or name
• Swapping type and name order
• Using braces incorrectly

2. Which of the following is a valid property assignment inside a Terraform resource block?

easy

A. instance_type = t2.micro

B. instance_type => "t2.micro"

C. instance_type = "t2.micro"

D. instance_type: "t2.micro"

Solution

1. Step 1: Identify correct property syntax

   Terraform uses = to assign values, and string values must be in quotes.

2. Step 2: Check each option

   instance_type = "t2.micro" uses instance_type = "t2.micro", which is correct. instance_type = t2.micro misses quotes, B and C use invalid assignment symbols.

3. Final Answer:

   instance_type = "t2.micro" -> Option C

4. Quick Check:

   Property assignment uses = and quotes for strings [OK]

Hint: Use = and quotes for string values inside resource blocks [OK]

Common Mistakes:

• Forgetting quotes around string values
• Using colon or arrow instead of =
• Missing equal sign

3. Given this resource block snippet, what will Terraform create?

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

medium

A. An S3 bucket named "mybucket" with public access

B. An S3 bucket named "my-unique-bucket-123" with private access

C. An S3 bucket named "aws_s3_bucket" with private access

D. A storage container with default public access

Solution

1. Step 1: Identify resource type and name

   The resource type is aws_s3_bucket, and the resource name is mybucket. The bucket property sets the actual bucket name.

2. Step 2: Understand properties

   The bucket property sets the bucket's real name to "my-unique-bucket-123". The acl is set to "private", meaning no public access.

3. Final Answer:

   An S3 bucket named "my-unique-bucket-123" with private access -> Option B

4. Quick Check:

   Bucket name = property value, ACL = private [OK]

Hint: Bucket name is from bucket property, not resource name [OK]

Common Mistakes:

• Confusing resource name with actual bucket name
• Assuming default ACL is public
• Ignoring property values inside the block

4. Identify the error in this Terraform resource block:

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

medium

A. Missing quotes around the instance_type value

B. Resource block missing closing brace

C. Incorrect resource type name

D. Missing resource name

Solution

1. Step 1: Check property value syntax

   The instance_type property value t2.micro is missing quotes, which is required for string values.

2. Step 2: Verify block structure

   The resource block has correct braces and resource type/name, so no errors there.

3. Final Answer:

   Missing quotes around the instance_type value -> Option A

4. Quick Check:

   String values must be quoted [OK]

Hint: Always quote string values inside resource blocks [OK]

Common Mistakes:

• Forgetting quotes around string properties
• Assuming braces are optional
• Mixing resource type and name order

5. You want to create two AWS EC2 instances with different names but the same AMI and instance type using resource blocks. Which is the best way to write this in Terraform?

hard

A. resource "aws_instance" "web1" {
ami = "ami-abc123"
instance_type = "t2.micro"
}
resource "aws_instance" "web2" {
ami = "ami-abc123"
instance_type = "t2.micro"
}

B. resource "aws_instance" "web" {
count = 2
ami = "ami-abc123"
instance_type = "t2.micro"
}

C. resource "aws_instance" "web" {
ami = "ami-abc123"
instance_type = "t2.micro"
name = ["web1", "web2"]
}

D. resource "aws_instance" "web" {
ami = "ami-abc123"
instance_type = "t2.micro"
for_each = ["web1", "web2"]
}

Solution

1. Step 1: Understand resource naming and duplication

   Each resource block must have a unique name.

   resource "aws_instance" "web1" {
     ami = "ami-abc123"
     instance_type = "t2.micro"
   }
   resource "aws_instance" "web2" {
     ami = "ami-abc123"
     instance_type = "t2.micro"
   }

   defines two separate resources with different names.

2. Step 2: Evaluate other options

   resource "aws_instance" "web" {
     count = 2
     ami = "ami-abc123"
     instance_type = "t2.micro"
   }

   uses count but does not differentiate names.

   resource "aws_instance" "web" {
     ami = "ami-abc123"
     instance_type = "t2.micro"
     name = ["web1", "web2"]
   }

   tries to assign a list to name property, which is invalid.

   resource "aws_instance" "web" {
     ami = "ami-abc123"
     instance_type = "t2.micro"
     for_each = ["web1", "web2"]
   }

   uses for_each incorrectly without mapping names.

3. Final Answer:

   Define two separate resource blocks with unique names -> Option A

4. Quick Check:

   Unique resource names needed for multiple instances [OK]

Hint: Use separate resource blocks with unique names for multiple instances [OK]

Common Mistakes:

• Using count without unique names
• Assigning list to single property
• Misusing for_each without proper keys