CLF-C02
Deep Dive
AWS global infrastructure is one of the most heavily tested topics on the CLF-C02. It covers regions, Availability Zones, Edge Locations, and their differences. The exam will distinguish between these concepts in concrete scenarios.
Contents
AWS operates the largest and most extensive cloud infrastructure in the world, designed to deliver high availability, fault tolerance, and low latency at global scale. The hierarchy is:
Additionally: Edge Locations (for CDN), Local Zones, and Wavelength Zones (for special latency use cases).
33+
Regions
geographic areas
105+
Availability Zones
isolated zones
400+
Edge Locations
points of presence
245+
Countries
with CDN coverage
A region is a geographic area of the world that contains multiple Availability Zones, isolated and physically separated. Each region is completely independent from the others.
Examples of AWS regions
| Name | Code | AZs |
|---|---|---|
| US East (N. Virginia) | us-east-1 | 6 |
| EU (Ireland) | eu-west-1 | 3 |
| Asia Pacific (Tokyo) | ap-northeast-1 | 4 |
| South America (São Paulo) | sa-east-1 | 3 |
| AWS GovCloud (US-West) | us-gov-west-1 | 3 |
4 criteria for choosing a region
Compliance and data governance
If your data must stay in Europe (GDPR), pick a European region. Data does NOT leave the region without your explicit consent.
Latency
Choose the region closest to your users. us-east-1 for users in North America, eu-west-1 for Europe, ap-northeast-1 for Asia.
Service availability
Not every AWS service is available in every region. New services launch first in us-east-1. Check availability of the service you need.
Pricing
Prices vary by region. us-east-1 tends to be the cheapest. sa-east-1 (São Paulo) is significantly more expensive.
Exam trap — Regions vs zones
AWS data is NOT automatically replicated across regions. If you want multi-region redundancy, you must configure it explicitly (e.g. S3 Cross-Region Replication, DynamoDB Global Tables). Within a region, data can be replicated automatically across AZs (e.g. RDS Multi-AZ).
An Availability Zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity within an AWS region. AZs are designed as independent failure zones.
Characteristics of AZs
At least 3 per region
Every AWS region has at least 3 AZs (some have as many as 6). This enables high availability without depending on a single AZ.
Physically separated
AZs are located in physically separate facilities, kilometers apart, to prevent a natural disaster from affecting all of them at once.
Connected by private fiber
They're interconnected with high-speed, low-latency private AWS fiber — NOT over the public internet.
Independent power and networking
Each AZ has its own power supply, UPS systems, backup generators, and independent network connectivity.
What are AZs for?
AZs let you build highly available, fault-tolerant applications:
RDS Multi-AZ: synchronous replica in another AZ. If the primary AZ fails, automatic failover in ~1 minute.
EC2 Auto Scaling: distributes instances across multiple AZs. If one AZ fails, instances in other AZs absorb the traffic.
ELB (Elastic Load Balancing): automatically distributes traffic across instances in multiple AZs.
S3: automatically replicates objects across at least 3 AZs (11-nines durability).
AZ naming
AZs are named like us-east-1a, us-east-1b, us-east-1c, and so on. The letter suffix varies by account — your "us-east-1a" may be physically different from another account's "us-east-1a." AWS does this to distribute load.
Edge Locations (also called "Points of Presence") are sites that Amazon CloudFront uses to cache copies of your content closer to end users, reducing latency. They are NOT for deploying EC2 or databases.
Services that use Edge Locations
Amazon CloudFront
CDN — caches static and dynamic content at Edge Locations to serve users from the nearest point of presence.
Amazon Route 53
DNS — answers DNS queries from Edge Locations for lower name-resolution latency.
AWS Global Accelerator
Optimizes application traffic routing using the AWS global network from Edge Locations.
AWS WAF and AWS Shield
DDoS protection and application firewall applied at the edge, before traffic reaches your origin.
How CloudFront works with Edge Locations
A user in Madrid requests an image from your app (origin in us-east-1)
The request goes to the nearest Edge Location (e.g. Madrid)
If the image is cached at that edge: it responds from there in <10ms
If it's NOT cached: the edge fetches it from the origin, responds to the user, and caches it for future requests
The user's second visit: served from the Madrid edge, not from us-east-1. Latency drops from ~200ms to ~5ms.
Critical trap: Edge Locations ≠ Regions ≠ AZs
Edge Location
✓ CDN cache, DNS
✗ NOT for deploying EC2 or RDS
Availability Zone
✓ High availability for apps
✗ NOT for CDN or caching
Region
✓ Data residency, full range of services
✗ NOT a single data center
AWS Local Zones
Extensions of an AWS region placed in specific metropolitan areas to deliver compute, storage, and database services with single-digit millisecond latency to users in that city.
• Available in cities like Los Angeles, Dallas, Miami
• Extends the region's VPC into the Local Zone
• Use cases: real-time video editing, gaming, media streaming
AWS Wavelength Zones
AWS infrastructure embedded directly within 5G telecommunications providers' data centers, to deliver applications with sub-millisecond latency to 5G devices.
• Works with carriers like Verizon, SK Telecom, Vodafone
• Traffic never leaves the carrier's 5G network
• Use cases: AR/VR, autonomous vehicles, real-time IIoT
| Component | Count | Main purpose | Can you deploy compute services? | Example |
|---|---|---|---|---|
| Region | 33+ | Geographic isolation, data residency, regulatory compliance | ✓ Yes — EC2, RDS, Lambda, etc. | us-east-1, eu-west-1, sa-east-1 |
| Availability Zone | 105+ | High availability and fault tolerance within a region | ✓ Yes — EC2, RDS (Multi-AZ), ELB | us-east-1a, us-east-1b, us-east-1c |
| Edge Location | 400+ | CDN caching (CloudFront) and DNS (Route 53) near the user | ✗ No — cache and CDN only | Madrid, Mexico City, Lima |
| Local Zone | 30+ | Single-digit ms latency in specific cities | ✓ Limited — compute, storage | us-west-2-lax-1a (Los Angeles) |
| Wavelength Zone | 18+ | Sub-ms latency for 5G devices | ✓ Limited — designed for 5G | us-east-1-wl1-nyc-wlz-1 (Verizon NY) |
Did you get this topic?
Test what you just learned
An architect needs to design a database solution that keeps running automatically if one of AWS's physical data centers in the same geographic area fails. Which AWS infrastructure feature enables this?
Put what you learned to the test with original CLF-C02 exam questions.
Start CLF-C02 mock examUnlimited mock exams with the Pro plan
Log in to track your progress.