Study CLF-C02 Cloud Technology and Services: key concepts, common traps, and exam decision cues.
This is the biggest CLF-C02 domain because AWS wants foundational candidates to recognize the major AWS service families and the jobs they solve. The exam is broad by design. It is not asking you to tune services. It is asking whether you can classify a requirement at the right level and then choose the AWS service family that fits it.
I verified the current CLF-C02 exam guide structure on May 11, 2026. AWS still treats Cloud Technology and Services as the largest weighted domain at 34% of scored content, which makes this the single biggest source of service-choice mistakes.
AWS currently weights Cloud Technology and Services at 34% of scored content.
AWS wants you to show that you can:
| Lesson | Why it matters |
|---|---|
| 3.1 Deploying, Operating & Connecting to AWS | Learn the human and automation access paths: console, CLI, SDK, IaC, and migration tooling. |
| 3.2 Global Infrastructure, Compute & Network Services | Learn Regions, AZs, edge locations, compute models, VPC basics, DNS, and global traffic-entry services. |
| 3.3 Storage & Database Services | Learn how to separate object, block, file, backup, relational, and NoSQL choices. |
| 3.4 Analytics, AI/ML, Integration & Other Service Categories | Learn the broader managed families that often appear as “which AWS service fits this job?” questions. |
| If the question is really about… | Go first to… | What to look for |
|---|---|---|
| console vs CLI vs SDK, CloudFormation, CloudShell, migration tooling, or how people interact with AWS | 3.1 Deploying, Operating & Connecting to AWS | operator path, automation path, migration lane |
| Regions, AZs, edge locations, VPCs, Route 53, CloudFront, Global Accelerator, EC2, containers, or Lambda | 3.2 Global Infrastructure, Compute & Network Services | geography, resilience, compute model, network service family |
| S3, EBS, EFS, FSx, lifecycle, AWS Backup, RDS, Aurora, DynamoDB, or DMS | 3.3 Storage & Database Services | storage shape, database model, management lane |
| Athena, Glue, Kinesis, QuickSight, SageMaker, Lex, SNS, SQS, EventBridge, WorkSpaces, Amplify, or IoT Core | 3.4 Analytics, AI/ML, Integration & Other Service Categories | job to be done, managed-service family |
| Trap | Better thinking |
|---|---|
| “EC2, ECS/EKS, and Lambda are all just compute, so any of them could work.” | First decide whether the requirement is VM control, container orchestration, or serverless event-driven execution. |
| “S3, EBS, and EFS all store data, so they are interchangeable.” | The exam expects you to separate object, block, and file storage clearly. |
| “Any data question is probably a database question.” | Some stems are really about analytics, messaging, or event routing rather than storage engines. |
| “If I recognize one AWS service in the answers, that is probably enough.” | CLF-C02 rewards classification, not random recognition. |