Creating your first resource in Terraform - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an AWS S3 bucket resource with the name 'my_bucket'.

Terraform

resource "aws_s3_bucket" "[1]" {
  bucket = "my-unique-bucket-name"
}

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

As3_bucket

Bbucket_name

Cmy_bucket

Dbucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using the actual bucket name instead of a resource identifier.

Using invalid characters or spaces in the resource name.

The resource name inside quotes is an identifier used to reference this resource in Terraform. 'my_bucket' is a clear and valid name.

2fill in blank

medium

Complete the code to specify the AWS provider version in Terraform.

Terraform

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "[1]"
    }
  }
}

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

A"~> 4.0"

B"^ 4.0"

C"~> 2.0"

D"= 3.0"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '^ 4.0' which has invalid syntax (space after ^).

Using exact version '=' which is too restrictive.

The version constraint '~> 4.0' means any version from 4.0 up to but not including 5.0, which is a common best practice.

3fill in blank

hard

Fix the error in the resource block by completing the missing attribute for the AWS EC2 instance type.

Terraform

resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0"
  [1] = "t2.micro"
}

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

Avm_type

Binstance_type

Cec2_type

Dtype_instance

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect attribute names like 'type_instance' or 'vm_type'.

Omitting the instance type attribute entirely.

The correct attribute to specify the EC2 instance size is 'instance_type'.

4fill in blank

hard

Fill both blanks to create a resource block for an AWS security group with a description and a name.

Terraform

resource "aws_security_group" "[1]" {
  name        = "[2]"
  description = "Allow SSH access"
}

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

Assh_sg

Bweb_sg

Cssh_security_group

Dssh-access

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing resource name and AWS resource name.

Using spaces or invalid characters in names.

The resource name is 'ssh_sg' and the security group name is 'ssh-access', which clearly describe the purpose.

5fill in blank

hard

Fill all three blanks to define an AWS IAM user resource with a name, path, and tags.

Terraform

resource "aws_iam_user" "[1]" {
  name = "[2]"
  path = "[3]"
  tags = {
    Environment = "Dev"
  }
}

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

Adev_user

Bdeveloper

C/developers/

D/dev/

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing resource name with IAM user name.

Using paths without slashes or invalid characters.

The resource name is 'dev_user', the IAM user name is 'developer', and the path is '/dev/' which organizes users under the dev folder.

Practice

1. What is the main purpose of a resource block in Terraform?

easy

A. To write a script to run on a server

B. To define a cloud component to create and manage

C. To store variables for reuse

D. To output values after deployment

Solution

1. Step 1: Understand Terraform resource blocks

   A resource block tells Terraform what cloud component to create, like a server or database.

2. Step 2: Differentiate resource from other blocks

   Variables store data, outputs show results, scripts run commands. Only resource creates infrastructure.

3. Final Answer:

   To define a cloud component to create and manage -> Option B

4. Quick Check:

   Resource block = cloud component definition [OK]

Hint: Resource blocks create cloud parts, not scripts or variables [OK]

Common Mistakes:

• Confusing resource with variable or output blocks
• Thinking resource runs code on servers
• Assuming resource stores data only

2. Which of the following is the correct syntax to create an AWS S3 bucket resource named my_bucket in Terraform?

easy

A. resource "my_bucket" "aws_s3_bucket" {}

B. resource aws_s3_bucket my_bucket {}

C. resource "aws_s3_bucket" {}

D. resource "aws_s3_bucket" "my_bucket" {}

Solution

1. Step 1: Recall Terraform resource syntax

   The syntax is: resource "resource_type" "resource_name" { ... } with quotes around type and name.

2. Step 2: Match correct syntax

   resource "aws_s3_bucket" "my_bucket" {} matches this exactly with resource type aws_s3_bucket and name my_bucket in quotes.

3. Final Answer:

   resource "aws_s3_bucket" "my_bucket" {} -> Option D

4. Quick Check:

   Correct resource syntax uses quotes for type and name [OK]

Hint: Resource type and name must be in quotes inside resource block [OK]

Common Mistakes:

• Omitting quotes around resource type or name
• Swapping resource type and name order
• Leaving resource name empty

3. Given this Terraform resource block:

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

What will Terraform do when you run terraform apply?

medium

A. Output the AMI ID without creating resources

B. Delete all EC2 instances in the account

C. Create an AWS EC2 instance with the specified AMI and type

D. Create an S3 bucket named example

Solution

1. Step 1: Identify resource type and attributes

   The resource is aws_instance named example with AMI and instance type set.

2. Step 2: Understand Terraform apply behavior

   Terraform will create the EC2 instance with given AMI and instance type when applied.

3. Final Answer:

   Create an AWS EC2 instance with the specified AMI and type -> Option C

4. Quick Check:

   Resource block creates EC2 instance as defined [OK]

Hint: Resource type aws_instance creates EC2 instances [OK]

Common Mistakes:

• Confusing resource type with S3 bucket
• Thinking terraform apply deletes resources by default
• Assuming terraform only outputs values

4. You wrote this Terraform resource:

resource "aws_s3_bucket" "mybucket" {
  bucket = mybucket
}

When running terraform plan, you get an error. What is the problem?

medium

A. The bucket name must be a quoted string, not a bare word

B. Resource type aws_s3_bucket does not exist

C. Resource name cannot be mybucket

D. Missing required provider block

Solution

1. Step 1: Check bucket attribute syntax

   The bucket attribute expects a string value, so it must be in quotes like "mybucket".

2. Step 2: Identify error cause

   Using bare word mybucket without quotes causes syntax error in Terraform.

3. Final Answer:

   The bucket name must be a quoted string, not a bare word -> Option A

4. Quick Check:

   String values require quotes in Terraform config [OK]

Hint: Always quote string values in resource attributes [OK]

Common Mistakes:

• Forgetting quotes around string values
• Assuming resource name restrictions cause error
• Thinking provider block is missing for this error

5. You want to create two AWS EC2 instances with Terraform using the same configuration but different names. Which is the best way to do this?

hard

A. Use a resource block with a count or for_each to create multiple instances

B. Use a single resource block with a list of names in the bucket attribute

C. Create one resource block and duplicate it manually in the config file

D. Write two separate resource blocks with different names

Solution

1. Step 1: Understand multiple resource creation methods

   You can create multiple similar resources by repeating blocks or using count/for_each.

2. Step 2: Identify best practice

   Using count or for_each is efficient and scalable compared to manual duplication or separate blocks.

3. Final Answer:

   Use a resource block with a count or for_each to create multiple instances -> Option A

4. Quick Check:

   count/for_each = best for multiple similar resources [OK]

Hint: Use count or for_each for multiple similar resources [OK]

Common Mistakes:

• Manually duplicating resource blocks causes errors
• Trying to pass list to unrelated attribute
• Not using count or for_each for multiple resources