Resource documentation reference in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Terraform resource documentation URLs

Which URL correctly points to the official Terraform documentation for the AWS S3 bucket resource?

A https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket

B https://aws.amazon.com/terraform/s3bucket/docs

C https://terraform.io/docs/aws/s3bucket

D https://registry.terraform.io/providers/aws/latest/docs/resources/bucket_s3

💡 Hint

Terraform official docs use registry.terraform.io with provider and resource path.

Terraform resource docs follow the pattern: registry.terraform.io/providers/{provider}/{version}/docs/resources/{resource_name}.

❓ Configuration

intermediate

Identifying correct resource attribute from documentation

You want to configure an AWS EC2 instance with a specific instance type. According to Terraform AWS provider documentation, which attribute sets the instance type?

A type_instance

B instance_type

C ec2_type

D vm_type

💡 Hint

Check the official AWS EC2 instance resource attributes in Terraform docs.

The attribute to specify the instance type is 'instance_type' as per Terraform AWS EC2 resource documentation.

❓ Architecture

advanced

Choosing the correct Terraform resource for a managed database

You want to provision a managed PostgreSQL database on AWS using Terraform. Which resource from the AWS provider documentation should you use?

A aws_rds_cluster

B aws_rds_cluster_instance

C aws_db_instance

D aws_postgresql_instance

💡 Hint

Look for the resource that supports single-instance managed databases.

The 'aws_db_instance' resource is used for single-instance RDS databases including PostgreSQL. 'aws_rds_cluster' and 'aws_rds_cluster_instance' are for clustered databases.

❓ security

advanced

Referencing sensitive attributes in Terraform resource documentation

According to Terraform AWS provider documentation, which attribute of the 'aws_iam_access_key' resource is marked as sensitive and should not be exposed in logs or outputs?

A secret

B key_id

C access_key_id

D secret_access_key

💡 Hint

Sensitive attributes usually contain secret keys or passwords.

The 'secret_access_key' attribute contains the secret part of the IAM access key and is marked sensitive in Terraform documentation.

❓ service_behavior

expert

Understanding lifecycle behavior from Terraform resource documentation

According to Terraform AWS provider documentation, what happens if you change the 'subnet_id' attribute of an 'aws_instance' resource in your configuration and apply it?

A Terraform will destroy the existing instance and create a new one in the new subnet.

B Terraform will update the subnet of the existing instance without downtime.

C Terraform will ignore the change and keep the instance in the original subnet.

D Terraform will throw an error and refuse to apply the change.

💡 Hint

Check the documentation for attributes that force resource replacement.

Changing 'subnet_id' forces a new resource because AWS does not allow moving an instance between subnets. Terraform destroys and recreates the instance.

Practice

1. What is the main purpose of Terraform resource documentation?

easy

A. To explain how to install Terraform on your computer

B. To provide pricing details for cloud services

C. To list all cloud providers available

D. To show how to configure cloud resources correctly

Solution

1. Step 1: Understand the role of resource documentation

   Resource documentation explains how to write code to create and manage cloud resources safely and correctly.

2. Step 2: Identify the correct purpose among options

   Only To show how to configure cloud resources correctly matches this purpose; others talk about pricing, providers, or installation, which are not the main focus.

3. Final Answer:

   To show how to configure cloud resources correctly -> Option D

4. Quick Check:

   Resource documentation = configuration guide [OK]

Hint: Docs explain resource setup, not pricing or installation [OK]

Common Mistakes:

• Confusing documentation with pricing info
• Thinking docs list all providers
• Assuming docs explain Terraform installation

2. Which of the following is the correct way to reference the official Terraform documentation for an AWS S3 bucket resource?

easy

A. https://aws.amazon.com/s3/docs/terraform

B. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket

C. https://terraform.io/docs/aws/s3bucket

D. https://docs.aws.amazon.com/terraform/s3_bucket

Solution

1. Step 1: Identify the official Terraform docs URL pattern

   Terraform official docs use registry.terraform.io with provider and resource paths.

2. Step 2: Match the correct URL format for AWS S3 bucket

   https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket matches the official pattern exactly; others are incorrect or non-existent URLs.

3. Final Answer:

   https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket -> Option B

4. Quick Check:

   Official docs URL = registry.terraform.io [OK]

Hint: Official docs always start with registry.terraform.io [OK]

Common Mistakes:

• Using AWS service docs instead of Terraform docs
• Incorrect URL paths or domains
• Mixing AWS and Terraform documentation URLs

3. Given this Terraform snippet referencing an AWS EC2 instance resource:

resource "aws_instance" "example" {
  ami           = "ami-12345678"
  instance_type = "t2.micro"
  tags = {
    Name = "ExampleInstance"
  }
}

According to the official documentation, what attribute is used to specify the instance type?

medium

A. instance_type

B. type_instance

C. ec2_type

D. instanceSize

Solution

1. Step 1: Check the resource attribute names in the snippet

   The snippet uses 'instance_type' to set the EC2 instance size.

2. Step 2: Confirm with official docs attribute naming

   Official docs confirm 'instance_type' is the correct attribute; others are invalid.

3. Final Answer:

   instance_type -> Option A

4. Quick Check:

   EC2 size attribute = instance_type [OK]

Hint: Look for exact attribute names in official docs [OK]

Common Mistakes:

• Using incorrect attribute names like 'type_instance'
• Guessing attribute names without checking docs
• Confusing AWS console terms with Terraform attributes

4. You wrote this Terraform resource for an AWS S3 bucket:

resource "aws_s3_bucket" "mybucket" {
  bucket = 12345
  acl    = "private"
}

According to the official documentation, what is the error here?

medium

A. The acl attribute is missing

B. The resource type should be aws_bucket_s3

C. The bucket name must be a string, not a number

D. The bucket attribute is optional and can be omitted

Solution

1. Step 1: Check the bucket attribute type in official docs

   The 'bucket' attribute must be a string representing the bucket name.

2. Step 2: Identify the error in the code snippet

   The code uses a number (12345) instead of a string, causing a type error.

3. Final Answer:

   The bucket name must be a string, not a number -> Option C

4. Quick Check:

   Bucket name type = string [OK]

Hint: Bucket names are strings, always use quotes [OK]

Common Mistakes:

• Using numbers instead of strings for bucket names
• Wrong resource type name
• Assuming bucket attribute is optional

5. You want to create a Terraform configuration for an Azure virtual machine. The official documentation shows the resource as azurerm_linux_virtual_machine with attributes like name, resource_group_name, and size. Which of these is the best practice when writing your Terraform code?

hard

A. Always refer to the official resource documentation to use correct attribute names and required fields

B. Guess attribute names based on Azure portal labels to save time

C. Use any attribute names you prefer as Terraform will auto-correct them

D. Skip reading documentation if you have used Azure before

Solution

1. Step 1: Understand the importance of official docs

   Official docs provide accurate, up-to-date attribute names and required fields for resources.

2. Step 2: Evaluate the options for best practice

   Only Always refer to the official resource documentation to use correct attribute names and required fields advises using official docs, ensuring valid and safe infrastructure code.

3. Final Answer:

   Always refer to the official resource documentation to use correct attribute names and required fields -> Option A

4. Quick Check:

   Use official docs = best practice [OK]

Hint: Always check official docs before coding resources [OK]

Common Mistakes:

• Guessing attribute names without docs
• Assuming Terraform auto-corrects mistakes
• Skipping docs due to prior experience