CLF-C02 Practice-First Study Plan

The goal: explain what AWS provides, who is responsible, and which broad service or cost model fits a business need.

This is CloudCert learning guidance, not an official AWS passing policy. It combines retrieval practice, immediate feedback, spaced review, mixed-domain practice, and realistic simulations.

Start with a diagnostic

Complete 25-30 mixed questions without notes. Use untimed practice mode so you can concentrate on reasoning.

Classify every mistake:

Concept gap: you did not understand a cloud benefit, security principle, or pricing idea.
Service gap: you confused the purpose of two AWS services.
Responsibility gap: you assigned a task to AWS when it belongs to the customer, or the reverse.
Reading gap: you missed words such as most cost-effective, managed, global, or compliance report.
Freshness gap: you relied on an outdated Free Tier, Support-plan, or service-name fact.

Write the failed assumption in one sentence. For example:

"I treated security in the cloud as entirely AWS's responsibility, but customers still control their data, identities, permissions, and workload configuration."

Start CLF-C02 practice

Build your study map

Use the official weights to prioritize your time:

Cloud Technology and Services - 34%
Security and Compliance - 30%
Cloud Concepts - 24%
Billing, Pricing, and Support - 12%

Do not ignore the smallest domain. Billing and Support questions are often highly learnable, but older study material is especially risky because the Free Tier and Support portfolio have changed.

Use one repeatable learning loop

Work on one task statement at a time:

Retrieve first - Say what you currently believe before opening documentation.
Learn narrowly - Read the relevant official AWS page, not an entire service manual.
Compare - Contrast the correct concept with the most plausible alternative.
Apply - Answer a fresh question without notes.
Explain - State why the correct option fits and why each distractor fails.
Record - Save the misconception, not the full question.
Revisit - Recall it again after roughly 1, 3, 7, and 14 days.

Move on when you can explain the idea in plain language and solve a different example without hints.

Learn services by purpose, not by catalogue

Organize services around business questions:

Where should this workload run?
Where should this data be stored?
Which service connects or delivers traffic?
Which database model fits the stated need?
Which service records activity, monitors resources, or detects threats?
Which tool forecasts, tracks, allocates, or controls cost?
Which AWS resource provides documentation, expert help, or account guidance?

For each service, learn four facts:

its primary purpose;
whether it is managed, serverless, global, or regional when that distinction matters;
the nearest confusing alternative;
one situation where it is not the correct choice.

Avoid memorizing changing quotas, prices, instance specifications, and console sequences unless the official task statement genuinely requires the concept.

Study the four domains deliberately

Cloud Concepts

Explain elasticity, scalability, high availability, agility, economies of scale, variable expense, global reach, migration value, and the AWS Cloud Adoption Framework at a business level.

Security and Compliance

Practise classifying shared responsibilities. Distinguish IAM, IAM Identity Center, Organizations, Artifact, CloudTrail, Config, GuardDuty, Inspector, Macie, Shield, and WAF by purpose rather than implementation steps.

Cloud Technology and Services

Build category-level comparisons across compute, storage, database, networking, analytics, integration, management, and AI/ML. Foundational questions usually ask what a service does, not how to configure it.

Billing, Pricing, and Support

Compare On-Demand, Savings Plans, Reserved Instances, Spot, and dedicated options conceptually. Distinguish Budgets, Cost Explorer, Cost and Usage Reports, and Pricing Calculator. Verify current Free Tier and Support facts in live AWS documentation.

Structure a focused 40-minute session

5 minutes: recall yesterday's misconceptions;
15 minutes: answer 12-20 questions from one weak task;
15 minutes: review every option, including correct guesses;
5 minutes: create one or two short retrieval prompts.

Once a weak task becomes stable, mix it with older topics so recognition depends on the scenario rather than the session label.

Run realistic exam simulations

Simulation setup

Reserve 90 uninterrupted minutes.
Use 65 fresh questions.
Remove notes, documentation, and notifications.
Include both single-response and multiple-response questions.
Use an approximate 16/19/22/8 split across Domains 1-4 when every practice item is scored.

During the simulation

Answer every question because AWS does not penalize guessing.
Flag uncertain items and return later.
Do not pause to research a service.
Check for unanswered questions before submitting.

After the simulation

Review reasoning only after submission.
Group mistakes by official task statement.
Separate knowledge, service-confusion, responsibility, reading, and freshness errors.
Turn repeated errors into the next focused sessions.

Open mock exams

CloudCert readiness target: at least 80% on three fresh timed simulations, with no domain below 75%.

This is a practical study recommendation, not an AWS passing rule or guarantee. A CloudCert percentage cannot be converted directly into AWS's scaled 700 passing score.

Use AI as a tutor

AI helps most when it makes you commit before it explains. Require current official AWS citations for changing technical claims, then open those sources yourself.

Prompt: diagnose a task

I am preparing for AWS CLF-C02.
Ask me five foundational questions about task [task ID], one at a time.
Do not reveal the answer until I commit.
After each answer, identify the assumption behind my reasoning,
explain every option, and cite current official AWS documentation.

Prompt: compare confusing services

Teach me the difference between [service A] and [service B] at CLF-C02 depth.
First ask what I think each service does.
Then give me one business scenario and make me choose before explaining.
Avoid implementation steps and changing quota trivia.

Prompt: practise shared responsibility

Give me ten short AWS shared-responsibility scenarios.
For each one, make me classify the owner as AWS, the customer, or shared.
Do not reveal the answer until I explain my choice.
Correct my rule in one plain-language sentence.

Prompt: repair an outdated fact

I learned this AWS fact: [claim].
Check whether it is still current using official AWS sources.
If it changed, explain the old model, the current model, the effective date,
and give me a new retrieval question that avoids unstable trivia.

Never treat AI output, leaked exam content, or an exam dump as authoritative. Current AWS documentation is the technical source of truth.

A simple four-week rhythm

Week 1 - Cloud value and core services

Establish the business-level cloud concepts, then learn the purpose of major compute, storage, database, and networking services.

Week 2 - Security and responsibility

Concentrate on the shared responsibility model, identity, governance, compliance resources, monitoring, and threat-protection services.

Week 3 - Costs, support, and mixed practice

Study purchasing models, cost tools, the current Free Tier, and current Support options. Mix earlier domains into every session.

Week 4 - Simulate and repair

Complete fresh 90-minute simulations. Spend more time repairing repeated misconceptions than consuming new content.

Final readiness checklist

I can finish 65 questions within 90 minutes.
I have completed three fresh timed simulations at my target level.
I can distinguish similar AWS services by their primary purpose.
I can classify shared responsibilities consistently.
I understand current Free Tier and Support concepts without relying on old absolutes.
I can explain why distractors fail, not only why the correct answer works.
I verify uncertain or changing facts in current official AWS documentation.
No official domain remains consistently weak.

Turn any remaining weak checklist item into the next small study mission.