AWS Cloud Practitioner (CLF-C02) · Lesson 7 of 26
Regions, Availability Zones and Edge Locations
Describe how AWS Regions, Availability Zones and edge locations relate, explain how multiple Availability Zones give high availability, decide when to use multiple Regions, and recognize Local Zones, Wavelength Zones and AWS Outposts.
Tip: turn your phone sideways or use full screen for larger labels.
Captions match the narration word for word. Press Space to play or pause and the arrow keys to change scenes.
Learning objective
Describe how AWS Regions, Availability Zones and edge locations relate, explain how multiple Availability Zones give high availability, decide when to use multiple Regions, and recognize Local Zones, Wavelength Zones and AWS Outposts.
Exam mapping
Domain 3: Cloud Technology and Services (34%). Task statement 3.2 in the official exam guide.
Key takeaways
- An AWS Region is a separate geographic area, isolated from other Regions. Most resources belong to one Region, and AWS doesn't copy them to other Regions for you.
- Each Region has multiple Availability Zones (AWS builds at least three per Region). An Availability Zone is one or more discrete data centers with redundant power, networking and connectivity.
- Availability Zones don't share single points of failure, but they're linked by low-latency, redundant, encrypted fiber, fast enough for synchronous replication.
- High availability: run across multiple Availability Zones, for example with a load balancer and a standby database. Use multiple Regions for disaster recovery, business continuity, low latency for distant users and data sovereignty.
- Choose a Region by compliance (data residency) first, then latency to users, available services and features, and cost.
- Edge locations sit close to users: CloudFront caches content there, Route 53 answers DNS, Global Accelerator brings traffic onto the AWS network, and Shield and WAF filter attacks. Local Zones, Wavelength Zones and AWS Outposts bring AWS compute closer still.
Exam tips
How the exam asks about this
Questions describe a situation and expect you to recognize the concept behind it.
| If the question mentions… | Think |
|---|---|
| Keep the application available if one data center fails | Deploy across multiple Availability Zones |
| Recover if an entire Region becomes unavailable | Multiple Regions (disaster recovery) |
| Data must remain in a specific country | Choose a Region in that country (data sovereignty) |
| Deliver content with low latency to users worldwide; caching | Amazon CloudFront and edge locations |
| Run AWS infrastructure in your own data center | AWS Outposts |
| Single-digit millisecond latency near a large city; 5G devices | AWS Local Zones; AWS Wavelength |
Common traps
- An Availability Zone isn't necessarily a single data center: it's one or more discrete data centers. And a Region is not one data center either.
- Edge locations aren't where you launch Amazon EC2 instances; they cache content and route traffic. To run servers closer to users, the answer is Local Zones, Wavelength Zones or Outposts.
- Multiple Availability Zones protect against a data center or zone failure; only multiple Regions protect against the loss of a whole Region. Every Region already has multiple AZs, so “more AZs” is never a reason to add a Region.
- AWS doesn't replicate your data between Regions automatically. If a question says data must stay in one country, keep it in a Region there.
Practice
Exam-style questions
Answer each one before you open the explanation.
Question 1. Which statement correctly describes an AWS Availability Zone?
- A single data center that serves one city
- One or more discrete data centers with redundant power, networking, and connectivity within an AWS Region
- A site that caches content close to end users
- A group of AWS Regions in the same country
Show answer
B. One or more discrete data centers with redundant power, networking, and connectivity within an AWS Region. An Availability Zone is one or more discrete data centers, with redundant power, networking and connectivity, inside a Region. “A single data center” is the tempting answer, but an AZ can contain several data centers. Caching sites are edge locations, and Regions contain AZs, not the other way around.
Question 2. A company wants its web application to stay available if a single data center fails. Which approach should it use?
- Run the application on one larger Amazon EC2 instance
- Run the application servers at Amazon CloudFront edge locations
- Deploy the application across multiple Availability Zones in one AWS Region
- Install an AWS Outposts rack in the company's office
Show answer
C. Deploy the application across multiple Availability Zones in one AWS Region. Availability Zones don't share single points of failure, so spreading the application across several of them, behind a load balancer, keeps it running when one fails. Edge locations are tempting because they're spread out, but they cache content and route traffic; you don't run your application servers there.
Question 3. Which are valid reasons to deploy a workload in more than one AWS Region? (Select TWO.)
- Disaster recovery if an entire Region becomes unavailable
- To get access to more than one Availability Zone
- To be able to use edge locations
- Lower latency for users on another continent
- AWS requires every account to use at least two Regions
Show answer
A. Disaster recovery if an entire Region becomes unavailable and D. Lower latency for users on another continent. The exam guide's reasons for multiple Regions are disaster recovery, business continuity, low latency for end users and data sovereignty. “More than one Availability Zone” is tempting, but every Region already has multiple AZs. Edge locations work with any Region, and AWS has no two-Region requirement.
Question 4. A company must keep its customers' personal data inside Germany to meet a national regulation. Which factor should drive its choice of AWS Region first?
- The price of services in each Region
- The number of edge locations nearby
- Which Region gets new services first
- Compliance and data residency requirements
Show answer
D. Compliance and data residency requirements. When a law requires data to stay in a country, compliance overrides the other factors, so the company picks a Region in Germany. Price is tempting because cost is a real Region-selection factor, but it only matters among Regions that already meet the legal requirement.
Question 5. A media company wants to deliver images and videos to viewers around the world with low latency by caching them close to the viewers. What should it use?
- Amazon CloudFront, which uses AWS edge locations
- An AWS Outposts rack in each country
- More Availability Zones in its current Region
- A larger Amazon EC2 instance in one Region
Show answer
A. Amazon CloudFront, which uses AWS edge locations. CloudFront caches content at edge locations near viewers, so most requests never travel back to the origin Region. More Availability Zones are tempting, but they're all in the same geographic area: they improve availability, not latency for viewers on other continents.
Transcript
Lesson transcript
The full narration, scene by scene. The captions file contains the same text with timings.
Scene 1 · 0:00
Lesson 7: Regions, Availability Zones and Edge Locations. Our store's team has a plan for moving to AWS. Now the question is where, physically, the store will run. This lesson covers task 3.2 in Domain 3, the AWS global infrastructure. We'll cover two ideas. First, Regions and Availability Zones, and how they give you high availability. Second, edge locations, plus when to use more than one Region and a few ways to bring AWS even closer to users.
Scene 2 · 0:30
Regions contain Availability Zones. An AWS Region is a separate geographic area, such as Northern Virginia or Frankfurt. Each Region is isolated from the others, and most resources you create belong to one Region. Inside every Region are multiple Availability Zones, and AWS builds each Region with at least three. Each Availability Zone is one or more discrete data centers. So the nesting is simple: Regions contain Availability Zones, and Availability Zones contain data centers.
Scene 3 · 1:01
What makes an Availability Zone independent. What makes an Availability Zone special is independence. Each one has its own redundant power, networking and connectivity, in separate facilities many kilometers apart, so a fire or a flood affects only one zone. Availability Zones don't share single points of failure. Yet they're linked by fast, redundant fiber, and AWS encrypts all traffic between them. That link is quick enough to copy data synchronously from one zone to another.
Scene 4 · 1:32
High availability with multiple AZs. That independence is how you get high availability. Our store runs a web server in Availability Zone A and another in Availability Zone B. A load balancer in front spreads shoppers' requests across both. The database keeps a primary copy in one zone and a standby copy in the other, kept in sync. Nothing important lives in only one place, so no single zone failure can take the store offline.
Scene 5 · 2:02
When one AZ fails. Now say Availability Zone B loses power. The load balancer's health checks notice that the server there isn't responding, so it sends every request to zone A instead. If the database's primary copy had been in zone B, the standby would take over. Shoppers keep checking out. This is a key exam idea: to survive the failure of a data center or a zone, deploy across multiple Availability Zones.
Scene 6 · 2:32
Choosing a Region. Which Region should the store use? Four factors decide. First, compliance: if a law says data must stay in a country, that overrides everything else. Second, latency: pick a Region close to your users. Third, services and features: not every service is in every Region, and new ones arrive gradually. Fourth, cost: prices differ between Regions. Most of our store's shoppers are in North America, so it picks a nearby Region.
Scene 7 · 3:03
When to use multiple Regions. Most workloads run well in one Region. The exam guide names four reasons to use more than one. Disaster recovery, with a copy ready in a second Region if a whole Region has trouble. Business continuity, keeping critical operations running through a major event. Low latency for users on another continent. And data sovereignty, keeping each country's data in that country. AWS doesn't copy your data between Regions automatically; you set that up.
Scene 8 · 3:35
Edge locations: close to your users. Now the edge. Edge locations are AWS sites in many cities, far more of them than Regions, placed close to users. You don't run your servers there. Amazon CloudFront caches copies of your content at edge locations, so a shopper in Europe gets product images from nearby, and only cache misses travel back to the Region. Route 53 answers DNS queries from the edge, Global Accelerator brings traffic onto the AWS network, and Shield and WAF filter attacks there.
Scene 9 · 4:09
Local Zones, Wavelength Zones and Outposts. Three more options bring AWS even closer. Local Zones extend a Region into a large city, for applications that need single-digit millisecond latency, like gaming or video editing. Wavelength Zones put AWS compute inside telecom 5G networks, for ultra-low latency to mobile devices. And AWS Outposts puts AWS-managed racks or servers in your own data center, with the same APIs and tools. Each one is still tied to a parent Region.
Scene 10 · 4:40
How the exam asks about this. Here's how the exam asks about this. Keep running if a data center fails: multiple Availability Zones. Survive the loss of a whole Region: multiple Regions. Data that must stay in one country: choose the Region for data sovereignty. Cache content close to users around the world: CloudFront at edge locations. Single-digit millisecond latency in a big city: Local Zones. AWS in your own data center: Outposts. Ultra-low latency for 5G apps: Wavelength.
Scene 11 · 5:12
Recap: the AWS global infrastructure. To recap: a Region is a separate geographic area with multiple isolated Availability Zones, and each zone is one or more data centers with no shared single point of failure. Use multiple zones for high availability, and multiple Regions for disaster recovery, distant users and data sovereignty. Edge locations cache and route traffic near users. Next, we'll look at the ways to work with AWS: the console, the command line, SDKs and infrastructure as code.
Sources and accuracy
Checked against AWS documentation and the official CLF-C02 exam guide on October 18, 2026. AWS changes often, so confirm details in the current documentation. Diagrams and numbers in the animation are illustrative.
- AWS Regions and Availability Zones
- AWS Global Infrastructure: Regions, Availability Zones, Local Zones and Outposts
- Amazon CloudFront FAQs: edge locations and regional edge caches
- AWS Global Accelerator: global static IP addresses at AWS edge locations
- CLF-C02 exam guide: Domain 3, Cloud Technology and Services
This free course is independent and isn't affiliated with or endorsed by Amazon Web Services. AWS and AWS Certified Cloud Practitioner are trademarks of Amazon.com, Inc. or its affiliates.
Preparing a team for AWS certification?
I run hands-on AWS training for teams, from Cloud Practitioner basics to architecture, built around your own environment.