Data source dependencies in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Identify the correct data source dependency resolution

Given the Terraform configuration below, which option correctly describes the order in which Terraform resolves the data sources?

Terraform

data "aws_vpc" "main" {
  filter {
    name   = "tag:Name"
    values = ["main-vpc"]
  }
}

data "aws_subnet" "selected" {
  filter {
    name   = "vpc-id"
    values = [data.aws_vpc.main.id]
  }
  filter {
    name   = "tag:Environment"
    values = ["prod"]
  }
}

A Terraform resolves aws_subnet.selected first, then aws_vpc.main because subnet depends on VPC ID.

B Terraform resolves both data sources in parallel since they are independent.

C Terraform cannot resolve either data source because of circular dependency.

D Terraform resolves aws_vpc.main first, then aws_subnet.selected because subnet depends on VPC ID from aws_vpc.main.

💡 Hint

Think about which data source provides input to the other.

The aws_subnet.selected data source uses the VPC ID from aws_vpc.main, so Terraform must resolve aws_vpc.main first to get the ID before it can resolve aws_subnet.selected.

❓ service_behavior

intermediate

Effect of missing data source dependency in Terraform

What happens if a Terraform data source references an attribute from another data source that is not declared or does not exist?

Terraform

data "aws_subnet" "example" {
  filter {
    name   = "vpc-id"
    values = [data.aws_vpc.missing.id]
  }
}

A Terraform will throw a runtime error during plan/apply indicating the reference is invalid.

B Terraform will ignore the missing data source and proceed with a null value.

C Terraform will create a new VPC automatically to satisfy the missing data source.

D Terraform will skip the data source and continue without error.

💡 Hint

Consider what happens when Terraform cannot find a referenced resource or data source.

Terraform requires all referenced data sources to be declared and valid. If a data source references a missing or undeclared data source, Terraform throws an error during plan or apply.

❓ Architecture

advanced

Designing data source dependencies for multi-region infrastructure

You have a Terraform configuration that needs to fetch VPC IDs from multiple AWS regions dynamically using data sources. Which approach ensures correct dependency resolution and avoids race conditions?

A Use a single data source with a for_each loop over regions, referencing each region's VPC data source independently without explicit dependencies.

B Use a local variable to store region list and dynamically create data sources with for_each, relying on Terraform's implicit dependency graph.

C Define separate data sources for each region with explicit depends_on blocks to enforce order of resolution across regions.

D Manually run Terraform apply separately for each region to avoid dependency conflicts.

💡 Hint

Think about how Terraform handles dynamic blocks and implicit dependencies.

Using for_each with a local variable list allows Terraform to create data sources per region dynamically. Terraform's implicit dependency graph manages resolution order without manual depends_on, avoiding race conditions.

❓ security

advanced

Security implications of data source dependencies in Terraform

Which of the following is a security risk when using data source dependencies in Terraform configurations that fetch sensitive information?

A Storing sensitive data fetched by data sources in Terraform state files without encryption.

B Using data sources to fetch public information like AMI IDs.

C Referencing data sources across modules without outputs.

D Using data sources with filters based on tags.

💡 Hint

Consider where Terraform stores data source results and how sensitive data is handled.

Terraform stores all data source results in its state file. If sensitive data is fetched and stored unencrypted, it risks exposure. Public info or referencing across modules is not a security risk by itself.

✅ Best Practice

expert

Optimizing Terraform data source dependencies for large infrastructure

In a large Terraform project with many data sources depending on each other, what is the best practice to optimize plan and apply times while ensuring correct dependency resolution?

A Flatten all data sources into a single module to reduce overhead and force sequential resolution.

B Use explicit depends_on for every data source to control order strictly, even if Terraform can infer dependencies.

C Group related data sources into separate modules with clear input/output interfaces and rely on Terraform's implicit dependency graph.

D Avoid using data sources and hardcode resource IDs to eliminate dependencies.

💡 Hint

Think about modular design and Terraform's dependency management.

Grouping related data sources into modules with clear inputs and outputs helps Terraform manage dependencies efficiently. Explicit depends_on everywhere can slow down plans. Hardcoding IDs reduces flexibility and is error-prone.