Creating your first resource in Terraform - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Terraform resource blocks

Which of the following Terraform resource blocks correctly creates an AWS S3 bucket named my-unique-bucket-123?

A

resource "aws_s3_bucket" "bucket" {
  name = "my-unique-bucket-123"
  acl  = "public-read"
}

B

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

C

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

D

}
"etavirp" =    lca  
"321-tekcub-euqinu-ym" = tekcub  
{ "tekcub" "tekcub_3s_swa" ecruoser

💡 Hint

Look for the correct attribute name to specify the bucket's name and proper string syntax.

In Terraform, the AWS S3 bucket resource requires the attribute bucket to specify the bucket name as a string. Option C uses the correct attribute and syntax. Option C uses name which is invalid. Option C uses bucket_name which is not recognized. Option C misses quotes around the bucket name, causing a syntax error.

❓ Configuration

intermediate

Terraform variable usage in resource creation

Given the variable bucket_name defined as "example-bucket-456", which resource block correctly uses this variable to create an AWS S3 bucket?

Terraform

variable "bucket_name" {
  type    = string
  default = "example-bucket-456"
}

A

resource "aws_s3_bucket" "bucket" {
  bucket = var.bucket_name
  acl    = "private"
}

B

resource "aws_s3_bucket" "bucket" {
  bucket = "var.bucket_name"
  acl    = "private"
}

C

resource "aws_s3_bucket" "bucket" {
  bucket = "${var.bucket_name}"
  acl    = "private"
}

D

resource "aws_s3_bucket" "bucket" {
  bucket = $var.bucket_name
  acl    = "private"
}

💡 Hint

Terraform variables are referenced without quotes and without interpolation syntax in modern versions.

Option A correctly references the variable var.bucket_name without quotes or interpolation. Option A treats it as a string literal. Option A uses deprecated interpolation syntax which is valid but deprecated in Terraform 0.12+. Option A uses shell-style variable syntax which is invalid.

❓ Architecture

advanced

Choosing the right resource for infrastructure setup

You want to create a virtual machine in AWS using Terraform. Which resource type should you use to create an EC2 instance?

A aws_virtual_machine

B aws_ec2_machine

C aws_vm

D aws_instance

💡 Hint

Look for the official Terraform AWS provider resource name for EC2 instances.

The correct resource type to create an EC2 instance in Terraform is aws_instance. The other options are invalid resource types and will cause errors.

❓ security

advanced

Securing AWS S3 bucket with Terraform

Which Terraform resource block correctly creates an AWS S3 bucket with public access blocked?

A

resource "aws_s3_bucket" "bucket" {
  bucket = "secure-bucket-789"
  acl    = "private"

  public_access_block = true
}

B

resource "aws_s3_bucket" "bucket" {
  bucket = "secure-bucket-789"
  acl    = "private"

  public_access_block {
    block_public_acls       = true
    block_public_policy     = true
    ignore_public_acls      = true
    restrict_public_buckets = true
  }
}

C

resource "aws_s3_bucket" "bucket" {
  bucket = "secure-bucket-789"
  acl    = "private"

  block_public_acls       = true
  block_public_policy     = true
  ignore_public_acls      = true
  restrict_public_buckets = true
}

D

resource "aws_s3_bucket" "bucket" {
  bucket = "secure-bucket-789"
  acl    = "private"

  block_public_access = true
}

💡 Hint

Public access block settings are configured inside a nested block named public_access_block.

Option B correctly uses the nested public_access_block block with all required settings to block public access. Option B tries to set these as top-level attributes which is invalid. Options B and D use incorrect attribute names causing errors.

❓ service_behavior

expert

Terraform apply behavior with resource changes

You have a Terraform configuration that creates an AWS S3 bucket named my-bucket. You change the bucket name in the configuration to my-new-bucket and run terraform apply. What will happen?

Terraform

resource "aws_s3_bucket" "bucket" {
  bucket = "my-new-bucket"
  acl    = "private"
}

A Terraform will delete the old bucket named 'my-bucket' and create a new bucket named 'my-new-bucket'.

B Terraform will rename the existing bucket from 'my-bucket' to 'my-new-bucket' without downtime.

C Terraform will update the bucket name in place without deleting the old bucket.

D Terraform will throw an error because bucket names cannot be changed.

💡 Hint

Consider how Terraform handles changes to resource identifiers that are immutable in the cloud provider.

Bucket names in AWS S3 are immutable. Changing the bucket name in Terraform causes Terraform to destroy the old bucket and create a new one. It cannot rename buckets in place. Therefore, option A is correct. Options A and C are incorrect because renaming is not supported. Option A is incorrect because Terraform does not throw an error but performs delete and create.