How to study for the AWS Cloud Practitioner exam
How to study for the AWS Cloud Practitioner exam (CLF-C02): spend time by domain weight, use spaced retrieval, separate look-alike services, and a 4-week plan.
The AWS Cloud Practitioner exam (CLF-C02) is mostly a matching game played at speed: here is a description, which service is it, or here is a scenario, who is responsible. The questions are short, but the answer options are deliberately close to each other. That points to a study method with two parts: make the service facts automatic, then practice telling neighbors apart.
If you have not yet seen the structure of the exam, what is on the AWS Cloud Practitioner exam covers the format and domains. The short version: 65 questions (50 scored), 90 minutes, a passing score of 700 on a 100 to 1,000 scale.
Spend time by weight
The four domains are weighted, and compensatory scoring means you pass on the total, not on each section.
| Domain | Weight |
|---|---|
| Cloud Technology and Services | 34% |
| Security and Compliance | 30% |
| Cloud Concepts | 24% |
| Billing, Pricing and Support | 12% |
Two domains make up 64% of the exam. A common mistake is to spend a third of your time on billing and support because those topics feel concrete and are easy to feel good about. They are worth 12%. Split your study time roughly in proportion to the weights, then shift a little extra toward whichever domain your practice results show is weakest.
Recall first, then discrimination
Most of this exam is vocabulary you either know or do not: what Amazon Macie is for, which S3 class has a 180-day minimum, which pillar of the Well-Architected Framework is Sustainability. That is flashcard material, and it works best as retrieval, not rereading. The testing effect is the research behind that, and what spaced repetition actually does explains why revisiting the same card over several days keeps it from fading.
The second skill is discrimination. Wrong answers on this exam usually come from look-alike services, so for each pair, learn the one word that separates them. The Encodr course's exam-day unit lists the main ones:
- Threat detection. GuardDuty finds threats, Inspector finds software vulnerabilities, Macie finds sensitive data in S3, Detective investigates root cause.
- Network filtering. A security group is stateful and allow-only at the instance; a network ACL is stateless with allow and deny at the subnet.
- Monitoring. CloudWatch watches performance, CloudTrail records who made API calls, Config records configuration history.
- Cost tools. Budgets alerts, Cost Explorer analyzes, the Pricing Calculator estimates.
- Storage. EBS is a block disk for one instance, EFS is a shared file system, S3 is object storage.
- Messaging. SNS pushes to many, SQS queues for pull, EventBridge routes events and schedules.
Write your own one-sentence version of each pair after you have seen it, then test yourself on it. A scenario such as "an engineer needs to find out who deleted a security group yesterday" is easy once CloudTrail is attached to "who made the API call".
Where the structure helps
Some topics are really tables, and learning them as tables is faster. The storage classes, for example, differ by minimum storage duration and access pattern; S3 storage classes compared puts them side by side. The shared responsibility model is the other one, since the answer depends on how much of the stack AWS operates for a given service; see the shared responsibility model explained. For list-and-table memorization in general, how to memorize a list, a table or a formula sheet has methods that apply directly.
One more point on this exam: some of what you may have learned elsewhere is out of date. Exam guide v1.3 changed the in-scope services and the support plan names, so check older notes against the current list rather than memorizing everything in them.
A 4-week plan
The Encodr course runs in 17 units and 58 chapters, ordered so each unit builds on the last. This plan walks through them in four weeks with daily sessions. The study schedule generator can turn your exam date into a day-by-day version of it.
| Week | Units | Focus |
|---|---|---|
| 1 | 1, 2, 3, 9, 10 | Cloud fundamentals and benefits, Well-Architected, global infrastructure, cloud economics, migration and adoption |
| 2 | 4, 5, 6, 7, 8 | Compute, storage, databases and analytics, networking, AI/ML and other services |
| 3 | 11, 12, 13, 14 | Shared responsibility, compliance and logging, IAM, security services |
| 4 | 15, 16, 17 | Pricing models, billing and support, then exam format and look-alike matchups |
Weeks 2 and 3 are the heaviest because Domains 3 and 2 live there, so keep those weeks the longest if you have to trade. Each day, do your due reviews first, then learn a limited number of new cards. Reviewing week 1 material during week 3 is what keeps it from fading.
In the last days, stop going unit by unit and mix everything. The real exam does not group questions by topic, and interleaving versus blocking explains why mixed practice trains you to recognize what a question is actually about. Try the AWS Cloud Practitioner practice questions as a mixed set once you have been through every unit.
If your date is close, cramming versus spacing is worth five minutes before you decide how to compress this.
What flashcards cannot do
Cards test recall of facts. They cannot replace using the service. Open the AWS console, create a free account and look at the services you are memorizing: launch nothing expensive, but click through the S3 storage class options, the IAM user and role screens and the Billing and Cost Management pages. Ten minutes of seeing a screen makes "Budgets alerts, Cost Explorer analyzes" much harder to forget.
The Encodr AWS Cloud Practitioner flashcards contain 1,302 study cards across the 17 units. The course is unofficial and not affiliated with or endorsed by AWS. When you are ready, start at Unit 1 and work in order.
Study Schedule Generator
Turn your exam date and topic list into a day-by-day spaced-repetition plan.
Try it →Encodr turns this into a habit: study anything in a feed, and it schedules the rest.
Get started free