The key insight before you start
AZ-900 rarely asks "what is X?" It asks "a company needs to achieve Y — which service/tool/model fits?" Passing is therefore a decision-making skill, not a memorisation exercise.
This changes how you should study: reading documentation builds recognition, but only scenario practice builds the selection reflex the exam actually tests. Plan your fortnight so at least half your time is spent answering questions and reviewing explanations, not reading.
Week 1 — build the map
Days 1–2: Cloud Concepts. Work through the shared responsibility model until you can place any responsibility (patching, physical security, data, identities) in the right column for IaaS, PaaS, and SaaS without thinking. Learn CapEx vs OpEx, the deployment models, and the scalability/elasticity distinction.
Days 3–5: Azure Architecture and Services — the biggest domain. Focus on decision pairs the exam loves: VM vs App Service vs Functions; ACI vs AKS; Blob vs Files vs Queues vs Disks; VPN vs ExpressRoute; Load Balancer vs Application Gateway vs Front Door; LRS vs ZRS vs GRS. For each pair, know the one-sentence rule for when each side wins.
Days 6–7: Take Mock Exam Set 1 in Study Mode. Read every explanation, including for questions you got right. Note your weakest domain — that is where Week 2 starts.
Week 2 — drill and rehearse
Days 8–9: Management and Governance. This domain fails more prepared-feeling candidates than any other, because beginners skim it. Learn the tool-to-question mapping cold: Pricing Calculator vs TCO Calculator; Policy vs RBAC; Advisor vs Monitor vs Service Health; budgets (alert, don't stop); locks (bind Owners too); tags (don't inherit).
Days 10–11: Quick Drill your weakest domain from the Set 1 results until you consistently score above 80%. Then take Sets 2 and 3 in Study Mode.
Days 12–13: Take Set 4 in Study Mode, then read the Cheat Sheet twice — once slowly, once fast.
Day 14: Dress rehearsal. Take Set 5 in Exam Mode under the full 65-minute clock. Score 80%+ and you are ready. Below 70%, delay the booking a few days and drill the gap — the real exam pass mark is 700/1000.
Exam technique on the day
Time is generous: 65 minutes for 40–60 questions leaves over a minute each. Do not rush.
Read the scenario's requirement words carefully. "Lowest cost" points to different answers than "highest availability" for the same setup — the exam deliberately writes scenarios where several services could work but one best fits the stated priority.
Eliminate before selecting. Two options are usually obviously wrong; deciding between the remaining pair against the requirement is the real task.
Flag and move on when stuck — the review screen lets you return. An unanswered question is guaranteed zero; there is no penalty for guessing.
Watch for absolute words in options: "always", "never", "all", and "guarantees" are usually wrong in cloud contexts, where answers are conditional by nature.
The five traps that fail candidates
One: assuming tags inherit from resource groups. They do not — a policy must copy them.
Two: believing budgets stop spending. Budgets only alert; nothing is switched off at the limit.
Three: thinking Owners bypass resource locks. Locks bind everyone until explicitly removed.
Four: confusing shutdown with deallocation. Shutting down inside the OS keeps compute billing; only deallocating (portal Stop) releases the hardware.
Five: mixing up the calculators. Pricing Calculator estimates a planned Azure build; TCO Calculator compares existing on-premises costs against Azure. Exam questions hinge on exactly this distinction.
All five appear throughout our question banks — if you have drilled the sets, you will recognise them instantly on exam day.
Your free preparation tools
Everything in this plan is on this site — free, no signup.