AWS Cloud Practitioner CLF-C02 Complete Guide — Exam Overview and Domain 1: Cloud Concepts

The AWS Cloud Practitioner CLF-C02 is the lowest entry point among the 12 AWS certifications, but treating it lightly almost guarantees you’ll stall at Solutions Architect Associate or Developer Associate. Without locking in the foundational domains, you cannot build the “design decision premises” that higher exams test. This article unpacks the CLF-C02 exam specification and systematizes one of its highest-weighted domains — Domain 1: Cloud Concepts (24%) — to a passing standard.

The full cloud picture is covered in Cloud Computing Fundamentals 2026 — AWS, Azure, GCP for AI Engineers (published 2026-05-25). With NIST definitions, service models, geographic topology, and market structure already in hand, this article walks directly into the AWS Cloud Practitioner CLF-C02 scope.

The Exact Numbers of the CLF-C02 Exam Specification

Pull the exact specifications from the official AWS Certified Cloud Practitioner (CLF-C02) Exam Guide. Vague articles saying “around 60 questions, about 90 minutes” will lead you to misallocate time on test day.

The 15 unscored questions are AWS’s data-gathering questions for future scoring calibration — they’re indistinguishable from scored ones, so the only response is to answer all 65 with equal seriousness. The 700 / 1000 passing score is a scaled score, not a raw correct-answer percentage. As a rough heuristic, “60–65% of scored questions correct” is the threshold.

Domain Weighting and Scope

CLF-C02 is split into four domains, each with explicit weighting. Knowing the weights tells you where to put your study time.

Domain 3 (Cloud Technology and Services, 34%) carries the largest weight, asking about specific service knowledge across EC2 / S3 / RDS / Lambda / IAM / VPC. Domain 2 (Security and Compliance, 30%) tests the shared responsibility model and security service grasp. Domain 1 (Cloud Concepts, 24%) is what this article centers on. Domain 4 (Billing, Pricing, and Support, 12%) is the lowest weight but the most concrete domain — there’s no ambiguity, so it’s the most direct points to capture.

Pass Strategy — Study Time and Exam Time Allocation

For total cloud beginners, the realistic study time for CLF-C02 sits at 30–50 hours. With prior IT experience (on-premise sysadmin, application development, etc.), 20–30 hours is enough. Pacing as 1 hour/day for 30 days yields a realistic month-long preparation cycle.

For exam day time allocation, allotting 1 minute 20 seconds per question is the standard. 65 questions × 1m20s = 86 minutes, leaving roughly 4 minutes for review. Flag any difficult question with the on-screen Flag for Review feature and skip immediately — that’s the cardinal rule. Spending 5 minutes hesitating ruins the rest of the exam.

Recommended study materials: the official AWS Skill Builder (Individual at $29/month) Cloud Practitioner Exam Prep Plan, the unofficial bestseller “AWS Certified Cloud Practitioner Study Guide” (Stephane Maarek, Udemy), and Tutorials Dojo practice tests ($14.99 USD). A “Skill Builder + Tutorials Dojo” combo is the most cost-effective. Stephane Maarek’s video course is best as a complementary lecture.

Domain 1 Overview — The Four Task Statements of Cloud Concepts

Domain 1 (Cloud Concepts, 24%) is broken into four Task Statements per the official exam guide.

1.1 corresponds to the “6 Benefits of Cloud Adoption” (AWS official). 1.2 corresponds to the AWS Well-Architected Framework’s 6 pillars. 1.3 corresponds to the AWS Cloud Adoption Framework (CAF) 6 perspectives and the 6R migration strategies. 1.4 corresponds to TCO (Total Cost of Ownership) and the CapEx vs OpEx distinction. The rest of this article works through each section.

The Six Benefits of Cloud Adoption (AWS Official)

AWS officially defines six benefits of cloud adoption. They appear directly in the exam — memorize the wording verbatim.

The exam tests with questions like “Which benefit of cloud adoption is described by ‘pay only for what you use’?” The answer is 1: Trade upfront expense for variable expense. Or “Which benefit allows expanding into multiple Regions worldwide in minutes?” — that’s 6: Go global in minutes.

AWS Well-Architected Framework — The Six Pillars

The AWS Well-Architected Framework expresses cloud architecture best practices through six pillars. Sustainability was added at re:Invent 2021, completing the current count of six.

The Sustainability pillar binds to specific practices: choosing Regions with renewable energy, using ARM-based Graviton (lower power consumption), improving hardware utilization, and data reduction (stop storing unnecessary data). The Carbon Footprint Tool is available in the AWS Console.

AWS Cloud Practitioner CLF-C02 asks for the definition of each pillar and “which pillar is relevant in a given scenario.” Examples: “Run AI batch processing on Spot Instances at night for cost savings” → Cost Optimization. “Place replicas in multiple AZs to keep service running during failures” → Reliability. “Choose a renewable-energy Region to cut carbon emissions” → Sustainability.

The Well-Architected Tool is a free service for self-evaluating designs against the 6 pillars, available from the AWS Console. If you’re aiming for Solutions Architect Associate or higher, design-review experience with this tool pays large dividends in real work.

AWS Cloud Adoption Framework (CAF) — The Six Perspectives

The AWS Cloud Adoption Framework is comprehensive guidance for organizations migrating to the cloud, split into six Perspectives.

While Well-Architected looks at “whether an individual architecture is sound,” CAF looks at “the organization’s overall cloud maturity” — that contrast keeps them straight. The exam asks things like “Which of the 6 Perspectives concerns workforce development?” The answer is People.

In real work, CAF is used at the start of a cloud migration project. “Is our organization ready for the cloud?” “Which Perspective is the weak one?” — those are the structural questions CAF helps frame. AWS Professional Services and partner firms typically present CAF assessment in deliverables.

The 6 Rs — Six Cloud Migration Strategies

The 6R framework (originally Gartner’s 5R, extended by AWS) systematizes the six options for migrating existing workloads to the cloud.

Rehost has the lowest effort and is the most common initial choice for legacy systems. Refactor offers the highest cloud benefit (autoscaling, serverless, microservices), but the effort and risk are both highest. Real-world migration projects typically combine multiple Rs — for example, “Rehost the main systems, Refactor only the high-traffic workloads, Replatform the data layer.”

Exam questions like “Which 6R strategy applies to ‘cutting infrastructure cost by replacing an existing email system with Microsoft 365’?” point to Repurchase. “Which 6R strategy moves on-premise applications to EC2 with no code changes?” — Rehost.

Cloud Economics — TCO and CapEx vs OpEx

TCO (Total Cost of Ownership) is the sum of all costs to acquire, operate, and maintain a system. AWS provides a free TCO Calculator (officially renamed Pricing Calculator) to compare on-premise vs cloud costs.

The dominant pattern is that cloud TCO comes in lower than on-premise. The reasons are clear: capital cost zero (no server purchase), operations cost large reduction (AWS handles data center ops), and high utilization (no overprovisioning headroom). Industry studies show cloud migrations typically cut TCO by 30–50%.

The CapEx (Capital Expenditure) vs OpEx (Operating Expenditure) boundary is where business-side stakeholders most easily get tripped up. CapEx is asset purchase — buying a server is a one-time large outlay (depreciable, typically 5 years). OpEx is operating cost — cloud usage fees are recurring expenses (immediately deductible). Cloud’s “CapEx → OpEx” conversion improves cash flow and removes the demand-forecast risk of asset purchase. Pre-IPO startups especially benefit from the CapEx-zero structure for balance-sheet flexibility.

The Six Perspectives in Real Project Scenarios

Understanding the 6 Perspectives abstractly is hard. Mapping them to actual project tasks makes them concrete.

Business: Defining the ROI of a cloud migration. Setting the goal as “30% infrastructure cost reduction in 18 months.” Securing executive sponsorship. People: Training existing operations staff in AWS, hiring cloud architects, building a Cloud Center of Excellence (CCoE). Governance: Setting up AWS accounts (multi-account strategy with Organizations), creating IAM policies, defining cost limits. Platform: Building landing zones (Control Tower), designing the VPC architecture, building the CI/CD pipeline. Security: Configuring GuardDuty / Security Hub / WAF, encrypting data with KMS, designing IAM Roles. Operations: Building CloudWatch dashboards, setting up incident response procedures, refining SLOs / SLAs.

The exam asks things like “Building a Cloud Center of Excellence (CCoE) belongs to which Perspective?” The answer is People. “AWS Organizations multi-account setup belongs to which Perspective?” — Governance.

The CapEx / OpEx Boundary by Real Examples

The CapEx / OpEx distinction is easy to confuse on the exam, so concrete cases help.

CapEx examples: Buying physical servers, building a data center, purchasing software licenses (perpetual), purchasing network equipment. These hit the books as fixed assets and are depreciated over time (servers typically 5 years). The IT department’s annual budget proposal centers on CapEx requests.

OpEx examples: AWS usage fees, SaaS subscriptions, electricity and rent, salaries, cloud database fees. These are immediately deductible against the period’s expenses. Cloud adoption converts most of what was traditionally CapEx into OpEx, which is the financial advantage.

An exam question like “Why is AWS usage fee structure attractive financially?” expects the answer “It converts CapEx to OpEx.” Or “What’s the difference between $1M on-premise server purchase and $1M annual AWS spend?” — “The on-premise outlay is CapEx (depreciated over 5 years), while AWS spend is OpEx (immediately deductible).”

The Three-Stage Cloud Adoption Model

AWS Cloud Adoption progresses through three stages: Envision → Align → Launch → Scale (4 stages strictly, but practically grouped into three).

Envision stage: Identify business outcomes and prioritize cloud transformation initiatives. Set quantitative goals (revenue growth, cost reduction, time-to-market improvement). Align stage: Identify the capability gaps to achieve the goals. Plan and execute cross-organizational alignment workshops. Launch & Scale stage: Deliver pilot initiatives in production. After successful pilots, scale across the organization. Use Well-Architected reviews to ensure quality.

The CAF appendix describes the same flow in detail. The exam asks “Which stage is ‘creating a quantitative goal of revenue growth or cost reduction’?” The answer is Envision.

Practice Questions (Domain 1 — 10 Sample Items)

10 sample questions matching the difficulty level of the real exam. Answers follow at the end.

Answers: 1-A / 2-B / 3-B / 4-C / 5-C / 6-C / 7-B / 8-B / 9-B / 10-B

Exam Day Notes

Reach the venue 30 minutes early — Pearson VUE check-in includes ID verification (photo ID + secondary ID required), and the longer the line, the more your start time slips. For OnVUE (online proctored) you must complete face / room / desk inspection with the proctor 30 minutes before start. Your room must be empty (no phones, books, smart watches, second monitors).

During the exam, paper notes and pens are prohibited. The test center provides a notepad and pen, OnVUE provides an on-screen whiteboard. Memos are limited so calculations should be done in your head where possible.

The result (pass/fail and scaled score) appears on screen the moment you finish the exam. The detailed score report (Domain-level breakdown) arrives in the AWS Certification portal within 5 days. A passing CLF-C02 unlocks a 50% discount voucher for the next certification — start applying it to SAA-C03.

Conclusion — Next Up Is Domain 2

The CLF-C02 exam specification, Domain 1 (Cloud Concepts) structure, the 6 benefits of cloud adoption, AWS Well-Architected 6 pillars, CAF 6 perspectives, 6R migration strategies, and TCO / CapEx vs OpEx — covered in one read. Domain 1 alone is enough material to claim “the bare minimum to pass CLF-C02,” and properly working through it puts you on the trajectory for Solutions Architect Associate and higher exams.

Next comes Domain 2 (Security and Compliance, 30%) — the largest-weighted security domain. The shared responsibility model, IAM, the major security services (GuardDuty / Security Hub / WAF / KMS), and compliance certifications (HIPAA / PCI DSS / SOC 2) are the focus. The next article in the series covers Domain 2 in depth.

References

ブラウザだけでできる本格的なAI画像生成【ConoHa AI Canvas】

swiftwand

X

AIを使って、毎日の生活をもっと快適にするアイデアや将来像を発信しています。 初心者にもわかりやすく、すぐに取り入れられる実践的な情報をお届けします。 Sharing ideas and visions for a better daily life with AI. Practical tips that anyone can start using right away.