AWS Certified Cloud Practitioner (CLF-C02)
AWS Cloud Practitioner Study Plan: Four Weeks to Prepare
A four-week AWS Cloud Practitioner study plan can work if you study consistently, test your understanding throughout and extend the timetable when your results show gaps. Start with cloud concepts, move into security and core AWS services, then reserve the final week for mock exams and targeted revision. As a planning allowance rather than a readiness guarantee, aim for about an hour on most study days, with a longer session for review or practice questions. Complete beginners may need more time, while people who already use cloud services may progress faster. Your ability to explain unfamiliar scenarios matters more than completing four calendar weeks.
This timetable supports preparation for AWS Certified Cloud Practitioner (CLF-C02), a foundational exam covering cloud concepts, security and compliance, cloud technology and services, and billing, pricing and support. Use the official AWS exam guide as your scope checklist and check the current exam page before booking. For structured lessons, the Erudex [AWS Certified Cloud Practitioner (CLF-C02) course](/courses/aws-cloud-practitioner) can sit alongside this plan. Combine lessons with closed-book recall, optional hands-on exploration and practice questions rather than relying on videos alone. Any course-completion certificate is separate from AWS Certification, which requires passing the official AWS exam. The weekly checkpoints below help you decide whether to continue or slow down.
Key points
- •Treat four weeks as an adaptable timetable, not a guaranteed preparation period.
- •Pair lessons with closed-book recall, spaced review and fresh scenario questions.
- •Use optional labs carefully and check costs before creating resources.
- •Extend preparation when mock exams reveal persistent gaps or memorised answers.
Set up your study schedule and establish a baseline
Before day one, download the current CLF-C02 exam guide and turn its task statements into a simple checklist. The published domain weightings are Cloud Concepts, 26%; Security and Compliance, 30%; Cloud Technology and Services, 34%; and Billing, Pricing and Support, 10%. Use these to balance revision, not to ignore smaller domains. Take a short diagnostic quiz without consulting notes, then label each topic as familiar, uncertain or new. Record why you missed each question: missing knowledge, confusion between services or misreading the requirement. This baseline gives your AWS Cloud Practitioner study guide a practical structure and shows where extra sessions may be needed.
If you are wondering how long to study for AWS Cloud Practitioner, begin with your baseline rather than someone else's timetable. Across each week, schedule five learning sessions, one review session and one rest or catch-up day. A useful one-hour session might include 25 minutes of lessons, 15 minutes of closed-book recall and 20 minutes of questions with explanation review. These are suggested allocations, not an AWS requirement. Keep a short error log and revisit older topics every few days. If work or family commitments regularly interrupt your sessions, spread the same sequence over more weeks rather than compressing missed lessons into a single exhausting weekend.
- •Keep the official exam guide as your master scope checklist.
- •Use one main lesson source and current AWS documentation.
- •Track errors by topic and cause, not just quiz score.
- •Reserve catch-up time before choosing an exam date.
Week one: Explain cloud concepts without your notes
Use days one and two to understand why organisations adopt cloud computing: on-demand resources, elasticity, agility and the shift away from purchasing all infrastructure upfront. Learn the differences between scalability, elasticity, availability and reliability, since they describe related but distinct properties. On days three and four, cover cloud deployment models, the AWS global infrastructure and the purpose of Regions, Availability Zones and edge locations. Include the AWS Well-Architected Framework pillars and basic migration concepts at an introductory level. On day five, revisit everything through short business scenarios, such as choosing infrastructure for variable demand or explaining why an organisation might deploy across multiple Availability Zones.
For each topic, close your notes and give a plain-English explanation before checking the lesson again. For example, explain why using several Availability Zones can improve resilience, while choosing an AWS Region also involves latency, service availability and data residency considerations. Optional exploration this week can be limited to AWS documentation and architecture diagrams; you do not need to create resources to understand these concepts. During the weekly review, answer a fresh set of concept questions and explain why the alternatives are less suitable. If your answers depend on recognising familiar wording rather than understanding the scenario, add more retrieval practice before moving on.
- •Days 1–2: Cloud benefits and essential terminology.
- •Days 3–4: Global infrastructure, architecture and migration concepts.
- •Day 5: Scenario questions and closed-book explanations.
- •Day 6: Review errors and revisit weak concepts.
- •Checkpoint: Distinguish elasticity, scalability and availability in new examples.
Week two: Learn security responsibilities and access controls
Focus the second week on the AWS shared responsibility model, identity, data protection and security-related services. Begin by distinguishing security of the cloud from security in the cloud, then compare customer responsibilities for Amazon EC2 with those for more managed services. Study AWS Identity and Access Management concepts, including users, groups, roles and policies, along with least privilege and multi-factor authentication. Understand why root user credentials require particular protection and should not be used for routine tasks. Extend your review to encryption, compliance resources and the broad purposes of services such as AWS CloudTrail, Amazon GuardDuty, AWS Shield and AWS Artifact.
Build comparison cards that ask a specific question rather than merely naming a service. For example, ask which service records account activity and API events, or where customers can access AWS compliance reports. Mix in questions from week one so that security study does not displace earlier knowledge. If you choose a hands-on activity, use an authorised sandbox and inspect an example IAM policy or a provided CloudTrail event. Avoid experimenting in a production account. The checkpoint is whether you can assign responsibilities correctly and select an appropriate security service in unfamiliar scenarios. Extend this week if you still assume that AWS manages every aspect of customer data or access.
- •Days 1–2: Shared responsibility and IAM fundamentals.
- •Days 3–4: Data protection, detection and compliance resources.
- •Day 5: Security scenarios mixed with cloud-concept questions.
- •Day 6: Review access-control mistakes and service confusion.
- •Checkpoint: Explain how customer responsibilities vary by service.
Week three: Compare core services and understand cloud costs
Start week three with the core service families: compute, storage, databases and networking. Compare Amazon EC2, AWS Lambda and container services at the level of their common use cases, not detailed implementation. Distinguish Amazon S3 object storage, Amazon EBS block storage and Amazon EFS file storage. Contrast relational database services such as Amazon RDS with Amazon DynamoDB, and learn the basic purposes of Amazon VPC, Elastic Load Balancing, Amazon Route 53 and Amazon CloudFront. Use the remaining days to survey other service categories listed in the exam guide, including analytics, AI and machine learning, application integration, migration, and management and governance.
Reserve meaningful time for billing and support rather than treating them as an afterthought. Compare On-Demand usage, commitment-based savings options and Spot Instances, including the interruption trade-off. Learn when to use AWS Pricing Calculator, AWS Cost Explorer and AWS Budgets, plus the broad role of consolidated billing through AWS Organizations. Check current AWS support documentation because offerings and features can change. An optional lab could involve exploring a cost estimate without deploying resources. If you do deploy anything, check charges first and remove resources afterwards; billing alerts are not spending caps. Your checkpoint is choosing suitable services and cost tools while explaining the trade-offs.
- •Days 1–2: Compute, storage and database comparisons.
- •Days 3–4: Networking and other exam-guide service categories.
- •Day 5: Pricing models, cost tools and support resources.
- •Day 6: Mixed review and optional low-risk exploration.
- •Checkpoint: Choose services from requirements, not keyword matching.
Week four: Use mock exams to decide whether you are ready
Begin the final week with a timed, full-length mock exam using questions you have not already memorised. The standard CLF-C02 exam has 65 multiple-choice or multiple-response questions and a 90-minute duration; confirm current arrangements and any applicable accommodations on the official exam page. Erudex [practice tests](/practice) can support your question practice, alongside official AWS preparation resources. Review every incorrect answer and every correct answer that was a guess. For each one, identify the underlying concept, explain why the distractors are unsuitable and schedule a short follow-up lesson. Spend the next two or three sessions repairing those gaps before attempting another fresh mock.
Use the second mock to judge consistency, pacing and reasoning, not just improvement in a percentage. AWS reports a scaled exam score, so a third-party practice percentage does not translate directly into an official result. Readiness looks like broadly consistent performance across domains, time to review flagged questions and explanations that do not rely on memorised wording. If one domain remains weak, add a focused week of lessons, recall and new questions, then reassess. If gaps span several domains, return to the earlier checkpoints. Keep the final day light: review your error log, confirm identification and test arrangements, and prioritise rest over another long mock.
- •Day 1: Complete a fresh timed mock.
- •Days 2–4: Repair gaps and revisit uncertain answers.
- •Day 5: Take a second fresh mock and compare error patterns.
- •Day 6: Make a readiness decision and check exam logistics.
- •Checkpoint: Extend preparation when reasoning or coverage remains inconsistent.
Frequently asked questions
- Is four weeks enough to prepare for AWS Cloud Practitioner?
- Four weeks can be a workable preparation window, but it is not a guarantee. Your starting knowledge, available study time and ability to retain concepts all affect the timetable. Someone familiar with IT terminology may move through foundational lessons faster than a complete beginner. Use weekly checkpoints and fresh practice questions to assess progress. If you cannot explain your answers or repeatedly miss the same concepts, extend the plan rather than booking solely because week four has arrived.
- Can a beginner follow this AWS Cloud Practitioner study plan?
- Yes. CLF-C02 is a foundational certification, and AWS does not require another certification before taking it. Beginners should allow extra time for basic ideas such as networking, databases, virtual servers and identity management. Start with plain-English explanations, then connect each concept to an AWS service. If the first week feels rushed, spread it over two weeks. That adjustment preserves the sequence of the plan without forcing you to learn unfamiliar cloud and IT terminology at the same pace.
- Do I need hands-on labs or a paid AWS account?
- Hands-on labs are optional for this plan. The exam assesses foundational knowledge and service selection rather than requiring you to perform live configuration tasks. Carefully chosen labs can make abstract concepts easier to remember, but documentation, diagrams and guided demonstrations also help. If your AWS training includes a sandbox, check its rules and limits. Before using your own account, verify current pricing and account offers, protect access and understand resource cleanup. Do not assume that a small experiment will automatically be free.
- What mock exam score means I am ready?
- There is no universal mock exam percentage that guarantees a pass. Practice providers differ in difficulty, coverage and scoring, while AWS uses a scaled scoring system. Look for consistent performance on fresh questions, balanced understanding across all four domains and the ability to explain why an answer fits the scenario. Review guessed answers even when they are correct. Repeating the same mock until its score rises is less informative than applying your knowledge to a new, well-aligned question set.
Study it properly: AWS Certified Cloud Practitioner (CLF-C02)
Master fundamental cloud computing architectures, security governance, and AWS core services for the CLF-C02 exam.