Availability zones data source in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What is the output of this Terraform code snippet?

This Terraform code uses the AWS availability zones data source. What will be the value of length(data.aws_availability_zones.available.names) after applying?

Terraform

data "aws_availability_zones" "available" {
  state = "available"
}

output "az_count" {
  value = length(data.aws_availability_zones.available.names)
}

A An error, because the data source requires a region argument

B Always 3, because AWS has 3 availability zones per region

C Zero, because the data source does not fetch any zones without explicit filters

D The number of availability zones in the AWS region configured in the provider

💡 Hint

Think about what the state = "available" filter does and how Terraform queries AWS regions.

The aws_availability_zones data source returns all availability zones in the configured AWS region that are in the specified state. The length function counts how many zones are returned. AWS regions can have varying numbers of zones, so the count depends on the region.

❓ Configuration

intermediate

Which option correctly filters availability zones by name prefix?

You want to get only availability zones starting with us-west-2a using the AWS availability zones data source in Terraform. Which option correctly applies this filter?

A

data "aws_availability_zones" "filtered" {
  filter {
    name   = "zone-name"
    values = ["us-west-2a*"]
  }
}

B

data "aws_availability_zones" "filtered" {
  filter {
    name   = "zone-name"
    values = ["us-west-2a"]
  }
}

C

data "aws_availability_zones" "filtered" {
  names = ["us-west-2a"]
}

D

data "aws_availability_zones" "filtered" {
  state = "available"
  names = ["us-west-2a*"]
}

💡 Hint

Remember that the filter values must match exact names, wildcards are not supported.

The filter block filters availability zones by exact values. Wildcards like * are not supported. To filter by zone name prefix, you must list exact zone names. Option B correctly filters for the exact zone name us-west-2a.

❓ Architecture

advanced

How does using the availability zones data source improve multi-AZ architecture design?

Why is it beneficial to use the AWS availability zones data source in Terraform when designing a multi-AZ architecture?

A It dynamically fetches the current available zones, ensuring resources are deployed only in active zones, improving fault tolerance.

B It hardcodes the zones to avoid accidental deployment in new zones, reducing complexity.

C It disables zone awareness to simplify networking configurations.

D It automatically balances traffic across zones without additional configuration.

💡 Hint

Think about how availability zones can change over time and how Terraform can adapt.

Using the availability zones data source allows Terraform to query which zones are currently available in the region. This ensures that resources are deployed only in zones that are active and supported, which improves fault tolerance and availability in multi-AZ architectures.

❓ security

advanced

What security consideration is important when using availability zones data source in Terraform?

When using the AWS availability zones data source in Terraform, which security consideration is most relevant?

A Ensure the IAM role or user running Terraform has permission to call <code>ec2:DescribeAvailabilityZones</code> API.

B Encrypt the availability zones data source output to protect sensitive zone names.

C Use a VPN to connect to AWS before running the data source to secure the data.

D Disable logging of availability zones data source queries to avoid audit trails.

💡 Hint

Consider what permissions Terraform needs to query AWS data sources.

The AWS availability zones data source requires permission to call the ec2:DescribeAvailabilityZones API. Without this permission, Terraform cannot fetch zone information. Encrypting or VPN is not required for this metadata, and disabling logs is not a best practice.

✅ Best Practice

expert

What is the best practice for handling availability zones in Terraform modules for multi-region deployments?

You are designing a Terraform module to deploy infrastructure in multiple AWS regions. What is the best practice for handling availability zones in this module?

A Use the <code>aws_availability_zones</code> data source inside the module without passing region as input, relying on provider configuration.

B Hardcode availability zones in the module to ensure consistency across regions.

C Pass the region as a variable to the module and use a data source with explicit region provider alias to fetch availability zones.

D Avoid using availability zones and deploy all resources in a single zone to simplify the module.

💡 Hint

Think about how Terraform handles multiple providers and regions in modules.

For multi-region deployments, the best practice is to pass the region as a variable to the module and configure a provider alias for that region. Then use the aws_availability_zones data source with that aliased provider to fetch zones dynamically per region. This avoids hardcoding and ensures correct zone data per region.