DEV Community: Aziz Farid

How to Prepare for AWS Cloud Practitioner (CLF-C02) by Domain

Aziz Farid — Sun, 04 Oct 2026 08:09:06 +0000

Most people start preparing for Cloud Practitioner the same way. They open the service list, see a few hundred names, and try to memorize what each one does. Two weeks later they can recite definitions, but they freeze when a question describes a business problem without naming a single service.

The fix isn't simply adding more flashcards. It's studying by domain, so you know what each part of the exam is asking you to do. Here's how to think about each of the four CLF-C02 domains, what they're really testing, and how to tell when you're ready to move on.

Start with what the exam is, and isn't

AWS's CLF-C02 exam guide describes the target candidate as someone with up to six months of exposure to AWS design, implementation, or operations. That could be someone early in a cloud career, or someone who works alongside cloud teams. The guide lists coding, designing cloud architecture, troubleshooting, implementation, and load testing as out of scope.

That tells you what depth to aim for. You need to recognize services, explain what they're for, and choose a sensible one for a described need. You don't need to build anything.

Domain weights: what they mean and what they don't

The current weights, as a share of scored content, are:

Domain 1, Cloud Concepts: 24%
Domain 2, Security and Compliance: 30%
Domain 3, Cloud Technology and Services: 34%
Domain 4, Billing, Pricing, and Support: 12%

Under AWS's current exam structure, the exam has 65 questions: 50 scored and 15 unscored. The unscored questions are used to evaluate content for future exams, and AWS doesn't identify them, so you can't tell which questions don't count. Treat every question as if it does.

The weights are a planning tool, not a forecast. You can't work out exactly how many questions from each domain will appear on your exam form, so don't build a plan around skipping anything.

The exam also uses compensatory scoring, which means you don't need to pass each section, only the exam overall. Your score report may include section-level feedback, but AWS advises caution in interpreting it. A weak-looking section isn't a failed domain, and a strong-looking one isn't permission to stop reviewing it. Use that feedback as a hint about where to look, not as a prediction of anything.

Domain 1: Cloud Concepts (24%)

This domain is less about services and more about how AWS thinks. It covers the benefits of the cloud, Well-Architected design principles, migration strategies, and cloud economics.

Here's where many candidates get tripped up. They skim this domain as common sense, then miss questions because every answer sounds reasonable and only one uses the concept the way AWS does.

Start with a few distinctions. Elasticity means adding and removing resources to match demand, so you aren't paying for idle capacity or running short during a spike. High availability means the application keeps working when something fails, which comes from redundancy. A system can have one without the other. Agility is about speed: how quickly a team can provision resources, try an idea, and move on if it doesn't work.

The Well-Architected Framework has six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. The exam guide asks you to identify the differences between them, so practice with scenarios. Automating deployments points to operational excellence. Recovering from failure points to reliability. Choosing the right resource type for a workload points to performance efficiency. Reducing the environmental impact of workloads points to sustainability.

On economics, two ideas often get blurred. Pay-as-you-go means you pay for what you use instead of buying capacity up front, which shifts fixed costs to variable ones. Economies of scale means AWS aggregates usage from a very large number of customers, which lets it operate at lower unit costs than most organizations could manage alone. Also know the costs hiding behind an on-premises environment (facilities, power, cooling, staff, hardware refresh), the difference between bring-your-own-license and license-included models, and what rightsizing and automation contribute. For migration, know that the AWS Cloud Adoption Framework helps organizations plan the move around outcomes like reduced risk, improved ESG performance, increased revenue, and operational efficiency.

How to study it: Explain each pillar and each benefit in a sentence or two, in your own words. If you can explain the difference without notes, you're in much better shape than if you can only recognize it.

Domain 2: Security and Compliance (30%)

This is the second-heaviest domain, and the one where understanding pays off most. Start with the shared responsibility model, because it ties everything else together.

Don't stop at "AWS secures the cloud, customers secure what they put in it." The exam guide expects you to understand how responsibilities shift depending on the service. With Amazon EC2, you manage the guest operating system, including patching, plus your applications, data, and network configuration. With Amazon RDS, AWS handles much more of the operating system and database maintenance, but you still control who can access the database, how the data is protected, and how the instance is configured. With AWS Lambda, AWS manages the servers and operating system, while your function code, its permissions, and your data remain yours. A good question to ask for any service is: what could I still misconfigure here?

Next, access management. Least privilege means giving an identity only the permissions it needs to do its job. The reasoning is practical: if credentials leak or someone makes a mistake, narrow permissions limit the damage. In IAM that shows up as using groups and roles instead of broad access, writing policies that name specific actions and resources, and protecting the root user with MFA and keeping it out of everyday use. Know which few tasks only the root user can perform, and know that roles provide temporary credentials, which is why they're used for things like cross-account access. IAM Identity Center and federated identity round out the picture.

The security services need a simple mental model, because they're easy to blur together:

Amazon GuardDuty detects suspicious activity and potential threats.
Amazon Inspector scans workloads for software vulnerabilities.
AWS Shield protects against DDoS attacks.
AWS WAF filters web requests against rules you define.
AWS Security Hub consolidates findings from services like GuardDuty and Inspector into one place.

For governance, keep three services separate. Amazon CloudWatch is about monitoring: metrics, logs, and alarms. AWS CloudTrail records API activity, so it answers who did what and when. AWS Config tracks resource configurations and changes over time, so it answers what something looks like and whether it drifted. Also know that AWS Artifact is where you find AWS compliance reports.

How to study it: Build a table with three columns: the service, the question it answers, and the service people confuse it with. The last column is where the learning happens.

Domain 3: Cloud Technology and Services (34%)

This is the largest domain and the one most likely to feel overwhelming, because it spans eight task areas: deployment methods, global infrastructure, compute, databases, networking, storage, AI/ML and analytics, and other in-scope service categories. Don't try to learn every service equally. Learn each category by the question it answers.

Global infrastructure. A Region is a geographic area. Each Region has multiple Availability Zones, which AWS describes as isolated locations within the Region. Because AZs are designed to be isolated from one another, running an application across more than one improves its resilience and availability if something goes wrong in one location. That doesn't make an application immune to every failure, since design and configuration still matter. Multiple Regions come into play for disaster recovery, lower latency for distant users, or data sovereignty. Edge locations are a different idea: services like Amazon CloudFront use them to deliver content closer to users.

Compute. EC2 gives you virtual servers and the most control, along with the most to manage. Amazon ECS and Amazon EKS orchestrate containers (EKS runs Kubernetes). AWS Fargate runs containers without you managing servers, and Lambda runs your code in response to events, also without servers to manage. Auto Scaling provides elasticity, and load balancers distribute traffic.

Databases. Amazon RDS provides managed relational databases, and Amazon Aurora is a MySQL- and PostgreSQL-compatible relational option. Amazon DynamoDB is managed NoSQL, a fit for key-value and document access patterns at scale. Amazon ElastiCache is in-memory, commonly used to speed up reads. Also understand the tradeoff between running a database on EC2 yourself and using a managed service: managed means less operational work for you.

Networking. Security groups and network ACLs both control traffic in a VPC, but they work differently. Security groups operate at the instance level and are stateful, so return traffic is automatically allowed. Network ACLs operate at the subnet level and are stateless, so return traffic must be explicitly allowed. Know that Route 53 is AWS's DNS service, and that a VPN connects over the internet while Direct Connect is a dedicated network connection.

Storage. The core distinction is object, block, and file. Amazon S3 is object storage, accessed through an API. Amazon EBS provides block volumes attached to EC2 instances. Amazon EFS is a shared file system, and Amazon FSx offers managed file systems for specific needs. Then learn the S3 storage classes as a tradeoff between cost and access pattern, plus lifecycle policies and AWS Backup.

AI/ML, analytics, and integration. Aim for a one-line purpose each. Amazon SageMaker AI builds, trains, and deploys machine learning models. Amazon Athena queries data in S3 with SQL. Amazon Kinesis handles streaming data, AWS Glue handles data preparation and integration, and Amazon Quick Sight builds dashboards. For messaging, Amazon SNS pushes notifications to subscribers, Amazon SQS queues messages so components can work independently, and Amazon EventBridge routes events based on rules.

How to study it: Short hands-on sessions help the vocabulary stick, even though the exam doesn't test implementation. Launch an instance, create a bucket, change a storage class, look at a VPC.

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

It's the smallest domain, but don't treat it as the easy one. Its questions can be precise, and the answer options are often close.

Learn the compute purchasing options by the situation they fit. On-Demand suits unpredictable or short-term usage with no commitment. Reserved Instances and Savings Plans offer discounts in exchange for a usage commitment, with Savings Plans generally the more flexible of the two. Spot uses spare capacity at a steep discount but can be interrupted, so it suits fault-tolerant work. Also understand at a conceptual level that data transfer in and out, and between Regions, is priced differently.

The cost tools are easy to mix up. AWS Pricing Calculator estimates costs before you build. AWS Budgets lets you set thresholds and get alerts. AWS Cost Explorer analyzes what you've already spent. Add AWS Organizations consolidated billing and cost allocation tags, and you've covered most of the billing material.

Support is where outdated study material can hurt you. The current exam guide lists Basic Support, AWS Business Support+, AWS Enterprise Support, and AWS Unified Operations, and AWS's Support plans page reflects the same lineup. If a course or video uses different plan names, check it against the current page. Also be familiar with Trusted Advisor, the AWS Health Dashboard, AWS Partners and the Marketplace, and resources like re:Post and the Knowledge Center.

Using practice questions to find gaps, not collect answers

Practice questions are most useful when each wrong answer becomes information. After every session, for each miss, ask why the right answer was right and why your choice wasn't. Then write down which concept you actually misunderstood. If all you remember is "the answer was C," you've learned nothing that transfers.

Two habits help. Keep a short error log sorted by domain so patterns show up, and be wary of repeating the same question set until your score climbs, because by then you're measuring memory of the questions rather than understanding of AWS.

If you'd like a quick starting point, CloudExamPro, an independent practice platform not affiliated with AWS, offers a free CLF-C02 diagnostic made up of 25 original practice questions. It's a short sample rather than a full exam simulation, so use it to spot areas worth reviewing, not as a prediction of how you'll score on the real exam.

From studying to being ready

A few signs you're close:

You can explain each domain's main ideas without notes.
When you miss a question, you can usually say why, and your misses aren't clustered in one area.
You can choose between similar services (CloudTrail versus Config, security groups versus network ACLs, Budgets versus Cost Explorer) and explain your reasoning.

If one area keeps producing misses, go back to the concept rather than more questions. And keep the scoring model in mind: you need to pass the exam overall, not every section, but a persistent gap in a 30% or 34% domain deserves real attention.

Where this leaves you

CLF-C02 rewards candidates who understand how AWS approaches cloud, security, services, and cost. Study each domain by asking what problem it solves, and the service names will start attaching to something real. Use AWS's exam guide as your map, build your own notes, and let your practice results tell you where to spend the next hour.

AWS CLF-C02 Study Guide: What to Study in Each Domain

Aziz Farid — Sun, 04 Oct 2026 05:47:21 +0000

If you write software for a living, the AWS service catalog can feel like a monorepo someone asked you to review in a week. There are hundreds of services, many with similar names, and the console surfaces a few more every time you click. The natural response is to cram, with mnemonics and a spreadsheet of one-line definitions.

That approach works poorly for Cloud Practitioner (CLF-C02), mostly because of how the exam is built. This guide is about organizing your study around the four domains so your time goes where it counts, services attach to the problems they solve, and you notice quickly when something hasn't sunk in.

Treat the exam guide like a spec

Before you open a course, read AWS's CLF-C02 exam guide. It's short, and a few details in it should change how you study.

The target candidate has up to six months of AWS exposure, and the guide lists coding, architecture design, troubleshooting, implementation, and load testing as out of scope. The exam is asking you to identify and describe, not to build.

Questions come in two forms: multiple choice (one correct answer, three distractors) and multiple response (two or more correct answers out of five or more options). AWS describes distractors as generally plausible responses that match the content area, the kind a candidate with incomplete knowledge might choose. Knowing a service exists isn't enough. You need to know where its job ends and its neighbor's begins.

Two more facts affect your approach. Unanswered questions are scored as incorrect, and there's no penalty for guessing, so never leave one blank. And the exam has 65 questions, of which 50 are scored and 15 are unscored. AWS doesn't identify the unscored ones, so you can't tell which questions to relax on.

Turn the four domains into tickets

The domain weights are 24% Cloud Concepts, 30% Security and Compliance, 34% Cloud Technology and Services, and 12% Billing, Pricing, and Support. Use them as a starting budget for your hours, not as a forecast of question counts. They describe scored content, and you can't derive an exact number of questions per domain for your exam form.

Here's a more useful unit of work. The four domains break down into 19 task statements: four in Domain 1, four in Domain 2, eight in Domain 3, and three in Domain 4. Treat each one as a ticket. "Identify AWS storage services" is a ticket. "Understand the AWS shared responsibility model" is a ticket. A ticket is done when you can demonstrate the skill it names, not when you've watched a video about it.

Then adjust the budget for what you already know. If you build on AWS at work, compute and storage might already feel familiar, while the shared responsibility model, purchasing options, and support plans might not. Start with the weights, then move hours away from what you can already explain and toward what you can't.

One caution about trying to game this. The exam uses compensatory scoring, so you need to meet the standard on the exam as a whole, not in every section. AWS also advises caution when interpreting section-level feedback on a score report. That's a reason not to panic about one weak area, but it isn't a reason to write off a domain.

Start from the problem, not the service name

A list of definitions teaches you to recognize words. The exam, and real work, give you a situation and expect you to find the tool. So practice in that direction. Write the problem in plain English first, then name the service:

A team wants code to run whenever a file lands in a bucket, with no servers to manage. That points to AWS Lambda, triggered by an Amazon S3 event.
Users on another continent complain about slow image loads. Amazon CloudFront serves content from edge locations closer to them.
A database is overloaded by repeated reads of the same data. Amazon ElastiCache keeps hot data in memory.
An order system needs intake and processing to work independently. Amazon SQS queues messages between the two.
Someone deleted a resource and you need to know who and when. AWS CloudTrail records API activity.
An auditor asks for AWS's compliance reports. AWS Artifact is where you find them.
Finance wants an alert when monthly spend crosses a threshold. AWS Budgets can send it.

Notice how few of these require remembering a definition. They require knowing what question each service answers. If you build your notes in this "problem, then service" shape, you end up with something you can use under exam pressure, because the exam hands you problems.

Give every service a four-question card

For each service you study, answer four questions in your own words:

What problem does it solve?
What's its nearest neighbor, and what separates them?
What am I still responsible for when I use it?
How is it charged, at a high level?

Here's what that looks like for Lambda. It runs code in response to events without you managing servers. Its neighbors are AWS Fargate (which runs containers without you managing servers) and Amazon EC2 (where you manage the servers). Responsibility boundaries are service-specific, so question 3 has a different answer for every card. For Lambda, AWS manages the underlying servers and operating system, while you remain responsible for your function code, its permissions, and your data. EC2 or Amazon RDS would draw that line in a different place. As for cost, Lambda is charged based on usage, such as the number of requests and the compute time they consume, rather than for a server you keep running.

Question 3 builds the habit behind the shared responsibility model, which is Domain 2 material, and question 4 keeps pricing in view for Domain 4. A card that takes a couple of minutes to write can touch several domains at once.

Write down the separating question for every confusing pair

Because distractors are plausible, some of your most valuable notes are the ones that separate similar services. Don't just list the pairs. For each, write the one question that tells them apart:

Pair	The question that separates them
AWS Trusted Advisor vs. AWS Health Dashboard	Is this a recommendation about how my account is set up, or news about an AWS event affecting my resources?
AWS Secrets Manager vs. AWS KMS	Am I storing a credential, or managing an encryption key?
IAM role vs. IAM Identity Center	Is this temporary access for a workload or another account, or sign-in access for people across accounts?
AWS Fargate vs. AWS Lambda	Am I running a container, or a function triggered by an event?
Console vs. CLI/SDK vs. infrastructure as code	Is this a one-time action, something scripted, or something I need to repeat reliably?
AWS VPN vs. AWS Direct Connect	Does this connection run over the internet, or over a dedicated link?

Treat this table as a starting point and build your own as you go. The act of writing the separating question is what makes the distinction stick.

Use the console on purpose

Short hands-on sessions help the vocabulary stick, even though the exam doesn't test implementation. Do them with a purpose, and in this order. First create a budget alert as a guardrail. AWS Budgets monitors your spending against a threshold and notifies you, which helps you notice unexpected costs sooner, but it's an alerting tool, not a guarantee that surprises can't happen. It's also Domain 4 material. Then create an S3 bucket, upload an object, and look at its storage class options. Create an IAM role with narrow permissions. Launch a small EC2 instance and terminate it when you're done. Finally, open the CloudTrail event history and find the API calls you just made, once they show up. Seeing your own actions appear as events makes the difference between CloudTrail and AWS Config much easier to remember.

Clean up whatever you create, every time.

Practice questions: use them like a debugger

A score tells you very little. A wrong answer tells you a lot, if you look at it properly. After each practice session, read the explanation for every option, including the ones you rejected correctly. Because distractors are plausible, understanding why each wrong option is wrong is half the learning.

Then log every miss, and label the cause rather than just the topic. Most misses fall into four buckets: a genuine knowledge gap, a vocabulary mix-up between neighbors, a misread of what the question asked, or overcomplicating it. On that last one, the exam is scoped to identifying and describing, so if you find yourself designing a multi-tier system in your head to answer, go back and reread what's actually being asked.

A log entry doesn't need to be fancy. Something like this is enough:

date: YYYY-MM-DD
domain: 2 (task 2.2)
topic: governance services
mistake: chose CloudTrail for "what did this resource look like last week"
cause: vocabulary mix-up (CloudTrail vs. Config)
fix: redo the pair note, then view a resource's configuration timeline in Config
recheck: in 3 days

Review the log weekly and sort it by cause, not only by domain. If most of your misses are vocabulary mix-ups, you need more pair notes. If most are misreads, you need to slow down, not study more content.

When you want a first read on where you stand, a short diagnostic is a reasonable place to start. CloudExamPro, an independent practice platform that isn't affiliated with AWS, offers a free 25-question CLF-C02 diagnostic built from original practice questions. It's a short sample rather than a full-length simulation, and it isn't a prediction of how you'll do on the real exam, but the questions you miss can feed your error log and show you which domain to open first.

How to tell a topic is actually understood

"I've read it" isn't a completion criterion. Use something closer to a definition of done. You can finish the four-question card from a blank page. You can explain the service to a developer who has never used AWS, without notes. You can pick it out of a scenario that never mentions its name. And you answer the related pair questions correctly in two separate sessions, with a few days between them.

If a topic fails one of those checks, it isn't done. That's useful information, not a setback.

What to leave out

You don't need to memorize every service. Sort what you meet into three tiers. First, the services named in the task statements: learn these properly, with all four card questions. Second, other services that appear in the guide's in-scope list: be able to recognize each from a one-line purpose. Third, anything the guide marks out of scope, which you can skip. The exam guide links to both lists, and it also says it isn't a comprehensive statement of the content, so treat the lists as your boundary and don't hunt for edge cases beyond them.

You also don't need CLI flags, template syntax, or exact prices. Prices change, and the guide frames pricing in terms of purchasing options, tools, and when to use them, not memorized numbers.

Start with one ticket

Study for CLF-C02 the way you'd get oriented in an unfamiliar codebase: find the entry points, learn the boundaries between modules, and don't read every file. Pick one task statement today, write four-question cards for the services in it, set up a budget alert, and run one small experiment in the console. Then log what surprised you. That loop, repeated across 19 tickets, will get you further than any amount of memorizing definitions.

How to Pass the AWS Certified Cloud Practitioner (CLF-C02) Exam on Your First Attempt in 2026

Aziz Farid — Thu, 25 Jun 2026 09:11:24 +0000

Most people who search for the AWS CLF-C02 exam fall into one of two groups: total beginners who want a credential proving they understand AWS, or people already working alongside AWS systems who are tired of nodding along in meetings without really knowing the answer.

Both groups tend to underestimate this exam. The AWS Certified Cloud Practitioner is one of the more approachable certifications AWS offers, but approachable doesn't mean casual. It tests real terminology, real service boundaries, and scenario-based reasoning — not just buzzwords. Candidates who treat it like a marketing overview of "what is the cloud" are often the ones retaking it three months later.

This guide covers what the exam measures, how to structure your study time, the mistakes that quietly sink first-time candidates, and how to know when you're genuinely ready to book a seat.

What the CLF-C02 Exam Actually Measures
Exam Domains and Their Weight Percentages
The 4-Week AWS Certification Roadmap for CLF-C02
Practical Study Tips That Actually Move the Needle
Common Mistakes Candidates Make
Recommended AWS Free Resources
The Role of Practice Exams
Exam Day: What to Expect
FAQ
Conclusion: Your Next Steps

What the CLF-C02 Exam Actually Measures

The Cloud Practitioner certification isn't built around a job title — it's built around a simple question: can you hold an accurate conversation about the AWS Cloud, its value proposition, the shared responsibility model, core services, and billing?

Per AWS's official exam guide, CLF-C02 validates your ability to:

Explain the value of the AWS Cloud
Understand and explain the AWS shared responsibility model
Understand the AWS Well-Architected Framework
Apply foundational security best practices
Understand AWS Cloud costs, economics, and billing practices
Describe and position core services across compute, networking, databases, and storage
Identify the right AWS service for a given use case

What's missing matters just as much: writing code, configuring infrastructure, or designing multi-tier architectures — that's Associate-level territory (think SAA-C03). CLF-C02 is conceptual by design.

The exam has 65 questions — multiple-choice and multiple-response — in a 90-minute window, scored on a scale of 100 to 1,000 with 700 as the minimum pass. A handful of unscored calibration questions are mixed in and not identified, so treat every question as if it counts.

For a feel of the real question style before committing to a schedule, browsing a current CLF-C02 practice exam early on helps calibrate expectations against AWS's actual phrasing.

Exam Domains and Their Weight Percentages

This table is the single most useful planning tool in your prep — it shows exactly where the exam's 65 questions concentrate.

Domain	Weight	Focus Area
Domain 1: Cloud Concepts	24%	Cloud value proposition, deployment and migration models, Well-Architected Framework basics
Domain 2: Security and Compliance	30%	Shared responsibility model, IAM, compliance programs, security services
Domain 3: Cloud Technology and Services	34%	Compute, storage, database, and networking — and how to choose between them
Domain 4: Billing, Pricing, and Support	12%	Pricing models, Cost Explorer, AWS Budgets, support plans, account structure

Here's what many study plans miss: Domains 2 and 3 alone account for 64% of your score. Spread study time evenly across all four, and you're quietly under-preparing for the domains that decide whether you pass.

Domain 1: Cloud Concepts (24%)

Covers the "why" behind cloud adoption — the six advantages of cloud computing, the Well-Architected Framework's six pillars, and migration strategies known as the "7 Rs" (Rehost, Replatform, Repurchase, Refactor, Retire, Retain, Relocate).

A typical scenario: a company moves its on-premises application to AWS with minimal code changes. That's a "rehost" or "lift and shift," not a refactor — recognizing the distinction is exactly what this domain tests.

Domain 2: Security and Compliance (30%)

The largest single domain, and AWS expects you to know the shared responsibility model cold. AWS secures the cloud — hardware, global infrastructure, facilities. You secure what's in the cloud — data, access configuration, application-level controls.

Responsibility shifts by service: with EC2, you patch the guest OS; with RDS, AWS patches the OS but you manage data and access; with Lambda, AWS manages almost everything except your code. Questions test exactly this shift, so build a mental map of where that line sits.

You'll also want familiarity with AWS Artifact, IAM fundamentals (users, groups, roles, policies), and security services like GuardDuty, Inspector, and Shield — conceptually, not at configuration depth.

Domain 3: Cloud Technology and Services (34%)

The heaviest domain by weight and the broadest in scope, covering four categories:

Compute — EC2, Lambda, Elastic Beanstalk, container basics (ECS/EKS)
Storage — S3 storage classes, EBS, EFS, Glacier
Database — RDS, DynamoDB, Aurora
Networking — VPC, Route 53, CloudFront, Direct Connect

You don't need to build a VPC — that's SAA-C03 territory. You need the instinct to match a scenario to the right category. "A company needs a fully managed NoSQL database with single-digit millisecond latency" points to DynamoDB. "A media company wants to deliver video globally with low latency" points to CloudFront, not a single-region EC2 instance.

Storage class scenarios show up often too: daily-access data fits S3 Standard, occasional-but-fast-needed data fits Standard-IA, and archival data fits Glacier. The access-frequency-versus-cost trade-off matters more than exact pricing.

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

The smallest domain by weight, but still roughly 6 to 8 questions. Know the difference between AWS Budgets (proactive alerts on projected spend) and Cost Explorer (retrospective spend analysis), the four AWS Support plan tiers (Basic, Developer, Business, Enterprise), and how AWS Organizations with Consolidated Billing works across multi-account environments.

The 4-Week AWS Certification Roadmap for CLF-C02

With zero cloud background, plan for four to six weeks at 60 to 90 minutes a day. With some technical background, two to three weeks is often enough. The roadmap below targets the beginner end — adjust pacing as needed, but don't skip the practice-exam weeks.

Week 1: Foundations and Cloud Concepts

Work through AWS Skill Builder's free "Cloud Practitioner Essentials" course (roughly six hours, spread across the week)
Learn the six advantages of cloud computing and the Well-Architected Framework's six pillars
Study the IaaS/PaaS/SaaS distinction and where AWS services fall on that spectrum
Close with a short diagnostic quiz to flag shaky domains before going deeper

Week 2: Security, IAM, and Compliance

Drill the shared responsibility model until you can explain it without notes, including how it shifts across EC2, RDS, and Lambda
Learn IAM fundamentals: users, groups, roles, policies, and least privilege
Get familiar with AWS Artifact, Service Control Policies, GuardDuty, Inspector, and Shield conceptually
Spend extra time on Security and Compliance scenarios, since this domain alone is worth 30%

Week 3: Core Services and Use-Case Matching

Build a service cheat sheet by category with a one-line use case for each
Practice reading short business scenarios and identifying which service solves them
Study S3 storage classes using cost-versus-access-frequency trade-offs
Review VPC, Route 53, and CloudFront conceptually — what each is for, not how to configure it

Week 4: Billing, Full Practice Exams, and Review

Learn the practical difference between AWS Budgets, Cost Explorer, and Cost and Usage Reports
Memorize the four support plan tiers and what separates them
Sit two to three full-length, timed practice exams under realistic conditions — no pausing, no notes
Review every missed question by domain and underlying concept, not just "got it wrong"

This is also a good week to browse the exam catalog and see the certification paths beyond CLF-C02 — useful context if you're already thinking about what comes next.

Practical Study Tips That Actually Move the Needle

Learn services by category, not in isolation. Studying S3 next to EBS and EFS shows why you'd choose one over another.
Translate every concept into a scenario. The exam rarely asks "What is DynamoDB?" — more like "A startup needs a database that scales automatically and bills by usage, with no servers to manage." Think in scenarios from day one.
Use active recall over passive rewatching. Watching a course twice teaches less than watching it once, then testing yourself with flashcards or quizzes.
Time-box practice questions early. Answer under a timer from week one so the pacing for 65 questions in 90 minutes becomes automatic.
Keep a running mistakes log. Each miss gets one sentence capturing the concept and correct reasoning — reviewing it the night before often beats cramming new material.
Say the shared responsibility model out loud, more than once. It threads through Domains 1, 2, and parts of 3, so internalizing it pays off across the whole exam.

Common Mistakes Candidates Make

Treating it as a "soft" exam. It's entry-level, not informal — skipping structured study is the top cause of first-attempt failures.
Ignoring the domain weightings. Splitting study time evenly when Security (30%) and Cloud Technology (34%) determine two-thirds of your score is a planning mistake.
Memorizing service names without use cases. "RDS is a database" isn't enough — you need to know which database fits which scenario.
Leaving practice exams until the final days. They train pacing and stamina, not just knowledge — leave them too late and there's no time to fix pacing problems.
Studying only outdated CLF-C01 material. CLF-C01 retired in 2023; older material misses the six-pillar Well-Architected Framework and added AI/ML coverage.
Rushing through multiple-response questions. These trip people up when they stop reading after one plausible answer — AWS always specifies how many to select.

Recommended AWS Free Resources

You don't need to spend money to build a strong foundation:

AWS Skill Builder – Cloud Practitioner Essentials — AWS's own free foundational course.
AWS Certification Official Practice Question Set — a short, free batch of exam-style questions straight from AWS.
AWS Whitepapers — especially Well-Architected Framework and Overview of Amazon Web Services. Dense, but authoritative.
AWS Cloud Quest — a free, game-based way to reinforce concepts.
AWS Free Tier — clicking around S3, EC2, and IAM in the console builds intuition no video replaces.
AWS Documentation — concise, exam-aligned service overviews for anything unfamiliar.

The Role of Practice Exams

Reading and watching videos builds recognition — you nod along because the material sounds familiar. Practice exams build recall under pressure, the actual skill the real test demands. Candidates who rely only on the former are often surprised when the real exam feels harder than their study sessions did.

A solid routine: sit a full-length, timed exam under realistic conditions; review every missed question — and a few lucky guesses too — until you understand why the answer is correct; then revisit your weakest domain before the next attempt. Repeating that cycle two or three times in your final week beats passively rereading notes.

Question quality matters as much as quantity. Generic banks that rephrase textbook definitions won't prepare you for AWS's scenario-driven style, where the correct answer often hinges on a detail buried in the second sentence.

Realistic, full-length simulations build more than recall — they build the calm, practiced confidence that comes from repetition under real time pressure. Pacing yourself across all four domains and reviewing mistakes methodically compounds over a few attempts, and that's usually the difference between walking in anxious and walking in ready.

Exam Day: What to Expect

Arrive or log in early. Online check-in can take 15 to 30 minutes with ID verification and room scans.
Budget your time loosely. 65 questions in 90 minutes is roughly 80 seconds per question.
Flag and move on. Don't let one hard question eat into time you need for the rest.
Trust your scenario training. Most questions resolve by identifying the core need — cost, scalability, security, managed versus unmanaged.

FAQ

1. How many questions are on the CLF-C02 exam, and how much time do I get?
65 questions, 90 minutes. A small number are unscored calibration questions and aren't identified during the test.

2. What is the passing score for CLF-C02?
A scaled score from 100 to 1,000, with 700 as the minimum pass — weighted by difficulty across exam forms, not a simple percentage.

3. Do I need hands-on AWS experience to pass?
Not strictly. CLF-C02 tests conceptual understanding over configuration skills, though a few hours in the AWS Free Tier console improves your intuition for services like S3 and EC2.

4. How is CLF-C02 different from the older CLF-C01 exam?
CLF-C01 retired in 2023. CLF-C02 increased the Security and Compliance weighting, expanded the Well-Architected Framework to six pillars, and added AI/ML coverage.

5. What score should I be hitting on practice exams before booking the real test?
Consistently 80% or higher across multiple full-length practice exams — a single good score can be partly luck, while consistency is the more reliable signal.

6. Is the Cloud Practitioner certification worth it if I'm not technical?
Yes, particularly for project managers, sales engineers, and career changers who need to speak credibly about AWS without doing hands-on architecture work.

7. What should I study after passing CLF-C02?
Most candidates move on to AWS Certified Solutions Architect – Associate (SAA-C03), which builds on these concepts but goes deeper into architecture decisions, VPC design, and high availability. If you're mapping out that next step, it's worth checking current pricing for study resources before committing to a particular course.

Conclusion: Your Next Steps

Passing CLF-C02 on your first attempt isn't about memorizing every AWS service name — it's about understanding the shape of the exam: 64% of your score rides on Security and Cloud Technology, questions lean scenario-based, and consistent practice-exam performance is the most reliable predictor of a real pass.

A simple way to start today:

Block out your study calendar using the four-week roadmap above, adjusted to your pace
Start with AWS Skill Builder's free Cloud Practitioner Essentials course this week
Build your service cheat sheet by category, not alphabetically
In your final week, sit at least two full-length timed practice exams and review every miss
Book your exam date only after you're consistently scoring well, not before

The Cloud Practitioner certification remains one of the better entry points into the cloud industry — broad enough to be useful in almost any role, focused enough to be achievable in a few weeks of honest, structured effort.

About the Author

Aziz Farid is a technical educator, AWS certification content creator, and founder of CloudExamPro, a platform dedicated to helping professionals prepare for AWS certification exams through realistic practice tests and structured learning resources.

Lessons Learned From AWS Exam Prep (With Free Practice Resources)

Aziz Farid — Tue, 30 Sep 2025 09:46:08 +0000

Preparing for AWS certifications has been one of the most rewarding (and sometimes frustrating) parts of my learning journey.

I quickly realized it’s not just about memorizing services — it’s about understanding how AWS wants you to think when solving real-world problems.

In this post, I’ll share the key lessons I learned while preparing for the AWS Cloud Practitioner (CLF-C02) and the AWS Solutions Architect Associate (SAA-C03).

And since practice exams were such a game-changer for me, I’ve also included free full-length resources at the end.

🚀 Lesson 1: Understand Core Services in Context

It’s easy to memorize what S3 or RDS does. The real challenge is knowing when to use them.

For example:

Do you use S3 or EFS for file storage?
When is RDS better than DynamoDB?

Think in terms of scenarios, not just definitions.

🚀 Lesson 2: The Well-Architected Framework Is Gold

The five pillars (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization) are not just buzzwords — they’re the DNA of AWS exam questions.

When I understood how AWS evaluates trade-offs between these pillars, the scenario-based questions started making a lot more sense.

🚀 Lesson 3: Hands-On Beats Reading

Spinning up an EC2 instance, configuring IAM roles, or building a simple 3-tier architecture on the free tier taught me more than hours of reading docs.

If you can touch it, you’ll remember it.

🚀 Lesson 4: Practice Exams Teach More Than Scores

The first time I tried a practice exam, my score was disappointing.

But then I realized: the explanations are the real value.

Every wrong answer was a chance to fix a weak spot — and that’s how I improved fastest.

Free Practice Exams 🎓

Since full-length, high-quality free exams were hard to find, I decided to create and share a couple for the community.

AWS Certified Cloud Practitioner (CLF-C02)

👉 65 real-style questions + detailed explanations

🔗 Try it here
AWS Certified Solutions Architect Associate (SAA-C03)

👉 65 real-style questions + detailed explanations

🔗 Try it here

No signup, no paywall — just open and practice.

Final Thoughts

Studying for AWS certifications is not about chasing a badge. It’s about building a mindset for cloud problem-solving.

If you’re starting your own journey:

Focus on scenarios, not just facts.
Get hands-on, even with small projects.
Treat practice exams as a learning tool, not just a test.

I hope these lessons (and the free practice resources) help you as much as they helped me.

Best of luck on your AWS journey — you’ve got this! ☁️🚀

🌐 More free AWS practice exams & resources: CloudExamPro

AWS Cloud Practitioner & Solutions Architect: Study Tips + Free Exams

Aziz Farid — Tue, 30 Sep 2025 09:30:51 +0000

Free AWS Certification Practice Exams (Cloud Practitioner & Solutions Architect Associate)

Preparing for AWS certifications can feel overwhelming — especially if it’s your first time. I remember when I started studying, I kept asking myself:

“Am I really ready for the exam, or am I just memorizing random facts?”

That’s why practice exams became the most valuable part of my preparation. They don’t just test your knowledge — they show you how AWS actually frames scenarios and expects you to think like a cloud architect.

Why practice exams matter

✅ They simulate the real exam environment (timed, multiple-choice, scenario-based).
✅ They help you identify weak spots quickly.
✅ The explanations teach you why an answer is correct, which is more important than just scoring high.

Free full-length practice exams 🚀

Since I didn’t find many free full-length exams, I decided to put together a couple to help others preparing:

AWS Certified Cloud Practitioner (CLF-C02)

👉 65 real-style questions + detailed explanations

🔗 Try it here
AWS Certified Solutions Architect Associate (SAA-C03)

👉 65 real-style questions + detailed explanations

🔗 Try it here

No signup required — just open and start practicing.

Study tips that worked for me

Understand core AWS services: EC2, S3, IAM, RDS. Don’t just memorize, think about when to use each.
AWS Well-Architected Framework: The 5 pillars (especially Reliability and Cost Optimization) are exam favorites.
Hands-on labs: Even with just the free tier, build something! A small project will stick in your memory way better than reading docs.
Review explanations: When you miss a question, take time to understand the reasoning — that’s where the real learning happens.

Final thoughts

Whether you’re starting with the Cloud Practitioner or aiming for the Solutions Architect Associate, remember:

💡 It’s not about memorizing answers — it’s about learning how AWS expects you to design and solve problems.

I hope these free practice exams make your journey a little easier. If you try them, I’d love your feedback so I can keep improving these resources for the community.

Good luck, and happy studying! ☁️🚀

🌐 More free AWS practice exams & resources: CloudExamPro

DEV Community: Aziz Farid

How to Prepare for AWS Cloud Practitioner (CLF-C02) by Domain

Start with what the exam is, and isn't

Domain weights: what they mean and what they don't

Domain 1: Cloud Concepts (24%)

Domain 2: Security and Compliance (30%)

Domain 3: Cloud Technology and Services (34%)

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

Using practice questions to find gaps, not collect answers

From studying to being ready

Where this leaves you

AWS CLF-C02 Study Guide: What to Study in Each Domain

Treat the exam guide like a spec

Turn the four domains into tickets

Start from the problem, not the service name

Give every service a four-question card

Write down the separating question for every confusing pair

Use the console on purpose

Practice questions: use them like a debugger

How to tell a topic is actually understood

What to leave out

Start with one ticket

How to Pass the AWS Certified Cloud Practitioner (CLF-C02) Exam on Your First Attempt in 2026

Table of Contents

What the CLF-C02 Exam Actually Measures

Exam Domains and Their Weight Percentages

Domain 1: Cloud Concepts (24%)

Domain 2: Security and Compliance (30%)

Domain 3: Cloud Technology and Services (34%)

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

The 4-Week AWS Certification Roadmap for CLF-C02

Week 1: Foundations and Cloud Concepts

Week 2: Security, IAM, and Compliance

Week 3: Core Services and Use-Case Matching

Week 4: Billing, Full Practice Exams, and Review

Practical Study Tips That Actually Move the Needle

Common Mistakes Candidates Make

Recommended AWS Free Resources

The Role of Practice Exams

Exam Day: What to Expect

FAQ

Conclusion: Your Next Steps

Lessons Learned From AWS Exam Prep (With Free Practice Resources)

🚀 Lesson 1: Understand Core Services in Context

🚀 Lesson 2: The Well-Architected Framework Is Gold

🚀 Lesson 3: Hands-On Beats Reading

🚀 Lesson 4: Practice Exams Teach More Than Scores

Free Practice Exams 🎓

Final Thoughts

AWS Cloud Practitioner & Solutions Architect: Study Tips + Free Exams

Free AWS Certification Practice Exams (Cloud Practitioner & Solutions Architect Associate)

Why practice exams matter

Free full-length practice exams 🚀

Study tips that worked for me

Final thoughts