AZ-900 study scenarios: three profiles
How you should study for AZ-900 depends on which of its three skill areas already feels familiar. The exam is 45 minutes, needs 700 out of 1000, and spreads its weight as 25-30% cloud concepts, 35-40% Azure architecture and services, and 30-35% management and governance. The same four-week plan fits most people, but the hours inside it move depending on where you start.
Example profiles, not real people. The profiles below are illustrative planning examples built from the official exam outline. They are not reviews or reports of anyone’s result.
Profile 1: the on-premises administrator who has not used Azure
Starting point. This candidate already runs servers, networks and directory services. Virtual machines, subnets, DNS, VPNs and permissions are daily vocabulary. The concepts exist; the Microsoft names do not.
Where the time goes. The architecture and services domain (35-40%) is mostly familiar ground with new labels, so the effort is in the details that on-premises work never exposes: regions, region pairs and availability zones, the management group to subscription to resource group hierarchy, and storage redundancy names such as LRS, ZRS, GRS and GZRS. The management and governance domain (30-35%) is the real gap: cost management, the pricing calculator, Azure Policy, resource locks, Purview and Azure Arc. Cloud concepts (25-30%) looks easy but asks for exact definitions of shared responsibility and consumption-based pricing.
The trap. Answering from practical experience instead of from Microsoft’s vocabulary. A question about governance may want “Azure Policy” where a sysadmin’s instinct says “role assignment”.
Order. Management and governance first, then storage and identity, then cloud concepts, with architecture last as a check.
Time budget. The study plan says two weeks is usually enough for someone already using Azure; this profile knows the concepts but not yet the Azure names, so allow a little more. A reasonable planning assumption is two to three weeks at four to six hours a week, so roughly eight to eighteen hours in total.
Profile 2: the colleague from a non-technical role
Starting point. Someone in sales, finance, procurement or project management who sits in meetings with Azure teams. They understand cost, contracts and risk, and little about networks or storage.
Where the time goes. The prerequisites page suggests five or six weeks rather than four, with the extra week spent on background: IP addresses, subnets, DNS, servers and virtual machines. After that, the largest domain, architecture and services at 35-40%, takes the most hours because it holds the most unfamiliar topics: compute types, virtual networking, storage tiers and identity. Cloud concepts (25-30%) is where this profile gains time back, because capital versus operational expenditure and pricing models are business ideas.
The trap. Over-studying the comfortable domain. Cost and benefits topics feel productive, but they are only part of the 30-35% governance domain and the 25-30% concepts domain. The exam still asks which service fits a scenario.
Order. Background week, then cloud concepts, then architecture split across two weeks, then governance and review.
Time budget. A reasonable planning assumption is five to six weeks at four to six hours a week, which is about twenty to thirty-six hours. Creating a free Azure account and reading the portal’s create screens without deploying anything helps the names stick.
Profile 3: the engineer who knows another cloud
Starting point. A developer or operations engineer with production experience on a different cloud. Regions, zones, IaaS, PaaS, SaaS and shared responsibility are old ideas.
Where the time goes. Week one is light. The investment is in mapping: which Azure service corresponds to which familiar one, and where Azure’s structure differs, especially subscriptions and management groups, Microsoft Entra ID, and the Azure-specific names for storage redundancy and access tiers. The governance domain (30-35%) is the second target, because tools such as Azure Advisor, Service Health and Azure Monitor with Log Analytics have local names.
The trap. Assuming one-to-one equivalence. Two services can look alike and still differ in the one detail a question tests.
Order. Architecture and services, then identity and security, then governance, then a quick pass over concepts.
Time budget. The study plan says to spend week one lightly and put the time into weeks two and three. A reasonable planning assumption is three weeks at four to six hours a week, so twelve to eighteen hours.
The three AZ-900 profiles compared
| Profile | Front-loaded domains | Main risk |
|---|---|---|
| On-premises administrator | Management and governance (30-35%), storage and identity | Answering from habit, not Microsoft terms |
| Non-technical colleague | Background, then architecture and services (35-40%) | Staying in the comfortable cost topics |
| Engineer from another cloud | Architecture and services, then governance | Assuming service names map one to one |
None of these budgets guarantees a pass. They are starting points for a calendar, and your practice scores should move them.
How to check which AZ-900 profile fits before booking
Take the free practice test cold and sort every miss by domain. If misses cluster in governance, you are profile 1. If they are spread across architecture and basic networking vocabulary, read the prerequisites first. Then use the four-week study plan and check the sample questions for style. The exam format page explains the time limit, the question types and the retake rules. If you are deciding between this and the AI fundamentals exam, AI-901 is the closest sibling hub, and AZ-900 versus AI-901 covers the overlap.