CLF-C02 Global Infrastructure, Compute and Network Services Guide

Study CLF-C02 Global Infrastructure, Compute and Network Services: key concepts, common traps, and exam decision cues.

This is one of the most visible CLF-C02 lanes because AWS uses global infrastructure, compute, and networking questions to test whether you can classify a workload at the right altitude. The exam does not need deep VPC design. It does need correct service-family recognition.

Serverless: Execution model where AWS manages the underlying server fleet and the user focuses on code or configuration.

Edge service: Service that helps users interact with AWS closer to their location, often for acceleration, caching, or network entry optimization.

Global infrastructure basics

Term Best mental model
Region geographic area for deploying workloads
Availability Zone separate datacenter location inside a Region for resilience
Edge location location closer to users for content delivery and acceleration

If the requirement is geographic deployment choice, think Region. If it is fault tolerance inside one Region, think multiple Availability Zones. If it is faster content delivery closer to users, think edge services such as CloudFront.

Compute chooser

Need Strongest first fit
Traditional virtual server control Amazon EC2
Managed container orchestration Amazon ECS or Amazon EKS
Event-driven code without managing servers AWS Lambda
Simple starter virtual private server pattern Amazon Lightsail

CLF-C02 does not expect deep container orchestration knowledge. It does expect you to know that EC2, containers, and Lambda are different compute models.

Service-family contrast

If the stem emphasizes… Strongest first reading Why
full operating-system control EC2 You control the virtual server directly
managed container scheduling ECS or EKS The unit of deployment is the containerized workload
code that runs on events without server management Lambda The requirement is serverless execution
simple small-scale site or starter stack Lightsail CLF-C02 often uses it as the simpler packaged VPS lane

Networking chooser

Need Strongest first fit
Private network boundary in AWS Amazon VPC
DNS and routing users to endpoints Amazon Route 53
Global content delivery and caching Amazon CloudFront
Private connectivity from on-premises to AWS AWS Direct Connect or AWS VPN
Faster network entry optimization AWS Global Accelerator

Do not overthink the infrastructure terms

Requirement clue Strongest first answer
deploy closer to a geography Region
improve resilience inside one Region multiple Availability Zones
speed content delivery nearer to users CloudFront and edge locations
create the private network boundary VPC
answer DNS queries and steer users to endpoints Route 53

Decision order that usually wins

When AWS gives you several plausible infrastructure answers, classify the requirement in this order:

  1. Is the question about geography, resilience, compute model, private networking, DNS, edge caching, or global traffic entry?
  2. If it is about where workloads live geographically, think Region first.
  3. If it is about fault tolerance inside one geography, think multiple Availability Zones.
  4. If it is about how code runs, choose between EC2, containers, and Lambda based on operating-model control.
  5. If it is about user traffic, separate Route 53, CloudFront, and Global Accelerator before you answer.

Common service-family traps

Trap Better reading
“CloudFront and Route 53 both help users reach the app, so they are basically the same.” Route 53 is the DNS lane; CloudFront is the content-delivery lane.
“Lambda is just a smaller EC2 instance.” Lambda is a serverless execution model, not a traditional virtual server.
“Availability Zone and Region are interchangeable.” They operate at different resilience and geographic levels.
“Global Accelerator is the same thing as a VPC.” Global Accelerator is a traffic-entry optimization service, not a private network boundary.

Common compute and network traps

  • choosing EC2 when the stem clearly wants serverless behavior
  • treating Route 53 like a content-delivery service
  • confusing CloudFront with the idea of a whole private network
  • forgetting that VPC is the private networking boundary while Route 53 is the DNS lane

A practical example

1Need: "Users around the world should load web content faster from nearby edge locations."
2Strong lane: CloudFront
3Not the first lane: Route 53 alone, EC2 size change, or S3 lifecycle policy

This works because CLF-C02 often tests whether you can match the user-facing outcome to the right AWS service family.

Harder scenario question

A company wants users around the world to reach a web application through a faster global entry path, but the stem does not emphasize content caching. Which lane is strongest first?

  • A. Amazon Route 53 because all global traffic starts with DNS
  • B. AWS Global Accelerator because the requirement is global traffic-entry optimization
  • C. Amazon EBS because storage speed affects every app
  • D. AWS Lambda because serverless is always faster

Correct answer: B. If the requirement is about global entry-path performance rather than edge caching, Global Accelerator is the stronger first lane.

Quiz

Loading quiz…
Revised on Sunday, May 10, 2026