AWS global infrastructure (regions, AZs) - Mini Project: Build & Apply

AWS Global Infrastructure: Regions and Availability Zones

📖 Scenario: You are working as a cloud architect for a company that wants to understand how AWS organizes its data centers worldwide. AWS uses Regions and Availability Zones (AZs) to provide reliable and scalable cloud services.Regions are separate geographic areas, and each Region contains multiple AZs, which are isolated locations within that Region. This setup helps keep applications running even if one AZ has a problem.

🎯 Goal: You will create a simple data structure to represent AWS Regions and their Availability Zones. Then, you will add a configuration variable to select a specific Region. Next, you will write code to list all AZs in the selected Region. Finally, you will complete the setup by adding a summary count of AZs in that Region.

📋 What You'll Learn

Create a dictionary named aws_infrastructure with exactly these Regions and AZs:

us-east-1: ['us-east-1a', 'us-east-1b', 'us-east-1c']

eu-west-1: ['eu-west-1a', 'eu-west-1b']

ap-southeast-1: ['ap-southeast-1a', 'ap-southeast-1b', 'ap-southeast-1c']

Create a variable selected_region set to 'us-east-1'

Write a loop to create a list az_list containing all AZs in selected_region

Add a variable az_count that stores the number of AZs in selected_region

💡 Why This Matters

🌍 Real World

Understanding AWS Regions and AZs helps design cloud applications that are reliable and available even if one data center fails.

💼 Career

Cloud architects and engineers must know AWS global infrastructure to plan deployments and disaster recovery strategies.

1

Create AWS Regions and Availability Zones dictionary

Create a dictionary called aws_infrastructure with these exact entries: 'us-east-1' mapped to ['us-east-1a', 'us-east-1b', 'us-east-1c'], 'eu-west-1' mapped to ['eu-west-1a', 'eu-west-1b'], and 'ap-southeast-1' mapped to ['ap-southeast-1a', 'ap-southeast-1b', 'ap-southeast-1c'].

AWS

# Create aws_infrastructure dictionary with Regions and AZs
# Your code here

Hint

Use curly braces {} to create a dictionary. Each Region is a key with a list of AZ strings as its value.

2

Select a Region to work with

Create a variable called selected_region and set it exactly to the string 'us-east-1'.

AWS

aws_infrastructure = {
    'us-east-1': ['us-east-1a', 'us-east-1b', 'us-east-1c'],
    'eu-west-1': ['eu-west-1a', 'eu-west-1b'],
    'ap-southeast-1': ['ap-southeast-1a', 'ap-southeast-1b', 'ap-southeast-1c']
}
# Set selected_region to 'us-east-1'
# Your code here

Hint

Assign the string 'us-east-1' to the variable selected_region.

3

List all Availability Zones in the selected Region

Create a list called az_list that contains all Availability Zones from aws_infrastructure[selected_region] using a for loop with the variable az.

AWS

aws_infrastructure = {
    'us-east-1': ['us-east-1a', 'us-east-1b', 'us-east-1c'],
    'eu-west-1': ['eu-west-1a', 'eu-west-1b'],
    'ap-southeast-1': ['ap-southeast-1a', 'ap-southeast-1b', 'ap-southeast-1c']
}

selected_region = 'us-east-1'

# Create az_list by looping over aws_infrastructure[selected_region]
# Your code here

Hint

Start with an empty list az_list. Use a for loop with az to add each AZ from the selected Region.

4

Count the number of Availability Zones in the selected Region

Create a variable called az_count and set it to the length of az_list using the len() function.

AWS

aws_infrastructure = {
    'us-east-1': ['us-east-1a', 'us-east-1b', 'us-east-1c'],
    'eu-west-1': ['eu-west-1a', 'eu-west-1b'],
    'ap-southeast-1': ['ap-southeast-1a', 'ap-southeast-1b', 'ap-southeast-1c']
}

selected_region = 'us-east-1'

az_list = []
for az in aws_infrastructure[selected_region]:
    az_list.append(az)

# Set az_count to the number of AZs in az_list
# Your code here

Hint

Use len(az_list) to get the number of AZs and assign it to az_count.

Practice

1. What is an AWS Region?

easy

A. A large geographic area containing multiple isolated data centers

B. A single data center inside AWS infrastructure

C. A network of connected servers in one building

D. A type of AWS service for storage

Solution

1. Step 1: Understand AWS Region concept

   AWS Regions are big geographic areas that contain multiple data centers.

2. Step 2: Differentiate from other options

   Options A and B describe smaller units like networks or data centers, not regions. A type of AWS service for storage is unrelated to infrastructure.

3. Final Answer:

   A large geographic area containing multiple isolated data centers -> Option A

4. Quick Check:

   Region = big area with many data centers [OK]

Hint: Regions are big areas, not single data centers [OK]

Common Mistakes:

• Confusing a region with a single data center
• Thinking regions are just networks or services
• Mixing up regions with availability zones

2. Which of the following correctly describes an Availability Zone (AZ) in AWS?

easy

A. A single isolated data center within a region

B. A group of regions connected by high-speed links

C. A virtual server instance in AWS

D. A storage bucket for backups

Solution

1. Step 1: Define Availability Zone

   An AZ is an isolated data center inside a region designed for fault tolerance.

2. Step 2: Eliminate incorrect options

   A group of regions connected by high-speed links describes regions, not AZs. A virtual server instance in AWS is about compute instances, and D is storage-related.

3. Final Answer:

   A single isolated data center within a region -> Option A

4. Quick Check:

   AZ = isolated data center inside region [OK]

Hint: AZs are isolated data centers, not servers or storage [OK]

Common Mistakes:

• Confusing AZ with a server or instance
• Thinking AZs are groups of regions
• Mixing AZs with storage services

3. You deploy an application in AWS using two Availability Zones in the same region. What is the main benefit of this setup?

medium

A. It reduces latency by serving users from multiple continents

B. It stores backups in different AWS services

C. It increases fault tolerance by isolating failures to one AZ

D. It automatically scales the application to more regions

Solution

1. Step 1: Understand multi-AZ deployment

   Deploying in multiple AZs protects the app from failure in one AZ by isolating faults.

2. Step 2: Analyze options

   It reduces latency by serving users from multiple continents is about continents, not AZs. It automatically scales the application to more regions talks about regions, which is different. It stores backups in different AWS services is unrelated to AZ deployment.

3. Final Answer:

   It increases fault tolerance by isolating failures to one AZ -> Option C

4. Quick Check:

   Multi-AZ = better fault tolerance [OK]

Hint: Multiple AZs protect from single data center failure [OK]

Common Mistakes:

• Thinking multi-AZ means multi-region
• Assuming it automatically scales globally
• Confusing AZs with backup storage

4. A developer tries to deploy an application across two AWS regions but uses the same Availability Zone name in both regions. What is the likely issue?

medium

A. Availability Zone names are globally unique, so this will cause a deployment error

B. Availability Zone names are unique only within a region, so using the same name in different regions is valid

C. Regions cannot have Availability Zones with the same name, so deployment will fail

D. Using the same AZ name in different regions will cause data loss

Solution

1. Step 1: Understand AZ naming scope

   AZ names are unique only inside their region; different regions can have AZs with the same name.

2. Step 2: Evaluate deployment impact

   Using the same AZ name in different regions is allowed and does not cause errors or data loss.

3. Final Answer:

   Availability Zone names are unique only within a region, so using the same name in different regions is valid -> Option B

4. Quick Check:

   AZ names unique per region, not global [OK]

Hint: AZ names repeat across regions, unique only inside region [OK]

Common Mistakes:

• Assuming AZ names are globally unique
• Believing same AZ name causes deployment failure
• Confusing AZ naming with region naming

5. You want to design a highly available web application on AWS that serves users worldwide with low latency. Which combination of AWS global infrastructure components should you use?

hard

A. Deploy the app in multiple regions but only one Availability Zone per region

B. Deploy the app in multiple Availability Zones within a single region only

C. Deploy the app in a single Availability Zone in one region and use AWS CloudFront

D. Deploy the app in multiple regions and use multiple Availability Zones in each region

Solution

1. Step 1: Identify requirements for high availability and low latency

   High availability needs multiple AZs to avoid single points of failure. Low latency worldwide needs multiple regions closer to users.

2. Step 2: Analyze options for meeting requirements

   Deploy the app in multiple regions and use multiple Availability Zones in each region uses multiple regions and AZs, covering both availability and latency. Deploy the app in multiple Availability Zones within a single region only lacks multi-region coverage. Deploy the app in a single Availability Zone in one region and use AWS CloudFront has single AZ, risking failure. Deploy the app in multiple regions but only one Availability Zone per region lacks multi-AZ redundancy.

3. Final Answer:

   Deploy the app in multiple regions and use multiple Availability Zones in each region -> Option D

4. Quick Check:

   Multi-region + multi-AZ = best availability & latency [OK]

Hint: Use multiple regions and AZs for best availability and speed [OK]

Common Mistakes:

• Using only one region limits global reach
• Using single AZ risks downtime
• Relying on CloudFront alone doesn't ensure availability