Cloud terms are new and service names feel arbitrary.
Begin with cloud value, shared responsibility and service categories before learning individual AWS names.FREE STUDY PLAN
AWS Cloud Practitioner: plan by evidence
This sequence is adjustable. Move forward when you can demonstrate the skill named by the official outline—not merely because a calendar says the week is over.
CHOOSE YOUR STARTING LINE
Three candidates need three different plans
Infrastructure concepts are familiar but AWS naming and billing are not.
Map familiar compute, network, storage, identity and monitoring concepts to AWS, then focus on responsibility and pricing differences.You know a few services deeply but have gaps across the official in-scope list.
Audit the exam guide to find categories your job does not touch, especially governance, support and cost tools.Week 1
Cloud value and responsibility
Master Cloud Concepts and the shared-responsibility model before memorizing service names.
- Write the official domain or task this work covers.
- Produce an explanation, comparison, interpretation, or safe practice outcome.
- Record uncertainty as a source to revisit—not a fact to guess.
Week 2
Security and core services
Study identity, governance and service categories with short use-case comparisons.
- Write the official domain or task this work covers.
- Produce an explanation, comparison, interpretation, or safe practice outcome.
- Record uncertainty as a source to revisit—not a fact to guess.
Week 3
Cost, support and mixed scenarios
Add billing and support, then mix all four domains with official-style scenarios.
- Write the official domain or task this work covers.
- Produce an explanation, comparison, interpretation, or safe practice outcome.
- Record uncertainty as a source to revisit—not a fact to guess.
Readiness check
Explain, do not only recognize
You should be able to justify a category, responsibility or cost tool without relying on answer choices.
- Write the official domain or task this work covers.
- Produce an explanation, comparison, interpretation, or safe practice outcome.
- Record uncertainty as a source to revisit—not a fact to guess.
WHEN MORE STUDY IS NOT BETTER STUDY
Recognize the failure loop
You keep adding service names to flashcards.
Why it fails: A name without a problem and boundary is easily confused with distractors.
Reset: For each service, add use case, customer responsibility, closest alternative and one limitation.
Mock scores stall despite long video courses.
Why it fails: Passive coverage may not repair specific comparison gaps.
Reset: Pause full mocks and drill only confusion pairs and missed task statements.
You study architecture design in depth.
Why it fails: Detailed design and implementation are outside the target role described by the foundational guide.
Reset: Return to the CLF-C02 task verbs: explain, understand, describe and identify.
Readiness checks by domain
A practice score can be useful, but it is not the only signal. Before scheduling, try to perform the checks below without prompts.
- Cloud Concepts — 24%Given a business goal, identify which cloud benefit addresses it and why.
- Security and Compliance — 30%For a scenario, name who is responsible, what control applies and which service category helps.
- Cloud Technology and Services — 34%Explain why a service category fits the requirement and why an adjacent category does not.
- Billing, Pricing and Support — 12%Choose the appropriate cost-management or support resource for a stated need.
A weekly review loop
1. Choose
Pick one official domain and a small number of objective statements.
2. Learn
Use a primary or clearly version-matched resource and write a plain-language explanation.
3. Demonstrate
Compare, interpret, configure, explain, or apply—matching the objective verb.
4. Repair
Return uncertainty to the exact official section and update your gap list.
Make the scheduling decision honestly
STRONG READINESS SIGNALS
- You can choose between commonly confused services and state the deciding requirement.
- You can explain shared responsibility for managed and less-managed service models.
- Your gap list covers the official in-scope categories, not just services used at work.
PAUSE AND REPAIR IF
- Your notes are mostly an alphabetical service glossary.
- You cannot explain why the wrong service is plausible but less suitable.