Remote state data source in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Remote State Data Source Behavior

You have a Terraform configuration that uses a remote state data source to read outputs from another workspace. What will happen if the remote state backend is unreachable during terraform apply?

Terraform

data "terraform_remote_state" "vpc" {
  backend = "s3"
  config = {
    bucket = "my-terraform-state"
    key    = "vpc/terraform.tfstate"
    region = "us-east-1"
  }
}

resource "aws_instance" "web" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
  subnet_id     = data.terraform_remote_state.vpc.outputs.subnet_id
}

A Terraform apply will proceed but use default values for the remote outputs.

B Terraform apply will fail with an error indicating it cannot read the remote state.

C Terraform apply will ignore the remote state data source and create resources without subnet_id.

D Terraform apply will create a new remote state backend automatically.

💡 Hint

Think about what happens if Terraform cannot access the state it depends on.

If Terraform cannot access the remote state backend, it cannot retrieve the outputs needed for resource creation. This causes the apply to fail with an error.

❓ Configuration

intermediate

Correct Remote State Data Source Configuration

Which Terraform configuration snippet correctly defines a remote state data source to read outputs from an S3 backend?

A

terraform_remote_state "network" {
  backend = "s3"
  config = {
    bucket = "tf-state-bucket"
    key    = "network/terraform.tfstate"
    region = "us-west-2"
  }
}

B

data "terraform_remote_state" "network" {
  backend = "s3"
  bucket = "tf-state-bucket"
  key    = "network/terraform.tfstate"
  region = "us-west-2"
}

C

data "terraform_remote_state" "network" {
  backend = "s3"
  config = {
    bucket = "tf-state-bucket"
    key    = "network/terraform.tfstate"
    region = "us-west-2"
  }
}

D

data "terraform_remote_state" "network" {
  backend = "s3"
  config = {
    bucket = "tf-state-bucket"
    key    = "network.tfstate"
  }
}

💡 Hint

Check the syntax for the remote state data source and required config keys.

Option C correctly uses the data source block with backend and config keys. Option C misses the config block. Option C uses invalid syntax. Option C misses the region key which is required for S3 backend.

❓ Architecture

advanced

Designing Terraform Remote State for Multi-Environment

You want to manage multiple environments (dev, staging, prod) using Terraform with remote state stored in S3. Which architecture ensures isolation and safe state management?

A Use a single S3 bucket with separate key prefixes for each environment's state files.

B Store all environment states locally and push to S3 only for backups.

C Use separate S3 buckets for each environment's state files.

D Use one S3 bucket and one key for all environments to simplify management.

💡 Hint

Think about cost, isolation, and ease of management.

Using one bucket with separate key prefixes isolates states per environment while keeping management simple and cost-effective. Separate buckets increase complexity and cost. Single key risks overwriting states. Local storage is unsafe for collaboration.

❓ security

advanced

Securing Terraform Remote State Access

Which practice best secures access to Terraform remote state stored in an S3 bucket?

A Disable encryption to improve performance when accessing state files.

B Make the S3 bucket public to allow easy access for all team members.

C Share AWS root account credentials with the team for state access.

D Enable bucket versioning and restrict access using IAM policies to only required users and roles.

💡 Hint

Consider AWS best practices for security and access control.

Enabling versioning protects against accidental deletions. Restricting access with IAM policies limits who can read or modify state. Public buckets or sharing root credentials are insecure. Disabling encryption exposes sensitive data.

✅ Best Practice

expert

Handling Remote State Dependencies in Terraform Modules

You have multiple Terraform modules that depend on outputs from a shared network module stored in remote state. What is the best practice to manage these dependencies to avoid state conflicts and ensure consistency?

A Use terraform_remote_state data sources in each module to read outputs from the shared network state, avoiding direct resource references.

B Copy the network module outputs manually into each module's variables to avoid remote state usage.

C Merge all modules into a single Terraform configuration to share one state file.

D Use local state files for each module and synchronize outputs via manual scripts.

💡 Hint

Think about modularity, state isolation, and automation.

Using terraform_remote_state data sources allows modules to consume outputs from shared modules without merging states, preserving isolation and consistency. Manual copying or scripts are error-prone. Merging all modules reduces modularity and increases risk of conflicts.