AWS Cloud Practitioner Study Plan and Revision Schedule

Start from the CLF-C02 exam guide

Study for AWS Certified Cloud Practitioner CLF-C02 by using the current exam guide as your scope map. The four domains are Cloud Concepts (24%), Security and Compliance (30%), Cloud Technology and Services (34%), and Billing, Pricing, and Support (12%). The largest domains deserve substantial time, but the weights are not a promise of exact question counts and do not make the 12% domain optional.

The target exam is foundational. AWS expects candidates to explain cloud value, understand shared responsibility, recognize core services and common use cases, and understand costs and billing. The guide lists coding, cloud architecture design, troubleshooting, implementation, and load or performance testing outside the target candidate's scope. This means preparation should focus on concepts and service fit rather than deep configuration tutorials.

A six-week study schedule

The schedule below is a flexible example. It does not prescribe a universal number of study hours or guarantee a pass. Candidates with AWS experience may spend less time on familiar services and more on weak topics; candidates new to IT or cloud can extend the phases. Use a diagnostic or official pretest to decide whether to add time.

A shorter plan can combine weeks, but preserve a final mixed review and a full timed practice session. A longer plan can break each domain into smaller topics and add regular retrieval practice. Do not let the calendar replace evidence of learning: extend the plan when fresh practice shows unresolved gaps.

Use a weekly learning loop

1. Read the domain task statements and note what a candidate must understand or identify.
2. Study one topic using an official guide, course, or concise reference.
3. Close the resource and explain the idea in plain language from memory.
4. Answer a short question set without looking at explanations first.
5. Review all incorrect and guessed answers; record the concept and why distractors fail.
6. Revisit one earlier topic in mixed order later in the week.

For example, a note that says 'CloudTrail equals API activity history; CloudWatch monitors metrics, logs, and events' is more actionable than copying two definitions into a notebook. A practice item can then ask which service helps investigate who changed a resource and which service can alarm when a metric crosses a threshold. The distinction is memorable because it is tied to different tasks.

Study Cloud Concepts through business decisions

Cloud Concepts includes cloud value, design principles, migration approaches, and economics. Practice explaining why a business might value elasticity, agility, high availability, global infrastructure, or economies of scale. Distinguish high availability from elasticity: multiple Availability Zones support availability, while Auto Scaling changes capacity with demand.

For migration, focus on the business constraint. A legacy application with strict dependencies may initially move with limited changes; another workload may be replaced by a managed service. Understand that migration strategy is a choice, and that cloud adoption includes people, process, and business change. The exam is not asking you to execute a migration plan.

For economics, compare fixed and variable costs, on-premises infrastructure expenses, licensing approaches, rightsizing, and automation. A company with idle compute might reduce waste by stopping nonproduction instances outside work hours or selecting a better-sized resource. The point is to identify the cost concept and appropriate tool, not calculate an exact bill from an incomplete prompt.

Build a shared responsibility comparison

Security questions become easier when you compare service models. AWS secures the cloud infrastructure it operates. Customers remain responsible for their data, identities, and service configuration, but the precise boundary shifts by service. On EC2 the customer manages the guest operating system and patches. In a managed database or serverless service, AWS manages more of the underlying stack, while customers still control data access, code, and configuration within their part.

Make a table for EC2, Amazon RDS, and AWS Lambda. For each, list what AWS operates and what the customer configures. Add examples for IAM least privilege, MFA, root-user protection, encryption, CloudTrail, CloudWatch, Config, Artifact, GuardDuty, and Security Hub. This prevents the common error of assuming that 'cloud provider handles security' means the customer has no security work.

Learn service fit by categories

Create comparisons for service categories rather than memorizing isolated product names. Compute: EC2 virtual machines, containers through ECS or EKS, serverless functions through Lambda, and container execution through Fargate. Databases: RDS or Aurora for relational workloads, DynamoDB for NoSQL patterns, and ElastiCache for in-memory caching. Storage: S3 for objects, EBS for block volumes, and EFS or FSx for file storage.

Then add networking and global services: VPC provides a logically isolated network, Route 53 handles DNS, CloudFront distributes content, and Direct Connect or VPN provides connectivity options. For integration, compare SQS queues, SNS notifications, and EventBridge event routing. Learn a one-sentence purpose and a likely use case for each service named in the current guide.

Practice Billing, Pricing, and Support explicitly

Billing and support receives the smallest listed weight but has distinct tool questions. AWS Pricing Calculator estimates a planned design. Cost Explorer helps inspect historical spending. AWS Budgets tracks cost or usage against thresholds and can notify. Cost allocation tags organize billing data. AWS Organizations supports multiple accounts and consolidated billing. Practice choosing by the verb in the scenario: estimate, inspect, alert, allocate, or consolidate.

Also recognize On-Demand, Reserved Instances, Spot Instances, Savings Plans, Dedicated Hosts, and Capacity Reservations at a high level. Match purchase choices to commitment, flexibility, interruption tolerance, and capacity requirements. For support, learn where to find documentation, Knowledge Center, Prescriptive Guidance, re:Post, support cases, and AWS Partner assistance.

Review questions for reasoning, not just a score

AWS's official preparation page recommends learning the exam, refreshing AWS knowledge, reviewing and practicing, then assessing readiness. It links an official practice question set, pretest, digital courses, Builder Labs, Cloud Quest, AWS Jam, SimuLearn, and the official practice exam. Use these resources to find gaps, not to assume that completing every activity is required.

When reviewing a question, name the business outcome, eliminate services that do a different job, and explain why the right choice fits. If an answer is correct because you guessed, count it as a learning gap. If a wrong answer stems from a close service distinction, write a short comparison and create a new example. Question-bank completion alone is not proof of readiness.

A timed readiness check

CLF-C02 has 65 questions in 90 minutes, about 83 seconds per item on average. Complete one 65-question timed practice session after broad study. Use checkpoints near questions 16, 32, and 48. Practice selecting all requested options on multiple-response items and flag difficult questions for later review. Finish with every item answered because unanswered responses are scored incorrect and guessing has no penalty.

After the session, review errors by domain, concept, and reason. Did you confuse shared responsibility, choose a service based on its name, overlook a cost qualifier, or spend too long? Then take a fresh set after review. AWS's reported 700 scaled passing score is not a raw percentage conversion from a practice test, so use the test to improve understanding and pacing rather than predict a precise official score.

The final week

In the final week, revisit your short comparisons, weak task statements, and official practice explanations. Avoid starting a large new course unless it addresses a concrete unresolved concept. Confirm the appointment time and time zone, account-name match, identification, and delivery setup. For online proctoring, run the system test on the actual computer and network. For a test center, plan travel and early arrival.

A sample week in practice

In Week 2, a learner can use one session to map the shared responsibility model across EC2, RDS, and Lambda. A second session can compare identity, logging, and security services. In a short question set, explain why a customer remains responsible for S3 bucket access even though AWS operates the storage infrastructure. Finish with a fresh scenario about an API change, identifying CloudTrail as the source for account activity and CloudWatch as a service for metrics, logs, and alarms.

In Week 5, take a sample monthly bill scenario. First decide whether the task is to estimate a planned architecture or inspect existing costs. Then decide whether the organization needs an alert, a project-level tag, or consolidated billing across accounts. This sequence helps separate tools that may all appear under the general label 'cost management.'

A weekly rhythm that balances learning and retrieval

This cadence reduces two common study problems. Reading every resource without checking recall can create familiarity without usable knowledge. Repeating question sets without learning concepts can create memorized letters. Alternating explanation, retrieval, and application gives a better view of whether a candidate can use a concept in a different context.

Adapt the plan to your background

A business professional may already understand budgeting and project tradeoffs but need more work with service categories and identity basics. A systems administrator may recognize EC2 and VPC yet need review of migration economics, AWS support resources, and the limits of the exam's security scope. A student with no cloud exposure can spend more time establishing vocabulary and use diagrams to connect Regions, Availability Zones, and edge locations.

Adapt by moving time toward gaps, but preserve a final mixed review of all domains. Do not conclude that experience in one AWS service covers a whole domain. Someone who works with S3 may still need to learn block and file storage, S3 storage classes, lifecycle policies, and AWS Backup. Someone who uses IAM daily may still need compliance documentation, root protection, federated identity, and other security services.

Make the error log specific

A useful error note is a short rule plus a new test. Examples: 'Pricing Calculator estimates a proposed design; Cost Explorer reviews recorded spend'; 'AWS operates physical infrastructure, while the customer configures data access'; 'SQS queues work for consumers; SNS publishes notifications to subscribers.' Then write or find a different scenario that asks you to apply the distinction. If you cannot explain why the other service is wrong, revisit the concept.

Include correct guesses in the log. A lucky correct answer can hide an incomplete mental model. Mark confidence if helpful, but do not turn confidence into a score target. A candidate's goal is a reasoned answer across unseen questions, not certainty about every service name.

Know when to extend a schedule

If fresh questions reveal broad gaps in two or more domains, extend the study period or narrow each session to a task statement. If the only issue is pace, practice timed mixed sets and use the flag-for-review method. If questions are missed because the prompt's business requirement is misread, slow the first pass and practice paraphrasing the ask before looking at answer choices.

A scheduled exam date is a planning aid, not proof of readiness. AWS's rescheduling deadline is 24 hours before the appointment, so make the decision early enough to preserve options. A late cancellation or no-show can forfeit the fee. Use diagnostic evidence and the current appointment policy rather than forcing an exam date because a calendar says the six-week plan is over.

Readiness is the ability to explain core concepts, select appropriate services in unfamiliar scenarios, distinguish customer and AWS duties, and finish a timed mixed set at a steady pace. A plan should adapt to evidence of learning. Keep all four domains in view, practice with explanations, and use the current official guide as the scope boundary.