CLF-C01 and CLF-C02 are successive versions of the AWS Certified Cloud Practitioner exam—not two certifications that candidates choose between today. AWS offered CLF-C01 through September 18, 2023 and introduced CLF-C02 on September 19, 2023. The distinction matters because search results, archived practice questions, and older study guides still refer to CLF-C01. A reader preparing now should follow AWS CLF-C02 and use the older blueprint only to understand why some material looks different.
The meaningful change is not that AWS abandoned foundational cloud literacy. CLF-C02 reorganized the same four broad areas, increased the weight of security and compliance, explicitly included cloud adoption and migration concepts, and refreshed the service examples. AWS documented the transition in its 2023 certification announcement and its current CLF-C02 exam guide. This comparison separates the historical facts from the present study consequences.
Compare the scored domain weights directly
| Domain | CLF-C01 | CLF-C02 | Change |
|---|---|---|---|
| Cloud Concepts | 26% | 24% | −2 percentage points |
| Security and Compliance | 25% | 30% | +5 percentage points |
| Technology / Cloud Technology and Services | 33% | 34% | +1 percentage point |
| Billing and Pricing / Billing, Pricing, and Support | 16% | 12% | −4 percentage points |
The table records the blueprint changes, not a prediction about exactly how many questions will appear in one sitting. In CLF-C02, AWS defines 50 scored and 15 unscored questions within a 65-question examination. The passing scaled score is 700, and the scheduled exam duration is 90 minutes. Domain percentages apply to scored content, so it is incorrect to multiply each percentage by 65 and treat the result as a fixed question count.
The five-percentage-point increase in Security and Compliance is the largest change in domain weight. Technology still accounts for the largest single share at 34%. Billing and pricing remain testable even at a smaller percentage, while the fourth domain’s name now explicitly includes support. A current learner should allocate effort according to both domain weight and their own knowledge gaps rather than dropping a domain that received a lower weight.
What AWS actually added and reorganized
AWS’s CLF-C02 comparison describes a new task statement on benefits and strategies for migration to the AWS Cloud, including the AWS Cloud Adoption Framework. It also describes recategorization of concepts that previously appeared under other tasks. This is important because a new location in the outline does not automatically mean a concept was invented for CLF-C02. Conversely, an old question bank does not become current merely because its general topic—say, S3 or IAM—still exists.
CLF-C01 labeled its third area “Technology”; CLF-C02 uses “Cloud Technology and Services.” The newer guide provides task statements for deploying and operating in the cloud, global infrastructure, compute, databases, networking, storage, and other service categories. It makes the evaluation of appropriate services more explicit. This is a change in instructional organization and emphasis, not an expectation that Cloud Practitioner candidates become cloud systems administrators.
The migration addition gives foundational students a reason to understand why organizations move workloads, how business and operational planning influence migration, and what architectural trade-offs can follow. It is not a command-line migration-engineering exam. CLF-C02 remains designed for candidates who can demonstrate overall AWS knowledge independently of any single job role.
Cloud Concepts: migration is now explicit
Cloud Concepts fell slightly from 26% to 24%, but the content still shapes the rest of the exam. Candidates must distinguish availability, elasticity, scalability, agility, and the economic value of usage-based services. CLF-C02 also directly references migration benefits and strategies, where the AWS Cloud Adoption Framework (CAF) helps examine business, people, governance, platform, security, and operations capabilities needed for cloud transformation.
Do not confuse CAF with the AWS Well-Architected Framework. CAF addresses an organization’s ability to adopt and operate cloud capabilities; Well-Architected reviews specific workloads against six architecture pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. Organizations can apply both at different decision levels. An old CLF-C01 lesson might cover design principles adequately but still under-explain migration and adoption governance as CLF-C02 describes them.
A useful transition exercise is to take an old “why move to cloud?” paragraph and ask whether it considers staffing, governance, security, and migration planning as well as costs and elasticity. That reveals genuine content gaps without assuming every passage written for CLF-C01 is wrong.
Security and Compliance: the weighting makes the boundary harder to ignore
Security and Compliance grew from 25% to 30%. The shared responsibility model is fundamental: AWS secures the underlying cloud infrastructure, while customers are accountable for their data, identity and access configurations, and other service-dependent controls. Managed services shift some operational responsibility to AWS but do not remove customers’ accountability for secure use.
Consider three levels of management. On Amazon EC2, the customer normally administers the guest operating system and workload. On Amazon RDS, AWS manages the underlying database platform infrastructure, while customers still manage application access, database configuration choices, and data controls. In AWS Lambda, AWS manages the server infrastructure but the customer owns code, dependencies, permissions, and data handling. Explaining these differences makes the model useful; memorizing “security of versus in the cloud” without examples does not.
For identity, know the purpose of IAM roles, policies, multi-factor authentication, root-account protection, and least privilege. Distinguish an IAM permission grant from a governance limit such as a service control policy. For monitoring and protection, separate services by task: CloudTrail records supported API/account activity, CloudWatch monitors operational telemetry, GuardDuty detects threats, AWS Config tracks configuration, and AWS KMS helps manage encryption keys.
These service categories have evolved since CLF-C01 was in use. An older source can be conceptually helpful but may use an obsolete product name, support-plan feature, or service scope. Use AWS’s current published task statements rather than assuming a historical example is still a recommended architecture.
Technology and Services: broader examples, same foundational level
The third domain rose from 33% to 34%, and its updated name emphasizes services. The main skill is matching needs to technology categories. For compute, EC2 is a virtual-server option; Lambda executes code in an event-driven managed environment; container services separate packaging from orchestration and compute management. A question about provisioning a guest operating system points toward a different answer from one about short functions triggered by events.
For storage, Amazon S3 is object storage, Amazon EBS is block storage commonly attached to EC2, and Amazon EFS is shared file storage. Their access models matter more than vague terms such as “secure cloud disk.” The practical EBS versus S3 difference also helps readers see why an old study card that classifies both simply as “storage” is too shallow.
For databases, Amazon RDS provides managed relational database options; Amazon DynamoDB provides a managed NoSQL model. For networking, Amazon VPC provides logical isolation, Route 53 supports DNS and related routing, Elastic Load Balancing distributes requests among targets, and CloudFront supports content delivery. Regions and Availability Zones concern placement and resilience, while edge locations concern delivery proximity for supported services.
AI/ML services and analytics appear in the CLF-C02 service references, but the level is service awareness rather than building and tuning a production model. The exact in-scope examples can change, so an old “complete list of AWS services you must memorize” is a particularly weak source. Confirm current examples against the official in-scope service list.
Billing, Pricing, and Support: a smaller percentage is not an exemption
The fourth domain moved from 16% to 12% and now says “Billing, Pricing, and Support.” CLF-C02 still expects candidates to compare pricing models and identify cost and support resources. On-Demand usage suits variable needs without a long-term discount commitment. Savings Plans exchange a defined spend commitment for reduced eligible usage pricing, while Reserved Instances involve instance-related commitment terms. Spot Instances can be interrupted, which changes their suitability for a workload.
Cost tools answer different questions. AWS Pricing Calculator supports estimates for planned resources. Cost Explorer analyzes actual usage and cost history; AWS Budgets tracks thresholds and notifications. Billing exports support detailed reporting and allocation. An old lesson may place all three into one generic “cost control” category, but exam scenarios can test why one tool is appropriate for an estimate and another for detecting a spending trend.
Support plans, pricing offers, and exact service entitlements may change. Avoid treating an archived support-tier name or stated response time as a permanent certification fact. Read current AWS support documentation when a question depends on a named benefit or date-sensitive commercial term.
How to handle old CLF-C01 preparation materials
Do not discard every older tutorial. Concepts such as IAM authorization, object versus block storage, high availability, and cloud economics remain useful. Instead, filter older material through three checks. Status: does it claim CLF-C01 is still bookable? If so, it is factually obsolete. Mapping: does the topic still appear in CLF-C02 task statements, and is it in a different domain? Technical currency: does the explanation match today’s AWS service behavior, vocabulary, and purchasing terms?
When an old question has a plausible answer but outdated service names, preserve the concept and replace the example with an official current reference. When a practice item assumes obsolete exam weights or claims that 65 questions all contribute to the score, reject it. Most importantly, do not confuse quantity of questions with quality of reasoning: a smaller bank with accurate explanations and realistic service-choice scenarios is more useful than thousands of unverified items.
A quick study audit is to review the six common comparisons: CAF versus Well-Architected; Region versus AZ versus edge; EC2 versus Lambda; S3 versus EBS; CloudTrail versus CloudWatch; and Pricing Calculator versus Cost Explorer. If an older resource does not help explain those contrasts correctly, supplement it with the current guide.
What the version change means for certification planning
CLF-C02 is a starting point for shared AWS vocabulary, not an automatic qualification to operate complex production systems. Candidates looking to design systems can later investigate AWS SAA-C03. Those aiming toward practical security engineering may eventually explore AWS SCS-C03. Neither credential is a required next step; choose based on the work you plan to do.
The conclusion is simple: CLF-C01 is historical, CLF-C02 is the current reference for this comparison, and the most important blueprint change is the increased emphasis on security along with explicit migration and updated service classification. Use old material selectively, verify time-sensitive claims, and measure readiness against the issuer’s present task statements rather than a previous exam version’s outline.