AWS Certified Cloud Practitioner (CLF-C02) #1: Exam Introduction — Structure and Study Strategy

10 min read

If the 27-post AWS Basics track put IAM, EC2, S3, VPC, ECS, and Lambda under your fingers on the console and CLI, the natural next step is getting that intuition validated by a certification. AWS certifications come in four tiers — Foundational, Associate, Professional, and Specialty — and the most entry-level of them is the AWS Certified Cloud Practitioner (CLF-C02). This series walks through every domain needed to pass CLF-C02 in ten posts.

Think of this post as the zeroth one. Before you sit down with the exam, you need the picture in your head — what the exam asks, how it asks it, and how to clear 700 points in 90 minutes.

What kind of certification is CLF-C02 #

CLF-C02 is a certification that asks whether you see the big picture of the cloud and AWS. It doesn’t test your ability to write code or design real infrastructure. Instead, it verifies that you can answer questions like the following without hesitation.

  • How does the cloud reshape the cost structure (CapEx → OpEx)?
  • Where does customer responsibility end inside AWS’s shared responsibility model?
  • What tradeoffs do the six pillars of Well-Architected resolve?
  • Which workloads fit EC2 / Lambda / S3 / RDS / DynamoDB?
  • Where do you set cost alerts, and how does consolidated billing work?

Someone who passes this exam doesn’t need to know all 200 AWS services. What they do have is the ability to classify which service solves which kind of problem at a glance, along with the operational vocabulary around cost, security, and scalability.

Who gets value from it #

RoleWhy
Developers / new engineersThe fastest path to acquiring infrastructure vocabulary. A plus in interviews
Product, marketing, salesThe minimum set for speaking the same language as engineers
PMs and project managersThe ability to read AWS quotes and roadmaps directly
AWS partner company employeesA company’s certification count counts toward partner tier

The flip side: an engineer who already holds the SAA (Solutions Architect Associate) or higher has little reason to come back and grab CLF. Higher-tier certifications already cover everything CLF does.

Exam structure #

The surface-level facts about CLF-C02 are worth committing to memory.

ItemValue
Number of questions65 (50 scored + 15 unscored)
Exam time90 minutes
Passing score700 / 1000 (scaled score, not percentage)
Exam fee$100 USD (same for retakes)
Validity3 years
EligibilityNone (anyone can sit)
LanguagesEnglish, Japanese, Korean, Chinese, and more
DeliveryPearson VUE test center or online proctored (OnVUE)

What the 15 unscored questions mean #

Of the 65 questions, 15 are unscored. AWS mixes in candidate questions for future exams to validate them, and you can’t tell which ones are scored. Because of that structure, missing one or two questions still leaves plenty of room above the passing line. That’s why not sinking time into questions you don’t know, just marking an answer and moving on, is so important.

What the 700 passing score actually means #

AWS reports a scaled score (100–1000), not a raw percentage. The mechanism keeps the passing line at 700 even when exam-form difficulty shifts. So the naive “get 70% right and you pass” math isn’t quite right. The empirical rule of thumb that holds up in practice: getting 36–38 of the 50 scored questions right (about 72–76%) puts you safely in the pass zone.

Two question formats #

Questions come in two shapes.

  1. Multiple choice — 1 correct answer out of 4
  2. Multiple response — 2 or 3 correct answers out of 5

Multiple response questions are explicitly marked “Choose TWO” or similar, and there’s no partial credit. You have to pick all of them correctly. People who don’t read the full question stem before jumping to the choices lose points here most often.

The weight of the four domains #

The CLF-C02 scope is laid out across four domains in the official exam guide.

#DomainWeightSeries mapping
1Cloud Concepts24%#2 , #3
2Security and Compliance30%#4 , #5
3Cloud Technology and Services34%#6 , #7
4Billing, Pricing, and Support12%#8

The weights translate directly into a study-time guide. Domains 2 (Security) and 3 (Services) make up 64% together, so these two are where the pass is won or lost. Domain 4 is small at 12%, but its question patterns are formulaic, making it the highest-return domain per hour of study.

Domain 1 — Cloud Concepts (24%) #

Asks about the cloud’s value proposition and operating model. CapEx/OpEx, economies of scale, the global footprint (regions, AZs, edge), the AWS Cloud Adoption Framework, and the six pillars of Well-Architected (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability) are the core keywords. The region/AZ diagram from Basics #1 lands almost directly on the exam.

Domain 2 — Security and Compliance (30%) #

The largest domain. The shared responsibility model (what the customer owns vs. what AWS owns) forms the skeleton, and IAM, MFA, encryption, audit, compliance certifications (GDPR/HIPAA/PCI DSS), and AWS Artifact come up often. We’ll cover how Basics #2 IAM and Basics #6 Security Foundations translate into exam questions in #4 and #5.

Domain 3 — Cloud Technology and Services (34%) #

The widest surface area. Compute (EC2, Lambda, ECS, Beanstalk), storage (S3, EBS, EFS, Glacier), databases (RDS, Aurora, DynamoDB), networking (VPC, Route 53, CloudFront, ELB), and ops tooling (CloudWatch, CloudTrail, Trusted Advisor) all live in one domain. The volume looks intimidating, but the question pattern collapses to “pick the service best suited to this workload”. Rather than memorizing every feature of every service, it’s more efficient to classify which kind of problem each service solves.

Domain 4 — Billing, Pricing, and Support (12%) #

Small in weight but easy to take near-full marks on. EC2 pricing models (On-Demand, Reserved, Savings Plans, Spot), the free tier, AWS Pricing Calculator, Cost Explorer, AWS Budgets, the four Support Plan tiers (Basic, Developer, Business, Enterprise), and the TCO Calculator are the core. The question shape is formulaic, so #8 wraps it up in one post.

Study strategy #

1) If you already have hands-on intuition, layer vocabulary on top #

If you’ve been through the 27-post AWS Basics track, you’ve actually touched IAM policies, VPC security groups, S3 bucket policies, and CloudWatch alarms. CLF-C02 prep is mostly layering the official vocabulary (Shared Responsibility Model, Well-Architected, Cloud Adoption Framework, and so on) on top of that. There aren’t that many genuinely new concepts, so you can be at passing level in 2 to 3 weeks.

2) If hands-on is new, start with Domains 1 and 2 #

Without the practice track behind you, start with Domain 1 (Cloud Concepts) and Domain 2 (Security). These two lay the vocabulary foundation that the other domains build on. Diving into Domain 3 first leaves you drowning in service names.

3) Save mock exams for the back half #

Don’t open with mock exams. After one pass through this series, you’ll find a full-scale mock in #10. If you clear the passing line on that one, head to the test center. If not, do another loop on the weak domains. For extra practice, AWS’s official Skill Builder or Tutorials Dojo’s mock exams are trustworthy.

4) Build the instinct for “the best answer” #

A common CLF-C02 question shape is two answers both look correct, and you pick the better one. The way to anchor that judgment is the six Well-Architected pillars plus the shared responsibility model. Train the habit of slicing answers with the right pillar: “cost question → cost optimization vocabulary”, “security question → shared responsibility framing”. We cover that pattern in detail in #9.

5) Take it in English or in your native language? #

Localized translations aren’t always consistent. Awkward phrasing often forces you to mentally translate back into English to guess what the question means, eating into time. If your developer English is reasonably comfortable, take it in English. The exam interface offers an English ↔ local-language toggle, so you can answer in English by default and flip to the local language only when you get stuck.

Registration and the testing environment #

Registration steps #

  1. Log in to the AWS Certification portal with your AWS Builder ID
  2. Choose CLF-C02 → move to Pearson VUE and book a date
  3. Pick a delivery mode — test center or online proctored (OnVUE)
  4. Pay ($100 USD, plus applicable tax). If you have a 50% discount voucher, apply it at the payment step

Test center vs. OnVUE #

AspectTest centerOnVUE (online)
EnvironmentCubicle booth + desktopYour PC + webcam
StabilitySystem downtime very unlikelyInternet, webcam, system checks add variables
IDOne English-readable IDTwo English-readable IDs
Pre-exam checkAlmost none30+ minutes of setup checks
Recommended forFirst-time test takers or environment-sensitiveThose without easy test-center access, repeat takers

For your first AWS exam, the test center is the safer pick. OnVUE is convenient, but setup, environment checks, and proctor chats often eat into your focus right before the actual exam.

Setup right before the exam #

  • ID — A passport with your name in Roman script is safest. Driver’s licenses without English text aren’t accepted
  • Personal items — At test centers, all belongings go in a locker. No drinks, watches, or writing implements
  • OnVUE environment — Clear everything off your desk, disconnect any second monitor, and block family and roommates from entering

Common traps #

1) Booking the exam too far out #

Study motivation tracks proximity to exam day. With hands-on experience, booking within 3 weeks of starting prep correlates with higher pass rates; even starting from scratch, within 6 weeks is the safe range. You can reschedule for free up to 24 hours before the exam, so book a near date and shift it once if you need to.

2) Spending all your time memorizing service names #

Because Domain 3 has so many services, beginners try to memorize every name. But the exam asks “pick the service that fits this scenario” rather than naming. The right unit to memorize is (workload type → matching service), not the service name itself.

3) Memorizing Well-Architected as five pillars #

Well-Architected was originally five pillars, but Sustainability was added in December 2021, making it six. Older study material still lists five, so we cover all six in #3.

4) Getting stuck on one question during the exam #

90 minutes across 65 questions is about 1 minute 23 seconds per question on average. If you sit on a question for 3+ minutes, you’ll fail to reach the last five or six. Mark for Review anything you don’t know and move on, then come back to flagged questions in the last 10 minutes.

5) Missing the answer count on “multiple response” questions #

Missing “Choose TWO” or “Choose THREE” and picking only one is an automatic wrong answer. The exam UI uses checkboxes for multiple-response questions, but the visual difference from multiple choice is subtle. Make a habit of reading the last line of the question stem every time.

Wrap-up #

What this post locked in:

  • CLF-C02 verifies the big picture and vocabulary of AWS. Coding and design ability aren’t tested
  • 65 questions / 90 minutes / 700 points / $100 / valid 3 years. With 15 unscored questions mixed in, missing one or two is easily recoverable
  • Four domains — Cloud Concepts (24%), Security (30%), Cloud Technology (34%), Billing (12%)
  • Study strategy — layer official vocabulary on hands-on feel. Save mock exams for the back half. Use the six pillars and the shared responsibility model as your answer-picking compass
  • Test center vs. OnVUE — test center recommended for first-timers
  • Traps — booking too far out, memorizing service names, the five-pillars myth, getting stuck on one question, missing answer counts

Next — Domain 1-1 Cloud Concepts #

The structure is in place. Now into the first domain.

#2 Domain 1-1 Cloud Concepts — Value, Economics, and the Cloud Adoption Framework covers the six value propositions of the cloud (agility, elasticity, global reach, CapEx→OpEx, economies of scale, reduced management burden), the six perspectives of the AWS Cloud Adoption Framework (Business, People, Governance, Platform, Security, Operations), and the comparison questions that show up often (cloud vs. on-prem, where the shared responsibility model sits).

X