AWS CLF-C02 30-, 60-, and 90-day study plan for cloud basics, security, billing, review loops, and final-week priorities.
Use this study plan when you want a structured route through AWS Certified Cloud Practitioner (CLF-C02) instead of bouncing between service names. CLF-C02 is a foundational exam, not an architecture lab. The goal is to become reliable at cloud vocabulary, service-family recognition, security boundaries, billing logic, and support choices.
AWS’s current exam guide says CLF-C02 is for candidates who can demonstrate overall AWS Cloud knowledge independent of a specific job role. That matters: the exam rewards correct altitude. You usually need the right broad concept or service family, not associate-level design detail.
I verified these current AWS exam facts on May 16, 2026.
| Item | Value |
|---|---|
| Exam | AWS Certified Cloud Practitioner |
| Exam code | CLF-C02 |
| Category | Foundational |
| Questions | 65 total |
| Scoring | 50 scored + 15 unscored (unscored items are not identified) |
| Question types | Multiple choice and multiple response |
| Time | 90 minutes |
| Passing score | 700, scaled 100-1000 |
| Cost | 100 USD |
| Target candidate | Up to 6 months of AWS Cloud exposure; no IT background required |
AWS lists coding, cloud architecture design, troubleshooting, implementation, and load/performance testing as out of scope for the target candidate. Treat that as a study guardrail. If a topic turns into subnet routing tables, IAM policy evaluation depth, or database tuning, you have probably drifted beyond CLF-C02.
| Domain | Weight | How to allocate study time |
|---|---|---|
| Cloud Technology and Services | 34% | Spend the most time grouping AWS services by job: compute, storage, database, network, analytics, AI/ML, integration, management, and migration. |
| Security and Compliance | 30% | Drill shared responsibility, IAM basics, root account protection, compliance evidence, logging, and high-level security services. |
| Cloud Concepts | 24% | Learn cloud value, elasticity, scalability, resilience, global infrastructure, Well-Architected language, migration benefits, and cloud economics. |
| Billing, Pricing, and Support | 12% | Learn pricing models, cost tools, billing alerts, support plans, documentation resources, and partner/help options. |
The largest domain is service technology, but many misses come from security and pricing confusion. Do not study service names in isolation. Build lanes: concept, security boundary, service family, pricing tool, support option.
| Starting point | Typical study time | Best-fit timeline |
|---|---|---|
| You are in a business, sales, product, project, or management role | 25-40 hours | 30-60 days |
| You are new to IT and cloud | 30-50 hours | 60 days |
| You have help desk, admin, or developer exposure but little AWS | 18-35 hours | 30 days |
| You already passed another cloud fundamentals exam | 12-25 hours | 14-30 days |
Choose the longer route if shared responsibility, support plans, billing tools, and storage/database differences still blur together. CLF-C02 is broad, and broad exams punish fuzzy boundaries.
Use the same short loop every week.
flowchart LR
T["Topic"] --> L["Lane"]
L --> C["Contrast"]
C --> R["Recall rule"]
R --> Q["Small mixed set"]
Q --> M["Miss log"]
| Step | What to do |
|---|---|
| Topic | Pick one focused concept, service family, pricing idea, or support resource. |
| Lane | Classify it as cloud concept, security/compliance, technology/service, or billing/support. |
| Contrast | Compare it with two likely distractors. |
| Recall rule | Write one sentence from memory, not copied notes. |
| Mixed set | Answer a short mixed set so you practice switching lanes. |
| Miss log | Record what you confused and the rule that fixes it. |
Use this route if you can study most days or already have basic IT experience.
| Week | Focus | What to produce |
|---|---|---|
| 1 | Cloud concepts and security boundaries | A one-page sheet for cloud value, elasticity vs scalability, global infrastructure, Well-Architected basics, shared responsibility, and root-account protection. |
| 2 | Core service families | A service-family map for compute, storage, database, networking, analytics, AI/ML, integration, management, and migration. |
| 3 | Billing, pricing, support, and governance | A tool chooser for Pricing Calculator, Cost Explorer, Budgets, Billing, Trusted Advisor, AWS Health, re:Post, docs, and AWS Support. |
| 4 | Mixed practice and repair | Two timed or semi-timed mixed sets, a cleaned miss log, and a final review pass through the cheat sheet. |
Every day should end with one small artifact.
| Artifact | Why it matters |
|---|---|
| Service-family map | Prevents treating every product name as a separate memorization task. |
| Responsibility table | Keeps AWS responsibility and customer responsibility separate. |
| Pricing/support chooser | Fixes common confusion among Cost Explorer, Budgets, Pricing Calculator, Support, Health, and Trusted Advisor. |
| High-confusion pairs | Converts wrong answers into contrast rules. |
| Miss log | Shows whether you are missing concepts, service families, responsibility, pricing, or support. |
This is the best default route for candidates who are new to AWS.
| Weeks | Focus | What to do |
|---|---|---|
| 1-2 | Cloud Concepts | Learn cloud benefits, global infrastructure, elasticity, scalability, high availability, Well-Architected principles, migration basics, and cloud economics. |
| 3-4 | Security and Compliance | Drill shared responsibility, IAM, MFA, root account protection, encryption basics, compliance evidence, CloudTrail, Config, GuardDuty, Security Hub, Shield, and WAF. |
| 5 | Cloud Technology and Services | Build broad service-family recognition across compute, network, storage, databases, analytics, AI/ML, integration, deployment, and operations. |
| 6 | Billing, Pricing, and Support | Separate pricing models, cost tools, billing alerts, support plans, AWS Health, Trusted Advisor, re:Post, docs, and partners. |
| 7 | Mixed practice | Run short mixed sets. Group misses by lane, not by individual service. |
| 8 | Final repair | Revisit weak chapters, answer sample questions, reread the cheat sheet, and schedule only if misses are narrow. |
Use this route if you are fitting study around work, school, or a role outside IT.
| Phase | Weeks | Outcome |
|---|---|---|
| Cloud vocabulary | 1-2 | You can explain cloud benefits, deployment concepts, global infrastructure, elasticity, scalability, availability, and the value of managed services. |
| Security foundation | 3-5 | You can separate AWS responsibility from customer responsibility and identify IAM, MFA, root protection, compliance, logging, and security resources. |
| Service-family recognition | 6-8 | You can classify common AWS services by job without memorizing a raw alphabetized list. |
| Billing and support | 9-10 | You can choose pricing models, cost tools, support plans, technical resources, and partner options. |
| Exam execution | 11-12 | You can answer mixed foundational questions under time pressure and explain every repeated miss. |
| Domain | Drill questions until you can answer… |
|---|---|
| Cloud Concepts | Is this asking about cloud value, elasticity, scalability, resilience, migration, Well-Architected thinking, or economics? |
| Security and Compliance | Who is responsible, what identity/control/resource fits, and is the question about evidence, protection, detection, or access? |
| Cloud Technology and Services | Which service family does this job: compute, storage, database, networking, analytics, AI/ML, integration, management, or migration? |
| Billing, Pricing, and Support | Is the need estimation, analysis, alerting, billing visibility, technical guidance, operational health, or partner support? |
| Pair | Clean distinction |
|---|---|
| Scalability vs elasticity | Scalability is the ability to handle growth; elasticity is automatic growth and shrinkage with demand. |
| Region vs Availability Zone | A Region is a geographic AWS area; an Availability Zone is an isolated location inside a Region. |
| Edge location vs Region | Edge locations improve content delivery and edge services; Regions host most workload resources. |
| S3 vs EBS vs EFS | S3 is object storage, EBS is block storage for EC2, and EFS is shared file storage. |
| RDS vs DynamoDB | RDS is managed relational database; DynamoDB is managed NoSQL key-value/document database. |
| CloudTrail vs CloudWatch vs Config | CloudTrail records API activity, CloudWatch observes metrics/logs/alarms, and Config tracks resource configuration and compliance. |
| Pricing Calculator vs Cost Explorer vs Budgets | Calculator estimates before use, Cost Explorer analyzes usage/cost, and Budgets alerts against thresholds. |
| AWS Health vs Trusted Advisor vs Support | Health reports AWS events affecting resources, Trusted Advisor gives recommendations, and Support provides help through a support plan. |
CLF-C02 preparation should stay foundational.
| Do not spend much time on… | Learn this instead |
|---|---|
| Writing IAM policies by hand | IAM users, groups, roles, MFA, least privilege, and root account protection |
| Designing VPC routing in detail | VPC basics, public/private connectivity concepts, Route 53, CloudFront, and security groups at a high level |
| Tuning databases | Relational vs NoSQL, managed database services, and storage/database service families |
| Building production architectures | Cloud benefits, broad service fit, shared responsibility, cost controls, and support choices |
| Memorizing every AWS service | Recognizing common services by job to be done |
Use the final week to tighten boundaries, not to add deep architecture topics.
| Day | Work |
|---|---|
| 7 days out | Reread the cheat sheet and mark every concept/service you cannot explain in one sentence. |
| 6 days out | Drill cloud concepts: benefits, global infrastructure, Well-Architected basics, migration, and economics. |
| 5 days out | Drill security and compliance: shared responsibility, IAM, root account protection, logging, compliance evidence, and security resources. |
| 4 days out | Drill cloud technology and services: compute, storage, database, networking, analytics, AI/ML, integration, deployment, and operations. |
| 3 days out | Drill billing, pricing, support, and cost tools. |
| 2 days out | Run one mixed set and rewrite every repeated miss as a one-line rule. |
| 1 day out | Review only weak rules, official facts, high-confusion pairs, and exam logistics. |
You are close to ready when:
This can work only if you already know the material and need a final pass.
Schedule when your misses are narrow and explainable. If you still answer by memorized service name instead of concept lane, responsibility boundary, service family, or billing/support purpose, keep studying. CLF-C02 is an entry exam, but it still expects clean cloud literacy.