The AWS Certified Cloud Practitioner exam rewards candidates who study in proportion to the exam blueprint, not in proportion to what feels interesting. The CLF-C02 version has four domains with very different weights, and a plan that mirrors those weights is the fastest route to a pass. This guide gives you a 2 to 4 week schedule, what to drill in each domain, and the traps that catch people who have only watched videos.
The exam is aimed at someone with up to 6 months of AWS exposure, and the target candidate can come from a non-IT background. You do not need to code, design architectures or troubleshoot anything. Those tasks are explicitly out of scope, along with implementation and load testing.
What the CLF-C02 Exam Looks Like
The AWS Certified Cloud Practitioner exam (CLF-C02) has 65 questions and runs for 90 minutes. Of those, 50 are scored and 15 are unscored. AWS does not tell you which are which, so treat every question as if it counts.
Questions are multiple choice or multiple response. Scores are scaled from 100 to 1000, and you need 700 to pass. There is no penalty for guessing, and an unanswered question counts as wrong, so never leave one blank. The exam fee is 100 USD.
For deeper coverage of fees and booking, see our dedicated posts on exam cost and format. This guide stays on how to prepare.
The Four Domains and Where Your Time Should Go
| Domain | Weight | Study priority |
|---|---|---|
| Cloud Technology and Services | 34% | Largest block of time |
| Security and Compliance | 30% | Second largest, most concept-heavy |
| Cloud Concepts | 24% | Short, high-yield reading |
| Billing, Pricing, and Support | 12% | Small but easy marks |
Cloud Technology and Services and Security and Compliance together make up 64% of the exam. Spend roughly two thirds of your study hours there. Billing, Pricing, and Support is only 12%, but the questions are usually answerable from a handful of facts, so it is the cheapest domain to score well in.
Exam Tip: Domain weights describe the share of scored content. A domain at 12% still appears in roughly one question in eight, so skipping it is a gamble you do not need to take.
Pick Your Timeline
Three weeks suits most people with no AWS background who can study an hour or two on weekdays. Two weeks works if you already use AWS at work. Four weeks gives breathing room if you are new to IT.
| Timeline | Best for | Shape |
|---|---|---|
| 2 weeks | Candidates already using AWS | Skim Cloud Concepts, focus on weak spots, mock exams from day 8 |
| 3 weeks | Most candidates | One domain block per week, mock exams in the final week |
| 4 weeks | Complete beginners | Add a first week on basic cloud and networking vocabulary |
The rest of this plan uses the three-week shape. Stretch or compress it to match your timeline.
Week 1: Cloud Concepts and Cloud Technology and Services (Part 1)
Start with Cloud Concepts, which is 24% of the exam and the foundation for everything else. Spend the first two or three days here, then move into the services domain.
What to drill in Cloud Concepts
- The value of the AWS Cloud, including trading upfront cost for variable cost and scaling up or down with demand.
- The difference between elasticity and scalability.
- High availability and fault tolerance, and how Regions, Availability Zones and edge locations support them.
- The AWS Well-Architected Framework pillars. Know each pillar by name and what it asks you to optimise.
- Cloud adoption concepts and the difference between capital and operating expense.
What to drill in Cloud Technology and Services (Part 1)
This domain is 34%, so it needs the most study hours. Split it across two weeks. In week 1, cover the core service families at a recognition level:
- Compute: what EC2, Lambda and container services are for, and when each fits.
- Storage: S3 versus EBS versus EFS, and the idea of storage classes.
- Databases: relational versus NoSQL, and which AWS service maps to each.
At this level the exam asks you to match a described need to a service. It does not ask you to configure one. If a question reads like an architecture design problem, the answer is almost always the simple, managed option.
Week 2: Security and Compliance, Then the Rest of Services
Security and Compliance is 30% and trips up many candidates because the vocabulary is precise. Give it the first four or five days of week 2.
What to drill in Security and Compliance
- The shared responsibility model. Know which side owns what. AWS secures the infrastructure of the cloud, and you secure what you put in it. Practise sorting examples into each side, including how responsibility shifts between services such as EC2 and managed services.
- IAM fundamentals. Users, groups, roles, policies, multi-factor authentication, least privilege, and protecting the root user.
- Encryption and data protection at rest and in transit, and which AWS services support them.
- Compliance resources. Know what AWS Artifact is for and how AWS reports on compliance.
- Monitoring and security services. Be able to say what each service detects or records, at the level of one sentence per service.
Exam Tip: When two answers both sound secure, pick the one that follows least privilege and uses a managed AWS feature rather than a custom process.
Finish Cloud Technology and Services (Part 2)
Spend the last two days of the week on the remaining service families:
- Networking: VPC, subnets, security groups versus network ACLs at a conceptual level, DNS and content delivery.
- Management and governance: monitoring, logging, auditing and infrastructure as code, again as "which service does what".
- Migration and AI/ML services: recognise the headline purpose of each.
- Deployment and connectivity options: the idea of public internet, private connections and hybrid setups.
Build a one-page cheat sheet as you go: service name on the left, one-line purpose on the right. Re-reading that sheet every day beats re-watching lectures.
Week 3: Billing, Pricing, and Support, Then Practice
Billing, Pricing, and Support is 12%, and the content is compact. Give it two days.
What to drill in Billing, Pricing, and Support
- Pricing models: On-Demand, Savings Plans, Reserved capacity and Spot, and which workload suits each.
- Cost tools: know the purpose of the pricing calculator, cost exploration and budgeting tools.
- Consolidated billing and what AWS Organizations changes.
- The support plan tiers and what each adds. Learn the differences between them as a comparison, since questions often ask which plan provides a specific capability.
- The free tier concept and how data transfer costs behave in general terms.
Use the remaining days for timed practice
Spend the last five days on full-length timed sets. Simulate the real conditions: 65 questions, 90 minutes, no notes. After each set, sort every miss into one of three buckets: did not know the fact, misread the question, or fell for a distractor. Drill each bucket differently.
A practice bank with explanations matters more than volume. The CertCrush AWS Certified Cloud Practitioner CLF-C02 course includes 400 practice questions, 200 flashcards and a study guide, so you can read a topic, test it and review the misses in one place.
Common Traps on the CLF-C02
These are the patterns that cost marks, even when the candidate knows the material.
- Over-engineering the answer. The exam targets foundational knowledge. Pick the answer that solves the stated need with the least complexity.
- Missing the multiple-response instruction. If the question asks you to choose more than one answer, you must select the stated number. Read the instruction line first.
- Confusing similar services. Security groups versus network ACLs, S3 versus EBS, and the different security detection services are frequent confusions. Write contrasts side by side.
- Mixing up the shared responsibility split. Read who is being asked about: AWS or the customer. The same service can appear on both sides depending on the wording.
- Leaving questions blank. Unanswered counts wrong and guessing carries no penalty. Flag hard questions, and answer every one before time runs out.
- Studying out-of-scope material. Coding, architecture design, troubleshooting, implementation and load testing are not tested. Do not spend hours on CLI syntax.
Your Study Guide Checklist
Before you book the exam, check that you can do the following without notes:
- Name the four domains and their weights.
- Explain the shared responsibility model with two examples for each side.
- Match a described need to a service across compute, storage, database and networking.
- Compare the pricing models and the support plans.
- Finish a timed set within 90 minutes with time left to review flagged questions.
If you pass your practice sets consistently with room to spare, you are ready. If one domain keeps dragging your results down, give it another two days before you book.
Frequently Asked Questions
How hard is the AWS Certified Cloud Practitioner exam?
It is an entry-level exam aimed at candidates with up to 6 months of AWS exposure, including people from non-IT backgrounds. Difficulty depends mostly on how much AWS service vocabulary you have absorbed. Candidates who study by domain and practise under timed conditions find the question style predictable.
Do I need to code for CLF-C02?
No. Coding, architecture design, troubleshooting, implementation and load testing are all out of scope for this exam. You need to recognise services and concepts, not build with them.
How long should I study for the AWS Cloud Practitioner exam?
Most candidates with no AWS background do well with three weeks of regular study. Existing AWS users can compress to two weeks, and complete beginners can stretch to four. Measure readiness by practice results, not by calendar days.
Is there a penalty for wrong answers?
No. There is no penalty for guessing, and an unanswered question counts as wrong. Answer every question.
Ready to Start Practising?
The fastest way to find your weak domain is to answer questions under exam conditions. Create a free CertCrush account and start with the CLF-C02 course. If you plan to continue after this exam, our AWS AI Practitioner study plan is the natural next step.