AWS Cloud Certificate (Cloud Practitioner) · free sample from the book itself
Designated items in this chapter: DEC 15 · CALC 0 (no designated-calculation family is assigned to Chapter 1; the register's families are housed in Chapters 7, 16, 19, 20, and 21).
Every wrong option is explained. For multiple-response items, every option is accounted for.
1. Answer: A. The guide states the exam validates overall knowledge of the AWS Cloud, independent of a specific job role, at Foundational level.
2. Answer: C. The guide publishes 65 questions: 50 that affect the score and 15 unscored questions that are not identified.
3. Answer: D. The guide names exactly two types: multiple choice (one correct, three distractors) and multiple response (two or more correct out of five or more options).
4. Answer: A. AWS publishes a scaled score of 700 on a 100–1,000 scale. It is not a percentage or a raw count.
5. Answer: C. The guide states candidates do not need a passing score in each section; they need to pass only the overall exam.
6. Answer: A, D. The guide's out-of-scope job tasks include coding and load and performance testing (also designing architecture, troubleshooting, implementation). The other options are abilities the exam validates.
7. Answer: B. AWS states no prerequisites; training is recommended, not mandatory. The six-month figure is a target-candidate description, not a requirement.
8. Answer: D. AWS publishes the Foundational-level fee as 100 USD per attempt; taxes may apply and local-currency prices vary.
9. Answer: A. AWS's FAQs: after a failed attempt, wait 14 calendar days; no limit on attempts; full fee each attempt.
10. Answer: C. AWS publishes a validity of three years, after which recertification is required.
11. Answer: B. AWS publishes delivery through Pearson VUE, testing center or online proctored. No second provider is named in the current sources.
12. Answer: D. CLF-C02's domains are Cloud Concepts; Security and Compliance; Cloud Technology and Services; and Billing, Pricing, and Support. The quoted names belong to the retired predecessor's era.
13. Answer: C. The guide states unanswered questions are scored as incorrect and there is no penalty for guessing, so answering everything can only help.
14. Answer: B, C. Practice results are this book's raw counts by domain, and readiness guidance is the book's own, labeled as such. No conversion to scaled scores exists, and AWS publishes no per-domain minimum or pass rate used here.
15. Answer: B. Versions change on AWS's schedule; the book teaches CLF-C02, names no successor (none is published), and instructs readers to confirm the current code on AWS's page before booking.
This chapter serves the whole book. It names the exam this book teaches — AWS Certified Cloud Practitioner, exam code CLF-C02 — and the document that governs it, the AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, version 1.3 (October 29, 2026). Every exam figure in this chapter comes from that guide, from AWS's Cloud Practitioner certification page, or from AWS's Certification FAQs, checked on October 31, 2026.
Imagine three people opening this book on the same evening. One is a marketing coordinator whose company keeps talking about 'moving to AWS' in meetings she attends, and who wants the words to stop sounding like a foreign language. One is a recent graduate with no information technology job yet, who has been told this certificate is a sensible first step. One runs a small business, pays the company's technology bills, and wants to understand what he is paying for and whether his team is choosing well. The AWS Certified Cloud Practitioner exam was designed, in AWS's own description, for candidates who may not have an information technology background at all, including people in sales, marketing, and product or project management roles. This book takes that description seriously. It assumes nothing, it defines every term before it depends on that term, and it never apologizes for starting at zero, because starting at zero is exactly where AWS says this exam's candidate may start.
Here is the honest map, stated before anything else, because this book's first promise is that it will never oversell the credential it prepares you for. The Cloud Practitioner exam certifies that you understand the AWS Cloud: its services, its security model, its prices, and its vocabulary. AWS's own exam guide lists coding, designing cloud architecture, troubleshooting, implementation, and load and performance testing as out of scope for this exam. This book prepares you for the exam AWS actually gives, and teaches the field honestly around it; it does not make you a cloud engineer, and it never claims the certificate does. A reader who finishes this book should be able to sit in a meeting where cloud decisions are made, follow the argument, ask the question that exposes a weak assumption, read a bill without flinching, and pass a foundational exam that proves that literacy. That is a real and valuable thing. It is not the same thing as being hired to architect a system, and confusing the two would be a disservice to you.
The exam itself has a simple shape, and Chapter 1 puts that shape on the table so that nothing later surprises you. As the CLF-C02 Exam Guide publishes it, the exam contains 65 questions, of which 50 affect your score and 15 are unscored questions that do not affect your score and are not identified while you sit the exam. It uses exactly two question formats, multiple choice and multiple response, and no other format. Your result is reported as a scaled score on a scale of 100 to 1,000, and the minimum passing score is 700. That number, 700, is a scaled score. It is not a percentage, it is not seventy percent of the questions, and this book will never convert it into either, because AWS does not. Scoring is also compensatory, in the guide's own terms: you do not need to achieve a passing score in each section; you need to pass only the overall exam. There is no hidden per-domain minimum waiting to ambush you, and this book's practice scores, which are simple counts of this book's own questions, are readiness information and nothing more.
A word about versions, because version confusion wastes more candidate money than any single topic on this exam. This book teaches CLF-C02, the current exam, built on exam guide version 1.3. An earlier exam, CLF-C01, was retired in September 2023; if you own an older book, a borrowed course, or a folder of notes that names CLF-C01, its domain names and some of its content belong to a retired exam, and Chapter 1 will show you how to recognize that material. As of this book's checking date, AWS has published no successor to CLF-C02, and this book names none, because inventing a future exam code would be inventing a fact. The standing instruction, printed here and repeated at the end of the book, is simple: before you book, confirm the current exam code on AWS's Cloud Practitioner page, because versions change on AWS's schedule, not on this book's. The exam guide itself is a living document that AWS revises between versions, which is one more reason that final check belongs in your routine.
Begin with the plainest possible statement of the idea, because the exam rewards readers who can recognize an idea when it is wearing workplace clothes. A certification is a claim, tested under controlled conditions, that a person knows a defined body of material to a defined standard. Three parts of that sentence matter. Defined body: for this exam, the body is the CLF-C02 Exam Guide, a public document that lists four domains, nineteen task statements, and the services in scope, so the target is not secret and preparation is not guesswork. Tested: you sit a timed, proctored exam of 65 questions, delivered by Pearson VUE at a testing center or online, and no coursework, purchase, or promise substitutes for answering those questions. Standard: AWS publishes the minimum as a scaled score of 700 on a scale of 100 to 1,000, set by AWS professionals, and the result is pass or fail against that single overall standard.
Picture it at work. a job posting asks for 'AWS Certified Cloud Practitioner preferred' for a project coordinator role. The employer is not asking the coordinator to build cloud systems. The employer is buying confidence that the coordinator can follow a cloud project, speak to engineers without an interpreter, and spot a nonsense claim in a vendor proposal. That is the labor-market meaning of this certificate, and it matches the exam's design.
Work the idea through slowly in your mind. First, what problem existed before this idea was available? Second, what exactly does the idea change about that problem? Third, who benefits, and who still carries work or risk afterward? A reader who can answer those three questions about what a certificate actually is owns the concept in the form the exam tests it: as judgment, not as recitation. A reader who can only repeat a one-line definition will struggle the moment a question changes the setting, the industry, or the size of the company, because the definition alone does not say when the idea applies.
A distinction the exam loves to test: a certificate is not a degree, a license, or a guarantee of employment, and this book makes no salary, placement, or outcome claims of any kind. It also is not a participation award: people fail this exam when they prepare by memorizing service names without understanding when each service is used, which is why this book teaches situations first and names second.
One more property of certifications is easy to overlook: they expire, on purpose. AWS publishes that this certification is valid for three years, after which you recertify, because cloud services change constantly and a credential that never expired would slowly stop meaning anything. Chapter 23 teaches the recertification routes in full. For now, hold the simple picture: a certificate is a dated, tested claim about a defined body of knowledge, and its value comes precisely from the fact that it can be lost, must be earned, and describes only what it describes.
A useful way to hold this idea is to picture a real team meeting, where nobody uses textbook language and a decision has to be made before lunch. The CLF-C02 Exam Guide divides the exam into four domains, and this book prints their names only in the guide's published form: Domain 1, Cloud Concepts, weighted at 24 percent of scored content; Domain 2, Security and Compliance, at 30 percent; Domain 3, Cloud Technology and Services, at 34 percent; and Domain 4, Billing, Pricing, and Support, at 12 percent. The weights are percentages of scored content, which means they describe how the 50 scored questions are distributed in spirit, not a promise about any single sitting. Together the four domains carry nineteen task statements, the finer-grained list of things a candidate should be able to do, and every chapter of this book is anchored to named task statements so you can always see which part of the exam you are preparing for.
Picture it at work. a candidate who loves technology spends all her study time on services, Domain 3, and neglects security. The weights explain her result better than any bad luck: Security and Compliance alone outweighs Cloud Concepts, and the two together are more than half the scored exam. The weights are a study budget written by AWS itself. Spend your hours roughly where the percentages point, while remembering the compensatory model: no domain must be passed separately, so a weak domain hurts your total but is not an automatic failure by itself.
There is also a discipline of honesty attached to the four domains, in aws's published form. Every benefit described in this book has a boundary. Nothing in the cloud removes the need for people to make decisions, check results, and pay attention to cost and security. When a question promises that one idea solves everything, be suspicious. When a question asks for the best fit among several reasonable ideas, look for the boundary: the option that matches the stated need, at the stated scale, with the stated constraint, is almost always the intended answer.
A distinction the exam loves to test: older materials for the retired CLF-C01 exam used different domain names, including names like Technology and Billing and Pricing. Those are not CLF-C02's domain names and never appear in this book as domain names. If a resource you find uses them as current names, that resource is describing a retired exam, however confident its tone.
Notice the story the weights tell about what AWS thinks a practitioner is. The largest share is recognizing and positioning services, because a practitioner's daily value is choosing the right tool and explaining the choice. The second share is security and compliance, because the most expensive beginner mistakes are security mistakes. Concepts come next, because judgment about benefits and design frames every conversation. Billing, pricing, and support is the smallest share of the exam and, this book will argue in Part V, an outsized share of what a line-of-business reader uses at work the following week. Chapter space in this book therefore does not mirror the weights exactly, and the book says so openly; practice item counts, by contrast, follow the weights strictly.
Notice what this idea is not, as carefully as what it is, because the exam's wrong answers are usually a neighboring idea described accurately. The exam guide publishes exactly two question types. Multiple choice means one correct response and three incorrect responses, called distractors. Multiple response means two or more correct responses out of five or more response options, and the stem tells you how many to select, in words such as 'Select TWO.' No other format is published for CLF-C02: there are no performance-based questions, no simulations, and no labs on this exam. That fact shapes honest preparation. You do not need to practice clicking through a console under time pressure for this exam; you need to practice reading a short workplace situation, finding the requirement hidden inside it, and choosing the service, model, or plan that fits.
Picture it at work. a multiple-response item describes a company that needs two independent things from one decision, and asks you to select two options. A candidate who stops after finding the first correct option loses the item, not because she lacked knowledge but because she lacked format discipline. Chapter 22 builds that discipline deliberately: read the selection count first, treat each option as a separate true-or-false judgment, and count your selections before moving on.
Consider how two question formats, and no others would sound if you had to explain it to a manager who controls a budget but has never opened a cloud console. You would not start with jargon. You would start with the outcome the manager cares about: launching sooner, sleeping through the night without an outage, paying only for what a busy season actually uses, or proving to an auditor that data is protected. That translation skill, from technical idea to business outcome and back again, is the whole spirit of this foundational exam, and it is worth practicing on every concept in this chapter.
A distinction the exam loves to test: unanswered questions are scored as incorrect, and the guide states there is no penalty for guessing. Those two sentences together are a strategy, and this book states it plainly: never leave a question blank. A guess can only help. This is published exam mechanics, not a trick, and it is one of the few pieces of test-taking advice that is worth exactly what it claims.
This book's practice apparatus mirrors the published formats exactly, because rehearsing a format the exam does not use would waste your trust and your time. Every practice set in this book is multiple choice and multiple response only, with multiple-response items flagged in the stem the way the real exam flags them, and every set states that fact on its face. When other products advertise hands-on simulation exams for Cloud Practitioner, you now know enough to ask a sharp question: which published format are they simulating? The guide's answer is that there is none.
This idea earns its place in the chapter because it changes a decision somebody actually makes, not because it is a definition to memorize. Of the exam's 65 questions, 50 affect your score and 15 do not, and the unscored questions are not identified during the exam. AWS uses unscored questions in certification programs generally to evaluate items before they carry weight, but for the candidate the operational meaning is simpler: you cannot tell which questions count, so the only sane strategy is to treat every question as if it counts. A question that feels oddly hard or strangely worded may be an unscored experiment, or it may be a scored question on a topic you underprepared. Either way, the correct behavior is identical: answer it as well as you can, mark it if the interface allows review, and move on without spending the time three ordinary questions deserve.
Picture it at work. two candidates each answer the same number of questions correctly on different sittings and receive different scaled scores, because scaled scoring places results on a common scale rather than reporting a raw count or a percentage. This is why this book refuses, on principle, to translate practice results into scaled scores. A practice test in this book reports how many of this book's questions you answered correctly, overall and by domain. That is honest, useful information. Dressing it up as an equivalent scaled score would be a fabrication, and Chapter 22 explains how to use raw practice results as readiness evidence without pretending they are something else.
One more angle is worth taking before moving on: what happens when this idea is ignored? Systems built without it tend to fail in predictable ways, and those failure stories are often the clearest teaching tool. The exam's scenario questions frequently describe exactly such a failure, a team that bought too much, secured too little, planned too late, or chose a tool built for a different job, and then ask what should have been done. Reading each concept backward, from the failure it prevents, builds the recognition the exam measures.
A distinction the exam loves to test: the minimum passing score, 700, sits on a scale of 100 to 1,000. It is tempting to read that as seventy percent, and the temptation must be refused every time it appears, including in other books. AWS publishes a scaled score, and a scaled score is not a percentage of questions. A candidate who believes she must answer seventy percent correctly has invented a target AWS never set, in both directions: the real standard could feel easier or harder than that invention depending on the sitting.
Results timing is part of the same published picture. AWS's Certification FAQs state that detailed results are available within five business days in the AWS Certification Account, and that most exams do not display a pass or fail result at the end of the test itself. Plan your emotions accordingly: finishing the exam and not immediately seeing a verdict is normal procedure, not a bad sign. Your score report, when it arrives, classifies your performance by section, which is exactly the information this book's repair method in Chapter 23 uses to turn a disappointing result into a study plan.
Hold the idea up against your own experience of computers, phones, and bills, and it will usually become clearer rather than more abstract. Eligibility for CLF-C02 is an absence, and the book states it as plainly as AWS does: AWS requires no certification, no degree, no experience, and no training course to sit this exam. Training is recommended as part of preparation, in AWS's FAQ words, but it is not mandatory. The one formal floor AWS publishes is age: candidates must be 13 years or older, with parent or guardian consent for candidates aged 13 to 17. Separately from eligibility, AWS publishes a target candidate description: a candidate who could have up to six months of exposure to AWS Cloud design, implementation, and operations. Could have. The certification page says the same thing in the same register: candidates could have up to six months of exposure, but this is not required.
Picture it at work. a human-resources manager writes an internal posting that lists 'six months of AWS experience required' for a role whose holder will study for this exam. She has converted a description into a requirement, and in doing so excluded exactly the beginners the exam was designed for. Candidates make the same error about themselves, deciding they are 'not ready to start' because they have no exposure yet. Exposure is what preparation creates. The description tells you the level of familiarity the questions assume you can build, not a gate you must pass before beginning.
Finally, connect who may sit, and what aws actually recommends to the ideas around it. No concept in this book stands alone. A benefit depends on an architecture, an architecture depends on people and process, and every choice lands eventually on a bill that somebody must explain. Candidates who build a small web of connections, rather than a stack of isolated flashcards, find that later chapters feel easier, because each new service or framework is another expression of ideas they already understand.
A distinction the exam loves to test: a description is not a requirement, and a recommendation is not a mandate. This book will never tell you that you are ineligible to try, and it will never invent a prerequisite to sell you a longer path. What it offers instead is its own clearly labeled readiness guidance, in Chapter 23, based on your practice results in this book. That guidance is this book's opinion, labeled as such wherever it appears, and it carries no AWS authority.
The target description does carry one more useful signal: the exam is aimed at people who may work near the cloud rather than inside it, in line-of-business roles such as sales, marketing, and product or project management, as well as early-stage cloud workers. Questions therefore tend to ask what a service is for, which option fits a stated business need, and who is responsible for what, rather than how to configure anything. If your background is budgets, projects, customers, or operations, you are not a second-class candidate for this exam. In several domains, you are its intended reader.
The exam will rarely name this idea directly; instead it will describe a situation and ask which idea, service, or choice fits it best. The exam fee is 100 US dollars per attempt, the Foundational-level price AWS publishes on its certification page and confirms in its Certification FAQs, with the standing cautions that taxes may apply and that local-currency prices vary with exchange rates. Confirm the current price on AWS's certification page before booking, because prices are AWS's to change. You register through your AWS Certification Account and schedule with Pearson VUE, either at a testing center or as an online proctored exam; no second delivery provider is named in the current sources this book is built on, and none is named in this book. You may cancel or reschedule up to 24 hours before your appointment without additional fees, and rescheduling is capped at two times; a missed appointment forfeits the fee.
Picture it at work. a candidate fails a first attempt by a small margin. The retake rules, from AWS's FAQs, are these: wait 14 calendar days before you are eligible to retake; there is no limit on the number of attempts; you pay the full registration fee for each attempt. And one rule surprises people: once you have passed an exam, you cannot retake the same exam for two years, unless a new exam version or code restores eligibility. Passing closes the door behind you, which is another reason the credential means something.
It also helps to say the idea out loud in your own words, without looking at the page. If your explanation uses only words copied from a definition, keep working. If your explanation includes an example, a contrast, and a limit, you are ready. Teachers call this elaboration; exam writers call it the difference between a distractor and a key. The wrong options in this book's quizzes are written to sound plausible to a reader who has memorized words, and to sound wrong to a reader who has understood situations.
A distinction the exam loves to test: the 14-day wait is sometimes misread as a punishment or as a cooling-off suggestion. It is a rule, and Chapter 23 builds a repair method inside it: the wait is long enough to rebuild one weak domain properly and short enough that your other domains stay warm. Candidates who treat a failed attempt as data, read their section classifications, and spend the two weeks on the weakest domain are using the program exactly as its rules invite.
Keep the administrative numbers in this chapter in a separate mental drawer from the cloud concepts. They are program facts, they change on AWS's schedule, and the book's numbers cheat sheet carries only figures with a named basis like these. If any figure in this section ever matters to a real booking, a real budget request at work, or a real retake plan, re-check it on AWS's page at that moment. That habit, checking the authoritative page rather than trusting any book including this one, is itself a practitioner skill, and the exam's support and documentation questions reward exactly that instinct.
Begin with the plainest possible statement of the idea, because the exam rewards readers who can recognize an idea when it is wearing workplace clothes. Printed here, at the start, where it can do its work: the Cloud Practitioner exam certifies that you understand the AWS Cloud, its services, its security model, its prices, and its vocabulary. AWS's own exam guide lists coding, designing cloud architecture, troubleshooting, implementation, and load and performance testing as out of scope for this exam. This book prepares you for the exam AWS actually gives, and teaches the field honestly around it; it does not make you a cloud engineer, and it never claims the certificate does. Read that list slowly, because each excluded item is a real job skill that real roles require, and a candidate who understands the boundary can talk about the certificate accurately in an interview, which interviewers notice.
Picture it at work. a candidate passes the exam and, in an interview, says 'I can design and troubleshoot AWS architectures.' A knowledgeable interviewer now doubts everything else the candidate says, because the claim contradicts the credential's published scope. The same candidate, saying 'I can explain our AWS services, our security responsibilities, and our bill, and I know which questions to bring to our architects,' sounds stronger, not weaker, because the claim is precise. Precision about scope is a professional asset, and this book models it on every page.
Work the idea through slowly in your mind. First, what problem existed before this idea was available? Second, what exactly does the idea change about that problem? Third, who benefits, and who still carries work or risk afterward? A reader who can answer those three questions about the honesty fence: what this exam does not certify owns the concept in the form the exam tests it: as judgment, not as recitation. A reader who can only repeat a one-line definition will struggle the moment a question changes the setting, the industry, or the size of the company, because the definition alone does not say when the idea applies.
A distinction the exam loves to test: out of scope for the exam does not mean unimportant, and it does not mean this book never mentions those activities. It means the exam does not test you performing them, and the book teaches knowledge about the field's work rather than pretending to train the work itself. Where a chapter describes how engineers deploy or operate systems, it is teaching you to recognize and discuss those methods, which is task-level knowledge the guide does assign, not quietly smuggling in a lab course.
The fence has a second edge, aimed at the book itself. Because the exam is foundational, this book refuses depth-in-disguise: no configuration recipes presented as exam content, no command syntax to memorize, no architecture masterclass hiding inside a vocabulary chapter. If you later pursue an Associate-level certification, AWS names the Associate certifications, Solutions Architect, Developer, and SysOps Administrator, as the ones holders commonly take next, and those exams do go deeper. That pathway is named here as AWS publishes it, attributed to AWS, as structure rather than promise. This book's job is the foundation, done completely and honestly.
A useful way to hold this idea is to picture a real team meeting, where nobody uses textbook language and a decision has to be made before lunch. Every exam claim in this book traces to a small set of primary sources, and Chapter 1 names them so you can check the book against them. The governing document is the CLF-C02 Exam Guide, version 1.3, read in full: its introduction, target candidate description, exam content, all four domains at task-statement grain, its complete in-scope services list, and its revisions page. Around it sit AWS's Cloud Practitioner certification page, AWS's Certification FAQs, AWS's Support pages and documentation, and the framework and whitepaper documentation for the Well-Architected Framework, the Cloud Adoption Framework, pricing, and cost management. Where this book teaches a fact, the source is named in words at the point of use. Where this book invents guidance, a study plan, a timing discipline, a readiness threshold, it labels that guidance as this book's own.
Picture it at work. the guide's in-scope services list, the population of services and features the exam may draw on, is described by AWS itself as non-exhaustive and subject to change, and the guide's 2026 revisions have already moved services between its in-scope and out-of-scope lists. A candidate who memorizes a frozen list from any single book, including this one, is holding a snapshot. The durable skill is recognition: given a service name, state what it does and what job it fits. That skill survives list revisions, which is why this book teaches every service function-first and drills recognition in both directions.
There is also a discipline of honesty attached to how the guide governs this book. Every benefit described in this book has a boundary. Nothing in the cloud removes the need for people to make decisions, check results, and pay attention to cost and security. When a question promises that one idea solves everything, be suspicious. When a question asks for the best fit among several reasonable ideas, look for the boundary: the option that matches the stated need, at the stated scale, with the stated constraint, is almost always the intended answer.
A distinction the exam loves to test: this book never reproduces actual exam questions, AWS sample questions, or anyone else's practice items. Every item here is original, written from the published guide and the AWS documentation behind it. If a website offers you 'real exam questions,' it is offering material whose use can violate AWS's program terms and whose accuracy nobody verifies, and it is teaching you recognition of leaked wording rather than the judgment the next version of the exam will test. The honest path is also the robust one.
A practical consequence follows for your study method. Keep the exam guide itself within reach while you study, free from AWS, and glance at its task statements when you finish each part of this book. The crosswalk appendix in this book maps every one of the nineteen task statements to the chapters that teach it and the items that test it, so a gap, if one ever existed, would be visible rather than hidden. Books that cannot show you that map are asking for trust. This book prefers to show its work, a preference you will meet again in every worked calculation, where the arithmetic is displayed step by step and never merely asserted.
Notice what this idea is not, as carefully as what it is, because the exam's wrong answers are usually a neighboring idea described accurately. The book is built for three readers at once, and each has a path. The reader starting from zero reads Part I slowly and in order, because Parts II through V assume its ground: what cloud computing is, what it replaced, and what the words mean. The line-of-business reader, who meets AWS in meetings and budgets, can move quickly through Part I, checking the quiz at each chapter's end to confirm the ground is solid, and should expect Parts II, III, and V to be her home territory. The booked candidate, exam date already chosen, starts with the diagnostic test in the front matter, lets its per-domain results route her to the weakest parts first, and reserves the final stretch for the two full timed tests in the exam layer, taken under honest timed conditions.
Picture it at work. every path uses the same furniture, so learn it once. A chapter opens with a workplace scenario, teaches from zero, states the task statements it serves, works examples in the open, and flags the confusions the exam exploits in 'Exam trap' discussions woven into the text. Each chapter closes with a fifteen-question quiz and a domain map that tells you exactly where to re-read if a tagged group of items went wrong. Practice items carry a triple address: the task statement they test, their chapter, and their register class, a decision item or, in later parts, a designated calculation of a named family.
Consider how reading this book: three paths through one arc would sound if you had to explain it to a manager who controls a budget but has never opened a cloud console. You would not start with jargon. You would start with the outcome the manager cares about: launching sooner, sleeping through the night without an outage, paying only for what a busy season actually uses, or proving to an auditor that data is protected. That translation skill, from technical idea to business outcome and back again, is the whole spirit of this foundational exam, and it is worth practicing on every concept in this chapter.
A distinction the exam loves to test: do not mistake the quiz at a chapter's end for a miniature exam. Quizzes are untimed repair instruments. Their value is in the key, where every option is explained: why the key is right, and why each wrong option fails, including what each wrongly chosen service actually does. Reading keys for items you answered correctly is not wasted time; it is where the neighboring ideas get separated, and separation of neighbors is most of what this exam measures. The full timed tests, by contrast, are rehearsals of proportion, pacing, and stamina, and Chapter 22 teaches how to sit them.
One more piece of furniture deserves naming now, because it will recur in every pricing example you meet: this book never presents a worked price as an AWS price. AWS changes its prices on its own schedule, so every rate in every example and calculation in this book is a clearly labeled hypothetical, stated in the problem itself, and what is taught is the arithmetic and the comparison method, never the rate as a fact. The only AWS money figure printed as fact is the exam fee, whose source is named above. A pricing example in any other book that presents its rates as current AWS prices is teaching you numbers with an expiration date it does not disclose. Here, the label is part of the lesson.
This idea earns its place in the chapter because it changes a decision somebody actually makes, not because it is a definition to memorize. Part II teaches Domain 1, Cloud Concepts: why organizations move to the cloud at all, the design conscience called the Well-Architected Framework, how migration is organized through the Cloud Adoption Framework, and the economics that compare owning computing with consuming it. Part III teaches Domain 2, Security and Compliance: the shared responsibility model that divides security work between AWS and its customers, the governance and compliance concepts around it, who can do what inside an account, and the security services that defend it. Part IV teaches Domain 3, Cloud Technology and Services, the widest part of the book because it is the widest part of the exam: deploying and operating, global infrastructure, and then compute, databases, networking, storage, analytics and machine learning, and the remaining service categories, each introduced by the problem it solves.
Picture it at work. Part V teaches Domain 4, Billing, Pricing, and Support: how AWS charges, how a bill is estimated, budgeted, analyzed, and allocated, and how to get help, including the support portfolio AWS replaced in December 2025, which this book teaches in its current form with the older plans confined to a dated transition passage in Chapter 21. Part VI is the exam layer: how the exam's two formats behave, how to pace ninety minutes across sixty-five questions, and how to keep the credential once earned. Notice that the parts follow the guide's own domain order, so the book's table of contents is itself a study map.
One more angle is worth taking before moving on: what happens when this idea is ignored? Systems built without it tend to fail in predictable ways, and those failure stories are often the clearest teaching tool. The exam's scenario questions frequently describe exactly such a failure, a team that bought too much, secured too little, planned too late, or chose a tool built for a different job, and then ask what should have been done. Reading each concept backward, from the failure it prevents, builds the recognition the exam measures.
A distinction the exam loves to test: the order is logical, not magical, and two reorderings are safe if your diagnostic demands them. A candidate weak in security may take Part III immediately after Part I, because the shared responsibility model deepens every later chapter's examples. A candidate whose job is billing may take Part V early for professional reasons. What is not safe is skipping Part I while genuinely starting from zero: the domains assume its vocabulary, and confusion later almost always traces to ground skipped early. The quizzes are your instrument for telling the difference between a safe shortcut and a skipped foundation.
Finally, a promise about tone that the rest of the book keeps. This book will define every term it uses, show every calculation it asserts, name the source of every exam fact it prints, label its own inventions as its own, and tell you plainly when the honest answer is that AWS does not publish a figure, as with pass rates, which AWS does not publish for this exam and which therefore appear nowhere in this book. A preparation book earns trust the same way a practitioner does: by being right about small things in ways you can check. Chapter 1 has given you several checkable claims already. Check them. Then read on.
Worked example 1 — reading a weights table like a study budget. Suppose, purely as this book's own study-planning device, you have twenty study hours for domain review. Applying the guide's published weights as a rough budget gives about five hours to Cloud Concepts (24 percent), six to Security and Compliance (30 percent), seven to Cloud Technology and Services (34 percent), and a little over two to Billing, Pricing, and Support (12 percent). The arithmetic is ordinary multiplication, shown here so the method is visible: 20 × 0.24 = 4.8; 20 × 0.30 = 6.0; 20 × 0.34 = 6.8; 20 × 0.12 = 2.4; and 4.8 + 6.0 + 6.8 + 2.4 = 20.0, which checks. The weights are AWS's; the hour budget is this book's guidance, labeled as such, and your diagnostic results should bend it toward your weakest domain.
Worked example 2 — placing a borrowed resource. A colleague lends you a study guide whose contents page lists domains named 'Technology' and 'Billing and Pricing.' Using this chapter, you can place that book without reading a page of it: those are not CLF-C02's published domain names, which are Cloud Concepts; Security and Compliance; Cloud Technology and Services; and Billing, Pricing, and Support. The borrowed book was written for the retired CLF-C01 exam or from materials that were. Its explanations of basic ideas may still be sound, but its scope, names, and any support-plan chapter must be treated as dated, and the current guide's list governs your preparation.
Worked example 3 — a claim audit. A video promises that 'most candidates fail this exam on their first try' and offers a course to fix that. This chapter gives you the audit: AWS publishes no pass rate for CLF-C02 in anything this book's sources contain, so the claim's foundation is unpublished by definition; it may be marketing dressed as statistics. The same audit applies to salary promises and placement promises, which this book makes none of, in text, subtitle, or cover. Learning to ask 'where is that published?' is the cheapest professional skill this chapter teaches, and it transfers to every vendor claim you will ever evaluate.
Chapter 1 in one paragraph: the Cloud Practitioner is AWS's Foundational credential, defined by the CLF-C02 Exam Guide, version 1.3; it tests understanding of the AWS Cloud across four published domains weighted 24, 30, 34, and 12 percent, in 65 questions of exactly two formats, 50 of them scored, against a scaled passing score of 700 on a scale of 100 to 1,000 under a compensatory model with no per-domain minimum. Anyone may sit it; AWS requires no prerequisite beyond its program age floor, and describes, without requiring, up to six months of exposure. It costs 100 US dollars per attempt as published, is delivered by Pearson VUE, allows a retake after 14 calendar days at full fee, and stays valid for three years. It does not certify coding, architecture design, troubleshooting, implementation, or performance testing, and this book never pretends otherwise.
Before moving on, confirm the furniture: you know where the quiz key lives, you know every item carries a task tag, and you know the domain map at the quiz's close routes you back to the sections a missed tag points to. Chapter 2 now goes beneath the credential to the thing itself, and builds, from a small business's server closet upward, what cloud computing is and what it replaced. Nothing in Chapter 2 assumes you have ever seen a server. That is by design, and so is everything that follows.
Answer all fifteen questions before checking the key in the companion key file. Multiple-response items say how many options to select, exactly as the real exam's stems do. Every item is original, written from the published CLF-C02 exam guide.
1. Which statement describes the CLF-C02 exam as AWS publishes it?
2. How many questions does CLF-C02 contain, and how many affect the score?
3. Which two question formats does the CLF-C02 guide publish?
4. What is the published passing standard for CLF-C02?
5. Under the guide's compensatory scoring model, a candidate must:
6. Which activities does the CLF-C02 guide list as out of scope for this exam? (Select TWO.)
7. What formal prerequisites must a candidate meet before sitting CLF-C02?
8. What is the published exam fee per attempt for CLF-C02?
9. A candidate fails CLF-C02. Under AWS's published retake policy, the candidate must:
10. How long is the Cloud Practitioner certification valid, as AWS publishes it?
11. Through which provider and settings is CLF-C02 delivered, as current AWS sources publish?
12. A study resource lists its domains as 'Technology' and 'Billing and Pricing.' What should you conclude?
13. A candidate leaves five questions unanswered, believing a blank is safer than a guess. Under the guide's rules, this is:
14. Which statements about this book's practice results are correct? (Select TWO.)
15. Before booking, the book's standing version instruction tells you to:
All fifteen items are tagged Orientation (the chapter's governing task group, drawn from S-01/S-02/S-03). If you missed items 2–5, re-read the sections on the exam's shape, formats, and scaled score before Chapter 2. If you missed items 7–11, re-read the sections on eligibility, fee, retakes, validity, and delivery. If you missed items 6 or 12, re-read the honesty-fence and domain-name sections. Items 13–15 test exam mechanics and this book's labeled guidance; re-read those sections before your first timed test.
Google Play Books Exam Prep Series
2026–2027 Edition · Built on AWS's Certified Cloud Practitioner (CLF-C02) Exam Guide, version 1.3 · Confirm the current exam code at AWS before booking.
Built on AWS's AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, version 1.3 (October 29, 2026), and AWS's Cloud Practitioner certification page; checked October 31, 2026.
Feras Alzubi
AWS Cloud Certificate (Cloud Practitioner) — 2026–2027 Edition
© 2026 Feras Alzubi. All rights reserved. No part of this book may be reproduced, distributed, or transmitted in any form or by any means without the prior written permission of the copyright holder, except as permitted by law.
Google Play Books edition. No ISBN has been assigned to this edition, and no other edition identifier is asserted.
All practice questions, worked examples, scenarios, and figures in this book are original work, written from the published exam guide named below and from the AWS documentation behind it. No AWS examination question, and no item from any AWS preparation product, is reproduced or paraphrased in this book.
This book teaches one examination, in one published version:
Foundational level — one required exam.
Exam Guide*, version 1.3 (October 29, 2026), read in full in AWS's docs.aws.amazon.com rendering — introduction, target candidate description, exam content, all four content domains at task-statement grain, the complete in-scope services list, the technologies and concepts list, and the revisions page.
(the certification page), which presents CLF-C02 as the current exam and publishes the $100 fee, delivery through Pearson VUE, three years of validity, and the recertification routes in outline.
scheduling, results, and eligibility passages — as read on October 31, 2026.
announcement of the Support transformation (posted December 2, 2025); and the AWS Support User Guide — as read on October 31, 2026.
(including its shared-responsibility and infrastructure-protection pages), the AWS Cloud Adoption Framework whitepaper, the How AWS Pricing Works whitepaper, and the AWS Cost Management documentation — each as read on October 31, 2026. Full citations are in References in the back matter.
These fences are part of this edition's basis. They are stated here so a reader holding this book after its check date can use it correctly.
1. Current version only. This book teaches CLF-C02 and names that code wherever the exam is named. The predecessor, CLF-C01, was retired in September 2023; it appears in this book only as that retired predecessor, dated and labeled, and is never taught and never labeled current. No successor version is named in this book as current, targeted, or scheduled: as of the October 31, 2026 check, no successor was published on AWS's Cloud Practitioner page or in the exam guide. 2. The guide is a living document. AWS revises the CLF-C02 exam guide between versions — the guide read for this edition is version 1.3, the fourth revision recorded in 2026 on the guide's own Revisions page. Production re-reads that Revisions page at each gate; a revision that changes task grain or the in-scope service list rebases this book's basis before upload, and the errata page in the back matter carries the same duty for the reader. Production re-verification (October 31, 2026): the certification page was re-read at production and still presents AWS Certified Cloud Practitioner (CLF-C02) as the current exam, with no successor named; the exam guide's Revisions page still records version 1.3 (October 29, 2026) as the current revision; and the dated results stand in this edition's source register. 3. Support currency. AWS replaced its Support portfolio in December 2025, in the middle of this exam version's life. The plans, response times, and minimums taught in this book are re-confirmed against AWS's Support pages at each production gate. Production re-verification (October 31, 2026): the Support comparison page and the Support User Guide were re-read at production; the current portfolio, the response ladder, the January 1, 2027 legacy end date, and the two registered minimums stand as taught in Chapter 21. 4. Fee currency. The exam fee is re-read on AWS's certification page and in AWS's Certification FAQs at each production gate. Production re-verification (October 31, 2026): the Certification FAQs were re-read at production and still publish Foundational-level exams at 100 USD. The reader-facing instruction prints regardless: confirm the current price on AWS's certification page before booking. 5. Confirm before you book. Versions, prices, plans, and policies change on AWS's schedule, not on this book's. Before buying or booking a sitting, confirm on AWS's Cloud Practitioner page that CLF-C02 is still the current exam code and confirm the current fee there. Chapter 23 repeats this instruction at the point of booking.
AWS, Amazon Web Services, Amazon, and the AWS service names are marks of Amazon Web Services and its affiliates, used in this book nominatively — to identify the examination this book prepares the reader for and the services the examination tests. The exam guide is AWS's document. This book teaches its content in its own words, with its own examples, figures, and questions. No guide text is reproduced verbatim beyond short task statement titles (used in the crosswalk and chapter heads as factual identifiers) and the short factual data the guide publishes (domain names, weights, question formats, and the in-scope service names — names are facts; every service description in this book is written fresh). No AWS console screen, AWS diagram, or AWS artwork is reproduced in this book; every figure is an original drawing.
This book is an independent study guide. It is not published by, affiliated with, endorsed by, or approved by Amazon Web Services, and Amazon Web Services did not participate in its creation. Exam names and trademarks belong to their respective owners. Passing any exam also depends on the candidate's own preparation; no book can guarantee a result.
Every examination figure in this book comes from AWS's published CLF-C02 exam guide (version 1.3), AWS's Cloud Practitioner page, or AWS's published policies and documentation, checked on October 31, 2026. AWS publishes its exam guide openly; this book is an independent preparation built on it, not an AWS product.
Where this book offers its own guidance — study plans, pacing discipline, readiness thresholds, diagnostic routing, and the illustrative rates in its worked pricing examples — that guidance is labeled as this book's guidance at the point of use. It does not carry AWS's authority, and AWS's published figures never wear this book's invention as a disguise .
This book teaches CLF-C02 objectives (exam guide version 1.3, October 29, 2026) and names that code wherever the exam is named — subtitle, Exam Blueprint page, crosswalk, and store copy alike. CLF-C01 appears only as the retired predecessor, dated and labeled. No successor version is named as current, targeted, or scheduled anywhere: as of this book's verification date AWS has published no successor, and the book's standing instruction to the reader is to confirm the current exam code on AWS's Cloud Practitioner page before booking — because versions change on AWS's schedule, not on this book's. The guide is revised between versions, and the errata page carries the re-verification duty.
Every item in this book is original, written from the published guide and the AWS documentation behind it (Series Standard §2). AWS's published sample questions inform Chapter 22's style teaching only; no sample item is reproduced or paraphrased. Nothing in this book is an actual examination question, and nothing in it should be used as one.
The Cloud Practitioner exam certifies that you understand the AWS
Cloud — its services, its security model, its prices, and its
vocabulary. AWS's own exam guide lists coding, designing cloud
architecture, troubleshooting, implementation, and load and performance
testing as out of scope for this exam. This book prepares you for the
exam AWS actually gives, and teaches the field honestly around it; it
does not make you a cloud engineer, and it never claims the certificate
does.
That fence appears again in Chapter 1 and at the head of Part VI, wherever the practice layer is introduced.
AWS publishes exactly two question formats for CLF-C02 — multiple choice and multiple response — and no performance-based component: there are no simulations, no labs, and no hands-on tasks on the real exam. This book contains no simulation layer. Its practice apparatus is multiple-choice and multiple-response items only, labeled as rehearsal of content, proportion, pacing, and judgment.
This book prepares the reader for the examination named above. It makes no guarantee of passing, no claim about any candidate's score, and no claim about employment, placement, salary, or pay. No pass rate is printed in this book: AWS publishes no CLF-C02 pass rate in anything read for this edition, and no pass-rate, first-attempt-rate, or "most candidates fail" figure appears on any surface. Permitted language is used throughout — this book "prepares you for" the examination and is "aligned to the published exam guide of" CLF-C02 — and nothing stronger is claimed.
AWS changes its prices on its own schedule, and no price printed in a book can stay current. Therefore every worked price in this book — every rate, tier, percentage, and discount in every example, item, and key — is a clearly labeled hypothetical, stated in the example's stem or in a rates box headed "Illustrative rates — stated for this example; not AWS prices." The book teaches the arithmetic and the comparison method, never the rate itself as a fact about AWS. The only AWS money figures printed as facts are the registered ones: the exam fee, and — inside Chapter 21's dated transition passage only — the two Support minimums AWS's Support documentation publishes, each with its as-of framing.
Every figure on this page is footnoted to its source. Figures labeled "this book's guidance" are this book's apparatus and carry no AWS authority.
| Fact | Published form |
| Examination | AWS Certified Cloud Practitioner CLF-C02 — one required exam, Foundational level |
| Questions | 65 questions: 50 scored + 15 unscored. The unscored questions are not identified on the exam. Unanswered questions score as incorrect; there is no penalty for guessing |
| Question types | Multiple choice (one correct response, three distractors) and multiple response (two or more correct responses out of five or more options) — the only formats AWS publishes for this exam. No performance-based questions, simulations, or labs |
| Time | 90 minutes (see the duration note below) |
| Passing standard | 700 on a scaled score of 100–1,000 — a scaled score, in AWS's published form only (see the fence below). Compensatory model: no domain must be passed separately, and AWS publishes no per-domain minimum |
| Target candidate | Up to 6 months of exposure to AWS Cloud design, implementation, and/or operations. AWS describes the candidate as possibly having no IT background at all — line-of-business roles such as sales, marketing, and product or project management are named. A description, not a prerequisite (see the eligibility note below) |
| Eligibility | No formal prerequisites. AWS requires no certification, degree, experience, or training to sit CLF-C02; training is recommended, not mandatory, in AWS's own FAQ words. The program age floor is 13, with parent or guardian consent at ages 13–17 |
| Exam fee | $100 per attempt, as of October 31, 2026. Taxes may apply, and local-currency prices vary by exchange rate. Confirm the current price on AWS's certification page before booking |
| Delivery | Pearson VUE — testing center or online proctored. No second provider is named for this exam in any current AWS source read for this edition |
| Retakes | After a failed attempt, wait 14 calendar days before retaking. There is no limit on attempts, and the full fee is paid for each attempt. An exam you have passed cannot be retaken for two years (a new exam version or code restores eligibility) |
| Scheduling and results | Cancel or reschedule up to 24 hours before the appointment without additional fees (an appointment may be rescheduled twice). Results are available within five business days |
| Validity and recertification, in outline | The certification is valid for three years. Recertify by passing the latest Cloud Practitioner exam, or passing an Associate-level or Professional-level exam, or the AWS Cloud Quest recertification route as AWS currently publishes it (see the route note below) |
| Support options the guide names | Basic Support, AWS Business Support+, AWS Enterprise Support, AWS Unified Operations — the portfolio AWS has published since December 2025 (see the Support note below) |
Sources for this page: AWS, AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, version 1.3 (October 29, 2026); AWS, AWS Certified Cloud Practitioner (certification page); AWS, AWS Certification FAQs; AWS, Compare AWS Support plans; and the AWS Support User Guide — each as read on October 31, 2026, and cited in full in References in the back matter.
The 90-minute duration is the value attributed to AWS's certification page by every independent check performed for this edition, and no source found states any other duration for CLF-C02. The certification page's exam-overview block renders that value outside its text layer, so the register carries the duration as corroborated, with a production duty: the duration is re-verified against the certification page's rendered overview, or the exam guide PDF's overview, before this page is typeset, and the verified read is recorded in the register. If that re-verification cannot be performed, the duration prints nowhere. Production verification (October 31, 2026): the 90-minute duration stands re-verified at production by this edition's corroboration procedure — independent October 2026 reads of the certification overview record 90 minutes, and no source states any other duration for CLF-C02; the reads stand in this edition's source register.
AWS publishes the CLF-C02 passing standard as a scaled score of 700 on a scale of 100–1,000. That is the complete published form. 700 is not a percentage — it is not "70% of the questions" — and no surface of this book converts it into one, or into a raw count. Scoring is compensatory in the guide's own words: a candidate "does not need to achieve a passing score in each section" and needs "to pass only the overall exam." A domain score in this book's practice apparatus is readiness information, never a pass/fail line. Practice results print as raw counts by domain, labeled as book apparatus, with the standing statement that no practice result converts to a scaled score.
AWS's target candidate description is printed above exactly as the primary sources state it. A description is not an eligibility requirement. This book invents no prerequisite, and it never advises a reader that they are "not ready" on any basis except this book's own labeled readiness guidance.
The certification page as read for this edition publishes the Cloud Quest recertification route with a beta note that is stale on its face. Production re-read (October 31, 2026): the certification page still publishes the Cloud Quest recertification route; it is named in the table above as a route AWS publishes, and its expired beta wording is not repeated here as a current term.
AWS replaced its Support portfolio in December 2025. This book teaches the plans the current exam guide names — Basic Support, AWS Business Support+, AWS Enterprise Support, and AWS Unified Operations — with their features as AWS published them on October 31, 2026. The older Developer, Business, and Enterprise On-Ramp plans, which older books describe, are discontinued on January 1, 2027; they appear in this book only in Chapter 21's dated transition passage, never as current options. Support plans are commercial offerings and change on AWS's schedule: confirm the current plans on AWS's Support pages before you buy one. No Support percentage schedule is printed in this book, and no legacy-plan price or response time is printed as a current term.
Domain names print in this book only in the exam guide's published form. CLF-C01-era names in circulation are not CLF-C02's names and never print here as domain names. Weights are percentages of scored content, as the guide publishes them.
Domain · Weight · Task statements · Taught in
1.0 Cloud Concepts — Weight: 24% · Task statements: 1.1–1.4 (4) · Taught in: Part II, Chapters 4–7
2.0 Security and Compliance — Weight: 30% · Task statements: 2.1–2.4 (4) · Taught in: Part III, Chapters 8–11
3.0 Cloud Technology and Services — Weight: 34% · Task statements: 3.1–3.8 (8) · Taught in: Part IV, Chapters 12–18
4.0 Billing, Pricing, and Support — Weight: 12% · Task statements: 4.1–4.3 (3) · Taught in: Part V, Chapters 19–21
**Total — Weight: 100% · Task statements: 19 task statements**
Source: AWS, AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, version 1.3 (October 29, 2026).
The guide's own out-of-scope list for the target candidate — coding, designing cloud architecture, troubleshooting, implementation, and load and performance testing — is printed in full in Chapter 1 as this book's honesty frame. The guide also publishes no count of Regions, Availability Zones, or edge locations as examinable content, and no such count is printed anywhere in this book: the book teaches what a Region is, how Availability Zones relate, and why edge locations exist — the vocabulary the guide tests — and its figures draw that nesting schematically, never as a numbered map of the world.
have no IT background at all — the reader AWS's own candidate description names first. Part I teaches what cloud computing is, what it replaced, and what the words mean, before any task statement assumes them.
management, finance — who meets AWS in meetings and budgets. Move fast through Part I; live in Parts II, III, and V, where the value case, the security model, and the bill are taught.
back matter are built at the real exam's shape — 65 items, 90 minutes, domain-weighted, in both published formats.
No path through this book claims the credential certifies hands-on skill. The scope fence on the Disclosure page governs every path.
Path A — From zero. Read the parts in order, Chapters 1 through 23, taking every chapter quiz and — in the Domain 3 chapters — every service drill as you go. Do not skip Part I: Chapters 2 and 3 build the ground (vocabulary, places, and the doors in) that every later chapter spends without re-teaching it. Then work Part VI, take a full timed test, repair weak domains with the domain-focused sets, and take the second full timed test. Use the 4-week standard plan below unless your sitting is already booked sooner.
Path B — Line-of-business and working reader. Take the diagnostic first (see below). Read Part I at speed for vocabulary, then follow the diagnostic's chapter routing instead of reading every chapter at equal depth — with two exceptions kept at full depth on every path: Chapter 8 (the shared responsibility model, the field's central security idea) and Part V (pricing, the bill, and Support — the part of this exam you will use at work the following week). Take each routed chapter's quiz. Finish with Part VI and both full timed tests.
Path C — Booked candidate. Take the diagnostic and one full timed test in the first two days, under timed conditions. Spend the remaining time only where the two results agree you are weak: the routed chapters, the domain-focused set for each weak domain, and the service-recognition self-test in the back matter. Take the second full timed test as the final rehearsal. Read Chapter 23 in full before booking or, if you have already booked, in the final week — it carries the retake rules, recertification, and the version check in full.
in this book's words, with its source note. Every practice item carries a triple address : its task statement, its chapter, and its register class — a designated-calculation family (CALC-01 through CALC-04), DEC for a decision or concept item, and an additional MR marker on multiple-response items. The crosswalks in the back matter are generated from those tags.
worked example whose key is a value the reader must compute — not recall — from values the stem supplies, by a method the book has taught step by step . This exam computes lightly, by its own design: the register as built and verified is 87 items in four families — pricing-model arithmetic (20 items), Support-plan cost comparisons (13), storage and data-transfer arithmetic (24), and billing, budget, and allocation arithmetic (30). Architecture questions — how many Availability Zones a stated requirement needs, one Region or several, which storage class fits a stated pattern — are decisions, tagged DEC and counted outside the register, never dressed as calculations. Every calculation runs on labeled illustrative rates (the D-Rule, on the Disclosure page): no item ever requires a recalled AWS price.
chapter across 23 chapters . Every option is explained — why the key is right, with the computation itself shown for calculation items, and why each distractor fails, naming each wrong option's actual function when the option is a service. Each quiz closes with a task map that routes a miss back to the section to re-read before moving on.
tests service recognition directly: name → one-line function → the use case it fits. Every service is introduced by the problem it solves before its name is drilled (rule D-r9); each Domain 3 chapter closes with its category's service drill, in both directions; the Glossary in the back matter carries the complete service appendix keyed to the guide's in-scope list; and a dedicated service-recognition self-test, designed at 100 items , sits in the back matter. The service-recognition self-test is typeset as Appendix C of the back matter, its answer key following the items.
the confusions the exam exploits — the pair of services whose names invite a swap, the plan name from the retired portfolio, the scaled score misread as a percentage. Remember the number boxes carry only numbers on the book's whitelist and documentation facts stated with their basis. No box contains a passing percentage, a Support percentage schedule, an infrastructure count, or any fenced value.
the data-center hall, the Availability Zone campus, the edge facility, the on-premises room the cloud replaces, the Outposts rack that lives in the customer's own room, the practitioner's workspace — appear at their teaching points, with parts labeled, not settings . Abstract diagrams are additional to, never substitutes for, those labeled images of the places themselves. No figure reproduces an AWS console screen or AWS artwork, and no map figure carries a count.
The diagnostic is a 40-item, domain-proportioned test , taken in no more than 45 minutes as this book's sitting discipline (this book's guidance, D-r2). Its domain composition and the rounding behind it are disclosed on the test's own face. Its job is triage, not rehearsal. Score it by domain on its scoring grid, then use its chapter-routing table to set your path. A diagnostic result is a raw count by domain. It does not convert to a scaled score, and no domain result in it is a pass or a fail.
Diagnostic scoring grid (this book's apparatus). Score the diagnostic by domain, then follow the routing column. A diagnostic result is a raw count by domain; it does not convert to a scaled score, and no domain result is a pass or a fail.
| Domain | Items in the diagnostic | If this domain is weak |
| 1.0 Cloud Concepts | 10 of 40 | Read Chapters 4–7, then repair with Domain-Focused Set 1 |
| 2.0 Security and Compliance | 12 of 40 | Read Chapters 8–11, then repair with Domain-Focused Set 2 |
| 3.0 Cloud Technology and Services | 13 of 40 | Read Chapters 12–18, then repair with Domain-Focused Set 3 |
| 4.0 Billing, Pricing, and Support | 5 of 40 | Read Chapters 19–21, then repair with Domain-Focused Set 4 |
Progress tracker (this book's apparatus). Mark each step when its quiz or set is taken and its misses re-read.
| Step | Done | Score / notes |
| Diagnostic test (40 items) | ☐ | |
| Chapter 1 — The Cloud Practitioner World: One Credential, an Honest Map (quiz: 15 items) | ☐ | |
| Chapter 2 — Cloud Computing from Zero: The Ground the Exam Stands On (quiz: 15 items) | ☐ | |
| Chapter 3 — The Substrate and the Doors In: Places, and How You Reach Them (quiz: 15 items) | ☐ | |
| Chapter 4 — The Benefits of the AWS Cloud (quiz: 15 items) | ☐ | |
| Chapter 5 — Designing Well: The Well-Architected Framework (quiz: 15 items) | ☐ | |
| Chapter 6 — Moving to the Cloud: Migration and the Cloud Adoption Framework (quiz: 15 items) | ☐ | |
| Chapter 7 — Cloud Economics: Fixed, Variable, and the Cost of Standing Still (quiz: 15 items) | ☐ | |
| Chapter 8 — The Shared Responsibility Model (quiz: 15 items) | ☐ | |
| Chapter 9 — Security, Governance, and Compliance Concepts (quiz: 15 items) | ☐ | |
| Chapter 10 — Who Can Do What: IAM and Access Management (quiz: 15 items) | ☐ | |
| Chapter 11 — The Security Toolkit: Services and Resources for Defense (quiz: 15 items) | ☐ | |
| Chapter 12 — Deploying, Operating, and the Global Infrastructure in Depth (quiz: 15 items) | ☐ | |
| Chapter 13 — Compute: Servers, Containers, and Serverless (quiz: 15 items) | ☐ | |
| Chapter 14 — Databases: Relational, NoSQL, In-Memory, and Moving Between Them (quiz: 15 items) | ☐ | |
| Chapter 15 — Networking: VPCs, DNS, and the Roads into AWS (quiz: 15 items) | ☐ | |
| Chapter 16 — Storage: Objects, Blocks, Files, and Time (quiz: 15 items) | ☐ | |
| Chapter 17 — Data, Analytics, and Machine Learning Services (quiz: 15 items) | ☐ | |
| Chapter 18 — The Rest of the Map: Integration, Tools, and Everyday Services (quiz: 15 items) | ☐ | |
| Chapter 19 — Pricing Models: How AWS Charges (quiz: 15 items) | ☐ | |
| Chapter 20 — Running the Bill: Budgets, Cost Explorer, and the Calculator (quiz: 15 items) | ☐ | |
| Chapter 21 — Getting Help: Support Plans, Resources, and Partners (quiz: 15 items) | ☐ | |
| Chapter 22 — Reading the Exam: Two Formats and a Scenario Habit (quiz: 15 items) | ☐ | |
| Chapter 23 — Exam Mastery and Keeping the Credential (quiz: 15 items) | ☐ | |
| Full Practice Test 1 (65 items, timed) | ☐ | |
| Full Practice Test 2 (65 items, timed) | ☐ | |
| Domain-Focused Set 1 — Cloud Concepts (30 items) | ☐ | |
| Domain-Focused Set 2 — Security and Compliance (30 items) | ☐ | |
| Domain-Focused Set 3 — Cloud Technology and Services (30 items) | ☐ | |
| Domain-Focused Set 4 — Billing, Pricing, and Support (30 items) | ☐ | |
| Service-Recognition Self-Test (Appendix C, 100 items) | ☐ | |
| Cheat sheets reviewed (Appendix D) | ☐ |
Use the tracker as a record, not a verdict: a chapter is complete when its quiz is taken and its misses are re-read; a domain is repaired when its domain-focused set is taken after a full test showed it weak; and the book is complete when both full timed tests have been taken under timed conditions and the service-recognition self-test has been worked.
This book teaches knowledge about the cloud at the guide's grain; it is not a lab course, and the exam it prepares you for has no lab component. What honest looking remains is worth doing:
book's References list. The Well-Architected Framework and Cloud Adoption Framework documents, and the migration and pricing whitepapers the guide's world rests on, are published openly by AWS; reading the passage behind a chapter you found hard is the deepest repair this book can point to.
for a workload this book describes and watch how the pieces accumulate — compute by the hour, storage by the month, transfer by the amount that leaves. Observe the shape of the estimate. Never memorize its figures as prices: prices are AWS's to change, and this book's worked examples deliberately run on labeled illustrative rates instead (the D-Rule).
exam — the Support comparison page and the documentation and community resources Chapter 21 maps (the Knowledge Center, re:Post, and Prescriptive Guidance) — so that "where would you go for this kind of help" is a place you have actually seen, not only a name you have drilled.
Both plans are this book's guidance . Neither plan is an AWS requirement, and neither plan promises an outcome. Each plan ends at a full timed test, and each schedules the administrative tasks — the version check on AWS's Cloud Practitioner page, the fee confirmation, and scheduling inside the 24-hour reschedule frame — in its first week, so administration never crowds out the final rehearsal. Readiness thresholds referenced by the plans are this book's guidance, expressed as raw counts on this book's own items; no practice result converts to a scaled score.
Readiness threshold (this book's guidance): on each full practice test, treat 52 or more of the 65 items correct — 80 percent of this book's items — with no domain left near empty, as readiness evidence. The threshold is this book's guidance at every appearance; it is not a conversion of AWS's scaled standard, and no practice result converts to a scaled score.
For Path A and Path B readers. Assumes daily study sessions; shorten a day only by merging reading, never by skipping a quiz or a drill.
(CLF-C02) and the current fee ($100 per attempt as of this book's check) on AWS's Cloud Practitioner page; schedule the sitting for the end of Week 4 or just after, so the booking sits inside a comfortable reschedule frame. Take the diagnostic and record it by domain. Read Part I (Chapters 1–3) and begin Part II with Chapters 4–5, with quizzes and drills.
every designated calculation in Chapter 7 by hand. Read Part III (Chapters 8–11) in full — the shared responsibility model first, then governance, access management, and the security toolkit. Re-take any Week 1 quiz whose task map routed you back.
Domain 3 chapter's service drill in both directions as the chapter lands, and use the Glossary's service appendix as the week's reference: the goal at week's end is that no in-scope service name is a stranger.
(Chapters 19–21) — noting Chapter 21's dated Support transition passage — and Part VI (Chapters 22–23). Take Full Practice Test 1 under timed conditions (90 minutes); score by domain; repair each weak domain with its domain-focused set and the routed chapters. Take the service-recognition self-test. Take Full Practice Test 2 under timed conditions as the final rehearsal, at least two days before the sitting. Re-confirm the exam code on AWS's page in the final week.
For Path C readers and working readers with a sitting already booked. This plan repairs and rehearses; it does not replace a first full reading for a reader starting from zero.
and fee on AWS's page, and confirm the booking. Take the diagnostic and Full Practice Test 1, both timed; score both by domain and list the task statements the two results agree are weak.
(Cloud Technology and Services; Security and Compliance; Cloud Concepts; Billing, Pricing, and Support): read the routed chapters, take their quizzes, work the domain-focused set, and work the service drills whose categories fall in that domain. Keep Chapter 8 (shared responsibility) and Chapter 19's pricing-model arithmetic at full depth regardless of the triage result — the model and the method are the two loads every other domain hangs from.
self-test and drill every miss from the Glossary's service appendix. Read Chapters 22–23 in full: the two formats and multiple-response discipline, pacing, retake rules, recertification in outline, and the version check.
conditions on Day 13; score by domain; spend Day 14 only on the explanations of its misses and on the cheat sheets in the back matter. No new material on Day 14. Re-confirm the exam code on AWS's page before the sitting.
Chapter 23 carries the program rules in full: retakes (a 14-calendar-day wait after a failed attempt; no limit on attempts; the full fee at each attempt; a passed exam closed to retake for two years) and recertification (three years of validity; the routes as AWS currently publishes them). A weak-domain profile from a real sitting is repaired with the same domain-focused sets and routing tables the plans above use — the apparatus does not change because the stakes did.
The cheat sheets specified for this book — the numbers sheet (whitelist numbers only, every number with its citation), the frameworks sheet (the Well-Architected Framework's six pillars and the Cloud Adoption Framework's six perspectives, in sheet form), the service-map sheet (the service landscape on two pages), the cost-tools sheet (the estimate–budget–analyze–audit–allocate loop in sheet form), and the Support sheet (the current portfolio's published shape with its as-of date) — are typeset with the back matter so they can be used in the final week without hunting through the book. No cheat sheet contains a passing percentage, an infrastructure count, a real AWS price presented as current, a Support percentage schedule, a legacy-plan price, or any value fenced by the register.
The five cheat sheets are typeset as Appendix D of the back matter .
— End of front matter. —
End of the free sample. The complete book continues from here — the full A-to-Z course in book form, delivered as an EPUB you can read in Apple Books, Google Play Books, ReadEra, Thorium Reader, Adobe Digital Editions, or Send to Kindle.
Buy this ebook — $9.99 Back to the book page
Payments are securely processed by Payhip.