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, or line-of-business cloud work.
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.
AWS positions this exam as a starting point for people with little or no prior cloud background. 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:
separate what cloud computing is from which AWS product implements it
keep AWS responsibility and customer responsibility distinct
recognize broad service families such as compute, storage, database, analytics, and networking before drilling into product names
treat pricing, billing, and support questions as a different lane from architecture questions
Review flow
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"]
Best fit for this guide
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
If two answers both sound right
For CLF-C02, the better answer is often the one that stays at the correct altitude:
choose the broader cloud concept over an overly deep implementation detail
choose the managed AWS service family over a lower-level build-it-yourself answer when the question is fundamentals-focused
choose the answer that matches the pricing or responsibility lane when the question is really about business fit rather than system design