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.

Practice

1. What is the main purpose of the availability_zones data source in Terraform?

easy

A. To delete unused availability zones

B. To create new availability zones in a region

C. To list all availability zones in a specified cloud region

D. To monitor the health status of availability zones

Solution

1. Step 1: Understand the data source role

   The availability_zones data source is used to fetch information, not to create or delete resources.

2. Step 2: Identify what information it provides

   It returns a list of availability zones available in the specified region, helping to distribute resources.

3. Final Answer:

   To list all availability zones in a specified cloud region -> Option C

4. Quick Check:

   Data source lists zones [OK]

Hint: Data sources fetch info; they don't create or delete [OK]

Common Mistakes:

• Thinking data source creates zones
• Confusing data source with resource
• Assuming it monitors zone health

2. Which of the following is the correct syntax to declare the AWS availability zones data source in Terraform?

easy

A. module "aws_availability_zones" {}

B. resource "aws_availability_zones" "example" {}

C. provider "aws_availability_zones" {}

D. data "aws_availability_zones" "example" {}

Solution

1. Step 1: Identify the correct Terraform block type for data sources

   Data sources use the data block, not resource, provider, or module.

2. Step 2: Check the correct resource type name

   The AWS availability zones data source is named aws_availability_zones, so the syntax is data "aws_availability_zones" "example" {}.

3. Final Answer:

   data "aws_availability_zones" "example" {} -> Option D

4. Quick Check:

   Data source syntax = data + resource type [OK]

Hint: Data sources start with 'data' keyword, not 'resource' [OK]

Common Mistakes:

• Using resource instead of data
• Using provider or module blocks incorrectly
• Misspelling the data source name

3. Given this Terraform snippet, what will output.zones contain?

data "aws_availability_zones" "available" {}

output "zones" {
  value = data.aws_availability_zones.available.names
}

medium

A. A list of availability zone names in the current AWS region

B. An error because names is not a valid attribute

C. A count of availability zones as a number

D. An empty list because no zones are specified

Solution

1. Step 1: Understand the data source attributes

   The aws_availability_zones data source provides an attribute names which is a list of zone names in the region.

2. Step 2: Check the output value

   The output references data.aws_availability_zones.available.names, so it will output the list of zone names.

3. Final Answer:

   A list of availability zone names in the current AWS region -> Option A

4. Quick Check:

   Output uses .names attribute = list of zones [OK]

Hint: Use .names to get zone names list from data source [OK]

Common Mistakes:

• Assuming .names attribute does not exist
• Expecting a count instead of list
• Thinking output is empty without explicit zones

4. You wrote this Terraform code but get an error: data.aws_availability_zones.invalid not found. What is the problem?

data "aws_availability_zones" "valid" {}

output "zones" {
  value = data.aws_availability_zones.invalid.names
}

medium

A. You must specify zones explicitly in the data source

B. The data source name used in output does not match the declared name

C. The names attribute does not exist

D. Terraform does not support availability zones data source

Solution

1. Step 1: Check the data source declaration

   The data source is declared as aws_availability_zones.valid.

2. Step 2: Check the output reference

   The output references data.aws_availability_zones.invalid, which does not exist.

3. Step 3: Identify the mismatch

   The error occurs because the output references a non-existent data source name.

4. Final Answer:

   The data source name used in output does not match the declared name -> Option B

5. Quick Check:

   Name mismatch causes not found error [OK]

Hint: Match data source names exactly in output references [OK]

Common Mistakes:

• Using wrong data source name in output
• Assuming .names attribute is missing
• Thinking zones must be specified manually

5. You want to deploy resources evenly across exactly 2 availability zones using Terraform's aws_availability_zones data source. Which code snippet correctly limits the zones to 2?

hard

A. data "aws_availability_zones" "example" {
state = "available"
filter {
name = "zone-name"
values = ["us-east-1a", "us-east-1b"]
}
}

B. data "aws_availability_zones" "example" {
state = "available"
all_availability_zones = false
filter {
name = "zone-name"
values = ["us-east-1a", "us-east-1b"]
}
}

C. data "aws_availability_zones" "example" {
state = "available"
all_availability_zones = true
filter {
name = "zone-name"
values = ["us-east-1a", "us-east-1b"]
}
}

D. data "aws_availability_zones" "example" {
state = "available"
zones = ["us-east-1a", "us-east-1b"]
}

Solution

1. Step 1: Understand filtering in aws_availability_zones

   The data source returns only AZs matching the filter criteria when a filter block is provided with name = "zone-name" and desired values.

2. Step 2: Identify valid configuration

   Use state = "available" and filter { name = "zone-name" values = ["us-east-1a", "us-east-1b"] } to limit exactly to those two zones.

3. Step 3: Invalid alternatives fail

   Using all_availability_zones or zones introduces non-existent arguments, causing Terraform validation errors.

4. Final Answer:

   data "aws_availability_zones" "example" { state = "available" filter { name = "zone-name" values = ["us-east-1a", "us-east-1b"] } } -> Option A

5. Quick Check:

   zone-name filter limits to specified AZs [OK]

Hint: Use zone-name filter to select specific AZs [OK]

Common Mistakes:

• Using invalid attributes like all_availability_zones
• Using unsupported 'zones' attribute
• Overcomplicating with non-existent parameters