Someone who studied for AWS Certified Cloud Practitioner CLF-C01 may open a CLF-C02 guide and assume that every new heading describes a completely new skill. That is an expensive mistake. AWS changed the exam’s domain weightings, reorganized several existing objectives and introduced explicit cloud-migration and AWS Cloud Adoption Framework coverage. It did not replace foundational cloud knowledge with an advanced architecture exam. The useful comparison is between the tasks AWS actually published, not between marketing descriptions of how quickly cloud technology is evolving.
CLF-C01 ended on September 18, 2023, and CLF-C02 began on September 19, 2023. Anyone preparing for the current AWS Certified Cloud Practitioner assessment should use CLF-C02 objectives. But older CLF-C01 learning materials are not automatically worthless: many of the underlying service, security and cloud-economics concepts remain relevant. The work is to identify which sections still match and where the new objective map requires an update.
What changed in the official domain weights
The original CLF-C01 outline assigned 26% of scored content to Cloud Concepts, 25% to Security and Compliance, 33% to Technology, and 16% to Billing and Pricing. For CLF-C02, AWS lists Cloud Concepts at 24%, Security and Compliance at 30%, Cloud Technology and Services at 34%, and Billing, Pricing and Support at 12%. These percentages describe exam blueprint weightings, not a guarantee about the order or exact number of questions in any individual session.
The five-percentage-point increase for Security and Compliance is the largest shift. That makes shared responsibility, governance, identity and security-service identification particularly important to preparation. Yet a larger domain percentage does not mean all its ideas are newly invented. CLF-C01 also assessed shared responsibility, security concepts and aspects of access management; CLF-C02 distributes and names those tasks more explicitly.
The Technology domain’s small increase accompanies a change in how services are grouped. CLF-C02 separates compute, databases, networking, storage, AI/ML and other services into task statements that are easier to map to specific use cases. Billing, Pricing and Support has a smaller share but still demands knowledge of cost-management tools, support options and how AWS pricing works. A candidate who ignores it because its weighting fell can still make preventable mistakes.
Migration and AWS CAF are the clearest new content task
AWS’s original side-by-side guide explicitly identifies CLF-C02 Task 1.3—understanding the benefits of and strategies for migration to the AWS Cloud—as new content. It includes the AWS Cloud Adoption Framework (AWS CAF). This is the most concrete place to direct additional study if an older course never discussed cloud-adoption planning.
At the Cloud Practitioner level, AWS CAF is about connecting cloud adoption to organizational outcomes and perspectives. A migration is not simply a server copy. Business sponsors may care about cost and time to market; security teams may care about controls and governance; operations teams may care about reliability, skills and support processes. A good candidate can distinguish the purpose of an adoption framework from the purpose of a technical migration service.
Consider a retailer planning to move a legacy inventory database to AWS. The question is not asking an entry-level candidate to implement database replication. It may ask why an organization assesses dependencies, defines business outcomes, chooses a migration approach and accounts for operational readiness. AWS cites strategies and resources including database replication and AWS Snow Family examples, but the expected competence remains recognition and explanation rather than hands-on implementation.
Older CLF-C01 material can provide the definitions of elasticity, pay-as-you-go economics and shared responsibility behind that decision. The new objective adds the migration perspective that ties those concepts to a planned organizational change.
What AWS retained and rearranged from CLF-C01
In its version-comparison appendix, AWS says that no content was deleted and identifies seven earlier CLF-C01 task statements whose content was retained and recategorized. The affected areas include the cloud value proposition, cloud economics, architecture principles, security and compliance, core services, technical support and billing resources. This matters because a section moving between domains is not the same as a new technology suddenly appearing on the exam.
A concrete example is CLF-C01 Task 3.3, identifying core AWS services. AWS maps it across CLF-C02’s separate service-identification tasks, including compute, databases, networking, storage, AI/ML and other service categories. The AI/ML task is more visible in the new outline, but the official mapping means it is inaccurate to say that CLF-C01 had no AI-related service coverage whatsoever. CLF-C02 expects candidates to recognize relevant services and the types of problems they solve, not to train a model or implement a machine-learning system.
The same caution applies to serverless and containers. CLF-C02 names AWS Lambda, AWS Fargate, Amazon ECS and Amazon EKS in its service examples. These services should be learned in terms of their general purpose and operational tradeoffs. However, a current example in CLF-C02 is not evidence that serverless computing or containers were wholly unknown to CLF-C01. Avoid exaggerating the historical difference simply to make the new syllabus sound more demanding.
How to prepare for the revised security coverage
Start with the shared responsibility model. AWS secures the underlying cloud infrastructure; customers remain responsible for decisions such as access control and protecting what they configure and store, with details varying by service. Compare Amazon EC2 with a more managed service such as Amazon RDS: the degree of customer management changes, but neither situation removes the need to make appropriate identity and data-access decisions.
For IAM, learn what a user, group, role and policy is for, why temporary credentials matter and how least privilege changes a design. Understand why the account root user should be protected and seldom used for ordinary work. Make the question practical: if an application requires temporary access to an S3 bucket, a properly scoped role is more appropriate than a permanent root-user key. That reasoning is more useful than memorizing screenshots from a console version that has changed.
Recognize the different jobs of monitoring, auditing, posture management and threat detection. Amazon CloudWatch supports operational monitoring, AWS CloudTrail records API activity, AWS Config helps evaluate resource configuration, Amazon GuardDuty analyzes signals for suspicious activity, and AWS Security Hub brings together security findings. Each service has deeper capabilities, but CLF-C02 is principally concerned with selecting the category of service that addresses a scenario.
Do not confuse the security domain’s greater weighting with a shift into advanced incident response. Candidates are not expected to perform unrestricted penetration testing or design a production security architecture during the Cloud Practitioner exam. The target is a sound understanding of controls, responsibilities and the reasons different services exist.
Study cloud technology by use case, not by invented novelty
For compute, contrast running a managed virtual machine with executing code through a serverless service or operating containers through a managed platform. Amazon EC2 gives the customer choices about instance configuration and operating-system management. AWS Lambda is used for event-driven functions without provisioning servers in the same way. Amazon ECS and Amazon EKS help run containerized applications, while AWS Fargate supplies serverless compute capacity for supported container workloads. The important skill is recognizing which abstraction matches the described responsibility.
For databases, distinguish the broad use of a managed relational service such as Amazon RDS from a managed NoSQL service such as Amazon DynamoDB. For storage, know why Amazon S3 differs from block storage and file systems and how lifecycle or backup choices affect cost and recovery. For networking, recognize the roles of Amazon VPC, Amazon Route 53, Amazon CloudFront, AWS Direct Connect and VPN connectivity. The exam is not a request to configure every route, database parameter or storage policy; it asks whether you understand what each service does.
CLF-C02 also names AI/ML services in Task 3.7. Map examples to tasks: Amazon Rekognition analyzes images and video, Amazon Polly converts text to speech, Amazon Lex supports conversational interfaces, and Amazon SageMaker AI supports machine-learning workflows. When a problem asks for image analysis, identifying an appropriate service is the Cloud Practitioner skill. Building a production model or debugging feature-engineering code is outside the stated target job tasks.
When older study material describes the same service with a prior name or an outdated feature list, confirm the name and in-scope status against the current AWS exam guide. The correct update is precise and local. It is not necessary to replace every foundational explanation because AWS has added capabilities since the earlier exam.
Separate billing knowledge from billing terminology
CLF-C02’s Billing, Pricing and Support domain includes AWS pricing models, cost-allocation methods, budgeting and support resources. Explain why consumption-based pricing differs from an up-front capacity purchase, and why turning off a resource may or may not eliminate all associated costs. Distinguish tools that forecast spending from tools that show historical charges or enforce budget notifications.
A useful practice case is a department that wants to identify which application is generating unexpected charges. Ask what tagging or account structure can support cost allocation, what billing reports can reveal, and whether alerts were configured. Another case might describe a team comparing purchasing options for a predictable workload. You should be able to explain the economic tradeoff without inventing an exact current price.
Support options also remain in scope. A candidate should recognize when to consult AWS documentation or technical support resources and why support plans differ. Be careful with old plan names and prices: these are operational facts that can change after a textbook is published. Use first-party current references whenever the scenario relies on a named plan or price.
A practical way to update CLF-C01 study notes
First, label your old materials by topic rather than by their original chapter order. Keep sound explanations of cloud economics, global infrastructure, shared responsibility, basic IAM and core services. Remove unsupported statements that a service was ‘introduced in CLF-C02’ unless AWS’s published comparison actually supports that claim.
Second, work through the new migration and AWS CAF task deliberately. Explain how business goals, people, governance, technology and operations connect to the decision to migrate. Test whether you can distinguish a strategic adoption framework from a tool for moving data or applications.
Third, use the current four-domain weightings to allocate review time in proportion to your actual knowledge gaps. Someone already comfortable with IAM may need more attention on pricing; someone coming from nontechnical work may need extra practice recognizing storage, databases and compute. The blueprint weighting is a planning input, not a substitute for evidence about what you understand.
Finally, test with scenarios that force you to identify a service or responsibility and explain why similar-looking alternatives do not fit. One question about GuardDuty versus CloudTrail and another about Lambda versus EC2 teach more than an unstructured list of 100 AWS product names. Review only those details that the current objective list treats as relevant to the target candidate.
The main lesson from CLF-C01 to CLF-C02 is continuity plus targeted change. Security gained exam weight; service knowledge was reorganized; cloud-migration and AWS CAF coverage gained an explicit task. Treating every named AWS service as newly added misrepresents that transition and wastes study effort. Accurate preparation starts by reading the actual comparison, then filling the gaps it reveals.