Querying existing resources in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the data block in Terraform?

The data block is used to query and read information about existing resources that are not managed by the current Terraform configuration.

beginner

How do you reference an existing AWS VPC by its ID in Terraform?

You use a data block like this:

data "aws_vpc" "example" {
  id = "vpc-12345678"
}

This lets you access its attributes in your configuration.

intermediate

Why should you use data sources instead of hardcoding resource attributes?

Using data sources keeps your configuration flexible and up-to-date by dynamically fetching current resource details instead of relying on fixed values that may change.

intermediate

What happens if the queried resource does not exist when using a Terraform data source?

Terraform will return an error during plan or apply because it cannot find the resource to read its attributes.

beginner

Can you modify existing resources using Terraform data sources?

No, data sources only read information. To modify resources, you must use resource blocks managed by Terraform.

What Terraform block is used to query existing resources?

A output

B resource

C data

D variable

The data block is specifically designed to query existing resources.

Which of the following is TRUE about Terraform data sources?

A They read information from existing resources.

B They store variables.

C They delete resources.

D They can create new resources.

Data sources only read information from existing resources; they do not create or delete resources.

If a data source references a non-existent resource, what will happen?

A Terraform will create the resource automatically.

B Terraform will ignore the missing resource.

C Terraform will skip the data source silently.

D Terraform will return an error during plan or apply.

Terraform requires the resource to exist to read its data; otherwise, it errors out.

How do you access an attribute from a data source in Terraform?

A Using <code>data.<resource_type>.<name>.<attribute></code>

B Using <code>resource.<name>.<attribute></code>

C Using <code>var.<attribute></code>

D Using <code>output.<attribute></code>

Attributes from data sources are accessed with the syntax data....

Why is it better to use data sources instead of hardcoding resource IDs?

A Data sources are faster to deploy.

B Data sources keep configurations flexible and accurate.

C Data sources automatically update resource attributes.

D Data sources create new resources.

Using data sources helps keep your configuration flexible and accurate by fetching current resource details.

Explain how Terraform data sources help you work with existing cloud resources.

Think about how you can read info without managing the resource.

Describe the difference between Terraform resource blocks and data blocks.

One manages, the other queries.

Practice

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

easy

A. To create new cloud resources from scratch

B. To delete resources that are no longer needed

C. To query and use existing resources created outside the current configuration

D. To define variables for user input

Solution

1. Step 1: Understand the role of data blocks

   data blocks in Terraform are used to look up or query existing resources that were created outside the current Terraform configuration or by other means.

2. Step 2: Differentiate from resource creation

   Unlike resource blocks that create new infrastructure, data blocks only read information without making changes.

3. Final Answer:

   To query and use existing resources created outside the current configuration -> Option C

4. Quick Check:

   Data blocks read existing resources = B [OK]

Hint: Data blocks read existing resources, not create them [OK]

Common Mistakes:

• Confusing data blocks with resource creation
• Thinking data blocks delete resources
• Using data blocks to define variables

2. Which of the following is the correct syntax to query an existing AWS VPC by its ID using a data block?

easy

A. data "aws_vpc" "example" { id = "vpc-123456" }

B. resource "aws_vpc" "example" { id = "vpc-123456" }

C. data "aws_vpc" "example" { vpc_id = "vpc-123456" }

D. data "aws_vpc" "example" { name = "vpc-123456" }

Solution

1. Step 1: Identify correct data block syntax

   The correct syntax uses data followed by the provider resource type and a name, then inside the block the attribute id is used to specify the VPC ID.

2. Step 2: Check attribute correctness

   The attribute to specify the VPC ID is id, not vpc_id or name.

3. Final Answer:

   data "aws_vpc" "example" { id = "vpc-123456" } -> Option A

4. Quick Check:

   Use id attribute in data block = A [OK]

Hint: Use 'id' attribute inside data block to query by resource ID [OK]

Common Mistakes:

• Using resource block instead of data block
• Using wrong attribute names like vpc_id
• Confusing resource creation syntax with data query

3. Given this Terraform data block:

data "aws_subnet" "selected" {
  filter {
    name   = "tag:Name"
    values = ["public-subnet"]
  }
}

What will data.aws_subnet.selected.id return?

medium

A. The ID of the subnet tagged with Name=public-subnet

B. A list of all subnet IDs in the AWS account

C. An error because filter is not allowed in data blocks

D. The name of the subnet instead of the ID

Solution

1. Step 1: Understand the filter block in data source

   The filter block selects resources matching the tag Name=public-subnet.

2. Step 2: Identify the returned attribute

   data.aws_subnet.selected.id returns the ID of the matched subnet, not a list or name.

3. Final Answer:

   The ID of the subnet tagged with Name=public-subnet -> Option A

4. Quick Check:

   Filter selects subnet by tag, id returns its ID = D [OK]

Hint: Filter selects resource; .id returns its ID [OK]

Common Mistakes:

• Thinking filter returns multiple resources
• Assuming .id returns name or list
• Believing filter is invalid in data blocks

4. You wrote this data block to query an existing AWS security group:

data "aws_security_group" "example" {
  name = "my-sg"
}

But Terraform returns an error: "Multiple security groups found with name 'my-sg'". What is the best fix?

medium

A. Remove the name attribute to query all security groups

B. Add a filter block with more specific criteria to narrow the search

C. Change data to resource to create a new security group

D. Rename the security group in AWS to have a unique name

Solution

1. Step 1: Understand the error cause

   The error means multiple security groups share the same name, so Terraform cannot pick one.

2. Step 2: Narrow the query with filters

   Adding a filter block with more attributes (like VPC ID) helps select exactly one security group.

3. Final Answer:

   Add a filter block with more specific criteria to narrow the search -> Option B

4. Quick Check:

   Use filters to avoid multiple matches = C [OK]

Hint: Use filters to narrow data queries when duplicates exist [OK]

Common Mistakes:

• Switching to resource block instead of filtering
• Removing name attribute causing ambiguous query
• Changing AWS resource names unnecessarily

5. You want to use an existing AWS IAM role in your Terraform configuration, but only know its ARN. Which is the best way to query this role using a data block?

hard

A. Use data "aws_iam_role" "existing" { id = "my-role" }

B. Use data "aws_iam_role" "existing" { name = "my-role" } and ignore ARN

C. Use resource "aws_iam_role" "existing" { arn = "arn:aws:iam::123456789012:role/my-role" }

D. Use data "aws_iam_role" "existing" { arn = "arn:aws:iam::123456789012:role/my-role" }

Solution

1. Step 1: Identify correct attribute to query by ARN

   The aws_iam_role data source supports querying by arn attribute to find the exact role.

2. Step 2: Avoid using resource block or wrong attributes

   Using resource block tries to create a new role, which is incorrect. Using name may fail if multiple roles share the name. id is not a valid attribute here.

3. Final Answer:

   Use data "aws_iam_role" "existing" { arn = "arn:aws:iam::123456789012:role/my-role" } -> Option D

4. Quick Check:

   Query IAM role by ARN using data block = A [OK]

Hint: Query IAM role by ARN attribute in data block [OK]

Common Mistakes:

• Using resource block instead of data block
• Querying by name when ARN is known
• Using invalid attribute 'id' for IAM role