Common AZ-900 Exam Scenarios and Practice
Key Takeaways
- Scenario items reward matching a service to a business need, not reciting definitions — read for keywords like 'most cost-effective' or 'minimum administrative effort'.
- Cost-effective usually means Reserved Instances (steady load), Spot VMs (interruptible batch), or serverless (bursty) — rarely the most powerful option.
- Governance keywords map cleanly: enforce rules = Azure Policy, who-can-do = RBAC, prevent deletion = resource locks, classify data = Microsoft Purview.
- Migration vocabulary: rehost (lift-and-shift), refactor (to PaaS), rearchitect (cloud-native), rebuild (start over).
- Read the whole question and all options; the most impressive-sounding service is frequently a distractor.
Quick Answer: Scenario questions are keyword puzzles. Most cost-effective → Reserved Instances / Spot / serverless. Enforce a rule → Azure Policy. Who can do what → RBAC. Prevent deletion → resource lock. Secure RDP without a public IP → Azure Bastion. Decode the keyword, ignore the impressive-but-wrong distractor.
Pattern 1: "Which service should you use?"
These give a requirement and ask for the best-fit service. Match on the verb and the constraint:
| The requirement says... | Answer |
|---|---|
| "full control over the OS" | Azure VMs (IaaS) |
| "host a web app, no server management" | Azure App Service (PaaS) |
| "run code only when an event fires, pay per run" | Azure Functions (serverless) |
| "run a container fast with no orchestration" | Container Instances / Container Apps |
| "orchestrate many microservice containers" | Azure Kubernetes Service (AKS) |
| "store images, video, backups" | Azure Blob Storage |
| "globally distributed, low-latency NoSQL" | Azure Cosmos DB |
| "migrate SQL Server with minimal code change" | Azure SQL Managed Instance |
| "store secrets, keys, certificates" | Azure Key Vault |
| "automate a business workflow, low code" | Azure Logic Apps |
Trap: App Service vs. VMs hinges on OS access. If the scenario says they do not need OS-level control, choose App Service; VMs are the trap that requires managing the OS.
Pattern 2: "Most cost-effective solution"
The cheapest answer depends on the workload shape, not raw power:
| Workload shape | Cheapest fit |
|---|---|
| Predictable, runs 24x7 for 1-3 years | Reserved Instances (up to ~72% off) |
| Fault-tolerant batch that can be evicted | Spot VMs (up to ~90% off) |
| Bursty, event-driven, idle most of the time | Azure Functions (Consumption plan) |
| Variable but must stay up | Pay-as-you-go with autoscale |
| You already own Windows/SQL licenses | Azure Hybrid Benefit |
| Rarely read data | Cool / Cold / Archive storage tiers |
Worked example: A nightly report job tolerates interruption and restart and must cost as little as possible. The eviction-tolerant batch cue points to Spot VMs, not Reserved Instances (which suit always-on workloads).
Pattern 3: "Compliance and governance"
| The requirement says... | Solution |
|---|---|
| "restrict which regions resources can deploy to" | Azure Policy (Allowed Locations) |
| "prevent accidental deletion of production" | Resource lock (CanNotDelete) |
| "track and report cost by department" | Tags + Cost Management |
| "force all storage accounts to use encryption" | Azure Policy |
| "control who can create resources" | RBAC role assignment |
| "classify and govern data org-wide" | Microsoft Purview |
| "prove HIPAA/GDPR/PCI compliance" | Trust Center + Compliance Manager |
Trap: Azure Policy vs. RBAC. Policy governs what a resource may be/do (region, SKU, encryption); RBAC governs who may act. A question about allowed configurations is Policy; a question about user permissions is RBAC.
Pattern 4: "Security and identity"
| The requirement says... | Solution |
|---|---|
| "require a second factor to sign in" | Multi-Factor Authentication (MFA) |
| "sign in once, reach all apps" | Single Sign-On (SSO) |
| "block sign-in from risky locations/devices" | Conditional Access |
| "same identity on-prem and in cloud" | Microsoft Entra Connect (hybrid identity) |
| "detect and respond to threats, SIEM/SOAR" | Microsoft Sentinel |
| "absorb large DDoS attacks" | Azure DDoS Protection |
| "RDP/SSH to a VM with no public IP" | Azure Bastion |
How to decode a scenario stem under time pressure
With roughly 40-60 questions in 45 minutes you have well under a minute per item, so a fast, repeatable decoding habit matters more than memorizing every service. First, find the goal keyword — the phrase that ranks the answers. "Most cost-effective" tells you to optimize price, so you weigh Reserved Instances, Spot, and serverless rather than the most powerful VM. "Minimum administrative effort" pushes you toward managed and SaaS options and away from raw VMs. "Maximum availability" steers you toward zones, region pairs, and geo-redundant storage.
Second, find the constraint — an OS-access requirement, an interruption-tolerance note, a compliance mandate — because the constraint usually eliminates two of the four options outright.
Third, beware the distractor pattern. AZ-900 reliably offers one impressive-sounding service that is wrong for the stated need: AKS when no orchestration is required, a three-year Reserved Instance for an interruptible batch job, or Azure Firewall when the question is really about who-can-do-what (RBAC). When two answers both look plausible, re-read the last sentence of the stem; the deciding detail is frequently parked there.
Finally, if you are genuinely unsure, eliminate the clearly wrong options, make your best choice, flag the item, and move on — every question is worth the same, there is no penalty for guessing, and leaving an item blank can only cost points. Banking the easy questions first protects your time for the few that need real thought.
Migration vocabulary (the four R's)
Migration scenarios test which strategy fits the goal:
- Rehost — "lift-and-shift" VMs as-is; fastest, least change.
- Refactor — minor changes to move onto PaaS (e.g., App Service).
- Rearchitect — redesign into cloud-native pieces (containers, microservices).
- Rebuild — discard and rewrite from scratch.
Final practice tips
- Read the whole stem — the decisive constraint often hides in the last sentence.
- Read all options — eliminate clear losers before choosing.
- Anchor on the business need, not the flashiest service.
- Hunt for keywords — "most cost-effective", "minimum administrative effort", "maximum availability" each steer toward a specific answer.
- Manage time — about 45 minutes for 40-60 items means under a minute each; flag and move on.
Final Reminder: AZ-900 is foundational. You never configure services or write code — you decode the requirement, map the keyword to the right service, and pick the best business fit. Eliminate distractors, trust your preparation, and answer every question.
A startup wants to host a web application with minimum administrative effort and does NOT need operating-system access. Which service is the best fit?
A nightly data-processing job can be safely interrupted and restarted, and the team wants the lowest possible compute cost. Which option is best?
An administrator must ensure that all new storage accounts are created with encryption enabled across the whole subscription. Which feature enforces this?
Order the Azure resource hierarchy from HIGHEST (broadest scope) to LOWEST (most specific):
Arrange the items in the correct order