The AWS Certified Cloud Practitioner (CLF-C02) exam has four domains, and Cloud Concepts is where the whole thing begins — weighted at 24%, nearly a quarter of your score. It’s the domain most candidates underestimate because it feels “soft”: no services to memorize, no CLI commands. But that’s exactly why it trips people up. The questions are about why the cloud exists, how it changes the economics of running IT, and what principles make a cloud workload well-built — and the wording is precise.
This guide is a structured tour of the Cloud Concepts domain the way AWS frames it: the cloud value proposition, cloud economics, the AWS Well-Architected Framework, and cloud migration and design principles. For each area you get plain-English explanations and the exact distinctions the exam rewards. If you want the exam logistics and full blueprint first, read the AWS Cloud Practitioner exam guide for 2026 and the domains breakdown.
What the Cloud Concepts Domain Covers
AWS breaks the domain into four task statements:
| Task statement | What it tests |
|---|---|
| Define the benefits of the AWS Cloud | The six advantages, the value proposition |
| Identify design principles of the AWS Cloud | The Well-Architected Framework and its pillars |
| Understand the benefits of and strategies for migration | Migration drivers, the Cloud Adoption Framework, migration strategies |
| Understand cloud economics | CapEx vs. OpEx, TCO, right-sizing, managed-service savings |
None of this requires you to build anything. It requires you to reason about trade-offs and recognize AWS’s own vocabulary. Let’s take each in turn.
The Cloud Value Proposition: Six Advantages of Cloud Computing
AWS defines six advantages of cloud computing, and the exam quotes them almost verbatim. Memorize these — questions frequently give you a scenario and ask which advantage it illustrates.
| Advantage | Plain-English meaning |
|---|---|
| Trade fixed expense for variable expense | Stop paying up front for data centers you might use; pay only for what you consume |
| Benefit from massive economies of scale | AWS’s aggregated usage across millions of customers drives lower pay-as-you-go pricing |
| Stop guessing capacity | Scale up or down on demand instead of over- or under-provisioning hardware |
| Increase speed and agility | Provision resources in minutes, so experiments cost less time and money |
| Stop spending money running and maintaining data centers | Focus on customers and applications, not racking servers |
| Go global in minutes | Deploy to Regions around the world with a few clicks for low latency |
Exam tip: Watch for scenario phrasing. “A startup wants to launch in Europe and Asia quickly with low latency” → Go global in minutes. “A retailer wants to handle Black Friday without buying servers that sit idle the rest of the year” → Stop guessing capacity (and trade fixed for variable expense). The exam tests whether you can map the story to AWS’s exact term.
The three cloud deployment models
You also need to recognize the deployment models:
- Cloud — everything runs in the cloud; the modern default for new applications.
- Hybrid — a mix of cloud and on-premises, connected (e.g. via AWS Direct Connect or VPN). Common for regulated data or gradual migration.
- On-premises (private cloud) — infrastructure run in your own data center, sometimes using cloud-like tooling.
The three cloud service models
And the service models, which define who manages what:
| Model | You manage | AWS manages | Example |
|---|---|---|---|
| IaaS (Infrastructure as a Service) | OS, apps, data | Hardware, virtualization | Amazon EC2 |
| PaaS (Platform as a Service) | Apps, data | OS, runtime, scaling | AWS Elastic Beanstalk |
| SaaS (Software as a Service) | Just your usage/config | Everything | Amazon WorkMail |
This “who manages what” idea is the same mental model behind the shared responsibility model, which lives in the Security domain — the more managed the service, the more AWS handles.
Cloud Economics: CapEx, OpEx, and Total Cost of Ownership
Cloud economics is the “money” half of the domain, and it hinges on one shift the exam returns to again and again: capital expenditure (CapEx) to operational expenditure (OpEx).
CapEx vs. OpEx
| CapEx (traditional data center) | OpEx (cloud) | |
|---|---|---|
| When you pay | Large up-front purchase | As you consume |
| What you buy | Servers, storage, facilities | A metered service |
| Risk | Over- or under-provisioning | Pay only for actual use |
| Accounting | Depreciated over years | Expensed as incurred |
The cloud converts big, risky, up-front hardware purchases (CapEx) into flexible, usage-based spending (OpEx). That’s the single most-tested economic concept in the domain.
Total Cost of Ownership (TCO)
TCO is the full cost of running a workload — not just the hardware, but power, cooling, data-center space, networking, and the staff to run it all. The cloud’s TCO argument is that AWS absorbs those hidden costs into a single metered price. The exam expects you to know that comparing cloud to on-premises means comparing total cost, not just server price.
Where cloud saves money
- Right-sizing — matching instance types and sizes to actual workload demand instead of over-buying “just in case.”
- Elasticity and automatic scaling — paying for capacity only while you need it, then releasing it.
- Managed services — offloading operational work (patching, backups, replication) to AWS reduces staffing and error-prone manual toil. A managed database like Amazon RDS costs more per hour than raw EC2 but often less in total once you count the DBA time it saves.
- Consumption-based pricing — services like AWS Lambda charge only for actual execution, so idle time is free.
The concrete pricing models (On-Demand, Reserved, Spot, Savings Plans) and the cost-management tooling (Cost Explorer, Budgets, Cost and Usage Report) belong to the Billing domain — the pricing, billing and cost management guide covers those in detail.
Design Principles: The AWS Well-Architected Framework
The Well-Architected Framework is AWS’s set of best practices for building in the cloud, organized into six pillars. The CLF-C02 expects you to name each pillar and match a scenario to the right one.
| Pillar | Core question it answers |
|---|---|
| Operational Excellence | Can we run and monitor systems, and continuously improve processes? |
| Security | Are we protecting data, systems, and assets? |
| Reliability | Can the workload recover from failures and meet demand? |
| Performance Efficiency | Are we using compute resources efficiently as demand changes? |
| Cost Optimization | Are we avoiding unnecessary costs? |
| Sustainability | Are we minimizing the environmental impact of our workloads? |
Exam tip: A memory hook for the pillars is “OSCARS-minus-A” isn’t quite it — instead try the phrase Operations, Security, Reliability, Performance, Cost, Sustainability. Match by keyword: a question about auto-recovery and Multi-AZ → Reliability; choosing the right instance type as load changes → Performance Efficiency; turning off unused resources → Cost Optimization; reducing carbon footprint / choosing efficient Regions → Sustainability (the newest pillar, added in 2021).
Well-Architected design principles
Beyond the pillars, AWS promotes general cloud design principles the exam may reference:
- Design for failure — assume components will fail and build so the system survives it (multiple AZs, health checks, automatic recovery).
- Decouple components — loosely coupled services (via queues like SQS or events via EventBridge) scale and fail independently.
- Implement elasticity — scale automatically with demand rather than provisioning for peak.
- Automate everything — use infrastructure as code (CloudFormation) so environments are repeatable and consistent.
- Think parallel — scale out (more instances) rather than only up (bigger instances).
The AWS Well-Architected Tool (free, in the console) lets you review a workload against these pillars and get improvement recommendations. Knowing the tool exists and what it does is enough for the exam.
Migration Benefits and Strategies
The final task statement covers why and how organizations move to the cloud.
The AWS Cloud Adoption Framework (CAF)
The AWS CAF organizes migration guidance into six perspectives, three business-focused and three technical:
| Perspective | Focus |
|---|---|
| Business | Business case, value realization |
| People | Staffing, skills, org change |
| Governance | Managing and measuring the cloud program |
| Platform | Building the cloud environment |
| Security | Meeting security and compliance objectives |
| Operations | Running and supporting workloads |
You don’t need deep detail — just recognize that the CAF exists to help plan an organization-wide cloud journey and that the perspectives split into business (Business, People, Governance) and technical (Platform, Security, Operations).
The migration strategies (the “R”s)
AWS describes common migration strategies as a set of “R” words. The CLF-C02 focuses on these:
| Strategy | What it means |
|---|---|
| Rehost (“lift and shift”) | Move as-is to the cloud without changes — fastest |
| Replatform (“lift, tinker, and shift”) | Minor optimizations during the move (e.g. move to a managed database) |
| Refactor / Re-architect | Redesign the application to be cloud-native |
| Repurchase | Move to a different product, often SaaS |
| Retain | Keep on-premises for now (not ready to move) |
| Retire | Decommission what’s no longer needed |
Exam tip: Map the scenario to the strategy. “Move a legacy app to EC2 unchanged to hit a data-center exit deadline” → Rehost. “Switch a self-managed database to Amazon RDS during the move” → Replatform. “Rewrite a monolith into microservices on Lambda” → Refactor. “Replace a self-hosted CRM with a SaaS product” → Repurchase.
Migration tools to recognize
You only need recognition-level awareness of the tools:
- AWS Migration Hub — a single place to track migration progress across tools.
- AWS Application Migration Service (MGN) — automated lift-and-shift of servers.
- AWS Database Migration Service (DMS) — migrate databases with minimal downtime.
- AWS Snow Family (Snowball, Snowcone) — physical devices to move large data volumes when the network isn’t practical.
Cloud Concepts Master Cheat Sheet
| Concept | The one thing to remember |
|---|---|
| Six advantages of cloud | Variable expense, economies of scale, stop guessing capacity, speed/agility, no data centers, go global fast |
| Deployment models | Cloud, Hybrid, On-premises |
| Service models | IaaS (EC2), PaaS (Beanstalk), SaaS (WorkMail) |
| CapEx → OpEx | Up-front hardware becomes pay-as-you-go |
| TCO | Total cost includes power, cooling, staff — not just servers |
| Well-Architected pillars | Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability |
| CAF perspectives | Business, People, Governance / Platform, Security, Operations |
| Migration “R”s | Rehost, Replatform, Refactor, Repurchase, Retain, Retire |
Practice with Realistic Exam Questions
The Cloud Concepts domain is won by recognizing AWS’s exact vocabulary under a scenario. The exam won’t ask you to calculate a TCO or design an architecture — it’ll ask which of the six advantages a sentence describes, which Well-Architected pillar a requirement maps to, or which migration “R” fits a story. That recall is built by answering scenario questions until “trade fixed expense for variable expense” and “design for failure” surface automatically.
Sailor.sh’s AWS Certified Cloud Practitioner (CLF-C02) Mock Exam Bundle gives you full-length, exam-style practice exams with the same scenario phrasing and concept-matching style you’ll face on test day, plus explanations that reinforce why an answer is correct. Combine the practice exams with a structured Cloud Practitioner study plan and warm up with the free Cloud Practitioner practice questions. If you’re brand new to AWS, start with the Cloud Practitioner for beginners guide, and once you’ve mastered concepts, move on to the core services tour for the biggest domain.
Frequently Asked Questions
What are the six advantages of cloud computing on the AWS exam?
They are: trade fixed expense for variable expense, benefit from massive economies of scale, stop guessing capacity, increase speed and agility, stop spending money running and maintaining data centers, and go global in minutes. The CLF-C02 quotes these almost word-for-word and asks you to match a scenario to the right one.
What is the difference between CapEx and OpEx in cloud computing?
CapEx (capital expenditure) is a large up-front purchase of hardware and facilities, depreciated over years. OpEx (operational expenditure) is metered, pay-as-you-go spending on services as you consume them. The core value proposition of the cloud is converting CapEx into OpEx, so you pay only for what you use instead of over-buying capacity in advance.
What are the six pillars of the AWS Well-Architected Framework?
Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. Sustainability is the newest pillar. On the exam you’ll match a requirement — auto-recovery, right instance selection, cost avoidance, carbon reduction — to the relevant pillar.
What is the difference between rehosting and replatforming?
Rehosting (“lift and shift”) moves an application to the cloud unchanged — the fastest strategy. Replatforming (“lift, tinker, and shift”) makes small optimizations during the move, such as switching a self-managed database to Amazon RDS, without redesigning the application. Both are common CLF-C02 scenario answers.
What is Total Cost of Ownership (TCO) in the cloud?
TCO is the complete cost of running a workload — including hardware, power, cooling, data-center space, networking, and staff — not just the price of servers. The cloud’s economic argument is that AWS folds those hidden operational costs into a single metered price, often lowering total cost even when the per-hour rate looks higher.
How much of the Cloud Practitioner exam is the Cloud Concepts domain?
Cloud Concepts is 24% of the CLF-C02. The other domains are Security and Compliance (30%), Cloud Technology and Services (34%), and Billing, Pricing and Support (12%). See the full domains breakdown for how to allocate your study time.
Conclusion
Cloud Concepts is the foundation the rest of the Cloud Practitioner exam is built on. You don’t need to configure anything — you need to speak AWS’s language fluently: the six advantages of the cloud, the CapEx-to-OpEx shift and what TCO really includes, the six Well-Architected pillars, and the migration strategies from rehost to retire. Learn the vocabulary, learn the scenario-to-term mappings in this guide, and nearly a quarter of the exam becomes quick, confident points.
The fastest way to lock that recall in is repetition under exam conditions. Work through the AWS Cloud Practitioner mock exams, drill the concept-matching questions until AWS’s terminology is automatic, and review every explanation. Pair that with the Cloud Practitioner study plan, and you’ll walk in fluent on the domain that frames everything else. For the full roadmap, start with the AWS Cloud Practitioner exam guide for 2026.