EXAMTOPICS / TECHNOLOGY INSIGHTS

AWS Cloud Practitioner CLF-C02: Exam Scope and Study Priorities

The AWS Certified Cloud Practitioner CLF-C02 exam asks whether you can recognize AWS cloud services, explain why organizations use them, and select appropriate foundational security, architecture, and cost concepts. It is a broad cloud-literacy examination, not a test of production engineering or command-line fluency. A useful preparation strategy begins with the exam’s four domains and repeatedly asks the same question: What decision does this service or concept help someone make?

The current AWS CLF-C02 is the foundational AWS examination. CLF-C01 ended on September 18, 2023; CLF-C02 began on September 19, 2023. Older CLF-C01 questions and study notes therefore need a status check before they are used for today’s exam. AWS’s official CLF-C02 exam guide is the authority for scope, task statements, and weighting.

Know the four domains and what they actually test

AWS groups scored CLF-C02 questions into four domains. Cloud Concepts (24%) tests the value of the AWS Cloud, reliability and elasticity, migration approaches, economics, and foundational architecture principles. Security and Compliance (30%) emphasizes shared responsibility, governance, identity, security services, and compliance resources. Cloud Technology and Services (34%) asks you to recognize infrastructure, compute, storage, databases, networking, and other core service types. Billing, Pricing, and Support (12%) covers payment options, cost-management tools, and support resources.

Those percentages describe scored content, not a guaranteed number of questions in any particular sitting. The assessment includes 65 questions, of which 50 count toward the score and 15 are unscored. AWS reports scores from 100 to 1,000, with 700 required to pass. You have 90 minutes and can receive multiple-choice or multiple-response questions. There is no separate domain pass mark, so a weakness in one section can be offset by strength elsewhere, but ignoring any domain remains an avoidable risk.

The largest domain is technology, but it overlaps the others. For example, choosing Amazon S3 rather than Amazon EBS is a storage decision; limiting access to the chosen data is a security decision; selecting a storage class is a cost decision. Study these connected decisions rather than memorizing service names in isolation.

Cloud concepts: value, economics, and architecture

The cloud’s principal business advantages include trading large upfront infrastructure purchases for consumption-based spending, provisioning resources quickly, and adjusting capacity as needs change. Elasticity means changing capacity with demand; scalability means an architecture can handle an increased load. Neither automatically guarantees high availability. A resilient workload needs appropriate redundancy, health checks, recovery arrangements, and operational design.

AWS organizes facilities into Regions and Availability Zones. A Region is a geographic area containing multiple distinct Availability Zones; deploying resources across AZs protects against some localized infrastructure failures. It does not automatically protect a workload from a whole-Region disruption. Edge locations primarily move content delivery and certain network services closer to users; they are not interchangeable with application deployment in a Region. Local Zones extend selected regional services closer to specified metro areas and have their own availability and connectivity considerations.

When comparing migration choices, distinguish rehosting an application from changing its architecture. A straightforward rehost may reduce the time to move, while a refactor can demand more development in exchange for cloud-native operational benefits. The AWS Cloud Adoption Framework (CAF) concerns enterprise transformation capabilities: business, people, governance, platform, security, and operations. The Well-Architected Framework instead evaluates workloads using operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. A company can use both, but they answer different questions.

The exam rewards the ability to match a term to its consequence. Multi-AZ normally addresses availability within a Region; multi-Region may address a broader resilience or geographical requirement but brings more complexity. Likewise, adopting managed infrastructure can reduce the operational work customers perform without transferring ownership of their data and access decisions.

Security: trace the shared-responsibility boundary

AWS is responsible for security of the cloud: the facilities, physical servers, foundational networking, and virtualization infrastructure underpinning its services. Customers are responsible for security in the cloud to the extent applicable to the service they choose. For Amazon EC2, customers still manage the guest operating system, instance-level patching, workloads, and many network and identity settings. For a managed database such as Amazon RDS, AWS operates more of the underlying platform, while the customer still decides who may access the database, how data is protected, and whether backups and configurations satisfy organizational requirements. In AWS Lambda, AWS manages the servers, but customers own function code, IAM permissions, dependencies, and data handling.

Think in controls rather than slogans: Who patches the guest? Who configures access? Who decides retention? Who manages encryption keys? Those questions help even when a service is unfamiliar. The shared responsibility model is also the reason AWS compliance attestations cannot be treated as an automatic substitute for a customer’s security controls.

At CLF-C02 depth, understand AWS Identity and Access Management (IAM) users, roles, and permission policies; root-user protection; multi-factor authentication; and the benefit of temporary credentials. Permission should follow least privilege, while an explicit deny takes precedence over an allow. Know broadly how AWS Organizations and service control policies help put limits around multiple accounts, but do not assume an SCP itself grants permissions.

Distinguish security services by purpose. AWS CloudTrail records supported account activity and API events; Amazon CloudWatch handles operational metrics, logs, and alarms. Amazon GuardDuty detects potential threats; AWS Config tracks resource configuration and changes; AWS Security Hub CSPM helps assess security posture; AWS KMS manages cryptographic keys. You need to recognize the appropriate capability, not memorize specialist incident-response playbooks. Readers planning to go deeper into defense engineering can explore AWS SCS-C03, whose scope is significantly more technical.

Technology: choose the service family before the service name

For compute, Amazon EC2 provides virtual servers with substantial guest-management responsibility. AWS Lambda executes code without having to provision application servers and suits event-driven functions within service limits. Container technologies package applications and their dependencies; Amazon ECS and Amazon EKS offer different ways to orchestrate them, and AWS Fargate is a serverless compute option for eligible container workloads. The foundational exam usually expects you to recognize the use case rather than configure a cluster.

For storage, Amazon S3 stores objects such as files, backups, and static content. Amazon EBS supplies block volumes for supported EC2 instances, while Amazon EFS supplies shared file storage accessible to compatible workloads. These are not synonyms for generic cloud storage: objects, blocks, and files create different access and lifecycle patterns. The practical difference between Amazon EBS and S3 is especially worth understanding because it helps with backup, durability, and workload-placement questions.

For databases, distinguish Amazon RDS, a managed relational database service, from Amazon DynamoDB, a managed NoSQL key-value/document database. A business needing structured relational queries and transactions might choose an RDS engine; one seeking a serverless key-value access pattern might evaluate DynamoDB. Avoid the common mistake of claiming every AWS database is relational or that every database scales the same way.

For networking, Amazon VPC provides the logical network boundary; subnets subdivide the VPC address space; security groups control supported resource interfaces and are stateful; network ACLs apply at subnet boundaries and are stateless. Route 53 supports DNS and related routing policies; Elastic Load Balancing distributes supported traffic to targets; Amazon CloudFront is a content-delivery network. These names often appear in scenario distractors because several can improve availability or performance for different reasons.

The exam also includes introductory AI/ML and analytics awareness. Identify the category of solution rather than promising that the exam requires specialist model training. When in doubt, return to AWS’s published in-scope service reference, since service lists can evolve independently from third-party notes.

Billing and pricing: distinguish visibility, prediction, and commitment

The right cost tool depends on the task. AWS Pricing Calculator estimates possible spending for a planned design. Cost Explorer helps investigate existing cost and usage patterns. AWS Budgets monitors thresholds and can generate alerts or configured budget actions. Detailed billing exports are suited to deeper cost allocation and reporting. A forecast is not a guarantee, and an account budget does not automatically prevent charges just because an alert is set.

For compute purchasing, On-Demand is flexible with no long-term commitment, Savings Plans exchange an hourly spend commitment for eligible discounts, Reserved Instances make commitments tied to relevant instance attributes, and Spot Instances use spare EC2 capacity at discounted prices but may be interrupted. A stable baseline workload and an interruption-tolerant batch job should not receive identical purchasing advice. The best answer names the workload requirement first and the purchasing option second.

Also understand shared or consolidated billing in organizations, tagging and cost allocation, and the general difference between technical support channels and architecture guidance. Support plan details can change; confirm current entitlements on AWS before quoting a specific response-time promise or feature as permanent exam fact.

Prepare with service-choice scenarios rather than flashcards alone

Start with the four-domain outline and write one line for each task statement in the exam guide. Mark it recognize, explain, or compare. A concept you can define but cannot distinguish from a similar option still needs work. For example, knowing that CloudTrail records events is not enough if you confuse it with CloudWatch metrics; knowing what an AZ is does not help if you treat it like an edge location.

A low-risk practice environment can improve recall: observe the console layout, identify billing dashboards, inspect IAM role concepts, or review the EC2 and S3 service descriptions. Before using any AWS account, enable billing safeguards and understand that usage can incur charges. No paid deployment is required simply to understand these introductory ideas. When hands-on work is impractical, use AWS product diagrams and scenario explanations from official training.

For a practical self-check, try the following without notes: explain the difference between availability and latency; compare EC2, Lambda, and Fargate; name who patches an EC2 guest; choose between S3, EBS, and EFS; tell CloudTrail from CloudWatch; and explain why Cost Explorer cannot replace Pricing Calculator. Every weak answer should lead to a targeted revision, not another indiscriminate pass over all services.

Use timed practice to rehearse reading all words in multiple-response questions. Classify each wrong answer as a service confusion, an incorrect assumption about responsibility, a cost-model error, or a misunderstanding of the stem. Revisit the relevant official task and retry a new scenario. A pass-rate target on an unverified third-party question bank is not proof of certification readiness.

Where Cloud Practitioner fits next

CLF-C02 can establish shared vocabulary for support, sales, project delivery, business analysis, and early cloud roles. It does not certify someone as a production architect or security engineer. If you move into solution design, AWS SAA-C03 involves deeper architecture decisions. If your focus is building software, AWS Certified Developer – Associate has a different engineering emphasis. The AWS certification lineup can help you place those pathways in context.

The useful outcome of studying CLF-C02 is not a memorized catalog. It is the ability to explain basic AWS choices correctly: which layer owns a problem, what a cloud service is meant to do, what makes a workload resilient, and what drives its cost. Check the official guide immediately before booking because AWS can revise guidance, in-scope services, and testing arrangements.