CertVector

AWS Cloud Practitioner study guide

A six-week path from cloud vocabulary to CLF-C02 readiness.

CLF-C02 rewards knowing what AWS services do, who is responsible for which controls, and how billing/support choices fit real scenarios. Use this plan with CertVector drills to find the weak service categories quickly.

Sign in

CLF-C02 domain weights

Cloud Concepts

24%

AWS Cloud value, shared cloud benefits, elasticity, scalability, migration value, and Well-Architected concepts.

Security and Compliance

30%

Shared responsibility, IAM, MFA, encryption, compliance resources, monitoring, and security-oriented AWS services.

Cloud Technology and Services

34%

Core compute, storage, database, networking, management, monitoring, migration, analytics, and integration services.

Billing, Pricing, and Support

12%

Pricing models, purchasing options, budgets, cost tools, support plans, Organizations, and AWS Marketplace.

Weekly progression

Keep each week practical: answer questions, read rationales, and review misses before moving to faster timed sets.

Week 1

Cloud Concepts

Learn cloud value, elasticity, scalability, global infrastructure, and the basic Well-Architected vocabulary.

Week 2

Security and Shared Responsibility

Review shared responsibility, IAM, MFA, encryption, CloudTrail, compliance resources, and security services.

Week 3

Core Services

Build recognition for EC2, Lambda, S3, EBS, RDS, DynamoDB, VPC, Route 53, CloudFront, and CloudWatch.

Week 4

Service Selection

Practice choosing services by use case: compute versus storage, relational versus NoSQL, DNS versus CDN, and monitoring versus auditing.

Week 5

Billing, Pricing, and Support

Study pricing models, Free Tier, Budgets, Cost Explorer, Organizations, Marketplace, Support plans, and Trusted Advisor.

Week 6

Timed Readiness

Run mixed drills, review missed explanations, tighten weak domains, and complete timed simulations before exam day.

Use the plan inside the product

Start with mixed Cloud Practitioner drills, then use missed review and weak-domain filters to separate service-name confusion from security and billing gaps.