AWS Global Infrastructure Explained for Cloud Practitioner: Regions, AZs and Edge Locations
Know this topic? Test it on a full CLF-C02 paper
A complete CLF-C02 practice exam: 65 questions in 90 minutes, an explanation on every item and an Exam Coach report that ranks your weakest domains.
AWS-CLF-FULL
Try a free Cloud Practitioner exam
Already have an account? Log in to redeem
A Region is a geographic area containing multiple isolated Availability Zones, and an AZ is one or more discrete data centers. Spreading across AZs gives high availability, since AZs do not share single points of failure. Edge locations serve content closer to users through services such as CloudFront.Checked against AWS's published exam guide on 9 November 2026.
In this guide
The pieces
| Component | What it is | Why it matters |
|---|---|---|
| Region | A geographic area with multiple AZs | Data residency, latency, service choice |
| Availability Zone | One or more discrete data centers | Isolated failure domains for high availability |
| Edge location | A site that caches and serves content | Lower latency, through CloudFront |
| Local Zone | Compute and storage closer to a metro area | Single-digit millisecond needs |
| AWS Outposts | AWS infrastructure on your premises | Hybrid workloads that must stay on-site |
How to choose a Region
- Compliance and data residency. A legal requirement overrides everything else.
- Latency. Choose a Region near your users.
- Service availability. Not every service exists in every Region.
- Pricing. Costs vary by Region.
High availability, simply
Run across at least two Availability Zones so one AZ failure does not stop the service. Use more than one Region for disaster recovery, business continuity, low latency for distant users or data sovereignty. Those are the reasons AWS's guide lists.
Three quick scenarios
| Situation | Answer |
|---|---|
| An application must stay up if one data center fails | Deploy across multiple Availability Zones |
| An application must survive the loss of a whole geographic area | Deploy across multiple Regions |
| Videos load slowly for distant users | Serve them through CloudFront edge locations |
| Data must remain in Germany by law | Choose a Region in Germany |
| Single-digit millisecond latency in one metro area | AWS Local Zones |
| Data must stay in your own data center | AWS Outposts |
Other infrastructure terms
- AWS Wavelength places compute at the edge of 5G networks for ultra-low-latency mobile applications.
- Availability Zones in a Region are connected by low-latency links, and AWS designs them not to share single points of failure.
- Some services are global rather than Regional, for example IAM and Route 53.
How the exam words it
| If the question says | Think |
|---|---|
| Geographic area with multiple AZs | Region |
| Isolated failure domain within a Region | Availability Zone |
| Cache content near users | Edge location |
| High availability | Multiple AZs |
| Disaster recovery, data sovereignty | Multiple Regions |
| AWS infrastructure on-premises | Outposts |
AWS Global Infrastructure: practice questions
Five original questions. Each explanation says why the other options fail.
Your free Cloud Practitioner exam code is ready
Sit the full CLF-C02 paper against the real 90-minute clock. Cloud Practitioner is $39 once, lifetime, future versions included.
AWS-CLF-FULL
Redeem the code
Already have an account? Log in to redeem
Frequently asked questions
What is the difference between a Region and an Availability Zone?
A Region is a geographic area. Availability Zones are isolated groups of data centers within a Region.
How should I choose an AWS Region?
Start with compliance and data residency, then latency to users, then service availability, then pricing.
What are edge locations used for?
Serving content closer to users, primarily through Amazon CloudFront, which reduces latency.