Study guide · Domain 1 · 24% of the exam
Cloud Concepts: the AWS Certified Cloud Practitioner objectives in plain English
Domain 1 is the starting point for this exam. It introduces the cloud built by Amazon Web Services, known as AWS, and explains what the AWS Cloud is, why organizations use it, how good design is judged, how a move to the cloud is planned, and how cloud costs differ from owning hardware. The ideas are broad rather than technical. You are not asked to configure a service or write code. You are asked to recognize the vocabulary, match a business need to the right cloud idea, and spot the answer that describes a real benefit instead of a promise the cloud does not make. At 24 percent of the exam, this domain carries real weight, and its terms return inside questions about security, billing, and support, so time spent here helps across the whole test.
What the objectives cover
1.1 Define the benefits of the AWS Cloud
The value proposition is the plain case for using the cloud at all. Instead of buying servers in advance, an organization trades a large upfront cost for a variable expense and pays only for the resources it actually uses, and it can stop guessing capacity because it no longer has to forecast its busiest day years ahead and buy hardware for that day. Economies of scale sit behind the pricing. Because AWS buys hardware, power, and network capacity for a huge combined customer base, its costs per unit fall, and those savings are passed on as lower prices than a single company could usually get on its own. Global infrastructure means applications can be placed close to users around the world in minutes, rather than after a long build out of a new site, which helps with low delay and with copies of data in more than one place. High availability means a workload stays reachable when a component fails, because it is designed across separate locations with no single point of failure. Agility is the speed benefit: teams can provision resources in minutes, test an idea, and shut it down if it fails, instead of waiting weeks for hardware to arrive. Scalability and elasticity sound alike but are tested as different ideas. Scalability is the ability of a system to handle growth, by using a larger resource or by adding more resources. Elasticity is the automatic matching of resources to demand as it changes, growing when load rises and shrinking when load falls, so you neither run short nor pay for idle capacity.
1.2 Identify design principles of the AWS Cloud
Design principles are summed up in the AWS Well-Architected Framework, a set of six pillars used to judge whether a workload is built well. Operational excellence is about running and monitoring systems and improving them over time, using small and reversible changes, learning from failures, and automating routine procedures so they run the same way every time. Security is about protecting information and systems, with strong identity controls, least privilege access, traceability of actions, and security applied at every layer rather than added at the end. Reliability is about a workload doing its job correctly and consistently, recovering from failures automatically where possible, and testing recovery, so that one failure does not become an outage for every user. Performance efficiency is about using the right resources for the task, reviewing new service options as they appear, and matching resource type and size to the actual work instead of buying the biggest option by habit. Cost optimization is about avoiding cost that adds no value, shutting down unused resources, and choosing the pricing model that fits the pattern of use. Sustainability is about understanding the environmental impact of a workload and reducing it, by using resources efficiently and designing so that the same result takes less energy and less hardware. Exam questions rarely ask you to recite the list. They describe a goal, such as cutting waste or recovering from failure, and ask which pillar it belongs to.
1.3 Understand the benefits of and strategies for migration to the AWS Cloud
Migration planning is guided by the AWS Cloud Adoption Framework, usually shortened to CAF, which looks at a move from six perspectives. Business focuses on making sure the move supports the goals the organization wants. People covers roles, skills, and training, because staff habits have to change along with the technology. Governance covers how the organization directs and measures the move, including risk and compliance. Platform covers the architecture and engineering standards the new environment will follow. Security covers the controls that protect the new environment from the start. Operations covers how the environment will be run and supported day to day. The migration strategies describe what happens to each application. Rehost, often called lift and shift, moves an application as it is, with little or no change, which is fast and suits large moves on a deadline. Replatform makes a few cloud changes during the move, such as swapping a self managed database for a managed one, without rebuilding the application itself. Other strategies you may meet at name level include repurchase, which replaces an application with a different product, refactor, which rebuilds it for the cloud, retain, which keeps it where it is for now, and retire, which shuts it down. Tools are tested at recognition level only. AWS Migration Hub tracks migration progress in one place, AWS Application Discovery Service gathers facts about on premises servers, AWS Application Migration Service moves servers, AWS Database Migration Service moves databases, and AWS DataSync and the AWS Snow family move large amounts of data.
1.4 Understand concepts of cloud economics
Cloud economics starts with the difference between fixed costs and variable costs. A fixed cost stays the same regardless of use, such as a data center lease. A variable cost changes with use, such as compute billed by the hour or storage billed by the amount stored. That connects directly to capital expenditure and operating expenditure. CapEx is money spent upfront to buy assets you own, such as servers, and it is paid before the value arrives. OpEx is ongoing money spent on services as you use them, which is the normal cloud pattern, with no large purchase at the start. Right sizing is the habit of checking that each resource matches the workload it runs, and shrinking or changing resources that are larger than the work requires, because oversized resources bill at the higher size whether the extra capacity is used or not. Licensing strategies matter because software licenses can cost as much as the hardware they run on. Some licenses are included in the price of a service, which keeps things simple. Bring your own license, or BYOL, lets an organization use licenses it already owns in the cloud, subject to the license terms, which can lower cost when those licenses would otherwise sit unused. Exam questions here usually give a short money story, such as a purchase or an idle oversized server, and ask you to name the cost idea it shows.
Worked example
A small company replaces buying its own servers with AWS services and pays only for the compute time it actually uses each month. Which value proposition does this best illustrate?
A core value of the AWS Cloud is paying for resources as they are consumed instead of investing heavily in hardware before the resources are needed.
Why the other options are wrong
- AIt must forecast capacity five years in advance: Forecasting far ahead is an on-premises planning burden that the cloud helps reduce, not a benefit described here.
- CIt removes the need to protect customer data: Customers still share responsibility for protecting their data when they use the cloud.
- DIt guarantees that monthly bills will never change: Variable bills change with usage, so a bill that never changes is not guaranteed.
Acronyms and terms in this domain
| Term | What it means |
|---|---|
| CAF | Cloud Adoption Framework, the AWS guidance that views a cloud move through six perspectives |
| CapEx | Capital Expenditure, upfront spending to buy and own physical infrastructure |
| OpEx | Operating Expenditure, ongoing spending for services that you pay for as you use them |
| SLA | Service Level Agreement, a formal commitment for uptime and connectivity for a service |
| Region | A geographic area with multiple isolated locations where AWS resources can be run |
| AZ | Availability Zone, one or more data centers with separate power, networking, and connectivity inside a Region |
| Elasticity | The automatic growing and shrinking of resources to match demand as it changes |
| Agility | The speed at which teams can provision resources, test ideas, and change direction |
| Well-Architected | The AWS framework of six pillars used to judge whether a workload is designed well |
| BYOL | Bring Your Own License, using licenses you already own in the cloud under their terms |
Where the help desk meets this domain
You already explain cloud concepts to users in ordinary words, even if the ticket never uses the exam labels. When a user asks why a shared drive is reachable from home without anyone building a new office, the answer is agility and global infrastructure in daily form: standard resources are ready on demand, in the place the user needs them. When you tell a caller that a mailbox still opens while a data center has a fault, you are describing high availability and design across separate locations. When you help a team that only needs extra accounts and storage for a busy season, then removes them afterward, you have watched elasticity and variable cost from the support side. The desk also hears the migration perspectives without the CAF names. Business is the manager asking what the move is for. People is the training session before a change. Operations is your queue after go live, when monitoring and runbooks decide whether the new system feels stable to users.
The economics in this domain also show up in conversations you already have. A request to replace an aging server usually starts with a large quote, a purchase approval, and a long wait, which is CapEx thinking: pay first, own the box, and carry the risk if it is the wrong size. A request to turn on a cloud service usually starts the same day and lands as a monthly line item that grows or shrinks with use, which is OpEx thinking. Help desk staff often spot right sizing problems before anyone else, because you see the software nobody opens and the test systems that were never shut down. Flagging those is cost optimization in practice. License questions follow the same pattern. Whether an existing license can move to a new setup is a small version of the licensing choices in this domain, including bring your own license. If you can translate a ticket into who pays, when they pay, and what they actually use, you can answer many Domain 1 questions.
Traps to watch for
The most tested trap in this domain is elasticity versus scalability, because the two words are often used as if they were the same. Scalability is the ability to handle growth. A system that can serve more users after resources are added is scalable, even if a person adds those resources by hand during a planned change. Elasticity adds timing and automation: resources grow and shrink on their own as demand changes, and capacity that is no longer needed is given back. A stem that says a team manually doubled its servers before a launch is describing scalability, not elasticity. A stem that says capacity rose during a spike and fell overnight without staff action is describing elasticity. Agility is a third nearby word and a common wrong choice. It is about how fast a team can get resources and try something new, not about how much load a system can carry. Read the stem for the problem being solved, growth, automatic adjustment, or speed of starting, and match the word to that problem.
The second trap set is money timing. CapEx and OpEx questions hide the answer in when the money is spent and whether an asset was bought. A large upfront purchase of hardware the company will own points to CapEx, even if the vendor offers a discount or the hardware is very modern. Pay as you go billing with no upfront purchase points to OpEx, even if the monthly total is large. A related trap turns a variable bill into a fixed promise. Variable pricing means the bill follows usage, so any choice that says costs will stay flat should be read with suspicion. Right sizing traps work in reverse: keeping an oversized resource because it might be useful one day conflicts with cost optimization, which favors matching the resource to the work now. The same careful reading helps with the pillars and the CAF perspectives, where the wrong choices are usually correct definitions of a neighboring idea. Name the goal in the stem first, then pick the term that matches it.
Now try it. The 5 free sample questions for this domain are in practice mode, with full explanations.
Practice Domain 1 questions