Cloud Technology and Services
Regions, Availability Zones, and Edge Infrastructure
CoreUnderstand the geographic hierarchy of AWS and choose multiple Availability Zones, multiple Regions, or edge infrastructure for the requirement stated.
Aligned to the current CLF-C02 exam guide, verified August 15, 2026.
Why this matters
Availability, disaster recovery, latency, and data-location questions depend on knowing which AWS geographic boundary addresses the risk.
Must Know
- An AWS Region is a separate geographic area. A Region contains multiple Availability Zones (AZs).
- An Availability Zone is one or more discrete data centers with redundant infrastructure and high-bandwidth connectivity to other AZs in the Region.
- Deploying across multiple AZs helps a workload remain available if one AZ has a failure.
- Multiple Regions can address Regional disaster recovery, business continuity, data sovereignty, or latency for globally distributed users.
- Edge locations support services such as Amazon CloudFront by serving content closer to viewers; they are not Regions or ordinary application-hosting AZs.
Compare and Distinguish
- Region vs Availability Zone: a Region is the geographic boundary; an AZ is an isolated location within that Region.
- Multi-AZ vs multi-Region: multi-AZ supports high availability within a Region; multi-Region addresses a larger failure boundary or geographic requirement.
- Region vs edge location: Regions host broad AWS service resources; edge locations deliver or route selected services close to users.
- CloudFront vs Route 53: CloudFront caches and delivers content; Route 53 provides DNS and routing policies.
Scenario examples
- Scenario: A web application must continue serving traffic if one data-center location fails. Think: Deploy across multiple Availability Zones in one Region.
- Scenario: A recovery requirement says the service must survive the loss of an entire AWS Region. Think: A second Region is required; multiple AZs stay within one Region.
- Scenario: Global users download the same static assets and need lower latency. Think: Use Amazon CloudFront edge locations to cache content near viewers.
Exam traps
- Two subnets are not automatically highly available if both are in the same AZ.
- Multi-AZ does not satisfy a requirement to survive an entire Regional disruption.
- An edge cache can improve content-delivery latency, but it is not by itself a disaster-recovery copy of the complete application.
- Multiple Regions add cost and complexity, so they are not required for every highly available workload.
Key takeaways
- Region contains AZs; AZs are separate failure locations within a Region.
- Multi-AZ supports high availability. Multi-Region supports Regional resilience or geographic requirements.
- Edge locations bring supported delivery and routing services closer to users.
How it works
- A workload can place redundant resources in separate AZs and direct traffic to healthy targets.
- CloudFront retrieves content from an origin and can cache copies at edge locations closer to viewers.
- A multi-Region design deploys or replicates the required workload components across separate geographic Regions.
When to use it
- Use multiple AZs when service availability must withstand an AZ failure.
- Use multiple Regions for Regional disaster recovery, data-location rules, business continuity, or a workload that must run closer to distant users.
- Use CloudFront when cached content delivery at the edge meets the latency need.
Security and governance implications
- Data residency and sovereignty requirements can constrain which Regions store or process data.
- Geographic redundancy does not replace access control, encryption, or backups.
Troubleshooting signals
- When an availability design still has a single failure point, check whether every critical component actually spans AZs.
- When global latency is the concern, identify whether the bottleneck is cacheable content, network path, or the application and data location before choosing a geographic service.
More detail
- AZs are designed so that a problem in one does not imply the same single point of failure in another. Applications still need to distribute resources and traffic across them.
- A multi-Region plan must decide what data and capabilities exist in the second Region. Merely selecting another Region in the console does not create disaster recovery.
- Amazon CloudFront uses a global network of edge locations and regional edge caches to deliver content from configured origins.
Ready for the quiz?
- Where do Availability Zones sit in the AWS geographic hierarchy?
- Would an AZ outage or a Regional outage require a different design?
- When would an edge location be more appropriate than adding another Region?
Related objectives
- D3.2