Querying existing resources in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Terraform data source output

You use a Terraform data source to query an existing AWS VPC by its ID. What will be the value of data.aws_vpc.selected_vpc.cidr_block after applying this configuration?

Terraform

data "aws_vpc" "selected_vpc" {
  id = "vpc-0abc123def456ghij"
}

output "vpc_cidr" {
  value = data.aws_vpc.selected_vpc.cidr_block
}

A "vpc-0abc123def456ghij"

B "10.0.0.0/16"

C null

D SyntaxError

💡 Hint

The data source fetches existing resource attributes, including the CIDR block.

The aws_vpc data source returns the attributes of the existing VPC identified by the given ID. The cidr_block attribute contains the IP range of the VPC, such as "10.0.0.0/16".

🧠 Conceptual

intermediate

Purpose of Terraform data sources

What is the main purpose of using a Terraform data source when working with existing cloud resources?

A To query and reference existing cloud resources without creating them

B To create new cloud resources with predefined settings

C To delete existing cloud resources safely

D To automatically update resource configurations

💡 Hint

Think about how Terraform can use information about resources it did not create.

Terraform data sources allow you to look up and use information about existing resources in your cloud environment without managing their lifecycle.

❓ Configuration

advanced

Correctly querying an existing AWS subnet by tag

Which Terraform configuration correctly queries an existing AWS subnet with the tag Environment=Production and outputs its subnet ID?

A

data "aws_subnet_ids" "prod_subnets" {
  filter {
    name   = "tag:Environment"
    values = ["Production"]
  }
}

output "subnet_id" {
  value = data.aws_subnet_ids.prod_subnets.ids[0]
}

B

data "aws_subnet_ids" "prod_subnets" {
  tags = {
    Environment = "Production"
  }
}

output "subnet_id" {
  value = data.aws_subnet_ids.prod_subnets.ids[0]
}

C

data "aws_subnet" "prod_subnet" {
  tags = {
    Environment = "Production"
  }
}

output "subnet_id" {
  value = data.aws_subnet.prod_subnet.id
}

D

data "aws_subnet" "prod_subnet" {
  filter {
    name   = "tag:Environment"
    values = ["Production"]
  }
}

output "subnet_id" {
  value = data.aws_subnet.prod_subnet.id
}

💡 Hint

Use the correct data source type and filter syntax for multiple subnets.

The aws_subnet_ids data source supports filtering by tags using the filter block. It returns a list of subnet IDs matching the filter. Option A correctly uses filter with name and values to find subnets tagged with Environment=Production.

❓ security

advanced

Security implications of querying existing resources

When using Terraform data sources to query existing cloud resources, what is a key security consideration?

A Data sources automatically grant Terraform full access to modify the queried resources

B Data sources expose sensitive resource credentials in the Terraform state by default

C Terraform must have appropriate read permissions to access the existing resources' metadata

D Using data sources disables encryption for the queried resources

💡 Hint

Think about what permissions Terraform needs to read existing resource information.

Terraform requires read permissions to query existing resources via data sources. It does not get write or modify permissions automatically. Proper IAM roles or policies must be assigned to allow safe querying.

❓ Architecture

expert

Designing Terraform to query multi-cloud existing resources

You need to write a Terraform configuration that queries existing virtual networks from both AWS and Azure in the same deployment. Which approach correctly supports querying both cloud providers' existing networks?

A Use the <code>terraform_remote_state</code> data source to import network IDs from AWS and Azure

B Use a single <code>aws_vpc</code> data source with filters for both AWS and Azure network IDs

C Use the <code>null_resource</code> to run scripts that query networks from both clouds

D Use separate provider blocks for AWS and Azure, then use respective data sources <code>aws_vpc</code> and <code>azurerm_virtual_network</code> to query existing networks

💡 Hint

Terraform supports multiple providers in one configuration.

Terraform can manage multiple cloud providers by defining multiple provider blocks. To query existing resources from AWS and Azure, use their respective data sources under their providers. Option D correctly separates providers and uses the correct data sources.