TL;DR
AZ-900 allows 45 minutes inside a 65-minute appointment (pass 700 of 1000), SC-500 allows 120 minutes, and SAA-C03 allows 130 minutes for 65 questions (pass 720 of 1000). All three run at test centers or online proctored; online rooms must be clear, quiet, and closed-door with phone away. No cloud exam penalizes guessing, so answer everything. Read the final sentence of long stems first. Format prep: AZ-900 4-week plan and SAA 8-week plan.
One week out: confirm the per-exam facts
Each cloud exam has different numbers, so verify yours rather than averaging. AZ-900: 45 minutes of exam time, Microsoft publishes no fixed question count, 700 to pass, fundamentals certs do not expire. SC-500: 120 minutes across four assessed areas; recheck the Microsoft certification page since new-exam details move. SAA-C03: 65 questions, 130 minutes, 720 to pass, 150-dollar fee. Confirm delivery: Microsoft exams schedule through the Microsoft flow at Pearson VUE (plus Certiport for students), AWS through PSI or Pearson VUE depending on region, each with center or online options. Read the confirmation email twice: arrival time, ID list, break policy, and whether the exam includes unscored trial items or non-revisitable case sets. Microsoft states plainly that some items may be unscored trials and that 700 is a scaled score, not 70 percent; AWS likewise scales 720 on the 100 to 1000 range. Knowing the scoring removes the most common mid-exam panic (why is this question weird, am I failing), which deserves its place in a checklist.
Online proctoring: the room is part of the exam
Most cloud-exam day failures are room failures, not knowledge failures. The compliant room: closed door, no other people, desk completely clear except ID, phone silenced and out of reach, no papers or books or second monitors, no reading questions aloud in some programs. Run the official system test days early on the same machine and network: webcam, microphone, upload speed, and administrator rights to install the proctoring client. Wired Ethernet beats Wi-Fi; a tested phone hotspot is the backup. Check in 30 minutes early: photos of you, your ID, and the room from four angles always take longer than expected. During the exam, look at the screen (reading aloud or looking away repeatedly triggers warnings), keep hands visible, and never cover your mouth. Breaks: on exams that offer one, the clock keeps running and answered items may lock, so use breaks only for genuine need. If the proctor messages you, respond promptly and do exactly what is asked; arguing with a proctor has never raised a score. One failed room scan costs more points in stress than any topic review gains, so photograph your clean desk setup the night before as your own compliance checklist.
Test centers: the same discipline, different building
Arrive 30 minutes early with the IDs from your confirmation email (government photo ID plus the backup the vendor names, names matching registration). Expect photo, signature, lockers for belongings, and either a whiteboard or an on-screen notepad depending on vendor and exam. Ask the administrator before touching anything: where the bathroom is, whether breaks pause anything (they do not), how to summon help, and how the question-flagging UI works. Test the noise level honestly: if the room hums, request earplugs or the provided headphones immediately rather than toughing it out for two hours. Seat comfort matters on 130-minute sittings; adjust the chair and screen before starting because mid-exam fidgeting breaks concentration rhythms. Nothing studied enters the building: no phone, no notes, no lucky flashcards in pockets. The CompTIA exam-day checklist covers center rituals in more detail and transfers directly.
Per-exam time budgets and formats
AZ-900 at 45 minutes: the pace is brisk but the questions are short, averaging around a minute each against an unpublished count. Answer in one confident pass, flag the few scenario items, return once, commit all. Drag-and-drop matching and hot-area items reward careful reading over speed; slow down for exactly those. SC-500 at 120 minutes: treat it like 60 items at 2 minutes each, read case stems final-sentence-first, and spend the extra budget on the AI-workload scenarios where two answers differ by one scope word. SAA-C03 at 130 minutes for 65 questions is exactly 2 minutes each: checkpoints at 16 questions per half hour, flag-and-return for the long architecture comparisons, never exceeding 3 minutes on one item. Question formats across vendors: single-answer multiple choice, multi-response (check how many it wants), Yes/No case sets that lock after commit, matching and ordering, and AWS-style scenario stems with decisive words (MOST cost-effective, LEAST operational overhead, HIGHEST availability). The decisive word picks the winner: cost words point to scheduled, serverless, and tiered-storage answers; overhead words point to managed services; availability words point to multi-AZ designs. The subnet tool gets one final evening only if hybrid-networking stems still wobble; otherwise trust preparation.
Scoring quirks that calm nerves
Three facts prevent mid-exam spirals. First, scaled scores are not percentages: Microsoft 700 and AWS 720 sit on 100 to 1000 scales set by difficulty calibration, so counting correct answers predicts nothing and wastes attention. Second, trial items exist invisibly on Microsoft exams, so one alien question is evidence of nothing; answer it and release it. Third, no penalty for wrong answers on any of these three exams means blanks are the only true errors; an answered question can score, an empty one cannot. Partial-credit mechanics on multi-part Microsoft items award per correct component, so attempt every checkbox and dropdown even when unsure. If the sitting feels hard around the middle third, that often means the item set is hard, not that you are failing; difficulty is calibrated across forms. Keep the same stuck protocol as every exam in this series: eliminate, commit, flag, move within the per-item budget, return with banked time. And protect the ending: the last 10 minutes belong to flagged returns and blank checks, never to new reasoning on settled answers.
After: reports, retakes, and records
Results arrive fast: Microsoft shows most scores within minutes (lab-bearing exams take longer, beta exams wait for live release), AWS posts to the certification account typically within a day, and both provide per-area bars showing strength and weakness. Read the bars even on a pass: the short bar names your first deepening project (often identity or cost design). Retake rules are humane but priced: Microsoft requires 24 hours after a first failed attempt with escalating waits after, AWS enforces a waiting period between attempts, and every attempt costs the full fee, so rebook from the report rather than from feelings. Update the certification profile, download the badge, and record the credential ID where employers verify it. Then choose the next step deliberately on the which-cert tool: AZ-900 graduates go to the SC-500 plan for defense or administrator tracks, SAA-C03 holders go deeper into networking or security specialties, and everyone updates the resume with exact exam codes while the details are fresh.
Who wrote this
SecLern Editorial. Timings, fees, scoring, and proctoring rules were read from the Microsoft and AWS pages on 2026-10-18. Room-failure warnings come from our student reports: online sittings fail on environment more often than on content.