Microsoft AZ-900: Skills Candidates Struggle With
People rarely fail to understand Microsoft Azure Fundamentals because they have never seen a virtual machine or a subscription. They struggle when an exam scenario places several familiar terms close together and asks them to distinguish service responsibility, resource scope or the appropriate management tool. The Microsoft AZ-900 blueprint updated July 20, 2026 covers cloud concepts (25–30%), Azure architecture and services (35–40%), and management and governance (30–35%). A useful final review should test the boundary between concepts, not recite their definitions yet again.
This is a diagnostic guide, not another timetable. For each contrast below, first make a decision without looking at the answer, then explain which detail would make you change it. Do not turn these examples into a memorized answer key: the same Azure product can be appropriate or inappropriate depending on the requirement.
A team wants to host a web application and reduce operating-system maintenance. One candidate proposes virtual machines because Azure manages the datacenter. Another recommends Azure App Service because the organization wants to avoid most server patching. Both use Microsoft’s infrastructure, but the operating responsibilities differ. Azure secures the underlying cloud infrastructure in either case. With virtual machines, the customer is generally responsible for guest OS configuration, patches, installed applications, identity, and data. With a managed application service, Microsoft takes on more platform operation while the customer retains responsibility for application behavior, identity, data protection, and appropriate service configuration.
The decisive clue is the requested control boundary. If the application depends on custom kernel behavior or direct OS administration, IaaS may fit. If the priority is deploying and scaling a conventional web application with less host administration, PaaS can be more suitable. “Serverless” is not synonymous with “free,” nor does managed hosting remove the need to plan security, logging, availability and cost.
Suppose a service must tolerate the failure of one datacenter within its region. Placing resources in two availability zones may meet that local failure requirement when the selected service supports the architecture. Moving data to a second geographic region addresses a different failure scope and often adds cost, latency, consistency and operational complexity. An availability zone is not a separate Azure region, and a region pair is not a guarantee that every service automatically fails over.
Now change the scenario: an administrator accidentally deletes valid customer data. More regional copies may reproduce the deletion. The relevant protection could be versioning, retention, backups, or tested recovery depending on the service. The diagnostic question is not “what is the most redundant option?” It is “which exact failure is the design required to survive, and how is recovery verified?”
Management groups organize subscriptions so governance can operate across a larger hierarchy. Subscriptions are billing and management boundaries for resources. Resource groups contain resources within one subscription and support grouped lifecycle management. The same Azure resource is not placed into several resource groups to make policy apply at different organizational levels.
Imagine headquarters wants every subscription under its management group to disallow particular public-resource configurations, while one application team needs permission to restart two virtual machines. The organization-wide configuration control points toward Azure Policy at an appropriate scope. The restart permission points toward an Azure role assignment covering the specific machines or resource group. Applying a resource lock would solve neither request: locks guard against certain management operations, not against every undesired configuration or unauthorized action.
The key distinction is the question being asked. Policy evaluates or enforces what resource configurations are permitted; Azure RBAC determines which principal may perform specific Azure operations. Tags provide metadata for organization and cost views; they are not authorization rules. A candidate who can identify the question will reject distractors even when several services appear in the same scenario.
A support engineer authenticates with Microsoft Entra ID but receives a denied access message when attempting to read storage data. Authentication established identity; it did not automatically authorize that data operation. The solution may involve a suitable data-plane role assignment, an application-level permission, a network restriction, or another control. Granting subscription Owner to stop an error is a poor default because the role is far broader than a data-reading task.
Make the scenario harder by adding a private endpoint. The private endpoint can shape how the service is reached, but it does not decide whether an authenticated user may read a particular object. Likewise, enabling multifactor authentication strengthens sign-in assurance without replacing fine-grained authorization. AZ-900 is not asking for every role definition or storage setting, but it does expect candidates to separate identity, resource permissions, network reachability, and security posture.
A company has user-uploaded pictures, a shared folder accessed through file protocols, and virtual-machine operating-system disks. These are different data shapes. Azure Blob Storage is commonly suited to object data, Azure Files to managed file shares, and Azure managed disks to VM block storage. A product with a lower headline capacity rate can be the wrong choice when an application requires file locking, a particular protocol, low latency or transactional behavior.
Replication is another independent decision. Locally redundant, zone-redundant and geographically redundant patterns address different failures and vary by service or account options. Storage tiers and operations charges also influence cost. A useful classification exercise identifies object versus file versus disk first, then the durability, access frequency, recovery and security requirements; pricing should follow from those needs instead of selecting the storage family for the lowest figure alone.
An Azure VNet and subnet organize private network address space. VNet peering connects supported virtual networks but does not universally imply transitive routing. A VPN Gateway and ExpressRoute address hybrid connections with different paths and security characteristics. Azure DNS concerns name resolution; a private endpoint exposes a supported service through private addressing but still depends on correct DNS and authorization. A load balancer distributes traffic under a particular model; a Web Application Firewall inspects application-layer requests according to policy.
For a candidate, the best test is to trace an entire request. Where is the client, what name must resolve, how does the packet reach the target, and which control can deny it? If the browser reports a timeout, that does not by itself show that identity failed; if a service rejects a token, network reachability might be functioning perfectly. AZ-104 administration goes deeper into troubleshooting these paths, but fundamentals candidates must identify the role of each service family.
The Azure Pricing Calculator estimates before deployment. Cost Management helps examine usage and spending; budgets can notify teams when thresholds are crossed. A budget notification does not ordinarily shut down the resources that triggered it. Azure Advisor may recommend actions to improve cost, reliability or other design dimensions; it is not a purchase approval or an automatic cost cap.
Consider a test environment whose virtual machines run overnight. The relevant expense may be the VM runtime, attached storage, network transfer, monitoring data and any eligible commitments—not simply the resource count. Scheduling a deallocation might reduce eligible compute charges, but disks and other resources can continue to incur cost. Tags help attribute expense when applied consistently, but they are not automatically inherited in every billing context. Estimate, observe, investigate and optimize are separate actions.
Two further traps appear when an apparently correct service is used at the wrong scope. A candidate may know that Service Health reports Azure incidents and still choose it for measuring an application’s request latency; the correct first investigative family is monitoring and application telemetry. Another may know that a resource lock can stop deletion but assume it prevents changes inside an application database. Locks apply to supported Azure management operations, not to every data-plane write. Naming the target operation makes the distinction visible.
A useful practice partner changes one word in a scenario and asks whether the choice should change. “Can the employee sign in?” becomes “may the signed-in employee read the blob?” “Survive a zonal failure” becomes “restore a deleted record.” “Estimate cost before launch” becomes “identify why spending rose yesterday.” If your answer remains unchanged in all three pairs, the category boundaries are still weak. That is a more revealing test than scoring a long run of definition-only flashcards.
In the final review, write seven short scenarios that pair two apparently plausible Azure terms. Explain the controlling requirement and what evidence would disprove your choice. You might contrast availability zones with backups, Entra sign-in with Azure data-plane authorization, RBAC with Policy, PaaS with IaaS, or Azure Monitor with Service Health. Another student should be able to challenge your answer by changing one condition.
The adjacent Azure Fundamentals certification material is useful for filling factual gaps, but doing more passive reading is not the solution when the real problem is choosing among closely related concepts. The practical sign of AZ-900 readiness is being able to name the layer, responsibility, service purpose and failure being described before looking at the answer choices.