AWS CLF-C02 Cloud Practitioner guide for cloud concepts, shared responsibility, security, compliance, AWS service families, global infrastructure, billing, pricing, support, and foundational cloud literacy.
This guide targets AWS Certified Cloud Practitioner (CLF-C02), AWS’s current foundational certification for people who need real cloud literacy before they move into architecture, administration, development, analytics, security, finance, sales, product, or line-of-business cloud work.
CLF-C02 stays at the foundational altitude. AWS expects overall AWS Cloud knowledge independent of a specific job role. The exam validates whether you can explain cloud value, shared responsibility, Well-Architected ideas, security best practices, cloud economics, core service categories, and common service use cases. It does not expect coding, architecture design, troubleshooting, implementation, or load/performance testing.
Shared responsibility model: Cloud security split where AWS secures the cloud infrastructure and the customer still secures their data, identities, configurations, and workloads.
Region: Geographic AWS boundary that contains multiple Availability Zones and matters for latency, resilience, and data placement.
| Exam fact | Current official value |
|---|---|
| Level | Foundational |
| Duration | 90 minutes |
| Format | 65 multiple-choice or multiple-response questions, including scored and unscored items |
| Delivery | Pearson VUE testing center or online proctored |
| Validity | 3 years |
| Typical next step | SAA-C03, DVA-C02, or SOA-C03 |
As of May 17, 2026, AWS positions this exam for candidates with up to 6 months of exposure to AWS Cloud design, implementation, or operations. The current exam guide lists 50 scored questions and 15 unscored questions, and AWS reports a minimum passing score of 700 on a scaled 100-1000 range.
The most important habit is not memorizing dozens of service names in isolation. The real skill is classifying the question first: cloud concept, security boundary, service family, pricing model, or support and governance choice.
AWS’s current exam guide breaks CLF-C02 into four weighted domains, and this online guide now follows that structure directly:
| Official domain | Weight | What this guide emphasizes |
|---|---|---|
| 1. Cloud Concepts | 24% | Cloud value, benefits, global infrastructure, elasticity, agility, migration drivers, Well-Architected pillars, and cloud economics. |
| 2. Security and Compliance | 30% | Shared responsibility, IAM basics, root account protection, security services, compliance resources, logging, governance, and protection boundaries. |
| 3. Cloud Technology and Services | 34% | AWS service families: compute, storage, databases, networking, global infrastructure, deployment, management, analytics, AI/ML, integration, and migration. |
| 4. Billing, Pricing, and Support | 12% | Pricing models, billing drivers, cost tools, support plans, documentation, AWS Marketplace, partner resources, and technical help paths. |
Security and compliance plus cloud technology and services make up most scored content. That does not mean CLF-C02 is deeply technical. It means you must know the category, purpose, and responsibility boundary of common AWS services.
Most CLF-C02 stems can be handled with this loop.
flowchart LR
Q["Question clue"] --> C{"Which lane?"}
C -- "Cloud value" --> V["Benefits, global reach, elasticity, agility, economics"]
C -- "Security" --> S["Shared responsibility, IAM, compliance, logging, governance"]
C -- "Service fit" --> T["Compute, storage, database, network, analytics, AI/ML, integration"]
C -- "Billing/support" --> B["Pricing model, cost tool, support plan, documentation"]
V --> A["Answer at foundational altitude"]
S --> A
T --> A
B --> A
If the answer requires deep implementation steps, code, packet-level troubleshooting, or a detailed architecture design, it is probably too deep for Cloud Practitioner unless the question only asks you to recognize the concept.
| Scenario pressure | Strong CLF-C02 reasoning |
|---|---|
| A business asks why cloud helps | Map the clue to agility, elasticity, global reach, variable cost, managed services, or reduced undifferentiated heavy lifting. |
| A security question asks who is responsible | Use shared responsibility first, then identify whether the topic is physical infrastructure, customer data, IAM, configuration, or workload security. |
| A service name appears unfamiliar | Classify the service family first: compute, storage, database, networking, analytics, AI/ML, migration, management, or integration. |
| A pricing question mentions usage changes | Think pay-as-you-go, reserved or committed-use options, storage class, data transfer, support tier, and cost tools. |
| A support question asks where to get help | Separate documentation, knowledge center, re:Post, Trusted Advisor, AWS Support plans, Professional Services, and partners. |
| A global infrastructure question appears | Separate Region, Availability Zone, edge location, Local Zone, Wavelength Zone, and Outposts by purpose. |
| Trap | Better exam posture |
|---|---|
| Studying every service at architect depth | Learn what the service does, its family, and common use cases first. |
| Treating shared responsibility as “AWS handles security” | AWS secures the cloud; customers still secure data, identities, configurations, and workloads. |
| Confusing pricing tools with support plans | Cost Explorer, Budgets, pricing calculator, and CUR answer cost visibility; support plans answer help and case access. |
| Mixing Regions, AZs, and edge locations | Regions are geographic boundaries, AZs are isolated facilities, and edge locations bring services closer to users. |
| Choosing a build-it-yourself answer | For foundational questions, a managed AWS service family is usually the better fit unless the clue says otherwise. |
| Over-reading operational details | CLF-C02 tests recognition and understanding, not hands-on troubleshooting or implementation. |
flowchart LR
A["Study plan"] --> B["1. Cloud Concepts"]
B --> C["2. Security and Compliance"]
C --> D["3. Cloud Technology and Services"]
D --> E["4. Billing, Pricing, and Support"]
E --> F["Cheat sheet, glossary, and final review"]
| If you are coming from… | Bias your review toward… |
|---|---|
| non-technical or business roles | cloud concepts, pricing logic, support, and shared responsibility |
| early IT support or help desk | service families, identity basics, and when AWS manages more for you |
| future cloud engineer or architect track | broad service recognition now, then move into SAA-C03 next |
For CLF-C02, the better answer is often the one that stays at the correct altitude: