AWS CLF-C02: Cloud Practitioner Study Guide for 2026

AWS Certified Cloud Practitioner CLF-C02 is a current foundational certification for people who need broad AWS Cloud knowledge without being expected to design, implement, or troubleshoot production architectures.

The exam is weighted across Cloud Concepts at 24%, Security and Compliance at 30%, Cloud Technology and Services at 34%, and Billing, Pricing, and Support at 12%. The AWS CLF-C02 exam and Cloud Practitioner certification should control scope.

The goal is service and concept recognition in business context: why cloud is useful, who owns security responsibilities, what major AWS services do, and how cloud pricing and support work.

Cloud Concepts — 24%

Cloud concepts cover the value of cloud computing, elasticity, agility, global reach, high availability, economies of scale, and consumption-based economics. In the cloud concepts 24% portion of AWS CLF-C02 foundational cloud knowledge, this matters because foundational candidates need to explain why organizations choose cloud rather than only name services. A strong candidate reviewing cloud concepts 24% should be able to name the requirement this decision satisfies and the evidence that would prove the result.

Use scenarios involving unpredictable demand, global expansion, disaster recovery, experimentation, and data-center reduction and explain the cloud value in each. During cloud concepts 24% practice, write the expected outcome and assumptions before making the change. After the cloud concepts 24% exercise, compare the observed state with that expectation and alter one meaningful condition to see whether the same decision still holds.

Memorizing benefit words without connecting them to a business scenario makes questions harder than necessary. In cloud concepts 24% scenarios, compare the preferred answer with the nearest plausible alternative and state the exact condition that makes the alternative weaker. That cloud concepts 24% distinction is more durable than memorizing one service, command, or exam phrase.

The AWS CLF-C02 Cloud Concepts guide provides supporting practice.

Security and Compliance — 30%

This domain includes the shared responsibility model, IAM, access management, security and compliance concepts, and foundational AWS security capabilities. In the security and compliance 30% portion of AWS CLF-C02 foundational cloud knowledge, this matters because cloud security depends on understanding which responsibilities remain with AWS and which remain with the customer. A strong candidate reviewing security and compliance 30% should be able to name the requirement this decision satisfies and the evidence that would prove the result.

Take EC2, a managed database, and a SaaS-like AWS service and compare customer responsibilities for operating system, data, identity, and configuration. During security and compliance 30% practice, write the expected outcome and assumptions before making the change. After the security and compliance 30% exercise, compare the observed state with that expectation and alter one meaningful condition to see whether the same decision still holds.

Assuming AWS handles all security because the infrastructure is managed is one of the most common foundational mistakes. In security and compliance 30% scenarios, compare the preferred answer with the nearest plausible alternative and state the exact condition that makes the alternative weaker. That security and compliance 30% distinction is more durable than memorizing one service, command, or exam phrase.

The shared responsibility guide and security and IAM guide provide deeper review.

Technology and Services — 34%

The largest domain requires recognition of major AWS service categories including compute, storage, database, networking, analytics, management, migration, security, serverless, and AI/ML. In the technology and services 34% portion of AWS CLF-C02 foundational cloud knowledge, this matters because Cloud Practitioner should know what problem a service category solves without needing associate-level configuration depth. A strong candidate reviewing technology and services 34% should be able to name the requirement this decision satisfies and the evidence that would prove the result.

For each major service, write its category, one common use case, and the neighboring service a beginner might confuse it with. During technology and services 34% practice, write the expected outcome and assumptions before making the change. After the technology and services 34% exercise, compare the observed state with that expectation and alter one meaningful condition to see whether the same decision still holds.

Trying to memorize the entire AWS catalog creates unnecessary volume and makes core service roles harder to recall. In technology and services 34% scenarios, compare the preferred answer with the nearest plausible alternative and state the exact condition that makes the alternative weaker. That technology and services 34% distinction is more durable than memorizing one service, command, or exam phrase.

Compare compute and storage by purpose

EC2, Lambda, containers, S3, EBS, EFS, archival storage, and related services differ by operating model, access pattern, and workload need. In the compare compute and storage by purpose portion of AWS CLF-C02 foundational cloud knowledge, this matters because foundational questions often test correct service positioning rather than implementation. A strong candidate reviewing compare compute and storage by purpose should be able to name the requirement this decision satisfies and the evidence that would prove the result.

Classify workloads as instance-based, serverless, object, block, file, or archival and choose the service category that fits. During compare compute and storage by purpose practice, write the expected outcome and assumptions before making the change. After the compare compute and storage by purpose exercise, compare the observed state with that expectation and alter one meaningful condition to see whether the same decision still holds.

Treating all storage or compute services as interchangeable hides the basic distinctions CLF-C02 expects. In compare compute and storage by purpose scenarios, compare the preferred answer with the nearest plausible alternative and state the exact condition that makes the alternative weaker. That compare compute and storage by purpose distinction is more durable than memorizing one service, command, or exam phrase.

The AWS CLF-C02 core compute and storage guide supports this comparison.

Understand Regions, Availability Zones, and edge infrastructure

AWS global infrastructure concepts explain geographic scope, fault isolation, latency, data location, and high-level resilience. In the understand regions, availability zones, and edge infrastructure portion of AWS CLF-C02 foundational cloud knowledge, this matters because many cloud decisions begin with where resources and users are located. A strong candidate reviewing understand regions, availability zones, and edge infrastructure should be able to name the requirement this decision satisfies and the evidence that would prove the result.

Explain why a workload might use multiple Availability Zones in one Region and why another workload might need users served closer to the edge. During understand regions, availability zones, and edge infrastructure practice, write the expected outcome and assumptions before making the change. After the understand regions, availability zones, and edge infrastructure exercise, compare the observed state with that expectation and alter one meaningful condition to see whether the same decision still holds.

Confusing a Region with an Availability Zone leads to incorrect assumptions about resilience and geographic separation. In understand regions, availability zones, and edge infrastructure scenarios, compare the preferred answer with the nearest plausible alternative and state the exact condition that makes the alternative weaker. That understand regions, availability zones, and edge infrastructure distinction is more durable than memorizing one service, command, or exam phrase.

The Regions, AZs, and edge infrastructure guide provides a current visual model.

Billing, Pricing, and Support — 12%

This domain covers pricing approaches, cost-management concepts, purchasing options, support resources, budgets, calculators, and AWS assistance channels. In the billing, pricing, and support 12% portion of AWS CLF-C02 foundational cloud knowledge, this matters because foundational cloud literacy includes understanding how usage becomes cost and where organizations get help. A strong candidate reviewing billing, pricing, and support 12% should be able to name the requirement this decision satisfies and the evidence that would prove the result.

Compare On-Demand, commitment-based, and Spot-style purchasing concepts and identify which workloads make each reasonable. During billing, pricing, and support 12% practice, write the expected outcome and assumptions before making the change. After the billing, pricing, and support 12% exercise, compare the observed state with that expectation and alter one meaningful condition to see whether the same decision still holds.

CLF-C02 usually tests pricing logic and service positioning rather than detailed invoice arithmetic. In billing, pricing, and support 12% scenarios, compare the preferred answer with the nearest plausible alternative and state the exact condition that makes the alternative weaker. That billing, pricing, and support 12% distinction is more durable than memorizing one service, command, or exam phrase.

Use hands-on exploration at the right depth

Console exploration helps foundational learners recognize services and infrastructure concepts even though production design and troubleshooting are outside the target role. In the use hands-on exploration at the right depth portion of AWS CLF-C02 foundational cloud knowledge, this matters because seeing Regions, IAM, S3, EC2, pricing tools, and support resources makes abstract terminology easier to remember. A strong candidate reviewing use hands-on exploration at the right depth should be able to name the requirement this decision satisfies and the evidence that would prove the result.

Spend a short lab session locating core services, reviewing IAM, examining an S3 bucket, and opening the Pricing Calculator without building complex architecture. During use hands-on exploration at the right depth practice, write the expected outcome and assumptions before making the change. After the use hands-on exploration at the right depth exercise, compare the observed state with that expectation and alter one meaningful condition to see whether the same decision still holds.

Turning Cloud Practitioner study into an associate-level engineering lab wastes time on skills the exam does not require. In use hands-on exploration at the right depth scenarios, compare the preferred answer with the nearest plausible alternative and state the exact condition that makes the alternative weaker. That use hands-on exploration at the right depth distinction is more durable than memorizing one service, command, or exam phrase.

Build final review from domain-specific gaps

Practice results are more useful when mistakes are classified as cloud concepts, security, service recognition, or billing and support rather than treated as one score. In the build final review from domain-specific gaps portion of AWS CLF-C02 foundational cloud knowledge, this matters because different weaknesses require different repair strategies. A strong candidate reviewing build final review from domain-specific gaps should be able to name the requirement this decision satisfies and the evidence that would prove the result.

Maintain a four-domain error log and revisit only unresolved distinctions during the final week. During build final review from domain-specific gaps practice, write the expected outcome and assumptions before making the change. After the build final review from domain-specific gaps exercise, compare the observed state with that expectation and alter one meaningful condition to see whether the same decision still holds.

Repeating random question banks can improve recognition while leaving the same conceptual gap unresolved. In build final review from domain-specific gaps scenarios, compare the preferred answer with the nearest plausible alternative and state the exact condition that makes the alternative weaker. That build final review from domain-specific gaps distinction is more durable than memorizing one service, command, or exam phrase.

The CLF-C02 readiness matrix can organize the final review.

Cloud Practitioner readiness is broad rather than deep: explain cloud value, shared responsibility, major service roles, global infrastructure, security basics, and cloud economics in plain language.

Keep the scope foundational and use the official CLF-C02 guide as the current source of truth.