Skip to content

CLF-C02 Study Notes: Define the AWS Global Infrastructure

1. AWS Global Infrastructure Overview

AWS global infrastructure is made up of geographically distributed infrastructure that helps customers build applications with:

  • High availability
  • Low latency
  • Fault tolerance
  • Disaster recovery capabilities
  • Data residency and compliance options

The primary building blocks are:

  1. AWS Regions
  2. Availability Zones
  3. Edge locations
  4. Local Zones
  5. AWS Wavelength Zones

AWS provides services across infrastructure categories such as compute, storage, databases, networking, security, management, migration, and application integration.

2. AWS Regions

Definition

An AWS Region is a separate geographic area that contains multiple isolated Availability Zones.

Examples include:

  • US East (N. Virginia)
  • Europe (Ireland)
  • Asia Pacific (Tokyo)

Each Region is designed to be isolated from other Regions to reduce the impact of regional failures.

Exam note: A Region contains multiple Availability Zones. AWS Regions commonly have three or more Availability Zones, although the exact number varies by Region.

Important characteristics

  • Regions are geographically separated from one another.
  • Each Region has its own infrastructure, services, and pricing.
  • Data stored in a Region generally remains in that Region unless you configure a service or transfer process to move or replicate it elsewhere.
  • Regions are useful for:
  • Disaster recovery
  • Business continuity
  • Data residency
  • Compliance requirements
  • Reducing latency for users
  • Protecting against regional failures

Choosing an AWS Region

When selecting a Region, consider:

Factor Explanation
Latency Choose a Region geographically close to users to reduce network delay.
Compliance Some laws and regulations require data to remain within specific countries or geographic boundaries.
Service availability Not every AWS service or feature is available in every Region.
Cost Pricing varies between Regions.
Disaster recovery A second Region can help protect against a complete regional outage.

Regions and compliance

Data sovereignty and regulatory requirements may restrict where data can be stored or processed.

For example:

  • A company may be required to store customer data within a specific country.
  • A company may choose a Region based on government or industry compliance requirements.
  • Using a different Region for disaster recovery may require additional compliance review.

Exam trap: Do not automatically choose the closest Region without checking compliance, service availability, and pricing.

3. Availability Zones

Definition

An Availability Zone (AZ) is one or more discrete data centers within an AWS Region.

Availability Zones have:

  • Independent power
  • Independent networking
  • Independent cooling and physical facilities
  • Redundant connectivity
  • Physical separation from other Availability Zones

Availability Zones within the same Region are connected through high-speed, redundant networking.

Why use multiple Availability Zones?

Deploying resources across multiple AZs helps achieve:

  • High availability
  • Fault tolerance
  • Resilience against a single data center or AZ failure
  • Reduced single points of failure

For example, an application could run:

  • Web servers in multiple AZs
  • A load balancer across multiple AZs
  • Databases configured for Multi-AZ operation

If one AZ becomes unavailable, resources in another AZ can continue serving users.

Availability Zone boundaries

An Availability Zone is an important failure boundary.

A failure in one AZ should not normally affect other AZs in the same Region. However, the exact resilience depends on the AWS service and its configuration.

Examples:

  • An Amazon EC2 instance is launched into a specific AZ.
  • An Amazon EBS volume is tied to a specific AZ.
  • An Amazon RDS Multi-AZ deployment can use multiple AZs for resilience.
  • A regional service such as Amazon EFS can provide access across multiple AZs within a Region.

Exam trap: A resource in one AZ is not automatically protected from an AZ failure. You must deploy or configure resources across multiple AZs.

Communication between Availability Zones

Resources in different AZs communicate over the AWS network. The method and cost depend on the service and architecture.

At the CLF-C02 level, remember:

  • AZs in the same Region are connected with high-speed, redundant networking.
  • Resources may need appropriate networking configuration, such as a VPC and subnets.
  • Some services are tied to one AZ, while others operate across multiple AZs or the entire Region.

4. AWS Service Resilience Models

AWS services can operate at different infrastructure scopes. Understanding the scope helps determine what happens during an AZ or Region failure.

Globally resilient services

A globally resilient service operates across AWS Regions or is not limited to a single Region.

Examples include:

  • AWS Identity and Access Management (IAM)
  • Amazon CloudFront
  • Amazon Route 53

A global service can continue operating even if one AWS Region becomes unavailable, depending on the service and configuration.

Exam tip: Global services do not necessarily mean that all data is automatically replicated everywhere. Always consider the specific service behavior.

Regionally resilient services

A regionally resilient service operates within one Region and typically provides resilience across multiple AZs in that Region.

Examples from the exam material include:

  • Amazon Elastic File System (Amazon EFS)
  • AWS Batch

If one AZ fails, the service can continue operating within the Region. However, if the entire Region fails, the service may become unavailable unless you have designed a multi-Region solution.

Availability Zone resilient or zonal services

A zonal service is tied to a specific Availability Zone.

Examples include:

  • Amazon EC2 instances
  • Amazon EBS volumes

If the AZ fails, resources in that AZ may become unavailable.

Comparison

Service scope Failure it is designed to tolerate Examples
Global Potential failure of a Region IAM, CloudFront, Route 53
Regional Failure of an AZ within a Region EFS, AWS Batch
Zonal Usually operates within one AZ EC2 instances, EBS volumes

Important: Resilience is service-specific. Some services can be configured for a different level of availability than their default behavior.

5. Edge Locations

Definition

An edge location is an AWS site used to deliver content and provide network entry points closer to end users.

Edge locations are part of the AWS global network and are located in many cities around the world.

Benefits of edge locations

Edge locations help:

  • Reduce latency
  • Deliver content closer to users
  • Improve application performance
  • Reduce the need for every request to travel to an origin Region

The edge location used for a request is generally selected by AWS based on network conditions and the user’s location.

Exam trap: Customers generally do not manually choose a specific CloudFront edge location for each user request.

6. Amazon CloudFront

What is CloudFront?

Amazon CloudFront is AWS’s content delivery network (CDN).

CloudFront distributes content through edge locations. When a user requests content:

  1. CloudFront receives the request at an edge location.
  2. If the content is cached, CloudFront returns it from the edge location.
  3. If the content is not cached, CloudFront retrieves it from the origin.
  4. The content may then be cached for future requests.

CloudFront can deliver:

  • Static content, such as images, videos, and files
  • Dynamic web content
  • APIs and web applications

CloudFront advantages

  • Lower latency for users
  • Content caching
  • Reduced load on the origin
  • Integration with AWS Shield for DDoS protection
  • Integration with services such as Amazon S3 and Application Load Balancers

CloudFront example

A video streaming company can cache frequently requested videos at edge locations. Users receive the content from a nearby edge location instead of retrieving it from a distant origin server.

CloudFront versus storing content only in a Region

CloudFront Regional origin only
Caches content near users Content is retrieved from the origin Region
Reduces latency for repeated requests May have higher latency for geographically distant users
Reduces origin requests Origin handles more requests

7. AWS Global Accelerator

What is Global Accelerator?

AWS Global Accelerator improves the performance and availability of applications by using the AWS global network and edge locations.

It provides:

  • Static anycast IP addresses
  • Entry points close to users
  • Traffic routing over the AWS global network
  • Fast regional failover
  • Support for TCP and UDP traffic

Global Accelerator forwards traffic to application endpoints in one or more AWS Regions.

Possible endpoints include resources such as:

  • Application Load Balancers
  • Network Load Balancers
  • Amazon EC2 instances
  • Elastic IP addresses

Important distinction

Global Accelerator does not cache application content.

It acts as a network traffic proxy:

  1. The user connects to an AWS edge location.
  2. Global Accelerator sends the traffic over the AWS global network.
  3. The traffic is forwarded to an application endpoint in an AWS Region.

When to use Global Accelerator

Use Global Accelerator when an application needs:

  • Static IP addresses
  • Improved global network performance
  • Fast failover between Regions
  • Support for TCP or UDP
  • Better availability for applications that cannot use caching

8. CloudFront Compared with Global Accelerator

Feature Amazon CloudFront AWS Global Accelerator
Primary purpose Content delivery and caching Application traffic acceleration
Caches content Yes No
Traffic types Primarily HTTP/HTTPS TCP and UDP, including HTTP/HTTPS
Static IP addresses Not the primary feature Yes
Uses edge locations Yes Yes
Regional failover Can support application failover patterns A major feature
Best for Websites, media, files, APIs, dynamic content Global applications requiring fast routing and failover

Exam question clues

Choose CloudFront when the question mentions:

  • Cached content
  • Static files
  • Videos or images
  • CDN
  • Content delivered from edge locations
  • Reducing origin requests

Choose Global Accelerator when the question mentions:

  • Static IP addresses
  • TCP or UDP
  • Fast regional failover
  • No caching
  • Improving performance for a global application

Exam trap: Both services use the AWS global network and edge locations, but only CloudFront is primarily a caching CDN.

9. AWS Local Zones

Definition

An AWS Local Zone is an extension of an AWS Region placed closer to a large population center.

Local Zones help run workloads closer to users who are far from the main AWS Region.

Use cases

  • Low-latency applications
  • Real-time gaming
  • Media production
  • Virtual desktops
  • Applications that need compute resources close to users

Local Zones remain associated with a parent AWS Region.

Local Zones compared with Availability Zones

Local Zone Availability Zone
Extension of a Region in a different geographic location Core isolated location within a Region
Designed to bring select services closer to users Designed for high availability and fault isolation
Useful for very low-latency workloads Commonly used for multi-AZ architectures

10. AWS Wavelength

Definition

AWS Wavelength allows applications to run in carrier network locations close to mobile users and devices.

A Wavelength Zone is an isolated zone where AWS infrastructure is deployed within a telecommunications provider’s network.

Use cases

  • 5G applications
  • Ultra-low-latency mobile applications
  • Connected vehicles
  • Augmented or virtual reality
  • Real-time video and communications

Wavelength Zones are tied to an AWS Region and act as extensions of that Region.

Local Zones versus Wavelength Zones

Local Zones Wavelength Zones
Located near metropolitan users Located within telecommunications carrier networks
Designed for general low-latency workloads Designed primarily for mobile and 5G workloads
Extend an AWS Region Extend an AWS Region into carrier locations

11. Cloud Computing Service Models

The AWS Cloud can be consumed using different service models.

Infrastructure as a Service (IaaS)

The customer manages more of the infrastructure and operating environment.

Examples:

  • Amazon EC2
  • Amazon VPC
  • Amazon EBS

Platform as a Service (PaaS)

AWS manages the underlying infrastructure and platform, while the customer focuses mainly on the application.

Examples may include:

  • AWS Elastic Beanstalk
  • Amazon RDS, from a database-management perspective

Software as a Service (SaaS)

The customer uses a complete software application managed by the provider.

Examples can include:

  • Amazon QuickSight
  • Amazon Chime

Other models include:

  • Database as a Service
  • Function as a Service
  • Storage as a Service

Exam tip: As you move from IaaS toward SaaS, AWS generally manages more of the underlying infrastructure and the customer manages less.

12. Common Exam Traps

Region versus Availability Zone

  • A Region is a geographic area.
  • An Availability Zone is an isolated location within a Region.
  • Multiple AZs provide protection against an AZ failure.
  • Multiple Regions can provide protection against a regional failure.

Availability Zone versus edge location

  • An AZ runs application infrastructure such as EC2 instances.
  • An edge location is primarily used for content delivery and network entry points.
  • Edge locations are not the same as Availability Zones.

EC2 versus EBS placement

  • EC2 instances are launched into a specific AZ.
  • EBS volumes are tied to a specific AZ.
  • An EBS volume normally must be copied or recreated in another AZ before it can be used there.

CloudFront versus Global Accelerator

  • CloudFront caches content.
  • Global Accelerator routes traffic but does not cache content.
  • Global Accelerator supports TCP and UDP and provides static IP addresses.
  • CloudFront is commonly used for websites, media, files, and APIs.

Multi-AZ versus multi-Region

  • Multi-AZ protects against an Availability Zone failure.
  • Multi-Region can help protect against a full Region failure.
  • Multi-Region architectures may introduce additional cost, complexity, data replication, and compliance considerations.

Compliance and latency

The closest Region is not always the correct Region. Check:

  1. Compliance and data residency
  2. Service availability
  3. Cost
  4. Latency
  5. Disaster recovery requirements

Example CLF-C02 Questions

Question 1

A company wants to protect its application from the failure of a single Availability Zone. Which solution provides the best protection?

A. Deploy all resources in a single Availability Zone
B. Deploy resources across multiple Availability Zones in the same Region
C. Deploy resources at multiple edge locations
D. Use a single AWS Region without redundancy

Answer: B

Explanation: Multiple Availability Zones within the same Region provide resilience against the failure of one AZ.

Question 2

Which AWS service is primarily designed to cache and deliver content from edge locations?

A. AWS Global Accelerator
B. Amazon CloudFront
C. Amazon EC2
D. Amazon EBS

Answer: B

Explanation: CloudFront is AWS’s content delivery network and caches content at edge locations.

Question 3

A company runs a global application that requires static IP addresses, supports TCP traffic, and needs fast failover between AWS Regions. Which service should the company use?

A. Amazon CloudFront
B. Amazon Route 53 Resolver
C. AWS Global Accelerator
D. Amazon S3 Transfer Acceleration

Answer: C

Explanation: Global Accelerator provides static anycast IP addresses, supports TCP and UDP, and supports rapid traffic failover between regional endpoints.

Question 4

Which statement best describes an AWS Region?

A. A single data center used for storing cached content
B. A geographic area containing multiple Availability Zones
C. A telecommunications carrier location used for 5G workloads
D. A single isolated virtual network

Answer: B

Explanation: An AWS Region is a geographic area containing multiple isolated Availability Zones.

Question 5

A company must ensure that its customer data remains within a specific country. Which factor is most important when selecting an AWS Region?

A. The number of edge locations
B. Data residency and compliance requirements
C. The number of IAM users
D. The operating system used by Amazon EC2

Answer: B

Explanation: Data sovereignty and regulatory requirements may require data to be stored in a particular country or geographic area.

Question 6

Which statement correctly compares CloudFront and AWS Global Accelerator?

A. Both services cache content at edge locations.
B. CloudFront provides static IP addresses, while Global Accelerator provides caching.
C. CloudFront caches content, while Global Accelerator routes traffic without caching it.
D. Global Accelerator can only support HTTP traffic.

Answer: C

Explanation: CloudFront is a CDN that caches content. Global Accelerator improves network routing and application availability without caching content.

Question 7

Which AWS resource is tied to a specific Availability Zone?

A. Amazon EC2 instance
B. AWS IAM user
C. Amazon Route 53 hosted zone
D. Amazon CloudFront distribution

Answer: A

Explanation: An EC2 instance is launched into a specific Availability Zone. IAM, Route 53, and CloudFront are global services.

Question 8

A company wants to run an application closer to users in a major city to reduce latency. The application does not specifically require a mobile carrier network. Which AWS infrastructure option should the company consider?

A. AWS Local Zone
B. AWS Wavelength Zone
C. Amazon Route 53 hosted zone
D. Amazon EBS volume

Answer: A

Explanation: Local Zones extend AWS infrastructure closer to users in specific geographic locations. Wavelength Zones are primarily designed for mobile and 5G workloads within carrier networks.

Quick Review Checklist

Before the exam, make sure you can explain:

  • The difference between a Region, Availability Zone, and edge location
  • How multiple AZs improve high availability
  • How multiple Regions support disaster recovery
  • Which resources are tied to an AZ
  • How compliance affects Region selection
  • Why latency affects Region selection
  • What CloudFront does at edge locations
  • What Global Accelerator does at edge locations
  • The difference between CloudFront caching and Global Accelerator traffic routing
  • The purpose of Local Zones and Wavelength Zones
  • The difference between global, regional, and zonal service resilience