AWS Cloud Practitioner: My Study Plan and Key Takeaways
In January 2024 I passed the AWS Certified Cloud Practitioner (CLF-C02) exam on my first attempt. I had already been working with AWS in production for over a year (Lambda, EC2, S3, RDS), but the exam tests breadth, not depth, and plenty of experienced engineers fail it by underestimating exactly that. Here is the plan I followed, and what I would tell anyone preparing for it.
Know what the exam actually tests
CLF-C02 has four domains: Cloud Concepts (24%), Security and Compliance (30%), Cloud Technology and Services (34%), and Billing, Pricing and Support (12%). The surprise for most working engineers is the last one: you can deploy serverless APIs all day and still not know the difference between a Savings Plan and a Reserved Instance, or which Support plan includes a Technical Account Manager. I lost the most practice-test marks in billing and support, so that's where I spent my final week.
My four-week plan
- Week 1: Core services. A structured video course end to end. I treated even the familiar services (EC2, S3, RDS, Lambda, IAM) as revision: the exam asks about them the way AWS describes them, which is not always the way you think about them day to day.
- Week 2: Security and the shared responsibility model. This is the single highest-yield topic. Learn exactly what AWS is responsible for versus the customer, and the roles of IAM users, groups, roles, and policies. Many questions are answerable from this model alone.
- Week 3: Billing, pricing, and support plans. Pricing calculators, Cost Explorer versus Budgets, consolidated billing in AWS Organizations, and the four support tiers. Pure memorization, but a quarter of the exam in practice.
- Week 4: Practice exams only. I did timed practice tests, reviewed every wrong answer, and re-read the relevant FAQ or whitepaper section. I didn't sit the real exam until I was consistently scoring above 85%.
Resources I used
- Free: AWS Skill Builder's official Cloud Practitioner learning path, the "Overview of Amazon Web Services" whitepaper, and the AWS pricing and support FAQ pages.
- Paid: One video course for structure and one set of practice exams. The practice exams mattered more. The score reports show you which domain is weak while you still have time to fix it.
Exam-day strategies that helped
- Eliminate first. Most questions have two obviously wrong options; the real decision is between two plausible ones, and the wording ("most cost-effective", "least operational overhead") tells you which AWS wants.
- Flag and move on. The exam gives you 90 minutes for 65 questions. Time is not the constraint, but momentum is. I flagged anything I hesitated on and cleared the easy ones first.
- Think like AWS marketing, not like an engineer. The "right" answer is the managed service, the pay-as-you-go option, the one that scales automatically.
Was it worth it?
For me, yes, but with the right expectations. The Cloud Practitioner cert won't prove deep technical skill; my production work does that. What it did was force me to fill the gaps experience doesn't cover (billing, support, compliance programs), and it gave me a verified credential to anchor the cloud part of my profile. It also became the foundation for the Cloud Computing course I later taught at AUST; the exam's structure turned out to be a surprisingly good syllabus outline.
If you're working backend or DevOps and touching AWS at all, I'd recommend it as a four-week side project. Start with a practice test to find your blind spots; they're rarely where you expect.