Overview
Domain 1 covers the concepts that underpin the whole certification. It has four task statements. Defining the benefits of the cloud covers agility, elasticity, scalability, global reach and the value proposition of moving from capital expense to operating expense. Identifying design principles covers the six pillars of the AWS Well-Architected Framework. Understanding migration covers strategies such as the common migration approaches and the AWS Cloud Adoption Framework. Understanding cloud economics covers how pay-as-you-go pricing, economies of scale and reduced total cost of ownership change the financial model.
At 24%, this is a core conceptual domain. It is not about configuring services but about understanding why the cloud is valuable and how its economics and frameworks work. These ideas recur throughout the exam, since security, services and billing all build on the cloud value proposition and the Well-Architected pillars introduced here.
How it's tested
CLF-C02 questions are recognition-level, asking which concept, benefit or framework fits a described situation. In this domain they describe a business goal or cloud characteristic and ask which benefit, Well-Architected pillar, migration strategy or economic concept applies, favoring clear definitions over configuration detail.
-
Name the benefit
A business goal is described, and you choose the cloud benefit it illustrates, such as elasticity, agility or global reach.
-
Match the pillar
A design concern is described, and you identify the Well-Architected pillar it belongs to.
-
Identify the economic concept
A cost or financial situation is described, and you choose the economic idea, such as pay-as-you-go or reduced total cost of ownership.
A company wants to handle unpredictable traffic without buying servers for peak load. Buying for peak is the old capital-expense model. The cloud benefit is elasticity: automatically adding and removing capacity to match demand, so the company pays only for what it uses. Recognizing that the scenario describes matching capacity to demand points to elasticity rather than simply scalability.
Task statements 4
Official task statements from the Amazon Web Services outline, in outline order.
1.1 Define the benefits of the AWS CloudAgility, elasticity, scalability, global reach and the cloud value proposition.
- What it means
- This covers the core benefits of the AWS Cloud: agility to move faster, elasticity to match capacity to demand, scalability to grow, high availability and global reach, and the value proposition of shifting from capital expense to operating expense and paying only for what you use.
- What to understand
- Elasticity means capacity automatically grows and shrinks with demand, while scalability means the ability to grow. Agility is the speed of provisioning and experimentation the cloud enables. Global reach means deploying close to users worldwide. The value proposition centers on not owning or over-provisioning hardware.
- How it shows up
- A business goal is described, and you must name the cloud benefit it illustrates, often elasticity or agility.
- Common confusion
- Confusing elasticity with scalability; elasticity automatically matches capacity to demand, while scalability is the ability to grow capacity.
1.2 Identify design principles of the AWS CloudThe six pillars of the AWS Well-Architected Framework.
- What it means
- This covers the AWS Well-Architected Framework and its six pillars: operational excellence, security, reliability, performance efficiency, cost optimization and sustainability. Each pillar represents a set of design principles for building well-architected cloud solutions.
- What to understand
- The six pillars are the lens AWS uses to judge a good design. Operational excellence covers running and improving systems, security covers protecting data and systems, reliability covers recovering from failure, performance efficiency covers using resources well, cost optimization covers avoiding unnecessary spend, and sustainability covers reducing environmental impact.
- How it shows up
- A design concern is described, and you must identify the Well-Architected pillar it belongs to.
- Common confusion
- Confusing reliability with performance efficiency; reliability is about recovering from failure, while performance efficiency is about using resources effectively.
1.3 Understand the benefits of and strategies for migration to the AWS CloudMigration strategies and the AWS Cloud Adoption Framework.
- What it means
- This covers why organizations migrate to AWS, common migration strategies such as rehost, replatform, repurchase, refactor, retire and retain, the AWS Cloud Adoption Framework and its perspectives, and resources that support the migration journey.
- What to understand
- Migration strategies, often called the migration approaches, describe how to move each workload: rehosting lifts and shifts it, replatforming makes small optimizations, refactoring rebuilds it for the cloud, and so on. The Cloud Adoption Framework organizes an organization's readiness across business and technical perspectives.
- How it shows up
- A migration situation is described, and you must choose the migration strategy or recognize the Cloud Adoption Framework.
- Common confusion
- Confusing rehost with refactor; rehosting lifts and shifts with minimal change, while refactoring rebuilds the application for the cloud.
1.4 Understand concepts of cloud economicsPay-as-you-go, economies of scale and total cost of ownership.
- What it means
- This covers the economics of the cloud: pay-as-you-go pricing, economies of scale that lower prices over time, reduced total cost of ownership, the shift from fixed capital expense to variable operating expense, and the cost savings from managed services and automation.
- What to understand
- Pay-as-you-go means paying only for the resources consumed, with no upfront hardware purchase. Economies of scale mean AWS's size lowers unit costs, passed on as price reductions. Total cost of ownership comparisons show cloud often costs less than owning and operating data centers when all costs are counted.
- How it shows up
- A cost or financial situation is described, and you must identify the economic concept, such as pay-as-you-go or reduced total cost of ownership.
- Common confusion
- Confusing capital expense with operating expense; the cloud shifts spending from upfront capital purchases to ongoing operating costs.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Elasticity vs. scalability
Elasticity automatically matches capacity to demand; scalability is the ability to grow.
- Remember
- Elasticity is automatic and bidirectional.
- Tested as
- Benefit identification questions.
- Trap
- Using the two terms interchangeably.
-
Agility
The speed to provision resources and experiment in the cloud.
- Remember
- It is about moving faster, not just capacity.
- Tested as
- Benefit questions.
- Trap
- Confusing it with elasticity.
-
Capital vs. operating expense
The cloud shifts spending from upfront hardware (capital) to ongoing usage (operating).
- Remember
- No large upfront purchase is needed.
- Tested as
- Economics questions.
- Trap
- Confusing the two expense models.
-
Six Well-Architected pillars
Operational excellence, security, reliability, performance efficiency, cost optimization and sustainability.
- Remember
- Sustainability is the sixth pillar added in recent guidance.
- Tested as
- Design principle questions.
- Trap
- Forgetting sustainability as a pillar.
-
Reliability vs. performance efficiency
Reliability recovers from failure; performance efficiency uses resources effectively.
- Remember
- They address different design goals.
- Tested as
- Pillar questions.
- Trap
- Confusing the two pillars.
-
Migration strategies
Rehost, replatform, repurchase, refactor, retire and retain.
- Remember
- Rehost is lift and shift; refactor rebuilds for the cloud.
- Tested as
- Migration questions.
- Trap
- Confusing rehost with refactor.
-
AWS Cloud Adoption Framework
A framework organizing cloud readiness across business and technical perspectives.
- Remember
- It guides organizational adoption, not a single workload.
- Tested as
- Migration questions.
- Trap
- Confusing it with the Well-Architected Framework.
-
Pay-as-you-go
Paying only for the resources consumed, with no upfront commitment.
- Remember
- It avoids over-provisioning and upfront cost.
- Tested as
- Economics questions.
- Trap
- Confusing it with commitment-based pricing.
-
Economies of scale
AWS's scale lowers unit costs, passed on as price reductions.
- Remember
- Prices tend to fall over time.
- Tested as
- Economics questions.
- Trap
- Attributing price drops to the customer's own scale.
-
Total cost of ownership
The full cost of owning and operating infrastructure, compared with cloud.
- Remember
- Cloud often lowers it by removing hardware and operations overhead.
- Tested as
- Economics questions.
- Trap
- Comparing only server price, not full ownership cost.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Elasticity vs. scalability vs. agility
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Elasticity | Capacity automatically matches demand | Automatic and bidirectional | Confusing it with scalability |
| Scalability | The ability to grow capacity | Growth, not automatic shrinking | Treating it as automatic |
| Agility | Speed to provision and experiment | About speed, not capacity | Confusing it with elasticity |
Six Well-Architected pillars
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Operational excellence | Running and improving systems | Operations focus | Confusing it with reliability |
| Security | Protecting data and systems | Protection focus | Overlapping it with reliability |
| Reliability | Recovering from failure | Recovery focus | Confusing it with performance |
| Performance, cost, sustainability | Efficient resources, low cost, low impact | Efficiency and impact focus | Forgetting sustainability |
Migration strategies
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Rehost | Lift and shift with minimal change | Fastest, least optimized | Confusing it with refactor |
| Replatform | Small optimizations during migration | Some improvement, limited change | Confusing it with refactor |
| Refactor | Rebuild the application for the cloud | Most change and benefit | Confusing it with rehost |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Elasticity is scalability
- What candidates pick
- Call automatic capacity matching scalability.
- Why it looks right
- Both involve capacity.
- Why it's wrong
- Elasticity automatically matches capacity to demand in both directions; scalability is the ability to grow.
Clue to watch for The scenario describes capacity automatically rising and falling with demand.
-
Capex still applies
- What candidates pick
- Describe cloud spending as an upfront capital purchase.
- Why it looks right
- Hardware was traditionally bought upfront.
- Why it's wrong
- The cloud shifts spending to operating expense, paying for usage without buying hardware.
Clue to watch for The benefit is avoiding upfront hardware purchases.
-
Five pillars
- What candidates pick
- List only five Well-Architected pillars, omitting sustainability.
- Why it looks right
- Older material listed five.
- Why it's wrong
- The framework now has six pillars, including sustainability.
Clue to watch for The question asks for all the pillars.
-
Rehost is refactor
- What candidates pick
- Call rebuilding an application for the cloud a rehost.
- Why it looks right
- Both are migration.
- Why it's wrong
- Rehost lifts and shifts with minimal change; refactor rebuilds the application.
Clue to watch for The migration involves significant redesign versus a simple move.
-
CAF is Well-Architected
- What candidates pick
- Use the Cloud Adoption Framework to judge a single workload's design.
- Why it looks right
- Both are AWS frameworks.
- Why it's wrong
- The Cloud Adoption Framework guides organizational readiness; the Well-Architected Framework judges workload design.
Clue to watch for The scenario is about organizational adoption versus workload design.
-
Server price is TCO
- What candidates pick
- Compare cloud and on-premises on server price alone.
- Why it looks right
- Server price is the obvious cost.
- Why it's wrong
- Total cost of ownership includes power, cooling, staff and operations, which cloud often reduces.
Clue to watch for The comparison asks about overall cost of ownership.
Answer framework
For any Domain 1 concept scenario, use these steps to find the answer CLF-C02 expects.
- Identify whether the scenario is about a cloud benefit, a design principle, migration or economics, since each has its own vocabulary.
- For benefits, match the business goal to the precise term, distinguishing elasticity, scalability and agility.
- For design, map the concern to one of the six Well-Architected pillars, remembering sustainability is included.
- For migration, choose the strategy that fits the described change, or recognize the Cloud Adoption Framework for organizational readiness.
- For economics, identify the concept, such as pay-as-you-go, economies of scale or reduced total cost of ownership, including all ownership costs, choosing the term that most precisely matches the scenario.
Practice question
Want more like this? The AWS CCP practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Treat this domain as learning the language of the cloud, since every other domain uses it. Start with the benefits, and nail the elasticity-versus-scalability distinction, which the exam tests repeatedly. Connect each benefit to a business reason, because questions are framed as business goals.
Next, memorize the six Well-Architected pillars and a one-line meaning for each, remembering sustainability is the sixth. Then learn the migration strategies by the amount of change each involves, and understand the Cloud Adoption Framework as organizational readiness rather than workload design.
Finally, study cloud economics: pay-as-you-go, economies of scale and total cost of ownership, and the capital-to-operating-expense shift. CLF-C02 is an awareness exam, so clear definitions and short practice questions are more valuable than hands-on labs here. Afterwards, move to Domain 2, security and compliance, the highest-weighted domain. This is an awareness exam, so flashcards and timed practice questions are more valuable than hands-on labs, and reviewing missed questions by domain shows where to focus next.
FAQ
How much of CLF-C02 is Domain 1?
Cloud Concepts is 24% of the scored content, a core conceptual domain whose ideas recur across the exam.
What is the difference between elasticity and scalability?
Elasticity automatically matches capacity to demand in both directions. Scalability is the ability to grow capacity. Elasticity is automatic and bidirectional.
How many Well-Architected pillars are there?
Six: operational excellence, security, reliability, performance efficiency, cost optimization and sustainability.
What are the common migration strategies?
Rehost (lift and shift), replatform (small optimizations), repurchase, refactor (rebuild for the cloud), retire and retain.
What is the AWS Cloud Adoption Framework?
A framework that organizes an organization's cloud readiness across business and technical perspectives, guiding adoption rather than judging a single workload's design.
What is pay-as-you-go pricing?
Paying only for the resources you consume, with no upfront hardware purchase, which avoids over-provisioning and large capital expense.
How does Domain 1 connect to the rest of the exam?
It establishes the cloud value, frameworks and economics that the security, services and billing domains build on.
Other Cloud Computing certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- CompTIA Cloud+ Same subject: Domain 1: Cloud Architecture (23%)
- Microsoft Certified: Azure Fundamentals Same subject: Domain 1: Describe cloud concepts (25–30%)
- AWS Certified Solutions Architect - Associate Study guide
- AWS Certified SysOps Administrator - Associate Study guide
- AWS Certified Solutions Architect - Professional Study guide
- Microsoft 365 Fundamentals Study guide
- Azure Developer Associate Study guide
- Google Cloud Associate Cloud Engineer Study guide
- AWS Certified Developer - Associate Study guide
- HashiCorp Certified: Terraform Associate Study guide
- Azure Administrator Associate Study guide
- Azure Solutions Architect Expert Study guide
Test your Domain 1 knowledge
You have covered cloud benefits, the Well-Architected pillars, migration strategies and cloud economics. Test whether you can name the right concept for a business scenario under exam conditions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the AWS CCP AI tutor Get any concept explained your way