AWS Certified Cloud Practitioner (CLF-C02) Study Guide: Format, Domains, Cost, and How to Pass

The AWS Certified Cloud Practitioner (CLF-C02) is Amazon Web Services’ foundational certification: 65 questions in 90 minutes, a passing score of 700 on a 100–1,000 scale, and a $100 USD exam fee, taken at a Pearson VUE test center or online with a proctor. It validates that you understand what the AWS Cloud is, how it is secured, which core services do what, and how AWS pricing and support work — no hands-on building required. This guide walks through the exam format, all four domains, registration, a four-week study plan, and what to do on exam day.

What the Cloud Practitioner certification is — and who it’s for

CLF-C02 sits at the Foundational level of the AWS certification ladder, below the Associate, Professional, and Specialty tiers. It is deliberately a breadth exam: it asks whether you can explain cloud concepts, identify the right AWS service for a described need, and reason about security responsibilities, pricing models, and support options. It never asks you to write code, configure a service console, or debug an architecture.

That scope makes it the right first certification for several groups:

• Career changers and students entering cloud computing who need a credential that proves baseline fluency.
• Sales, marketing, finance, project management, and legal professionals who work alongside technical teams on AWS and need to speak the language — this is genuinely a cert AWS designed for non-engineers too.
• IT professionals from other stacks (on-premises administrators, network technicians, developers on other platforms) who want a structured on-ramp before attempting an Associate-level exam.
• Managers and executives who make purchasing or governance decisions about AWS and want the vocabulary to make them well.

AWS recommends up to six months of general AWS exposure before sitting the exam, but that is a suggestion, not a prerequisite. There are no formal prerequisites at all — you can register today. Plenty of candidates with zero prior AWS time pass after a few focused weeks of study, because the exam rewards understanding of concepts and service purposes rather than operational experience.

One honest framing: CLF-C02 will not, by itself, qualify you for a cloud engineering job. What it does is prove you can hold your own in AWS conversations, and it de-risks the jump to Solutions Architect Associate or another Associate exam, which share much of the same conceptual foundation.

Exam format at a glance

Attribute	Detail
Exam code	CLF-C02
Questions	65 total — 50 scored, 15 unscored
Time limit	90 minutes
Question types	Multiple choice (one correct answer) and multiple response (two or more correct)
Passing score	700 on a scale of 100–1,000
Scoring model	Compensatory — overall score matters, not per-domain passing
Cost	$100 USD
Delivery	Pearson VUE test center or online proctored
Prerequisites	None
Validity	3 years

Three of those rows deserve unpacking, because they change how you should prepare.

The 15 unscored questions. Fifteen of your 65 questions are experimental items AWS is evaluating for future exams. They do not count toward your score, and you cannot tell which ones they are. The practical consequence: never let one brutal question rattle you. It may literally not count. Answer it, flag it if you want, and move on.

Compensatory scoring. You need 700 overall; you do not need to pass each domain individually. A weak showing in one domain can be offset by strength elsewhere. This means your study time should go where the points are — the two domains worth 34% and 30% deserve more hours than the one worth 12% — and a known weak spot is not fatal if you are solid everywhere else.

The time budget. Ninety minutes for 65 questions is roughly 83 seconds per question, and most CLF-C02 questions are two or three sentences long. Time pressure is rarely the reason people fail this exam; second-guessing is. Most candidates finish with 20 or more minutes to spare.

The four domains, in depth

The CLF-C02 exam guide defines four domains with fixed weightings:

Domain	Weight
Cloud Concepts	24%
Security and Compliance	30%
Cloud Technology and Services	34%
Billing, Pricing, and Support	12%

Notice that Security and Compliance plus Cloud Technology and Services together account for 64% of the exam. Weight your study accordingly.

Domain 1: Cloud Concepts (24%)

This domain tests whether you understand why cloud computing exists — the economics and the architecture philosophy — independent of any particular service.

Expect questions on the value proposition of the AWS Cloud: trading capital expense (buying servers) for variable expense (paying for what you use), benefiting from massive economies of scale, eliminating guessing at capacity, increasing speed and agility, and going global in minutes. You should be able to recognize each of these benefits when a scenario describes it without naming it — for instance, a company that no longer needs to forecast server purchases two years out is enjoying “stop guessing capacity.”

You also need the design vocabulary: elasticity (capacity grows and shrinks with demand), scalability (capacity can grow with demand), high availability (the system survives component failures), fault tolerance, and agility. Candidates lose points by treating these as synonyms; the exam tests the distinctions.

Two frameworks anchor this domain. The AWS Well-Architected Framework describes six pillars of good architecture: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. The AWS Cloud Adoption Framework (CAF) organizes cloud migration guidance into perspectives spanning business and technical concerns. For CLF-C02 you need to recognize the pillars and perspectives and match a described concern to the right one — not apply them in depth.

Finally, know the migration concepts: the common migration strategies (rehost, replatform, refactor, and so on), AWS Snow Family devices for moving large datasets physically, and the difference between cloud, hybrid, and on-premises deployment models.

Domain 2: Security and Compliance (30%)

The heaviest conceptual domain, and the one where precise mental models pay off most.

The centerpiece is the AWS Shared Responsibility Model: AWS is responsible for security of the cloud (physical facilities, hardware, the virtualization layer, managed-service infrastructure), while the customer is responsible for security in the cloud (their data, identity and access configuration, operating-system patching on Amazon Elastic Compute Cloud (EC2) instances, network traffic protection, encryption choices). The exam presents a task — say, patching the guest operating system on an EC2 instance, or patching the infrastructure under a managed database — and asks whose job it is. The answer shifts with the service model: the more managed the service, the more responsibility slides to AWS.

The second pillar is AWS Identity and Access Management (IAM): users, groups, roles, and policies; the root user and why it should be locked away with multi-factor authentication (MFA) enabled and never used for daily work; the principle of least privilege; and when to use IAM roles (for granting temporary permissions to services or federated users) versus long-lived access keys.

Round out the domain with the security service lineup — you need purposes, not configuration: Amazon GuardDuty (threat detection), AWS Shield (DDoS protection), AWS WAF (web application firewall), Amazon Inspector (vulnerability scanning), AWS Key Management Service (KMS) for encryption keys, AWS Artifact (on-demand compliance reports), AWS Config (resource configuration auditing), and AWS CloudTrail (a record of API calls in your account — who did what, when). Distinguishing CloudTrail (audit log of actions) from Amazon CloudWatch (metrics, logs, and alarms for performance monitoring) is one of the most reliably tested pairs on the whole exam.

Domain 3: Cloud Technology and Services (34%)

The largest domain by weight, and the one that intimidates newcomers most because AWS has more than 200 services. The good news: CLF-C02 only expects you to match a service to its purpose, and a much smaller core set does the heavy lifting.

Organize your study by category:

• Compute: EC2 (virtual servers, with purchasing options covered under billing), AWS Lambda (run code without managing servers, billed per invocation), and container services — Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS) — plus AWS Elastic Beanstalk (upload code, AWS handles the environment).
• Storage: Amazon Simple Storage Service (S3) object storage and its storage classes (Standard through Glacier tiers, and when each fits), Amazon Elastic Block Store (EBS) volumes for EC2, Amazon Elastic File System (EFS) shared file storage, and AWS Backup.
• Databases: Amazon Relational Database Service (RDS) and Amazon Aurora for relational workloads, Amazon DynamoDB for key-value at scale, Amazon Redshift for data warehousing, Amazon ElastiCache for in-memory caching. The recurring question pattern: relational versus non-relational versus analytics, matched to a described workload.
• Networking and content delivery: Amazon Virtual Private Cloud (VPC) and its building blocks (subnets, internet gateways, security groups versus network access control lists), Amazon Route 53 (Domain Name System, or DNS), Amazon CloudFront (content delivery network), Elastic Load Balancing, and the connectivity options — AWS Direct Connect (dedicated private line) versus a Site-to-Site VPN (encrypted over the internet).
• Global infrastructure: Regions (isolated geographic areas), Availability Zones (one or more discrete data centers within a Region), and edge locations (CloudFront’s points of presence). Know that deploying across multiple Availability Zones is the standard prescription for high availability, and that data residency requirements are solved by choosing Regions.
• Application integration and emerging tech: Amazon Simple Queue Service (SQS) versus Amazon Simple Notification Service (SNS) for decoupling, plus one-line awareness of the analytics and machine-learning lineup (Amazon Athena, Amazon QuickSight, Amazon SageMaker, and friends).

This domain also covers the human side of getting help building on AWS. Know AWS IQ — the marketplace for hiring independent, AWS-certified experts for short-term projects, paid directly through AWS — and how it differs from AWS Professional Services (AWS’s own consulting organization for large engagements) and the AWS Partner Network. Scenarios about a small business needing a one-off project done by a certified expert point to AWS IQ every time.

Domain 4: Billing, Pricing, and Support (12%)

The smallest domain by weight, but the most memorization-friendly — these are some of the easiest points on the exam to lock down, because the facts are finite and stable.

Pricing models: On-Demand (pay by the second or hour, no commitment), Savings Plans and Reserved Instances (commit to one or three years for a discount), Spot Instances (up to 90% off for interruptible workloads), and Dedicated Hosts. The exam describes a workload — steady-state, interruptible batch, unpredictable spiky — and asks for the cheapest fitting model.

Cost tools: AWS Cost Explorer (visualize and analyze past and forecasted spend), AWS Budgets (set thresholds and get alerts), the AWS Pricing Calculator (estimate costs before deploying), and cost allocation tags. AWS Organizations enables consolidated billing — one bill across many accounts, with usage pooled so volume discounts apply — plus service control policies for governance.

Support plans are the deepest sub-topic, and the exam is precise about which feature belongs to which tier. Start with the full comparison in AWS Support Plans Compared, then drill each tier:

• AWS Basic Support — free on every account: billing and account customer service, documentation and forums, the AWS Health Dashboard, and core AWS Trusted Advisor checks. No technical support cases.
• AWS Developer Support — business-hours email access to support for development and test workloads.
• AWS Business Support — the first production-grade tier: 24/7 phone and chat, full Trusted Advisor checks, third-party software support.
• AWS Enterprise On-Ramp — the newer tier between Business and Enterprise, with a pool of Technical Account Managers and a 30-minute business-critical response target.
• AWS Enterprise Support — designated Technical Account Manager, Concierge Support Team, and a 15-minute business-critical response target.

Two cross-cutting details round it out: the response-time commitments at each severity level, which the exam uses to make you pick the lowest sufficient tier, and the Technical Account Manager role — specifically the pooled-versus-designated distinction that separates Enterprise On-Ramp from Enterprise.

Registering for the exam

Registration runs through the AWS certification portal, where you sign in (or create an AWS Builder ID), choose the Cloud Practitioner exam, and schedule through Pearson VUE. You have two delivery choices:

• Test center: you sit the exam at a Pearson VUE facility on their hardware. Bring two forms of identification, arrive early, and expect to store your belongings in a locker. This is the lower-friction option if a center is nearby — no environment checks, no webcam anxiety.
• Online proctored: you take the exam from home under live webcam supervision. You will run a system test beforehand, show your ID and a 360-degree view of your room, and need a private, quiet space for the full duration — no one entering the room, no talking aloud, desk cleared of everything but your machine.

The fee is $100 USD, paid at scheduling. If English is not your first language, request the ESL +30 accommodation before scheduling to get 30 extra minutes. Reschedule and cancellation are free up to 24 hours before your appointment. Results typically arrive within a few days by email and in your certification portal, though many candidates see a pass indication at the test center immediately. A pass earns a digital badge and — nice perk — a 50% discount voucher toward your next AWS exam, which meaningfully reduces the cost of continuing to an Associate certification.

A four-week study plan

This plan assumes roughly one to one and a half hours a day. Compress it to two or three weeks if you have prior AWS exposure; stretch it to six if you are brand new to IT and can only manage a few sessions a week.

Week 1 — Cloud Concepts and the lay of the land. Learn the value proposition of cloud computing cold: the capital-versus-variable expense trade, economies of scale, elasticity, agility, global reach. Study the global infrastructure (Regions, Availability Zones, edge locations) until multi-AZ-for-high-availability is reflexive. Read the six Well-Architected pillars. Finish the week with a set of practice questions on Domain 1 only, and read every explanation — including for questions you got right.

Week 2 — Security and Compliance. Spend two full sessions on the Shared Responsibility Model, working scenario variations: who patches what, who encrypts what, how responsibility shifts between EC2 and managed services. Then IAM: root user hygiene, MFA, users versus groups versus roles, least privilege. Close the week with the security service lineup — one-sentence purpose for each of GuardDuty, Shield, WAF, Inspector, KMS, Artifact, Config, CloudTrail — and a Domain 2 practice set.

Week 3 — Cloud Technology and Services. The heaviest week. Work category by category: compute one day, storage the next, then databases, then networking. Build a personal one-line-per-service cheat sheet as you go; the act of writing it is the studying. Use flashcards or spaced repetition for the service-to-purpose mapping — this is the domain where drilling recognition genuinely converts to points, because the exam asks “which service does X” over and over.

Week 4 — Billing, Pricing, Support, and full rehearsal. Two days on pricing models and cost tools, one day on the five support plans and their response times (memorize the comparison table), then two or three full-length timed practice exams under real conditions — 90 minutes, no notes, no pausing. Score each one, and spend as much time reviewing wrong answers as you spent taking the test. If you are scoring comfortably above passing on honest practice exams, you are ready; if one domain keeps dragging, remember the scoring is compensatory and shore up your strongest domains too.

Whatever resources you use, make practice questions the backbone from week one, not a final check. Reading about AWS produces familiarity; answering questions produces the discrimination between similar-sounding options that the exam actually measures.

Exam-day tips

• Answer everything. There is no penalty for wrong answers. A blank is a guaranteed zero; a guess among four options is 25% before you eliminate anything.
• Eliminate first, choose second. Most questions have two obviously wrong options. Cutting them turns a guess into a coin flip weighted by whatever partial knowledge you have.
• Read for the qualifier. Words like “MOST cost-effective,” “LEAST operational overhead,” and “MOST secure” change the correct answer. Two options may both technically work; the qualifier picks between them.
• Match the scenario’s scale to the service tier. A small business with a short-term project points to different answers (AWS IQ, lower support tiers) than an enterprise running mission-critical workloads (Professional Services, Enterprise Support). The exam embeds these cues deliberately.
• Use the flag-and-return feature. First pass: answer everything you know quickly and flag anything shaky. Second pass: revisit flags with your remaining time. Do not change an answer without a concrete reason — first instincts on recognition questions are usually right.
• Don’t spiral on a hard question. Fifteen questions are unscored field items. The bizarre one that seems beyond the syllabus may be exactly that. Give it your best elimination and move on.
• Multiple-response questions tell you how many to pick. “Choose TWO” means exactly two. You must get all of them right for credit, so treat each option as its own true/false judgment.
• Logistics: sleep normally, arrive or log in early, handle ID and environment checks calmly, and remember you have more time per question than you think.

Quick reference

• CLF-C02: 65 questions (50 scored, 15 unscored), 90 minutes, pass at 700 on a 100–1,000 scale, compensatory scoring.
• Fee is $100 USD; delivery is a Pearson VUE test center or online proctored; no prerequisites; valid 3 years.
• Domains and weights: Cloud Concepts 24%, Security and Compliance 30%, Cloud Technology and Services 34%, Billing, Pricing, and Support 12%.
• The two heavyweight domains — services (34%) and security (30%) — deserve the majority of study time.
• Master the Shared Responsibility Model and the CloudTrail-vs-CloudWatch distinction; both are near-certain to appear.
• Memorize the five support plans, their response times, and pooled vs designated TAMs — small domain, easy points.
• Passing earns a 50% discount voucher toward your next AWS exam.
• Practice questions from day one; timed full-length exams in the final week.