CredenTrek
Independent roadmaps for accredited credentialsEdition 2026.2 · Register verified 9 October 2026
Library / AWS Cloud Practitioner / Guide 05 of 8
AWS Cloud Practitioner · Study hours and plan

AWS Cloud Practitioner study plan: turn your real week into an exam date, and practise without a surprise bill

By Mustafa K. Al-Dori · Checked against official documents on 9 October 2026 · 6 min read

The short answer

AWS publishes no single study-hour figure. CredenTrek uses 25 to 50 hours as a working assumption for CLF-C02. Split them by the four domain weights, divide by your ordinary weekly hours and add one buffer week for every eight. Give almost half the plan to practice and timed simulation, and practise only in an account with root user MFA and a budget alert.

Cloud Practitioner looks small from the outside, so candidates plan it loosely. Many give security a quarter of their hours when it carries 30 per cent of the scored questions. Others open an AWS account to practise, forget a database and meet the bill a month later.

This page gives you the hours, the split by domain, the weeks and a practice account set up in the order that keeps it free. AWS's figures were checked against its documents in October 2026; the study-hour range is a working assumption, explained below.

How many hours does AWS Cloud Practitioner take?

AWS does not publish a single study-hour figure. CredenTrek uses 25 to 50 hours as a working assumption for the current exam, CLF-C02.

Where you land depends on your starting point. Move towards 25 hours if you already work with IT or AWS. Move towards 50 if the cloud is new to you, or if English is not your first language. If you are unsure, plan near the top and let a diagnostic practice test in week one pull the figure down.

The exam itself has 65 questions in 90 minutes, so some of your hours must go on timed work, not reading.

A total is only useful once you decide where it goes.

How should you split the hours across the four domains?

Start in proportion to the CLF-C02 domain weights. For a 40-hour plan, the starting split looks like this.

Domain Weight Hours Study first
Cloud Technology and Services 34% 14 Global infrastructure, compute, storage, networking
Security and Compliance 30% 12 Shared responsibility, access management
Cloud Concepts 24% 10 Well-Architected pillars, cloud economics
Billing, Pricing, and Support 12% 4 Pricing models, current support plans

Then move hours towards your weak points. Rate yourself from 1 to 5 on each of the 19 task statements, the numbered items in AWS's exam guide. Your five lowest scores become your first targets, whichever domain they sit in.

Billing, Pricing, and Support is the smallest domain, but outdated material does most damage there. AWS replaced its support plans, and older courses still teach the old ones. What has changed in CLF-C02 lists them, and the exam map explains every task statement in plain English.

What to study is now settled. How long it takes depends on your week.

How many weeks will your plan take?

Pick the track that matches an ordinary week, with its late meetings and family evenings. Your best week is not your plan.

Track Hours a week Weeks for 40 hours
Light 2 to 4 14 at 3 hours
Standard 5 to 8 7 at 6 hours
Intensive 9 to 15 4 at 12 hours

The formula is total hours divided by weekly hours. Then add one buffer week for every eight weeks of plan. The buffer absorbs the busy month-end, the sick child and the evening the course video will not load.

Divide the weeks into four stages. Cloud Practitioner rewards understanding over memory, so practice and simulation take almost half the plan.

  • Stage A, foundation (about 10 per cent): rate yourself on every task statement, take the diagnostic test and set up your safe account.
  • Stage B, first coverage (about 45 per cent): work through your course once, with a short hands-on task for each domain.
  • Stage C, practice (about 30 per cent): question sets by domain, the commonly confused services learnt as contrasts and a review of every wrong answer.
  • Stage D, simulation (about 15 per cent): full timed practice exams and light revision.

On a 40-hour plan, the stages take 4, 18, 12 and 6 hours. A finance analyst with 6 hours a week gets 7 weeks plus one buffer week, and books the exam for week 9.

Stage A includes the account. Its set-up order matters more than any service you try in it.

How do you set up a practice account that cannot surprise you?

The exam does not test building skills. A little hands-on practice still makes services easier to tell apart. Set up your account in this order, before you create anything else:

  1. Create the account under the free plan, which AWS states will not charge you unless you upgrade to a paid plan.
  2. Turn on multi-factor authentication (a second code, usually from your phone) for the root user, the account's original identity with full access. Then stop using it for daily tasks.
  3. Create a separate user for yourself with IAM Identity Center or IAM, AWS's tools for users and permissions.
  4. Set a monthly budget alert in AWS Budgets at a small amount.
  5. After each session, delete what you created, and check the Billing console once a week.

What should you practise, and with which material?

Try five short tasks, each linked to a task statement. Store a file in Amazon S3, AWS's object storage. Launch and stop a small EC2 instance, which is a virtual server. Read the events in CloudTrail, which records who did what. Then explore Cost Explorer and price a small website in the Pricing Calculator.

Keep notes as you go. The same tasks later become a small project for your CV.

For the rest of your study, choose one route and stop buying. Candidates who collect three video courses and four question banks learn conflicting answers and lose confidence.

  • The official route: AWS Skill Builder, AWS's own training site, offers free digital training such as Cloud Practitioner Essentials and an official practice question set. At the time of writing, a paid subscription adds more exam preparation, including the official practice exam.
  • An instructor-led course: AWS and its training partners run classroom and virtual courses. You get structure, deadlines and someone to answer questions.
  • The limited-time route: for three hours a week or less. Use one free official course, one practice-question source and the safe account, starting with your lowest-rated task statements.

Before you pay for any material, confirm four things. It names CLF-C02, not the retired CLF-C01. It follows the task statements. It teaches the current support plans, including Business Support+ and Unified Operations. Its refund policy is in writing.

A question bank that still lists the Developer or Enterprise On-Ramp plans as current answers can stay for service questions. Check every support question in it against the exam guide.

When are you ready to book?

Readiness is a pattern, not a single score. Look for three things together:

  1. Consistent results across two or three full practice exams
  2. No domain far behind the others
  3. The ability to explain each commonly confused pair aloud, without notes

The third test catches people who score well by recognising questions they have seen before. If you cannot contrast CloudWatch with CloudTrail, or AWS Budgets with Cost Explorer, in a sentence each, the services candidates confuse is your next hour.

If one domain lags, give it more practice before you book. Every attempt is paid in full, so read AWS Cloud Practitioner exam cost and booking before you choose the date.

What to do this week

Take one diagnostic practice test and place yourself between 25 and 50 hours. Write down your ordinary weekly hours, divide, add the buffer and mark the four stage dates. Rate yourself on all 19 task statements and move hours towards your five lowest. Then open the practice account and set the budget alert before anything else.

Chapter 7 of the book walks through the whole method. The weekly plan template in Appendix B puts your track, hours, budget alert date and stage dates on one page. When your first results come in, test yourself with original scenario questions.

Your next step
  1. Take one diagnostic practice test and decide whether your total sits nearer 25 or 50 hours.
  2. Rate yourself from 1 to 5 on all 19 task statements and list your five lowest scores.
  3. Divide your total hours by your ordinary weekly hours, add the buffer week and mark the four stage dates in your calendar.
  4. Create your practice account under the free plan, then turn on root user MFA and set a budget alert before you create anything else.

Questions readers ask

Do I need six months of AWS experience before I start counting hours?
No. Cloud Practitioner has no prerequisites. The exam guide describes a target candidate with up to six months of exposure to AWS, and the certification page adds that this is not required. Treat it as a measure of difficulty. Without that exposure, start your plan near 50 hours.
Can I pass Cloud Practitioner in two weeks?
Only if your hours support it. Even the low end of 25 hours means about 13 hours a week for two weeks, which sits in the intensive track. That low end assumes you already work with IT or AWS. If the cloud is new to you, two weeks is a plan built on hope.
Do I have to pass every domain separately?
No. The exam is compensatory: you pass on your overall scaled score of 700, on a scale of 100 to 1,000. Unanswered questions count as wrong and there is no penalty for guessing, so answer everything. A weak domain still costs points, which is why readiness means no domain far behind.
Is the free plan the same as the 12-month Free Tier my course describes?
No. New AWS accounts now receive credits under a free plan, not the older 12-month offer many courses still describe. Check the credits and limits on the AWS Free Tier page when you open the account, and set the budget alert anyway.
Sources

This guide is independent and is not endorsed by AWS. Facts change: confirm them on the official page before you act.