CLF-C02
AWS Certified Cloud Practitioner
CLF-C02 Exam Guide: What It Validates and How to Prepare
CLF-C02, the AWS Certified Cloud Practitioner exam, validates broad knowledge of AWS Cloud concepts, security, core services, common use cases, and cloud economics rather than a specific job role. It suits candidates with limited practical exposure, including people beginning an AWS career and colleagues who work with cloud specialists. This guide helps you decide what to study first, how deeply to learn each service category, and when you are ready to schedule the exam.
Is CLF-C02 the right AWS certification for you?
CLF-C02 is designed for overall AWS Cloud knowledge independent of a specific job role. AWS describes the target candidate as someone with up to 6 months of exposure to AWS Cloud design, implementation, or operations. The practical decision is whether you need broad vocabulary and service recognition now, rather than role-specific engineering depth.
Who benefits most from this exam
The exam can fit several starting points: an early-career candidate pursuing cloud work, a nontechnical professional who needs to discuss AWS accurately, or someone who works with people in AWS Cloud roles. AWS identifies cloud concepts, security and compliance, core AWS services, and economics of the AWS Cloud as recommended knowledge areas.
A useful readiness question is not “Have I built a production system?” but “Can I explain why an AWS service or cloud approach fits a stated requirement?” You should be able to distinguish common service purposes, identify responsibility boundaries, and connect a business need such as availability, cost control, or low latency to an appropriate cloud concept.
What the certification does not require
Coding, cloud-architecture design, troubleshooting, implementation, and load or performance testing are listed as out of scope for CLF-C02. That does not make practical exposure useless; a small lab can make service distinctions easier to remember. It does mean your preparation should not turn into an advanced implementation course unless another goal requires it.
Do not postpone the exam because you cannot configure every service. Instead, learn the role of each service, the problem it addresses, and the major alternatives named in the blueprint. That is a better match for the official scope than memorizing command syntax or attempting complex architecture builds.
What does the CLF-C02 exam measure?
The exam measures four scored domains: Cloud Concepts, Security and Compliance, Cloud Technology and Services, and Billing, Pricing, and Support. AWS also includes unscored questions. Use the domain labels as a study map, but treat the task statements and service examples within each domain as the more useful guide to what you must recognize.
Domain 1: Cloud Concepts — 24% of scored content
Cloud Concepts represents 24% of the scored content on the exam. Its four task statements cover the benefits of the AWS Cloud, AWS design principles, migration benefits and strategies, and cloud economics.
Study this domain through decisions rather than isolated definitions. Link global infrastructure to speed of deployment and global reach; high availability, elasticity, and agility to workload behavior; and cloud economics to fixed versus variable costs, rightsizing, automation, licensing approaches, and economies of scale.
The AWS Well-Architected Framework is also in scope. Know the differences among operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. You do not need to treat the pillars as interchangeable: a question may describe one outcome while presenting another pillar as a distractor.
Migration preparation includes the AWS Cloud Adoption Framework and appropriate migration strategies, including database replication. Learn the business outcomes AWS associates with the framework, such as reduced business risk, improved environmental, social, and governance performance, increased revenue, and increased operational efficiency.
Domain 2: Security and Compliance — 30% of scored content
Security and Compliance represents 30% of the scored content on the exam. It covers the shared responsibility model, security governance and compliance, access-management capabilities, and security components and resources.
Make the shared responsibility model your anchor. AWS responsibilities, customer responsibilities, and shared responsibilities can shift with the service used. The official examples include Amazon RDS, AWS Lambda, and Amazon EC2, so compare what the customer manages in each rather than learning a single fixed division of work.
Access management preparation should include IAM users, groups, policies, access keys, password policies, MFA, IAM Identity Center, federated identity, cross-account IAM roles, and protection of the root user. The principle of least privilege should guide your reasoning: grant only the access needed for the task, not broad permissions because they are convenient.
Separate security, governance, and compliance capabilities by purpose. AWS Artifact helps locate compliance information; CloudTrail and Config support auditing; CloudWatch supports monitoring; and services such as GuardDuty, Security Hub, Inspector, Shield, and WAF address different security or protection needs. The exam expects recognition of those roles, not a full security operations design.
Domain 3: Cloud Technology and Services — 34% of scored content
Cloud Technology and Services represents 34% of the scored content on the exam, the largest domain. It covers deployment and operating methods, global infrastructure, compute, databases, networks, storage, AI/ML and analytics, and other in-scope service categories.
Begin with service families and use cases. For compute, distinguish Amazon EC2 instance purposes, containers through Amazon ECS and Amazon EKS, serverless options such as AWS Fargate and AWS Lambda, auto scaling, and load balancers. The question is usually about matching a requirement to a service type, not selecting a detailed configuration.
For databases, compare EC2-hosted databases with managed databases. Recognize relational options such as Amazon RDS and Amazon Aurora, NoSQL through Amazon DynamoDB, memory-based caching through Amazon ElastiCache, and migration tools including AWS DMS and AWS SCT.
Networking study should cover VPC components such as subnets and gateways, security groups and network ACLs, Route 53, AWS VPN, and AWS Direct Connect. Storage, AI/ML, analytics, and other in-scope categories deserve a service-purpose map as well; do not spend all your time on compute because the domain spans a broad catalogue.
Global infrastructure requires clear relationships among Regions, Availability Zones, and edge locations. Know that multiple Availability Zones can support high availability and that Availability Zones do not share single points of failure. Multiple Regions can be relevant to disaster recovery, business continuity, end-user latency, or data sovereignty.
Domain 4: Billing, Pricing, and Support — 12% of scored content
Billing, Pricing, and Support represents 12% of the scored content on the exam. It covers pricing models, billing and cost-management resources, and technical resources and Support options.
Compare compute purchasing options such as On-Demand Instances, Reserved Instances, Spot Instances, Savings Plans, Dedicated Hosts, Dedicated Instances, and Capacity Reservations at a recognition level. Also understand storage options and tiers, and the distinction between incoming and outgoing data transfer costs in the situations named by AWS.
Know which tool answers which question. AWS Budgets supports budget monitoring, Cost Explorer supports cost analysis, and Pricing Calculator supports estimation before deployment. AWS Organizations supports consolidated billing and cost allocation, while cost allocation tags connect resource information with billing reports such as the AWS Cost and Usage Report.
Technical-resource preparation includes AWS documentation, whitepapers, blogs, Prescriptive Guidance, the Knowledge Center, re:Post, AWS Support Center, and AWS Support options. Also recognize the roles of Trusted Advisor, the AWS Health Dashboard, the AWS Health API, Trust and Safety, AWS Partners, AWS Marketplace, and AWS Professional Services.
What are the CLF-C02 delivery and scoring details?
AWS lists CLF-C02 as a 90-minute exam with 65 questions consisting of multiple-choice and multiple-response items. AWS offers it at Pearson VUE testing centers and through online proctoring. Confirm the available appointment choices and current delivery instructions through the official AWS certification process before booking.
Question formats
A multiple-choice question has one correct response and three incorrect responses. A multiple-response question has two or more correct responses out of five or more options. Read the instruction on each item carefully: selecting one answer when several are required is a different error from misunderstanding the service.
AWS says distractors are generally plausible options that a candidate with incomplete knowledge or skill might choose. When reviewing practice questions, record why each wrong option fails the requirement. That habit is more valuable than remembering the position of a correct answer.
Scored and unscored questions
The exam includes 50 questions that affect your score and 15 unscored questions that do not affect your score. The unscored questions are not identified, so treat every question as an opportunity to demonstrate your knowledge.
AWS states that unanswered questions are scored as incorrect and that there is no penalty for guessing. A practical tactic is to eliminate clearly unsuitable options, choose the best remaining answer, and avoid leaving an item blank when you reach the end of your review.
Results, price, languages, and renewal
AWS reports results as a scaled score of 100–1,000, with a minimum passing score of 700. The exam cost listed by AWS is USD 100; AWS directs candidates to its exam-pricing information for foreign-exchange and additional-cost details. These are official exam facts, while your personal preparation budget and scheduling choice are separate decisions.
AWS lists CLF-C02 in Arabic, English, Indonesian, French, German, Italian, Japanese, Korean, Brazilian Portuguese, Latin American Spanish, Spain Spanish, Simplified Chinese, and Traditional Chinese. Choose the language in which technical distinctions are clearest for you, and verify the language offered when scheduling.
AWS Certifications are valid for three years. AWS provides Cloud Practitioner recertification options including Cloud Quest: Recertify Cloud Practitioner, passing the current exam, or passing an Associate- or Professional-level exam. Keep the certification date and renewal route in your own certification account rather than relying on an old study page.
How should you turn the blueprint into a study plan?
Use the blueprint to allocate attention, then use task statements to choose study activities. A sensible sequence is Cloud Concepts, Security and Compliance, core services in Cloud Technology and Services, and finally Billing, Pricing, and Support, followed by mixed review. This order builds the mental models needed to interpret service and cost questions.
Step 1: Establish a baseline
Before reading everything, test your recall with a small set of representative questions or a self-made inventory. Mark each topic as confident, uncertain, or unknown. Do not interpret a practice score as an official AWS result; use it only to locate gaps.
Your inventory should include the four domains and their task statements. For each service, write a one-line answer to three prompts: What problem does it solve? What service is a nearby alternative? What requirement would make it a poor choice? This exposes confusion faster than copying product descriptions.
Step 2: Build concepts before service lists
Start with cloud value, shared responsibility, the Well-Architected pillars, global infrastructure, and cost behavior. These concepts appear inside service scenarios, so memorizing names first often produces shallow recognition.
For example, a high-availability question should lead you to think about Availability Zones and failure isolation before you search your memory for a product name. A cost question should make you ask whether the situation concerns estimation, monitoring, analysis, organizational allocation, or a purchasing model.
Step 3: Create a service decision table
Organize services by the decision they help answer, not by the order in which you encounter them. A compact table can have columns for category, primary purpose, managed versus customer-managed emphasis, common alternative, and a short scenario.
Useful rows include EC2 versus Lambda versus containers; RDS or Aurora versus DynamoDB; S3-style object storage versus block or file storage categories; VPN versus Direct Connect; and Cost Explorer versus Budgets versus Pricing Calculator. Add only distinctions supported by your study sources, then revisit the rows that remain ambiguous.
Step 4: Study security through responsibility boundaries
Draw the shared responsibility model for several services and label the customer, AWS, and shared areas. Then connect identity, encryption, logging, monitoring, governance, and compliance tools to the responsibility they help the customer fulfil.
A common mistake is treating a managed service as eliminating all customer security work. Another is treating every security service as interchangeable. Ask whether the requirement is identity control, threat detection, vulnerability identification, web filtering, DDoS protection, auditing, monitoring, or compliance evidence.
Step 5: Finish with economics and support
Leave enough time for Domain 4 even though Billing, Pricing, and Support represents 12% of the scored content. Its tools are easy to confuse when learned as a list. Practice choosing the resource based on the action: forecast a design, inspect current spending, set a threshold, allocate costs, find technical guidance, or request assistance.
Review pricing models using short scenarios. A workload with uncertain or interruptible demand should trigger different reasoning from a stable workload with a longer planning horizon. Do not invent savings claims; focus on the characteristics AWS identifies for each option and the requirement in the question.
What does a practical CLF-C02 roadmap look like?
A roadmap should produce evidence of understanding at each stage, not just a completed reading list. Work in cycles of learn, retrieve, apply, and review. The schedule below is a flexible sequence rather than an official AWS timetable; adjust the pace to your experience, available study time, and baseline gaps.
Phase 1: Map the exam and vocabulary
Read the official exam guide and copy its four domains and task statements into your notes. Learn the basic AWS vocabulary: Region, Availability Zone, edge location, elasticity, agility, high availability, managed service, shared responsibility, and variable cost.
Output: a one-page map of the exam and a glossary written in your own words. If you cannot explain a term without repeating its product-page wording, flag it for another pass.
Phase 2: Master Cloud Concepts
Study the value proposition, Well-Architected pillars, migration concepts, AWS CAF, and cloud economics. Convert each topic into a requirement-and-response pair: a business need on one side and the relevant concept on the other.
Output: a comparison sheet for the six Well-Architected pillars and a set of brief migration and economics scenarios. Include fixed versus variable costs, BYOL versus included licenses, rightsizing, automation, and economies of scale.
Phase 3: Make security operational in your reasoning
Cover the shared responsibility model first, then governance and compliance, access management, and security resources. Practice distinguishing authentication from authorization, customer control from AWS control, and monitoring from auditing.
Output: a responsibility matrix for EC2, RDS, and Lambda; an IAM concept map; and a security-tool table. Include root-user protection, least privilege, MFA, IAM Identity Center, federated identity, encryption at rest and in transit, and locations for AWS compliance or security information.
Phase 4: Traverse the service categories
Study Domain 3 by category: deployment and operations, global infrastructure, compute, databases, networking, storage, AI/ML and analytics, then other in-scope categories. Use the official task statements to stop you from drifting into advanced implementation detail.
Output: a service map with a purpose and a differentiating clue for each service you study. Test yourself by hiding the service names and reconstructing them from scenarios, then hide the descriptions and explain each service from memory.
Phase 5: Apply billing and support choices
Review pricing models, storage tiers, data transfer concepts, AWS Budgets, Cost Explorer, Pricing Calculator, Organizations, cost allocation tags, support options, and technical resources. Tie each resource to a verb such as estimate, monitor, analyze, allocate, document, protect, or escalate.
Output: a decision tree that starts with the user’s goal and ends with the most suitable AWS resource or support option. Check the official Domain 4 task statements when two resources seem similar.
Phase 6: Use mixed review before scheduling
Mix domains rather than studying one category forever. Read the stem, identify the requirement, eliminate options that belong to a different problem, and justify the selected answer in one sentence. Then review the relevant task statement.
Output: an error log with four fields—topic, mistaken assumption, correct distinction, and follow-up action. Schedule only after your errors show isolated gaps rather than repeated confusion across shared responsibility, service purpose, and cost-management tools.
How can you tell whether you are ready?
Readiness is stronger when you can explain unfamiliar scenarios using the blueprint’s concepts, not merely recognize familiar wording. Before scheduling, confirm that you can work through multiple-choice and multiple-response items, identify the requirement in a long stem, and make a reasoned choice even when two services appear plausible.
Use an evidence-based readiness check
Review every task statement and label it strong, developing, or weak. For each developing or weak item, write a fresh scenario and answer it without notes. Then explain why the nearest distractor is wrong.
Pay particular attention to areas that are broad rather than difficult: Domain 3 service categories, Domain 2 security resources, and Domain 4 billing tools. Broad coverage creates avoidable blind spots when preparation focuses only on the services used in your current job.
Do not overinterpret section feedback
AWS cautions candidates to use care when interpreting section-level feedback. Treat a section classification as a prompt for further study, not as a precise diagnostic of every service or task you know. Your revision should return to the official domain and task statement rather than chasing an assumed question pattern.
The result is reported for the exam as a whole, and the minimum passing score is 700 on the reported scaled score. Preparation decisions should therefore combine your error log, task-statement coverage, and ability to explain choices—not a claim that one isolated percentage guarantees readiness.
Which exam-day habits prevent avoidable mistakes?
Most avoidable errors come from reading the requirement too quickly, confusing neighboring services, or leaving questions unanswered. Use a simple process: identify the requested outcome, note constraints, compare only relevant options, select the best response, and reserve time to revisit flagged items.
Read for the decisive constraint
Words such as managed, serverless, relational, NoSQL, repeatable, low latency, disaster recovery, cost estimate, budget alert, audit, and least privilege change the answer. Underline or mentally isolate those constraints before looking at the options.
Do not select a familiar service merely because it can technically perform part of the task. Foundational questions often test the most appropriate service or concept for the stated requirement, not whether an option is possible in some broader architecture.
Handle multiple-response items deliberately
For multiple-response questions, determine how many responses the instruction requires and evaluate every option independently. A response can be relevant to the topic but still fail the exact requirement. Avoid selecting an answer because it is generally true about AWS.
If uncertain, compare the options against the stem’s nouns and verbs. For example, “estimate” points to a different kind of resource from “analyze current usage,” while “authenticate” is not the same as “authorize.”
Use the final review intelligently
Flag questions where the uncertainty is genuine, but do not repeatedly change an answer without a specific reason. Re-read the stem, check the service purpose, and look for a constraint you missed. Ensure every question has a response because AWS states that unanswered questions are scored as incorrect and there is no penalty for guessing.
What preparation mistakes should you avoid?
The most damaging mistake is studying the AWS catalogue without mapping it to the exam tasks. Other common problems are pursuing out-of-scope engineering depth, memorizing product slogans, ignoring billing, and treating practice-question familiarity as proof of knowledge. Correct these by returning to requirements, distinctions, and official scope.
Mistake: treating the exam as an implementation test
You do not need to become an expert at coding, architecture design, troubleshooting, implementation, or performance testing for this exam. Those activities can be useful career practice, but they should not replace learning the foundational concepts and service purposes named in the blueprint.
Mistake: memorizing isolated service names
A list of names does not explain when to choose EC2, Lambda, containers, managed databases, storage types, or network connectivity options. Attach each name to a problem, a defining characteristic, and a nearby alternative. If you cannot make that comparison, continue studying the category.
Mistake: collapsing security into IAM
IAM is important, but Domain 2 also includes the shared responsibility model, governance, compliance, encryption, logs, security services, and security documentation. Prepare across all four task statements. A strong IAM score cannot compensate for ignoring responsibility boundaries or compliance concepts.
Mistake: skipping cost management because it is the smallest domain
Billing, Pricing, and Support represents 12% of the scored content, so it is smaller than the other named domains but not optional. Tool confusion is preventable: distinguish estimation, monitoring, analysis, consolidated billing, allocation, technical guidance, and support escalation.
Mistake: using unauthorized or misleading shortcuts
Exam dumps and leaked-question material do not replace understanding and should not be used as a preparation strategy. Memorizing recalled items is unreliable, risks violating exam rules, and does not build the service distinctions needed for unfamiliar scenarios. Use official exam content and legitimate learning resources instead.
What should you do after passing?
Passing CLF-C02 confirms foundational AWS knowledge, but it does not by itself establish role-specific implementation ability. Use the result to choose the next practical step: deepen a technical specialty, strengthen cloud-finance or governance knowledge, or apply the concepts in supervised hands-on work.
Turn weak areas into work skills
If Domain 3 was difficult, choose a small learning project that compares service categories without trying to build a production system. If Domain 2 was difficult, study identity, logging, encryption, and responsibility boundaries in a controlled environment. If Domain 4 was difficult, practise reading cost and support scenarios.
Keep the exam blueprint as a boundary. The next certification or job goal may require skills that CLF-C02 explicitly excludes, such as implementation, troubleshooting, or architecture design. That is a reason to extend your learning—not a reason to assume the foundational exam covered those skills.
Plan renewal rather than losing track
AWS Certifications are valid for three years, and AWS lists Cloud Practitioner recertification options that include Cloud Quest: Recertify Cloud Practitioner, passing the current exam, or passing an Associate- or Professional-level exam. Record your certification date and revisit the official recertification page before choosing a renewal path.
Your next actions
Start with the official CLF-C02 exam guide, mark your current confidence against all four domains, and build an error log before collecting more study material. Then work through the task statements in the roadmap, using service comparisons and scenario explanations to test understanding. Schedule only when your review shows consistent coverage and your remaining errors are specific and correctable.
A short action checklist
1. Read the official exam guide and domain pages. 2. Record the four domains with their official labels and weightings. 3. Create a service-purpose and nearest-alternative table. 4. Draw responsibility boundaries for EC2, RDS, and Lambda. 5. Practise the differences among Pricing Calculator, Budgets, Cost Explorer, and Organizations. 6. Review multiple-response instructions and answer every item. 7. Verify current scheduling, delivery, language, and pricing information through AWS before booking. 8. Keep the official recertification page for later planning.
Conclusion
CLF-C02 preparation is most efficient when you study the decisions behind AWS services rather than attempting to memorize the entire catalogue. Cover every domain, give extra attention to Security and Compliance and Cloud Technology and Services, and use Billing, Pricing, and Support as a focused scoring opportunity. Your final checkpoint is simple: explain the requirement, identify the relevant AWS concept or service, reject the closest distractor, and know where your remaining gaps are.