Provider aliases for multi-region in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Identify the correct provider alias configuration for AWS multi-region

Given the need to deploy resources in two AWS regions using Terraform provider aliases, which configuration correctly defines the provider aliases for us-east-1 and us-west-2?

A

provider "aws" {
  region = "us-east-1"
  alias  = "east"
}

provider "aws" {
  region = "us-west-2"
  alias  = "west"
}

B

provider "aws" {
  alias  = "east"
  region = "us-east-1"
}

provider "aws" {
  alias  = "west"
  region = "us-west-2"
}

C

provider "aws" {
  region = "us-east-1"
}

provider "aws" {
  region = "us-west-2"
  alias  = "west"
}

D

provider "aws" {
  region = "us-east-1"
  alias  = "east"
}

provider "aws" {
  region = "us-west-2"
}

💡 Hint

Remember that each provider block for a different region must have a unique alias.

Provider aliases must be explicitly set with the alias attribute. Both provider blocks need aliases to be referenced separately.

❓ service_behavior

intermediate

Determine the provider used for resource creation with aliases

Given the following Terraform resource and provider aliases, which provider configuration will be used to create the resource aws_instance.example?

Terraform

provider "aws" {
  region = "us-east-1"
  alias  = "east"
}

provider "aws" {
  region = "us-west-2"
  alias  = "west"
}

resource "aws_instance" "example" {
  provider = aws.west
  ami           = "ami-12345678"
  instance_type = "t2.micro"
}

A The AWS provider configured for region us-east-1

B Terraform will raise an error due to missing provider

C The default AWS provider without alias

D The AWS provider configured for region us-west-2

💡 Hint

Check the provider attribute in the resource block.

The resource explicitly uses provider = aws.west, which refers to the provider alias configured for us-west-2.

❓ Architecture

advanced

Best practice for managing multiple provider aliases in large Terraform projects

In a large Terraform project managing resources across multiple AWS regions, which approach best organizes provider aliases to ensure maintainability and clarity?

A Define all provider aliases in a single providers.tf file and reference them explicitly in each module

B Avoid using provider aliases and create separate Terraform projects per region

C Use a single default provider without aliases and switch regions dynamically in resource blocks

D Define provider aliases inside each module separately without sharing them across modules

💡 Hint

Consider how to keep provider configurations centralized and reusable.

Centralizing provider aliases in one file and referencing them in modules improves clarity and reduces duplication.

❓ security

advanced

Security implications of provider alias misconfiguration in multi-region deployments

What is a potential security risk if provider aliases are misconfigured in Terraform when deploying resources across multiple AWS regions?

A Provider aliases do not affect security, only resource naming

B Terraform will automatically encrypt all resources regardless of region

C Resources may be created in unintended regions, exposing data to unauthorized zones

D Misconfiguration causes Terraform to block deployment until fixed

💡 Hint

Think about where your resources actually get created.

If provider aliases point to wrong regions, resources might be created where you don't expect, potentially exposing sensitive data or violating compliance.

🧠 Conceptual

expert

Understanding provider alias inheritance in nested modules

Consider a root Terraform module defining two AWS provider aliases: east and west. A child module is called without explicitly passing providers. Which provider configuration will the child module use for AWS resources?

Terraform

provider "aws" {
  region = "us-east-1"
  alias  = "east"
}

provider "aws" {
  region = "us-west-2"
  alias  = "west"
}

module "child" {
  source = "./child_module"
  # no providers passed explicitly
}

# Inside child_module, resource uses default provider aws

A The AWS provider with alias "east" from the root module

B The default AWS provider without alias, causing an error since none is defined

C The AWS provider with alias "west" from the root module

D Terraform automatically merges both provider aliases for the child module

💡 Hint

Think about how provider inheritance works when no default provider is defined.

When all providers in root have aliases and no default provider is defined, child modules expecting the default provider will fail unless providers are explicitly passed.