Study CLF-C02 Global Infrastructure, Compute and Network Services: key concepts, common traps, and exam decision cues.
This lesson covers the most visible CLF-C02 service families: AWS global infrastructure, compute choices, and core network services. The exam is not asking for deep VPC design. It is asking whether you can classify the requirement at the right altitude: geography, resilience, compute model, DNS, content delivery, or global traffic entry.
Serverless: Execution model where AWS manages the underlying server fleet and the user focuses on code or configuration.
Edge location: AWS location closer to users that supports content delivery and acceleration services.
AWS wants you to know:
| Term | Best mental model | Strongest when… |
|---|---|---|
| Region | geographic area for deploying workloads | the question is about geography or where workloads live |
| Availability Zone | separate location inside a Region for resilience | the question is about fault tolerance within one Region |
| Edge location | user-near location for delivery or acceleration | the question is about faster user access or edge services |
If the requirement is global geography, think Region. If it is high availability within one geography, think multiple Availability Zones. If it is faster user delivery from locations near users, think edge services.
| Need | Strongest first fit | Why |
|---|---|---|
| full virtual-server control | Amazon EC2 | The requirement is traditional VM control. |
| managed container deployment | Amazon ECS or Amazon EKS | The workload is containerized. |
| event-driven code without managing servers | AWS Lambda | The requirement is serverless execution. |
| simple packaged VPS-style environment | Amazon Lightsail | The requirement is a simpler starter virtual server model. |
| If the stem emphasizes… | Strongest first reading |
|---|---|
| operating system control and direct server management | EC2 |
| deploying and running containers | ECS or EKS |
| code triggered by events without server management | Lambda |
| a simpler bundled server option | Lightsail |
This is a classic CLF-C02 classification pattern. The exam often gives several valid AWS services, but only one matches the compute model the stem is actually asking for.
| Need | Strongest first fit | Why |
|---|---|---|
| private network boundary inside AWS | Amazon VPC | This is the private networking lane. |
| DNS and directing users to endpoints | Amazon Route 53 | This is the DNS and routing lane. |
| global content delivery and caching | Amazon CloudFront | This is the CDN and edge caching lane. |
| global application entry-path acceleration | AWS Global Accelerator | This is the global traffic-entry lane. |
| private connectivity from on premises into AWS | AWS Direct Connect or AWS VPN | This is the hybrid connectivity lane. |
| If the requirement is mainly about… | Think first about… |
|---|---|
| DNS answers and where clients are directed | Route 53 |
| cached content and delivery from edge locations | CloudFront |
| fast global entry into healthy endpoints when caching is not the point | Global Accelerator |
These services often appear together in answer choices because they all affect how users reach applications, but they solve different problems.
| Trap | Better thinking |
|---|---|
| “CloudFront and Route 53 both help users reach the app, so they are basically the same.” | Route 53 is DNS; CloudFront is content delivery. |
| “Lambda is just a smaller EC2 instance.” | Lambda is a serverless execution model, not a traditional VM. |
| “Region and Availability Zone are interchangeable.” | They operate at different geographic and resilience levels. |
| “Global Accelerator is basically a VPC.” | Global Accelerator is a global traffic-entry optimization service, not a private network boundary. |
Users around the world need to retrieve web content from locations closer to them so the content loads faster. The question emphasizes content delivery and caching near users.
Which service is strongest first?
Correct answer: 2
Why: The requirement is edge content delivery and caching close to users, which is CloudFront’s core job.