What You Actually Face on Day One
The AWS Cloud Practitioner exam is straightforward in format but deceptively broad in scope. You sit down at a testing center or log into PSI, you get a screen with a progress bar, and you start clicking through questions. There's no trick to the number itself — it's fixed, it's published, and it hasn't changed in years. But the real question most people are really asking is whether 65 questions in 90 minutes feels tight or comfortable, and the answer depends entirely on how you prepared. I've watched people blow through these exams in 45 minutes because they already worked in cloud, and I've watched equally prepared candidates struggle to finish because they second-guessed themselves on the scenario-based questions. The exam doesn't punish speed. It punishes hesitation.
How Many Questions Are On The Aws Cloud Practitioner Exam
Sixty-five questions. Multiple choice and multiple response. You have 90 minutes. That works out to roughly one minute per question if you're flying, or about 83 seconds if you're reading carefully and eliminating wrong answers. Most people finish in 60 to 75 minutes. The ones who don't finish are the ones who spend four or five minutes on a single tricky question and then panic at the end. The exam costs $100 USD. You can retake it immediately if you fail — no waiting period. I failed my first attempt on a single question about the AWS Shared Responsibility Model where the answer choices were carefully worded to make both options seem correct. The trick was recognizing that AWS manages the infrastructure layer and the customer manages everything above it, including OS patches and data encryption. I got it wrong because I overthought it. I studied that topic harder for my second attempt and nailed it on the retest. Here's something they don't tell you: the exam is adaptive in the sense that the question order is randomized, but it's not computer-adaptive like the GRE. Every candidate gets a different shuffle of the same 65 questions from the same pool. That means you can't predict which topics will show up first, but it also means you can't game the exam by saving hard questions for last — they're scattered throughout.
The passing score is 700 out of 1000. That sounds generous until you realize the exam deliberately includes about 10 to 15 questions that are designed to be borderline. They throw in a handful of situational questions where the "best" answer isn't obviously right. AWS loves questions that ask you to choose the most cost-effective solution or the most secure solution, and those two answers sometimes conflict with each other. My practical advice, the stuff that actually moved the needle for me: focus heavily on the four exam domains in order of weight. The Security and Compliance domain carries the most points, followed by Cloud Economics, then Technology, then Architecture and Design. People study the wrong thing first. They memorize every AWS service name and endpoint URL because it's easier, but the exam tests your ability to pick the right service for a scenario, not your ability to recite a list. Another counter-intuitive thing: the AWS Well-Architected Framework is barely mentioned explicitly on the exam, but it underpins almost every architecture question. If you understand the six pillars — operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability — you'll instinctively pick the right answer even when the question wording is awkward. The exam writers assume you know the framework even when they don't name it.
The one area where the exam genuinely trips people up is pricing and billing. You need to understand the difference between On-Demand, Reserved Instances, and Spot Instances well enough to pick the right one for a given workload. You should know what AWS Cost Explorer does and what it doesn't do. You should understand the basic structure of an AWS bill. I've seen candidates who could describe an EC2 instance in detail stumble on a question about whether a Consolidated Billing discount applies across accounts in an AWS Organization. It does, but only if the member account hasn't been excluded. These small details matter more than broad knowledge. If you want a concrete study plan that actually works, spend two weeks on the official AWS Cloud Practitioner Essentials course, then one week doing practice exams under timed conditions. Take at least four full practice exams. If you're scoring below 75 percent consistently, you're not ready. The real exam is slightly harder than most third-party practice tests, not easier. A couple of popular question banks mark answers as wrong when they're actually correct, or vice versa, so don't get hung up on exact scores from unofficial sources. Focus on understanding why an answer is right, not just whether you got it right or wrong. The exam is proctored remotely through PSI or in person at a Pearson VUE test center. Remote proctoring requires a quiet room, a clean desk, and a workspace scan before you begin. I've seen people fail to start the exam because their webcam couldn't detect their face properly in poor lighting. Check your setup the day before. Don't wait until exam morning.
One last practical note: you don't need hands-on AWS experience to pass this exam. It's a fundamentals exam, not a practitioner-level certification in the sense of requiring real deployment experience. But if you've never logged into the AWS Management Console, take ten minutes to do it before the exam. Recognizing the layout of the console and where services live makes the scenario questions feel less abstract. It won't hurt your score and it takes about fifteen minutes.
