AWS Cloud Practitioner Study Plan: A 6-Week Roadmap to the CLF-C02 Exam

9 min read ยท 2026-10-14

A good aws cloud practitioner study plan takes about 6 weeks at 5 to 7 hours a week. Give one week to each of the four exam domains, give the largest domain two weeks, and use the last week for full practice exams. That gives you time to learn the concepts, click through the main services in a real account and fix your weak spots before you sit the exam.

This roadmap follows the official CLF-C02 exam guide from AWS. It is built for beginners, career changers and non-technical people such as sales, finance or project staff who work with cloud teams. Each phase has a clear goal, concrete steps and a milestone you can check. You know you are ready when you hit the milestones, not when you feel ready.

The roadmap at a glance

Goal: Pass the AWS Certified Cloud Practitioner (CLF-C02) exam on the first attempt. Duration: 6 weeks, about 5 to 7 hours per week, with the exam early in week 7 or 8

  1. Setup and Cloud Concepts (Week 1)

    Set up your study tools, take a baseline test and learn why companies move to the cloud.

    • Read the official CLF-C02 exam guide from start to finish and copy the four domains into your study notes.
    • Take a short diagnostic practice test without studying, and write down your score per domain.
    • Start the free AWS Cloud Practitioner Essentials course on AWS Skill Builder.
    • Learn the benefits of the cloud, the six pillars of the AWS Well-Architected Framework and the main migration strategies.
    • Create an AWS account and set a budget alert in AWS Budgets before you touch any service.

    Milestone: You can explain in your own words what the cloud is, you can name the six Well-Architected pillars, and your budget alert is active.

  2. Security and Compliance (Week 2)

    Understand who is responsible for what, and how access is controlled in AWS.

    • Learn the shared responsibility model and practice sorting tasks into "AWS" or "customer".
    • Study IAM users, groups, roles and policies, plus the principle of least privilege.
    • Turn on MFA for your root user and create an admin IAM user for daily work.
    • Review the security services you need to recognize: AWS Shield, AWS WAF, Amazon GuardDuty, Amazon Inspector, AWS KMS and AWS Artifact.

    Milestone: You score 75% or more on a 20-question quiz about security and compliance.

  3. Core Services: Compute, Storage and Networking (Week 3)

    Learn the services that come up in the largest exam domain.

    • Study Amazon EC2 instance types, Auto Scaling and Elastic Load Balancing.
    • Compare Amazon S3 storage classes, Amazon EBS and Amazon EFS.
    • Learn Regions, Availability Zones and edge locations, plus Amazon VPC, subnets, security groups and Amazon CloudFront.
    • Launch a small EC2 instance, connect to it, then stop and terminate it.
    • Create an S3 bucket, upload a file and change its storage class.

    Milestone: You can match each core service to a one-line use case without notes, and your lab resources are deleted.

  4. Core Services: Databases, Monitoring and More (Week 4)

    Finish the Cloud Technology and Services domain and learn to tell similar services apart.

    • Compare Amazon RDS, Amazon Aurora, Amazon DynamoDB and Amazon Redshift.
    • Study monitoring and management tools: Amazon CloudWatch, AWS CloudTrail, AWS Config and AWS Trusted Advisor.
    • Get a high-level view of serverless, containers, analytics and AI services such as AWS Lambda, Amazon ECS, Amazon Athena and Amazon SageMaker.
    • Build a one-page cheat sheet of service pairs that look alike, such as CloudWatch vs CloudTrail.
    • Book your exam for a date in week 7 or 8, and read the rescheduling rules before you confirm so you know how to move it if needed.

    Milestone: You score 70% or more on a full-length practice exam. This test is a checkpoint, not a final verdict. You have not studied billing yet, so questions from that domain can still be weak. What matters is that the first three domains hold up.

  5. Billing, Pricing and Support (Week 5)

    Learn how AWS charges and where customers get help.

    • Compare On-Demand, Reserved Instances, Savings Plans and Spot Instances, with one use case for each.
    • Use the AWS Pricing Calculator to estimate a small setup with one EC2 instance and one S3 bucket.
    • Open Cost Explorer and the Billing console in your own account to see what each page shows.
    • Learn the AWS Support plans and what each one adds, plus AWS Marketplace and AWS re:Post.

    Milestone: You can pick the right pricing model for five sample scenarios and explain why.

  6. Practice Exams and Final Review (Week 6)

    Turn knowledge into exam speed and close the last gaps.

    • Take two or three full practice exams under real conditions: 65 questions in 90 minutes, no notes.
    • Review every wrong answer and every lucky guess, and write down why the right answer is right.
    • Reread your cheat sheet daily and redo the quizzes from your weakest domain.
    • If you test from home, run the system check on the computer and room you will use.

    Milestone: You score 80% or more on two practice exams in a row. If you do, keep your exam date. If you do not, move the date and add one more week of practice.

How the CLF-C02 exam is built

According to the official AWS exam guide, CLF-C02 has 65 questions in 90 minutes. 50 questions are scored and 15 are unscored questions that AWS is testing for future use. You cannot tell which ones are unscored, so treat every question as if it counts. Results are given on a scale of 100 to 1,000, and the passing score is 700.

Scoring is compensatory. You do not need to pass each domain on its own, only the exam as a whole. A strong security score can make up for a weaker billing score. Even so, do not skip a domain, because 12% of the exam is still a lot of points to give away.

The exam covers four domains, and the plan above gives each one time based on its weight:

  • Cloud Concepts: 24% of scored content.
  • Security and Compliance: 30% of scored content.
  • Cloud Technology and Services: 34% of scored content, which is why it gets two weeks.
  • Billing, Pricing, and Support: 12% of scored content.

Hands-on labs that make the concepts stick

You do not need to build anything complex for this exam. But clicking through the console once makes service names much easier to remember. A question about stopping an EC2 instance is easier if you have actually done it.

Keep labs short and always clean up after yourself. Free Tier terms change over time, so check the current rules when you create your account. Then set a budget alert on the first day so a forgotten resource never surprises you. These five labs cover most of what the exam expects you to recognize:

  • IAM setup: turn on MFA for the root user, create an admin user and attach a policy.
  • EC2 basics: launch the smallest instance type, look at its security group, then terminate it.
  • S3 basics: create a bucket, upload a file, block public access and change the storage class.
  • Monitoring: open CloudWatch and look at the metrics for your instance, then check CloudTrail for the events you created.
  • Cost tools: build an estimate in the Pricing Calculator and look at your own spending in Cost Explorer.

How to use practice tests the right way

Practice tests are your best tool for measuring progress, but only if you review them properly. Your score matters less than what you do after. A test you take without reviewing it only tells you where you stand. A test you review in depth tells you what to fix.

Do not take the same test again and again. After two or three tries you remember the answers, not the concepts, and your score stops meaning anything. Use different question sets, and keep at least one full exam you have never seen for the last week.

Use a simple review routine after every practice exam:

  • Sort every wrong answer by domain, so you can see which part of the exam costs you the most.
  • Mark the questions you got right by guessing, and review them as if they were wrong.
  • For each mistake, write one sentence that explains the correct answer in your own words.
  • Look for patterns, such as always mixing up two services or misreading "most cost-effective".

How to adjust the plan to your schedule

Six weeks fits most people who study about an hour a day on weekdays. If you already work with AWS or hold another cloud certification, you can compress the plan into 4 weeks, as shown in the list below.

If you are new to tech or can only study on weekends, stretch the plan to 8 to 10 weeks. Add one extra week to Cloud Technology and Services, because it has the most service names to learn. Add another week of practice exams at the end. The milestones stay the same. Only move to the next phase when you reach the current one.

A few habits help whatever pace you choose. Study at the same time each day, even if it is only 30 minutes. Keep one running document of service names, with a one-line description of each. Book your exam when you finish the Cloud Technology and Services phase, for a date one or two weeks after your final practice week. The deadline becomes real, and you still have room to move it.

  • Week 1: Setup, Cloud Concepts, and Security and Compliance (weeks 1 and 2 combined).
  • Week 2: all Core Services, from compute to monitoring (weeks 3 and 4 combined).
  • Week 3: Billing, Pricing and Support, as in the full plan.
  • Week 4: Practice Exams and Final Review, as in the full plan.

Common mistakes to avoid

  • Memorizing every service in the catalog wastes weeks, so focus on the services named in the official exam guide and learn them at the "what is it for" level.
  • Skipping the shared responsibility model is risky because it shows up in many questions, so practice sorting tasks into AWS and customer until it is automatic.
  • Studying only theory makes similar services blur together, so do the five short labs to give each service a picture in your head.
  • Reusing the same practice test inflates your score, so rotate question sets and keep one unseen exam for the final week.
  • Leaving lab resources running can create charges, so set a budget alert on day one and delete everything at the end of each lab.
  • Keeping your exam date when you have not hit the week 6 milestone leads to guesswork on test day, so if you do not have two practice scores of 80% or more in a row, move the date and keep practicing.

Frequently asked questions

How long should I study for the AWS Cloud Practitioner exam?

Most beginners need about 6 weeks at 5 to 7 hours per week. If you already use AWS at work, about 4 weeks can be enough with the compressed plan above. If you are new to tech, plan 8 to 10 weeks. Use practice exam scores, not the calendar, to decide when you are ready.

When should I book the CLF-C02 exam?

Book it when you finish the Cloud Technology and Services phase, for a date one or two weeks after your final practice week. Check the rescheduling rules when you book. If you do not reach two practice scores of 80% or more in a row, move the date.

Can I pass CLF-C02 without a technical background?

Yes. The exam tests what services are for and how the cloud works, not how to write code or configure servers. Non-technical candidates should spend extra time on Cloud Technology and Services and do the short labs, because seeing the console makes service names easier to remember.

Do I need hands-on experience before the exam?

AWS does not require any for this certification. That said, a few short labs in your own account help a lot with questions that compare similar services. Keep them small and set a budget alert before you start.

What should I do after passing the Cloud Practitioner exam?

Pick an associate-level certification that matches your role. Solutions Architect Associate is a common next step for people who design systems, and Developer Associate fits people who build applications. Start the next study plan within a few weeks, while the basics are still fresh.

Generate this roadmap with AI