Module 1: CLF-C02 Exam Overview and AWS Cloud Basics

Welcome & What You’ll Learn in This Module

In this first module, you will:

• Get oriented to the AWS Certified Cloud Practitioner (CLF-C02) exam
• Understand the exam format, domains, and scoring
• Build a high-level mental model of the AWS Cloud
• Recognize the major AWS service categories and basic cloud characteristics

This module is designed for about 15 minutes of focused study. Keep a notepad (or notes app) open to jot down:

• Key numbers (question count, timing, passing score)
• Domain names and their weightings
• Core cloud concepts (scalability, elasticity, pay-as-you-go)

> Tip: Treat this module as your orientation map for the entire CLF-C02 journey. You’ll keep referring back to these basics as you go deeper in later modules.

CLF-C02 Exam Basics: Format, Time, and Scoring

Let’s lock in the core facts about the CLF-C02 exam (current as of early 2026):

Exam Format

• Number of questions: 65
• A mix of multiple-choice (one correct answer) and multiple-response (two or more correct answers)
• Time allowed: 90 minutes (1.5 hours)
• Delivery: Testing center or online proctored exam via Pearson VUE

Scoring

• Scaled score range: 100–1000
• Minimum passing score: 700
• AWS uses scaled scoring, which means:
• Your raw score (how many questions you got right) is converted to a standardized scale (100–1000)
• This compensates for small variations in difficulty between different test forms

You don’t see how many questions you got right; you only see your scaled score and a pass/fail result.

> Mental anchor: Remember 65 questions, 90 minutes, 700 to pass, 100–1000 scale.

CLF-C02 Exam Domains and Their Weightings

The CLF-C02 exam is organized into four domains, each with a percentage that shows its weight on the exam. As of the current blueprint (still current in 2026):

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

Why these weightings matter

• Domains with higher percentages (Security & Compliance, Cloud Tech & Services) will:
• Have more questions
• Deserve more of your study time
• Even the lowest-weight domain (Billing, Pricing, and Support at 12%) is not optional—it can still decide pass vs fail.

> Quick rule of thumb: Concepts (24) + Security (30) + Services (34) + Billing (12) = 100%.

Mini Mapping Exercise: Domains vs Topics

Let’s quickly map topics to domains to build intuition.

Task: For each topic below, decide which single best domain it fits into:

1. Understanding the difference between CapEx and OpEx
2. Knowing what the AWS Shared Responsibility Model is
3. Describing the benefits of cloud computing (e.g., agility, elasticity)
4. Knowing when to use Amazon S3 vs Amazon EBS

Write your answers in this format: `1: [domain], 2: [domain], ...` before checking the solution below.

<details>

<summary>Show suggested answers</summary>

1. Billing, Pricing, and Support – CapEx vs OpEx is a cost model topic.
2. Security and Compliance – The Shared Responsibility Model lives here.
3. Cloud Concepts – Benefits of cloud computing are core concepts.
4. Cloud Technology and Services – Choosing between S3 and EBS is about services.

</details>

> As you study, always ask: “Which domain does this belong to?” It helps you prioritize and remember.

What Is the AWS Cloud? A High-Level Definition

At the CLF-C02 level, you don’t need deep configuration skills, but you must understand what the AWS Cloud is.

Simple definition

> AWS Cloud is a global platform of on-demand IT resources—such as compute power, storage, databases, and networking—delivered over the internet with pay-as-you-go pricing.

Key characteristics (that AWS loves to test)

• On-demand self-service – You can provision resources without human interaction with AWS staff.
• Broad network access – Access over the internet from anywhere, via web consoles, SDKs, and APIs.
• Resource pooling – AWS uses multi-tenancy; resources are shared across many customers but logically isolated.
• Rapid elasticity – You can scale up or down quickly, often automatically.
• Measured service – Usage is metered (e.g., per hour, per GB, per request) and billed accordingly.

These characteristics map closely to the classic NIST definition of cloud computing, which AWS still aligns with in 2026.

Real-World Scenario: From On-Prem to AWS Cloud

Imagine a small e-commerce startup that used to run everything in its own on-premises data center.

#### Before AWS (On-Premises)

• They buy servers upfront (CapEx) sized for peak holiday traffic.
• Most of the year, those servers are underutilized.
• Scaling up for a sale or campaign takes weeks or months (procurement, installation, configuration).
• They must maintain power, cooling, physical security, and hardware.

#### After Moving to AWS

• They run their web application on Amazon EC2 (compute) and store product images in Amazon S3 (storage).
• During normal traffic, they use a small number of EC2 instances.
• During Black Friday, Auto Scaling automatically adds more instances to handle the load.
• After the spike, AWS scales back down, and they stop paying for the extra capacity.

What this illustrates:

• Elasticity & scalability: Automatically adjust resources to demand.
• Pay-as-you-go: Pay only for capacity when you actually need it.
• Reduced operational burden: AWS handles data center infrastructure so the team can focus on features.

> This kind of scenario is exactly the level of detail CLF-C02 expects: you can explain why organizations move to AWS, not just list service names.

AWS Global Infrastructure: Regions, AZs, and Edge Locations

A high-level understanding of where AWS runs is essential.

Core building blocks

• Region
• A geographic area (e.g., `us-east-1` in Northern Virginia, `eu-west-1` in Ireland).
• Each region is isolated from others for fault tolerance and data residency.

• Availability Zone (AZ)
• One or more physically separate data centers within a region.
• Connected by high-speed, low-latency networking.
• Designed so that if one AZ has an issue, others in the region can keep running.

• Edge locations
• Sites used by services like Amazon CloudFront (CDN) and AWS Global Accelerator to cache content closer to users.

Visual description

Imagine a map of the world:

• Dots representing regions on multiple continents
• Each region has multiple small dots inside it (the AZs)
• Hundreds of smaller points scattered widely (the edge locations)

> For CLF-C02, you don’t need an exact count of regions or AZs, but you must understand: Regions = geographic separation, AZs = high availability within a region, Edge locations = low-latency content delivery.

Major AWS Service Categories (High-Level View)

You’ll see many service names on the exam, but CLF-C02 mainly tests if you can recognize the category and purpose, not configure them.

1. Compute

• Amazon EC2 – Virtual servers in the cloud.
• AWS Lambda – Run code without managing servers (serverless compute).

2. Storage

• Amazon S3 – Object storage for files, backups, static website content.
• Amazon EBS – Block storage for EC2 instances (like a virtual hard drive).

3. Database

• Amazon RDS – Managed relational databases (e.g., MySQL, PostgreSQL).
• Amazon DynamoDB – Fully managed NoSQL key–value database.

4. Networking & Content Delivery

• Amazon VPC – Your logically isolated virtual network in AWS.
• Elastic Load Balancing (ELB) – Distributes traffic across multiple targets.
• Amazon CloudFront – Content Delivery Network (CDN) for faster content delivery.

5. Security, Identity, and Compliance

• AWS Identity and Access Management (IAM) – Controls who can do what in your AWS account.
• AWS Organizations – Manage multiple AWS accounts centrally.
• AWS Key Management Service (KMS) – Manage encryption keys.

> For now, focus on matching service names to categories and one-sentence purposes. Depth comes later.

Quick Check: Cloud Characteristics and Services

Test your understanding of basic cloud characteristics and service categories.

Review Key Terms for CLF-C02 and AWS Basics

Use these flashcards to reinforce the most important terms from this module.

Apply It: Match Needs to AWS Service Categories

Let’s connect real needs to service categories, just like CLF-C02 scenario questions.

For each situation, decide which service category is most relevant: Compute, Storage, Database, Networking, Security.

1. A company needs a place to store user-uploaded photos and access them via URLs worldwide.
2. A startup wants to run code in response to image uploads without managing servers.
3. A team needs a managed relational database for a transactional web app.
4. An organization wants to control which employees can access which AWS resources.
5. A global app wants to distribute static content (images, CSS, JS) closer to users to reduce latency.

Pause and write your answers (e.g., `1: Storage, 2: Compute, ...`). Then check below.

<details>

<summary>Show suggested answers</summary>

1. Storage – Likely Amazon S3 (object storage).
2. Compute – AWS Lambda (serverless compute).
3. Database – Amazon RDS (managed relational database).
4. Security – AWS IAM (identity and access management).
5. Networking – Amazon CloudFront (content delivery network).

</details>

> As you continue with later modules, keep practicing this “situation → category → likely service” mapping. It’s central to success on CLF-C02.

Wrap-Up: Connect Exam Domains to AWS Cloud Basics

You’ve now built a foundation for the rest of your CLF-C02 preparation.

You should be able to:

• State the exam format: 65 questions, 90 minutes, scaled score 100–1000, 700 to pass.
• List the four domains and their weightings:
• Cloud Concepts (24%)
• Security and Compliance (30%)
• Cloud Technology and Services (34%)
• Billing, Pricing, and Support (12%)
• Define the AWS Cloud as an on-demand, pay-as-you-go platform for IT resources.
• Recognize the global infrastructure elements: Regions, AZs, and edge locations.
• Identify major service categories: compute, storage, database, networking, and security.
• Explain basic cloud characteristics: scalability, elasticity, and pay-as-you-go.

Next study move (recommended):

• Create a one-page summary with:
• Exam numbers (65 / 90 / 700 / 100–1000)
• Domain names and percentages
• 1–2 example services under each major category (compute, storage, database, networking, security)

You’ll refer back to this summary throughout your CLF-C02 preparation.