CLF-C02 should be studied from concepts to service recognition, not by memorizing the AWS catalog alphabetically. Start with cloud value and economics, then shared responsibility/security, global infrastructure and core services, management/analytics/AI categories, and finally pricing/support. The current CLF-C02 domain weights help prioritize the sequence.
Phase one: learn why cloud exists
Study agility, elasticity, high availability, global reach, variable cost and economies of scale. Compare cloud with on-premises fixed infrastructure.
Attach every benefit to a business example so the language becomes concrete.
Phase two: learn Well-Architected and migration concepts
Review the six Well-Architected pillars and AWS CAF at a high level. Learn common migration strategies conceptually.
The goal is recognizing the right principle, not designing an enterprise migration.
Phase three: master shared responsibility
Compare customer/AWS responsibility for EC2, RDS and Lambda-style services. Ask who patches the guest OS, database engine, physical host and application code.
A shared responsibility table is one of the highest-value study aids for the security domain.
Phase four: build IAM and security vocabulary
Review IAM users/groups/roles/policies, MFA, federation, Identity Center, encryption, KMS, GuardDuty, Shield, WAF, Security Hub, Inspector and Artifact.
Use IAM to anchor least privilege and root-account protection before memorizing security-service names.
Phase five: learn global infrastructure
Understand Regions, Availability Zones and edge locations. Then map which concepts improve availability, latency or geographic reach.
Do not over-study architecture patterns beyond the foundational exam level.
Phase six: group services by problem
Create categories for compute, storage, databases, networking, analytics, integration, management/governance, security, serverless and AI/ML.
Use S3, RDS, EC2, Lambda and VPC as anchors for the most common categories.
Phase seven: learn networking and content delivery at a high level
Review VPC, subnets conceptually, Route 53, CloudFront, API Gateway, Direct Connect, VPN, PrivateLink and Transit Gateway by use case.
Route 53 and CloudFront make DNS versus content-delivery roles easier to separate.
Phase eight: study management and operations services
Learn CloudWatch, CloudTrail, Config, Systems Manager, Organizations, Control Tower, Trusted Advisor and Well-Architected Tool by purpose.
Again, the exam asks “what is this for?” more often than “how do I configure it?”
Phase nine: master pricing, cost and support
Compare On-Demand, Reserved Instances, Savings Plans, Spot, storage tiers and data-transfer concepts. Review Pricing Calculator, Cost Explorer, Budgets, CUR and support resources.
Use the 12% domain weight to keep this section important but proportionate.
Finish with business-oriented scenarios
Practice choosing a service or concept for simple business needs: global static content, object storage, relational database, serverless code, budget alert, compliance report or least-privilege access.
Keep a one-page cloud glossary during the first phase: elasticity, scalability, availability, agility, fault tolerance, variable cost, economies of scale, Region, Availability Zone and edge. Rewrite each term in business language rather than copying definitions verbatim.
During Well-Architected study, create six mini-scenarios—one for each pillar. For example, automated operational learning, encryption/least privilege, multi-AZ recovery, right resource type, rightsizing/commitment discounts and efficient resource use. This makes the pillars easier to distinguish.
During migration study, review AWS CAF perspectives/capabilities only to the depth needed to recognize the framework’s role. Then compare rehost, replatform, refactor/modernize and other migration strategies conceptually. Avoid implementation details that belong to associate/professional exams.
During shared-responsibility study, use a matrix for EC2, RDS, Lambda and S3. Put physical facilities, hypervisor, OS/runtime, application, data, IAM and configuration on rows and mark AWS/customer responsibility. This prevents memorizing one oversimplified slogan.
During security study, categorize services by problem: identity (IAM/Identity Center), detection (GuardDuty/Inspector), protection (WAF/Shield), encryption (KMS), compliance (Artifact), audit/configuration (CloudTrail/Config) and secrets. Categories reduce the load of remembering many service names.
During global-infrastructure study, draw one Region with several Availability Zones and an edge location outside it. Annotate why a company might choose another Region or use CloudFront. Keep the diagram simple enough to reproduce from memory.
During compute study, compare EC2, Lambda, ECS/EKS/Fargate and Lightsail by management model and use case. The exam is likely to reward the simplest fit, not a deeply engineered architecture.
During storage study, make a four-column table for object, block, file and archive. Add typical service examples and access patterns. Then practice one-line scenarios such as website assets, EC2 boot disk, shared Linux files and long-term backup retention.
During database study, separate relational, key-value/NoSQL, graph, document and cache categories at a recognition level. AWS’s in-scope list includes several specialized services, but the exam does not expect database-engine tuning.
During networking study, learn VPC, Route 53 and CloudFront first because they solve clearly different problems. Then add Direct Connect/VPN, Transit Gateway, PrivateLink and Global Accelerator by use case. Avoid detailed routing-table exercises.
During operations study, compare CloudWatch, CloudTrail and Config in one scenario. A high CPU alert points to CloudWatch; unexpected API change to CloudTrail; a resource drifting from required settings to Config. These distinctions are repeatedly useful.
During cost study, create simple examples for On-Demand, Spot, Savings Plans/Reserved commitment and Capacity Reservation. Ask what the organization values: flexibility, discount for predictable use, interruptible low cost, or guaranteed capacity.
During cost-tool study, separate before-versus-after spend. Pricing Calculator helps estimate before deployment; Cost Explorer reviews spend; Budgets alerts on thresholds; CUR supports detailed reporting. Use one business sentence for each tool.
During support study, map common resources: documentation/Knowledge Center/re:Post for self-service help, Support for account/technical assistance according to plan, partners for third-party expertise and Professional Services for AWS-led assistance.
Use the in-scope service list late in preparation as a gap check, not as your first study method. Mark each service with one category and one use case. If you can do that, you likely know enough for a foundational recognition question.
Practice multiple-response questions carefully because AWS can require two or more correct choices. Read whether the prompt asks for “two” or “all that apply” style selections and evaluate each option independently rather than searching for one obviously correct service.
Keep final mock questions business-oriented. CLF-C02 explicitly excludes implementation and troubleshooting. If your practice questions require CLI commands or subnet calculations, they are probably outside the intended exam depth.
Before test day, rebuild the 24/30/34/12 weights from memory and allocate review accordingly. Cloud Technology/Services and Security together account for 64% of scored content, but Cloud Concepts and Billing/Support still provide enough questions to affect the overall 700 passing score.
Add one scoring-awareness session before final mocks. Remember that 50 questions are scored and 15 are unscored, but candidates cannot identify which are which. Treat every question seriously and use the published domain weights for preparation rather than trying to infer scoring during the exam.
Add one responsibility comparison for customer-managed EC2 software versus RDS versus Lambda. This is a high-yield security exercise because the same concept appears in architecture, compliance and service-selection questions.
Add one “same requirement, different service” drill. Need compute? Compare EC2, Lambda and containers. Need storage? S3, EBS and EFS. Need database? RDS/Aurora and DynamoDB. The contrast trains recognition faster than learning each service alone.
Add one governance drill that separates Organizations, Control Tower, Config, CloudTrail and IAM. Each can appear in multi-account/security questions, but they manage accounts, landing-zone governance, configuration compliance, API auditing and access respectively.
Add one cost scenario for each purchasing model. An always-on predictable workload may benefit from commitment discounts; batch work tolerant of interruption may fit Spot; uncertain short-term demand may fit On-Demand; guaranteed EC2 capacity is a different requirement from a discount.
Add one support-resource drill: documentation/re:Post/Knowledge Center, AWS Support, partners and Professional Services. Identify whether the scenario asks for self-service information, a technical support relationship, third-party expertise or AWS-led consulting.
For the final 48 hours, stop adding obscure services. Review domain weights, the shared-responsibility matrix, one service map, cost tools and common security/governance distinctions. CLF-C02 is a breadth exam; clarity on fundamentals is more valuable than associate-level depth.
Add one daily 10-minute service-category drill. Pick five AWS services from the in-scope list and state category plus one use case in a single sentence. Stop when you can classify unfamiliar names by context rather than memorizing long feature lists.
Add one security-distinction drill covering CloudWatch, CloudTrail, Config, GuardDuty, Security Hub, Inspector, WAF, Shield and Artifact. Ask whether the service monitors, audits, evaluates configuration, detects threats, aggregates findings, assesses vulnerabilities, filters web traffic, protects against DDoS or supplies compliance documents.
Add one global-infrastructure scenario where the user base is worldwide. Decide whether the question is about choosing a Region, spreading across Availability Zones or serving cached content from edge locations. This prevents “global” from automatically meaning multi-Region.
Add one final pricing worksheet with workload type, purchasing option, storage class, data-transfer concern and cost tool. Keep it conceptual; CLF-C02 does not require detailed bill calculations, but it does require recognizing which pricing model or tool fits the situation.
Finish with a verbal explanation suitable for a nontechnical manager: what AWS cloud provides, who secures what, which categories of services exist, how AWS charges for them and where support/compliance information comes from. If you can explain that clearly without jargon, you are studying at the intended foundational level.
Keep a final list of the few services you repeatedly confuse and rewrite each as “problem → service” rather than a definition. This targeted cleanup is more effective than rereading the entire service catalog during the last hours before the exam.
The Cloud Practitioner study approach should remain foundational. You are ready when you can explain why a service fits without drifting into implementation details the exam explicitly places out of scope.