AWS Certified Cloud Practitioner (CLF-C02) #2 Domain 1-1 Cloud Concepts — Value, Economics, and the Cloud Adoption Framework

#1 locked in the exam structure and study strategy. Now into the first domain.

Domain 1 (Cloud Concepts) accounts for 24% of the exam and asks how the cloud changes the way a business operates. Less about technical depth, more about clear vocabulary and concepts — that’s where the points are decided. This post covers the first half of the domain — the cloud’s value propositions and economic model, the Cloud Adoption Framework, and the global infrastructure — and the second half on Well-Architected lands in #3.

The six value propositions of the cloud #

These are the Six Advantages of Cloud Computing that AWS repeats across its official materials. The exam tends to hand you a scenario and ask “which advantage of the cloud does this scenario show?”

You don’t need to memorize the order of these six. But because the answer choices will list five or six similar-looking options, you do need one or two pieces of core vocabulary per item locked in your head.

CapEx vs. OpEx #

The most frequently tested comparison concept on CLF-C02.

The cloud is described as the model that converts CapEx into OpEx. The “buy a server and depreciate it over five years” approval structure turns into “we ran EC2 for 200 hours this month, here’s the bill”. On the exam, “Convert capital expenses to variable expenses” frequently appears as the correct answer.

Economies of scale — AWS’s real weapon #

Economies of scale is the ability to buy the same resources for less. AWS is one of the world’s largest buyers of servers, disks, and network gear, so it acquires resources at a unit cost far below what a single company can achieve by building its own data center. Part of that cost saving is then passed on to customer pricing.

Why this matters — the exam sometimes asks “why has AWS been able to cut prices year after year?” The answer is economies of scale. AWS has announced more than 70 price reductions since launch in 2006, and the rationale has always been framed as economies of scale.

Cloud deployment models #

Even within the cloud, deployment splits into three models depending on where the resources sit.

AWS offers two key tools for hybrid: AWS Outposts (AWS hardware installed inside the customer’s data center) and AWS Storage Gateway (on-prem ↔ S3 bridge). The exam’s most common shape is “keep the existing data center but move some workloads to the cloud — which deployment model?” → Hybrid.

The Private Cloud trap #

“Private Cloud = better security” is one of the exam writers’ favorite traps. Security is a function of correct configuration and operation, not of the deployment model. AWS holds certifications like ISO 27001, SOC, and FedRAMP, and its verified security posture is often higher than that of a typical company’s in-house data center. On the exam, any answer that reads “Private Cloud is the answer because it’s more secure” is almost always a trap.

The three service models (IaaS / PaaS / SaaS) #

Service models classify how much the user is responsible for.

Pair these three models with the #4 Shared Responsibility Model when you commit them to memory. The more IaaS, the more user responsibility; the more SaaS, the more AWS responsibility.

AWS Cloud Adoption Framework (CAF) #

The Cloud Adoption Framework (CAF) is AWS’s official guidance on what a company needs to check when moving to the cloud. It splits into six perspectives, and the exam asks which department’s responsibility each perspective maps to.

A grouping that helps with memorization: the first three (Business, People, Governance) are the business perspectives, and the last three (Platform, Security, Operations) are the technical perspectives.

How CAF shows up on the exam #

“Company A is planning training for employees on new skills as part of its cloud migration — which CAF perspective does this match?” The answer is People.

“Company A wants to monitor resource usage in its cloud environment and track costs — which perspective?” The answer is Governance (or Operations when Governance isn’t in the choices).

The core of CAF questions is matching the perspective name to its area of responsibility. The details live in the official guide, but at the exam level the table above is enough.

AWS Global Infrastructure #

The content from Basics #1 gets converted into certification vocabulary.

Recurring question patterns #

1) Region selection criteria — you choose from “legal requirements / latency / cost / service availability”. The most common correct set is (1) compliance (2) latency (3) cost (4) service availability.

2) The meaning of an AZ — “what’s the blast radius when one AZ fails?” Answer: only resources in that AZ. Other AZs stay up.

3) The use of Edge Locations — “I want to deliver static content fast to users worldwide?” Answer: CloudFront (caches via Edge Locations).

4) The use of Outposts — “I need to keep data in my on-prem data center for data sovereignty but still run it with AWS APIs” → AWS Outposts.

Common motivations for cloud migration #

When scenario-style questions show up, they often ask what motivates the company to move to the cloud. Common motivations and the value they map to:

Common traps #

1) “Private Cloud is the most secure” #

Already covered above. Security is a function of operations, not of the deployment model.

2) “Hybrid is Public + On-premises, so it has the strongest security” #

Hybrid is simply a connection between two environments. Its security level depends on how well each side is operated.

3) Limiting CAF’s People to just the HR department #

People isn’t simply HR — it means the cloud capability and cultural change of the entire organization. Training, hiring, and org-change management all fall under People.

4) Confusing Edge Locations with Regions #

Edge Locations are not regions. They are separate, smaller sites used by CloudFront and Route 53. If the exam asks “what’s the data-center unit in AWS?”, the answer is Region (or AZ).

5) Mixing up the names of the six value propositions #

“Elasticity” and “Scalability” are used as subtly different terms on the exam.

• Elasticity — the property of growing and shrinking automatically with demand (think Auto Scaling)
• Scalability — the capability of growing in the first place. Doesn’t say whether it’s automatic or manual

Among the six value propositions, “Stop guessing capacity” maps to Elasticity.

Wrap-up #

What this post locked in:

• Six value propositions of the cloud — CapEx → OpEx / economies of scale / stop guessing capacity / speed and agility / no more running data centers / go global in minutes
• CapEx vs. OpEx — asset purchase vs. usage-based. The most frequent comparison on the exam
• Three deployment models — Cloud / Hybrid / On-premises. Watch out for the “Private Cloud is more secure” trap
• Three service models — IaaS / PaaS / SaaS. Classified by how much the user is responsible for
• Six perspectives of the Cloud Adoption Framework — Business / People / Governance / Platform / Security / Operations
• Global infrastructure — Region / AZ / Edge Location / Local Zone / Wavelength / Outposts
• Traps — the Private Cloud myth, the Hybrid myth, limiting People to HR, confusing Edge Locations with regions, Elasticity vs. Scalability

Next — The six Well-Architected pillars #

Onward to the second half of Domain 1.

#3 Domain 1-2 Cloud Design — The Six Well-Architected Pillars covers the six pillars (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability), each pillar’s design principles, and which pillar decides the right answer on the exam.