CLF-C02 — AWS Certified Cloud Practitioner Study Plan
A practical 7-, 14-, 30-, and 60/90-day study plan for the AWS Certified Cloud Practitioner (CLF-C02) exam.
Who this Study Plan is for
This Study Plan is for candidates preparing for the AWS Certified Cloud Practitioner (CLF-C02) exam from AWS. It is designed for people who need a practical schedule, not just a list of topics.
The CLF-C02 exam is foundational, but it still requires disciplined review. You should be able to recognize AWS services, explain basic cloud concepts, understand shared responsibility, identify billing and support options, and choose appropriate services for common business scenarios.
Use this plan to organize:
- AWS cloud concepts and terminology
- Security, compliance, and shared responsibility topics
- Core AWS services and common use cases
- Billing, pricing, support, and cost-management concepts
- Timed practice and missed-question review
This page is independent exam-prep guidance and is not affiliated with AWS.
Which plan should you use?
Choose the path based on your remaining time and current comfort level.
| Time available | Best for | Main goal | Practice expectation |
|---|---|---|---|
| 7 days | Final review or urgent retake prep | Tight weak-area correction and exam readiness | Daily timed sets, one or two mock exams |
| 14 days | Candidates with some AWS exposure | Focused coverage plus repeated practice | Diagnostic, domain drills, two mock exams |
| 30 days | Most candidates | Balanced learning, practice, and review | Weekly timed practice, two or three mock exams |
| 60/90 days | Newer cloud learners or busy professionals | Full concept build with gradual retention | Weekly drills, hands-on review, staged mocks |
If you are unsure, start with a diagnostic set before choosing:
| Diagnostic result | Recommended path |
|---|---|
| Strong score with only a few weak areas | 7-day final review |
| Mixed score, many recognizable topics | 14-day focused plan |
| Low or uneven score across domains | 30-day balanced plan |
| New to AWS or limited study time per week | 60/90-day full preparation path |
What to study for CLF-C02
Do not study every AWS service equally. For the AWS Certified Cloud Practitioner (CLF-C02) exam, focus on recognizing service purpose, basic use cases, cloud value, security ownership, and cost implications.
| Area | What you should be able to do |
|---|---|
| Cloud concepts | Explain elasticity, scalability, high availability, global infrastructure, managed services, and cloud value |
| Shared responsibility | Identify what AWS manages and what the customer manages in common scenarios |
| Identity and access | Understand IAM users, groups, roles, policies, MFA, least privilege, and root user protection |
| Security and compliance | Recognize encryption, logging, monitoring, governance, compliance programs, and security services |
| Compute | Compare EC2, Lambda, containers, and managed compute at a high level |
| Storage | Match S3, EBS, EFS, Glacier-class archival concepts, and storage use cases |
| Databases | Identify when to use relational, key-value, document, data warehouse, and managed database services |
| Networking | Understand VPC basics, subnets, route tables, security groups, network ACLs, DNS, and content delivery concepts |
| Monitoring and operations | Recognize CloudWatch, CloudTrail, AWS Config, Trusted Advisor, and basic operational visibility |
| Cost and billing | Understand pricing models, cost allocation, budgets, cost exploration, savings options, and support resources |
| Architecture | Choose simple, reliable, secure, cost-aware AWS designs for common business needs |
Daily practice rhythm
Use the same daily structure regardless of your timeline. Short, consistent sessions are better than passive reading.
| Session block | Time | What to do |
|---|---|---|
| Warm-up recall | 5-10 min | Write down key services or concepts from memory before looking at notes |
| Focused study | 25-45 min | Review one topic area, service family, or exam objective cluster |
| Practice questions | 20-40 min | Complete a targeted set, not just random questions |
| Missed-question review | 20-30 min | Classify mistakes and rewrite the rule you missed |
| Quick recap | 5-10 min | Add 3-5 facts, comparisons, or decision rules to your review sheet |
For longer study days, repeat this rhythm twice with different topic areas.
Diagnostic-first setup
Before building a schedule, complete a diagnostic practice set.
| Step | Action | Output |
|---|---|---|
| 1 | Take a mixed CLF-C02 practice set without notes | Baseline score and timing |
| 2 | Mark every question as confident, unsure, or guessed | Confidence map |
| 3 | Review missed and guessed questions | Weak-area list |
| 4 | Group misses by topic | Study priorities |
| 5 | Choose your plan | 7, 14, 30, or 60/90 days |
Track mistakes by category:
| Mistake type | Example | Fix |
|---|---|---|
| Service confusion | Mixing CloudWatch and CloudTrail | Build service comparison cards |
| Responsibility error | Misidentifying AWS vs customer duties | Drill shared responsibility scenarios |
| Cost misconception | Confusing discount models or support resources | Review billing and pricing decision rules |
| Security gap | Missing IAM, MFA, encryption, or logging clue | Review security controls by use case |
| Architecture mismatch | Choosing the wrong service for a simple scenario | Practice service-selection questions |
7-day final review plan
Use this plan if your exam is within one week. Do not try to learn every AWS service from scratch. Focus on high-value recognition, weak areas, and timed practice.
7-day schedule
| Day | Focus | Study actions | Practice actions |
|---|---|---|---|
| 1 | Diagnostic and triage | Take a mixed timed set. Build your weak-area list. | Review every missed and guessed question. |
| 2 | Cloud concepts and global infrastructure | Review Regions, Availability Zones, edge locations, elasticity, scalability, fault tolerance, and managed services. | Drill cloud concepts and architecture vocabulary. |
| 3 | Security and shared responsibility | Review IAM, MFA, root user protection, least privilege, encryption, logging, and compliance concepts. | Drill shared responsibility and security scenario questions. |
| 4 | Core services | Review compute, storage, database, networking, and monitoring service purposes. | Complete service-selection drills. |
| 5 | Billing, pricing, and support | Review pricing models, cost tools, budgets, tagging, support resources, and account governance. | Complete cost and support questions. |
| 6 | Timed mock exam | Take a full timed mock. Review deeply. | Build a final weak-area sprint list. |
| 7 | Final review only | Review notes, missed-question log, service comparisons, and exam-day pacing. | Light mixed set only; stop early if accuracy is stable. |
7-day rules
- Stop adding new services after Day 5 unless they appear repeatedly in missed questions.
- Spend more time reviewing explanations than taking new questions.
- Do not take a full mock late on the night before the exam.
- Focus on recognition: “What problem does this AWS service solve?”
- Keep a one-page sheet of confusing pairs, such as CloudWatch vs CloudTrail, security groups vs network ACLs, and S3 vs EBS vs EFS.
14-day focused plan
Use this plan if you have two weeks and some AWS familiarity. The goal is to cover all major CLF-C02 topic areas while building a strong missed-question review loop.
14-day schedule
| Day | Focus | Main task | Practice task |
|---|---|---|---|
| 1 | Diagnostic | Take a mixed diagnostic set and sort misses. | Create your tracker. |
| 2 | Cloud value and deployment models | Review cloud benefits, CapEx vs OpEx concepts, scalability, elasticity, and migration drivers. | Cloud concepts drill. |
| 3 | AWS global infrastructure | Study Regions, Availability Zones, edge locations, high availability, and disaster recovery basics. | Infrastructure scenario questions. |
| 4 | Shared responsibility | Review customer vs AWS responsibilities by service type. | Shared responsibility drill. |
| 5 | IAM and security basics | Review IAM users, groups, roles, policies, MFA, root account, KMS, and encryption concepts. | IAM and security drill. |
| 6 | Governance and compliance | Review CloudTrail, CloudWatch, AWS Config, Organizations, control concepts, and compliance resources. | Security and governance questions. |
| 7 | Compute and containers | Review EC2, Lambda, Elastic Beanstalk, container concepts, and managed compute selection. | Compute service-selection drill. |
| 8 | Storage and databases | Review S3, EBS, EFS, archival concepts, RDS, DynamoDB, Redshift, and database selection. | Storage/database comparison drill. |
| 9 | Networking and content delivery | Review VPC basics, subnets, routing, security groups, network ACLs, Route 53, and CloudFront concepts. | Networking scenario questions. |
| 10 | Monitoring and operations | Review CloudWatch, CloudTrail, Trusted Advisor, AWS Health, Systems Manager concepts, and operational visibility. | Operations drill. |
| 11 | Billing and cost management | Review pricing models, budgets, cost tracking, tags, cost optimization, and support plans. | Billing and support questions. |
| 12 | Mixed review | Revisit the three weakest areas from your tracker. | Timed mixed set. |
| 13 | Full timed mock | Take a full mock under exam-like conditions. | Review all misses and guessed answers. |
| 14 | Final readiness | Review final notes, confusing services, and pacing plan. | Light practice only. |
14-day checkpoints
| Checkpoint | You are ready to move on if… |
|---|---|
| After Day 5 | You can explain shared responsibility and IAM basics without notes |
| After Day 9 | You can match common workloads to compute, storage, database, and networking services |
| After Day 11 | You can answer cost, billing, and support questions without relying on memorized wording |
| After Day 13 | Your missed questions are concentrated in a few fixable areas, not spread everywhere |
30-day balanced plan
Use this plan if you want a complete but efficient preparation cycle. This is the best default option for many CLF-C02 candidates.
Weekly structure
| Week | Goal | Outcome |
|---|---|---|
| Week 1 | Build cloud and AWS foundation | Understand AWS terminology, infrastructure, and shared responsibility |
| Week 2 | Learn service families | Recognize compute, storage, database, networking, and monitoring services |
| Week 3 | Strengthen security, governance, cost, and support | Improve scenario accuracy and billing knowledge |
| Week 4 | Timed practice and final weak-area repair | Convert knowledge into exam-ready performance |
30-day schedule
| Days | Focus | Actions |
|---|---|---|
| 1 | Diagnostic | Take a mixed diagnostic. Create your missed-question tracker. |
| 2-3 | Cloud concepts | Study cloud value, elasticity, scalability, reliability, deployment models, and managed services. |
| 4 | AWS global infrastructure | Review Regions, Availability Zones, edge locations, global services, and high availability basics. |
| 5-6 | Shared responsibility and IAM | Study AWS vs customer responsibility, IAM identities, roles, policies, MFA, root user protection, and least privilege. |
| 7 | Weekly review | Take a timed mixed set. Review misses. Update weak-area list. |
| 8-9 | Compute | Review EC2, Lambda, container concepts, managed compute, scaling, and when to use each. |
| 10-11 | Storage | Review S3, EBS, EFS, archival storage concepts, lifecycle ideas, and storage selection. |
| 12-13 | Databases and analytics | Review RDS, DynamoDB, Redshift, data lake concepts, and database selection patterns. |
| 14 | Weekly review | Timed service-selection practice. Review all confused services. |
| 15-16 | Networking | Review VPC basics, subnets, route tables, gateways, security groups, network ACLs, Route 53, and CloudFront. |
| 17-18 | Monitoring and operations | Review CloudWatch, CloudTrail, AWS Config, Trusted Advisor, AWS Health, and operational support concepts. |
| 19-20 | Security and compliance | Review encryption, KMS concepts, logging, governance, Organizations, account management, and compliance resources. |
| 21 | Full or near-full timed mock | Take a timed mock. Spend at least as long reviewing as testing. |
| 22-23 | Billing and pricing | Review pricing concepts, budgets, cost allocation, tags, cost-management tools, and optimization principles. |
| 24 | Support and account resources | Review support plans, documentation resources, Trusted Advisor concepts, account support, and AWS service health resources. |
| 25-26 | Weak-area sprint 1 | Re-study your two weakest areas. Use targeted practice only. |
| 27 | Timed mock | Take a full timed mock under exam-like conditions. |
| 28 | Mock review | Review every missed, guessed, and slow question. Rewrite decision rules. |
| 29 | Final weak-area sprint 2 | Light targeted practice. Review service comparisons and shared responsibility. |
| 30 | Final review | Stop adding new material. Review notes, pacing, and exam-day checklist. |
30-day study targets
By the end of the plan, you should be able to:
- Explain the value of cloud computing in plain language.
- Identify common AWS services by purpose.
- Distinguish customer responsibilities from AWS responsibilities.
- Recognize IAM, encryption, monitoring, and governance controls.
- Select basic compute, storage, database, and networking services for simple scenarios.
- Interpret cost-management and support questions.
- Complete timed practice without rushing at the end.
60/90-day full preparation path
Use this path if you are new to cloud computing, have limited weekly study time, or want to build durable AWS knowledge before the CLF-C02 exam.
How to choose 60 vs 90 days
| Path | Best for | Weekly study time |
|---|---|---|
| 60 days | Some IT or cloud background | 5-7 hours per week |
| 90 days | New to cloud or very busy schedule | 3-5 hours per week |
The same phases apply to both paths. For 90 days, spend more time on hands-on review, repetition, and lower-pressure practice.
Phase plan
| Phase | 60-day timing | 90-day timing | Focus |
|---|---|---|---|
| Phase 1 | Days 1-10 | Days 1-15 | Cloud foundations and AWS terminology |
| Phase 2 | Days 11-25 | Days 16-38 | Core AWS service families |
| Phase 3 | Days 26-38 | Days 39-58 | Security, governance, monitoring, and operations |
| Phase 4 | Days 39-48 | Days 59-72 | Billing, pricing, support, and cost optimization |
| Phase 5 | Days 49-60 | Days 73-90 | Timed mocks, weak-area repair, and final review |
Phase 1: Cloud foundations
| Topic | Study actions | Practice actions |
|---|---|---|
| Cloud value | Review cloud benefits, agility, elasticity, scalability, reliability, and managed services. | Explain each concept in one sentence. |
| Deployment and service models | Review public cloud concepts, hybrid ideas, IaaS, PaaS, and SaaS. | Match examples to model types. |
| AWS global infrastructure | Study Regions, Availability Zones, edge locations, and high availability basics. | Answer infrastructure scenario questions. |
| Well-architected thinking | Review reliability, security, performance, cost, and operational excellence concepts at a high level. | Identify which pillar a scenario emphasizes. |
Phase 2: Core AWS service families
| Service family | What to learn | Practice focus |
|---|---|---|
| Compute | EC2, Lambda, containers, managed deployment concepts | Choose compute based on workload style |
| Storage | S3, EBS, EFS, archival concepts | Match storage to access pattern and use case |
| Databases | RDS, DynamoDB, Redshift, other managed database concepts | Distinguish relational, NoSQL, and analytics needs |
| Networking | VPC, subnets, routing, security groups, network ACLs, DNS, CDN concepts | Identify basic connectivity and access controls |
| Integration and messaging | Queue, notification, and event-driven concepts | Recognize decoupling scenarios |
| Migration and transfer | Common migration and data transfer concepts | Recognize when migration tools are relevant |
Keep service notes brief. For each service, write:
| Field | Example prompt |
|---|---|
| Purpose | What problem does this service solve? |
| Common use case | When would a beginner choose it? |
| Managed by AWS? | What operational work is reduced? |
| Security angle | How is access controlled or logged? |
| Cost angle | What usage pattern may affect cost? |
| Confused with | Which service is commonly mixed up with it? |
Phase 3: Security, governance, monitoring, and operations
| Topic | What to know |
|---|---|
| Shared responsibility | Responsibility changes depending on service type and configuration |
| IAM | Users, groups, roles, policies, MFA, root user protection, least privilege |
| Encryption | Basic encryption concepts, key management concepts, and data protection terminology |
| Logging and monitoring | Difference between operational metrics, logs, API activity, and configuration tracking |
| Governance | Multi-account concepts, policy guardrails, tagging, and account organization |
| Security services | Recognize common AWS security and compliance services by purpose |
| Operational support | Health, advisory, monitoring, and support resources |
Practice with scenario wording. Many CLF-C02 questions are less about command syntax and more about recognizing the service or concept that fits the business need.
Phase 4: Billing, pricing, support, and cost optimization
| Area | Study actions |
|---|---|
| Pricing concepts | Understand pay-as-you-go, usage-based pricing, reservation/savings concepts, and free-tier style ideas at a high level |
| Cost visibility | Review budgets, cost exploration, billing dashboards, tags, and cost allocation concepts |
| Cost optimization | Identify right-sizing, managed services, storage lifecycle ideas, and pricing model selection |
| Support | Understand support resources, support plan concepts, documentation resources, and account help paths |
| Account management | Review account structure, consolidated billing concepts, and governance basics |
Do not memorize long pricing tables. Focus on which tool, model, or support resource answers the scenario.
Phase 5: Timed practice and final review
| Timing | Action |
|---|---|
| 12-14 days before exam | Take a full timed mock or long timed set |
| 10 days before exam | Review all misses and rebuild weak-area list |
| 7 days before exam | Begin final review plan |
| 5 days before exam | Stop broad new learning |
| 2-3 days before exam | Take final timed practice if it helps confidence |
| 1 day before exam | Light review only |
Hands-on concept review for CLF-C02
The CLF-C02 exam is not a deep hands-on administration exam, but light console familiarity can make service concepts easier to remember.
Use hands-on review carefully:
| Topic | Useful hands-on review | What not to overdo |
|---|---|---|
| IAM | View users, groups, roles, policies, and MFA settings conceptually | Do not spend hours writing complex policies |
| S3 | Review buckets, objects, access settings, encryption, and lifecycle concepts | Do not memorize every storage setting |
| EC2 | Review instance concept, AMIs, security groups, and basic launch flow | Do not practice advanced troubleshooting |
| VPC | Review VPC, subnet, route table, and security group relationships | Do not go deep into custom network builds |
| CloudWatch and CloudTrail | Compare metrics/logs/alarms with API activity history | Do not memorize every dashboard option |
| Billing tools | Review budgets, cost views, tags, and cost allocation concepts | Do not memorize prices |
If you use an AWS account for practice, stay cost-aware and clean up resources after review.
Service comparison drills
Create short comparison cards for services that are easy to confuse.
| Pair | Decision rule |
|---|---|
| CloudWatch vs CloudTrail | CloudWatch is for metrics, logs, alarms, and operational monitoring; CloudTrail records AWS account API activity. |
| Security groups vs network ACLs | Security groups are instance/resource-level firewall controls; network ACLs apply at the subnet level. |
| S3 vs EBS vs EFS | S3 is object storage, EBS is block storage for EC2-style use, and EFS is shared file storage. |
| EC2 vs Lambda | EC2 provides virtual servers; Lambda runs code without managing servers. |
| RDS vs DynamoDB | RDS is managed relational database service; DynamoDB is managed NoSQL key-value/document style database. |
| Route 53 vs CloudFront | Route 53 handles DNS; CloudFront helps deliver content through edge locations. |
| AWS Config vs CloudTrail | AWS Config tracks resource configuration and changes; CloudTrail records API activity. |
| AWS Organizations vs IAM | Organizations manages multiple AWS accounts; IAM manages access within an account. |
| Budgets vs Cost Explorer | Budgets helps track and alert against cost or usage thresholds; Cost Explorer helps analyze cost and usage trends. |
Missed-question review method
The fastest way to improve is to review missed questions systematically. Do not just read the explanation and move on.
Use a five-step review
Restate the question in plain language. What was the scenario actually asking?
Identify the clue. Was the key clue cost, security, scalability, managed service, monitoring, or support?
Explain why the correct answer is correct. Write one sentence in your own words.
Explain why your answer was wrong. Was it the wrong service, wrong responsibility, wrong cost tool, or wrong level of management?
Create a decision rule. Example: “If the question asks for API activity history, think CloudTrail before CloudWatch.”
Missed-question tracker
| Date | Topic | Question clue | Your error | Correct rule | Retest date |
|---|---|---|---|---|---|
| IAM | Least privilege access | Picked broad permissions | Use least privilege and roles where appropriate | ||
| Monitoring | API call history | Chose monitoring metrics | CloudTrail records API activity | ||
| Cost | Analyze spend trends | Chose alerting tool | Cost Explorer analyzes cost trends |
Review the tracker every two or three study sessions. If the same topic appears repeatedly, schedule a focused drill before taking another mock.
When to use timed mock exams
Timed mocks are useful, but only after you have enough content coverage to learn from the results.
| Preparation stage | Use timed mock? | Better action |
|---|---|---|
| First few study days | Usually no | Take a diagnostic set instead |
| After first full content pass | Yes | Take a timed mixed set or mock |
| Two weeks before exam | Yes | Use results to plan weak-area repair |
| Final week | Yes, but limited | One full mock early in the week; lighter sets later |
| Day before exam | Usually no | Review notes and rest |
How to review a mock exam
| Review item | What to check |
|---|---|
| Missed questions | Why was the chosen answer wrong? |
| Guessed correct answers | Would you get it right again? |
| Slow questions | What concept caused hesitation? |
| Repeated weak areas | Which domain needs targeted study? |
| Service confusion | Which comparison card should you create? |
| Timing | Did you finish with enough review time? |
A mock exam is not complete until you have reviewed every missed, guessed, and slow question.
Final-week rules
Use the final week to stabilize, not to overload.
| Rule | Why it matters |
|---|---|
| Stop broad new material 3-5 days before the exam | New facts can crowd out recall of core concepts |
| Keep practice mixed | The real exam will not announce the topic area |
| Review weak areas daily | Repetition helps fix recurring errors |
| Prioritize shared responsibility, IAM, services, and billing | These concepts appear across many scenario types |
| Avoid memorizing exact pricing details | Focus on pricing models, tools, and decision logic |
| Sleep and pacing matter | Tired candidates misread simple scenario clues |
Exam-readiness checks
You are close to ready for the AWS Certified Cloud Practitioner (CLF-C02) exam when you can do the following without heavy notes:
| Readiness check | Yes/No |
|---|---|
| Explain AWS shared responsibility for common managed and customer-managed scenarios | |
| Identify when to use IAM users, groups, roles, policies, and MFA | |
| Match common workloads to EC2, Lambda, S3, EBS, EFS, RDS, DynamoDB, and CloudFront at a high level | |
| Distinguish CloudWatch, CloudTrail, AWS Config, Trusted Advisor, and AWS Health | |
| Recognize basic VPC, subnet, routing, security group, and network ACL concepts | |
| Choose cost-management tools for budgets, alerts, cost analysis, and allocation | |
| Understand basic AWS support and account resources | |
| Finish timed practice without consistently rushing | |
| Explain missed questions in your own words | |
| Identify and correct your top three weak areas |
If several checks are still “No,” delay full mock repetition and return to targeted drills.
Final 48-hour review
Use the last two days for consolidation.
Two days before exam
- Review your missed-question tracker.
- Revisit confusing service pairs.
- Complete one moderate mixed timed set if you need pacing practice.
- Review shared responsibility and IAM scenarios.
- Review billing, pricing, support, and cost-management decision rules.
One day before exam
- Do light review only.
- Stop difficult new practice early.
- Review your final notes and pacing strategy.
- Prepare exam logistics.
- Sleep normally.
Practical next step
Start with a mixed diagnostic practice set for CLF-C02. Then choose the 7-day, 14-day, 30-day, or 60/90-day path based on your weak areas and available study time. Use daily practice, missed-question review, and timed mocks to turn AWS concept knowledge into exam-ready performance.