AZ-900 Cheat Sheet
Quick-reference summary of the key facts for the AZ-900 exam.
AZ-900 cheat sheet — one-screen revision
Exam: 45 minutes, roughly 40–60 questions (Microsoft publishes no fixed count), 700 to pass on a 100–1000 scaled score, $99 USD, no prerequisites, and the certification never expires. Skills measured as of July 20, 2026.
Domain 1 — Describe cloud concepts (25–30%)
- Cloud computing: delivery of computing services over the internet, pay-as-you-go. Five characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service.
- Cloud models: public (shared, provider-owned), private (dedicated to one organisation), hybrid (public + private bound together). Multi-cloud is a strategy, not one of the three models.
- Shared responsibility: customer ALWAYS owns data, accounts, and access; provider ALWAYS owns physical infrastructure. IaaS: customer owns the OS. PaaS: provider owns the OS and runtime. SaaS: provider owns almost everything except data/accounts/access.
- CapEx vs OpEx: buying hardware upfront is CapEx; paying monthly for consumed services is OpEx. The consumption-based model = pay for what you use.
- Pricing: pay-as-you-go (flexible, no commitment) · reserved instances (1–3 year commitment, big discount, steady workloads) · savings plans (commit to hourly spend, flexible across resources) · Azure Hybrid Benefit (reuse existing licences) · spot (deep discount, can be reclaimed, interruptible work only).
- Serverless: provider manages servers; code runs on events; pay per execution; scales to zero. Example: Azure Functions.
- Benefits: high availability (stays up) · scalability (change size; vertical = bigger, horizontal = more instances) · elasticity (automatic scaling with demand) · reliability (recover from failures) · disaster recovery (restore after a region/datacenter failure) · predictability (cost + performance) · security · governance · manageability · agility · geo-distribution.
- Service types: IaaS = VMs, you manage the OS · PaaS = App Service, SQL Database, Functions, provider manages the platform · SaaS = Microsoft 365, Dynamics 365, finished apps. Azure SQL Database is PaaS; SQL Server on a VM is IaaS.
Domain 2 — Describe Azure architecture and services (35–40%)
- Regions: geographic area with one or more datacenters; 60+ worldwide. Region pairs: each region paired with another ≥300 miles away, same geography; updates roll out one at a time; geo-replication target. Sovereign regions: isolated Azure for governments (Azure Government, Azure China).
- Availability zones: physically separate datacenters in a region (≥3 where supported); VMs across zones = 99.99% SLA. Availability sets: fault domains + update domains inside one datacenter; 2+ VMs = 99.95% SLA. Single VM with premium SSD = 99.9%.
- Hierarchy (top → bottom): management groups → subscriptions → resource groups → resources. Management groups = governance across subscriptions. Subscriptions = billing + access boundary. Resource groups = one resource belongs to exactly one group; groups cannot nest; deleting a group deletes its contents; resources in a group can be in different regions.
- Compute: VMs (IaaS, full OS control) · containers (share host OS, start in seconds; Container Instances, AKS) · Functions (serverless, event-driven). VM Scale Sets = identical autoscaling VMs. Azure Virtual Desktop = Windows desktops from Azure. VM needs: resource group, virtual network, network interface, storage.
- App hosting: web apps (App Service, deployment slots for zero-downtime releases) · containers · VMs.
- Networking: VNet (isolated private network, one region) · subnets (segments with different rules) · VNet peering (two VNets, Microsoft backbone) · VPN Gateway (encrypted over the internet) · ExpressRoute (private dedicated connection, never the internet) · Azure DNS (hosts DNS zones) · public endpoint (internet-reachable) vs private endpoint (private IP in your VNet).
- Storage: Blob (unstructured objects) · Files (SMB/NFS shares) · Queues (messages) · Tables (NoSQL) · Disks (VM disks). Tiers: Hot (frequent) · Cool (infrequent, 30+ days) · Cold (rare, 90+ days) · Archive (almost never, 180+ days, retrieval takes hours). Redundancy: LRS 3 copies, one datacenter · ZRS 3 copies across zones · GRS 6 copies, two regions · GZRS 6 copies, zones + second region. RA- adds read access to the secondary region.
- Moving data: AzCopy (command-line bulk copy) · Storage Explorer (graphical) · File Sync (sync on-premises file server with Azure Files) · Azure Migrate (assess + migrate servers/apps) · Data Box (physical device, ~100 TB, for huge transfers over slow links).
- Identity: Microsoft Entra ID (cloud directory; formerly Azure AD) · Entra Domain Services (managed domain join, Group Policy, no domain controllers) · SSO (sign in once) · MFA (two or more factors) · passwordless (Authenticator, Windows Hello, FIDO2) · B2B (partners as guests) · B2C (customers) · Conditional Access (if signal, then control — require MFA, block, require compliant device) · RBAC (security principal + role definition + scope; Owner / Contributor / Reader / User Access Administrator; Owner alone can grant access; least privilege, narrowest scope).
- Security: Zero Trust — verify explicitly, least privilege access, assume breach. Defense in depth — physical → identity and access → perimeter → network → compute → application → data. Defender for Cloud — secure score, recommendations, threat detection.
Domain 3 — Describe Azure management and governance (30–35%)
- Cost factors: resource type, size/tier, region, usage time, data egress (ingress is free), commitments and licences.
- Pricing calculator: estimates cost BEFORE deploying. Cost Management: analyses spend AFTER — cost analysis, budgets (alert, do not cap), alerts, recommendations, exports.
- Tags: name-value pairs for cost allocation and organisation; NOT inherited automatically; metadata only (no access control, no enforcement).
- Purview: data governance — discover, map, catalogue, classify data. Policy: rules for resources — Deny (block), Audit (record), Append/Modify (fix), DeployIfNotExists, Disabled; initiatives group policies; Policy does NOT delete non-compliant resources. Locks: CanNotDelete (change yes, delete no) · ReadOnly (neither); inherited by contents; apply to everyone including admins.
- Management tools: portal (web GUI) · Cloud Shell (browser shell, Bash or PowerShell, no install) · Azure CLI (cross-platform az commands) · Azure PowerShell (Az cmdlets). Azure Arc: manage on-premises/multi-cloud servers from Azure. IaC: define infrastructure in files — consistent, repeatable, version-controlled. ARM: the deployment/management layer all requests pass through. ARM templates: declarative JSON, idempotent; what-if previews changes; Bicep compiles to ARM templates.
- Monitoring: Advisor (recommendations: reliability, security, performance, operational excellence, cost) · Service Health (is Azure healthy? status, service issues, planned maintenance, Resource Health) · Monitor (your resources: metrics + logs, Log Analytics workspace + KQL, alerts + action groups) · Application Insights (application performance: requests, response times, failures, availability).
Confusion pairs — decide in seconds
- Zones (datacenter fails) vs sets (rack fails) · Peering (two VNets) vs VPN/ExpressRoute (on-premises ↔ Azure) · ExpressRoute (private) vs VPN Gateway (encrypted internet) · Policy (rules) vs locks (accidents) vs RBAC (who) vs Purview (data) · Advisor (recommendations) vs Service Health (Azure status) vs Monitor (your resources) · Pricing calculator (before) vs Cost Management (after) · Budgets (alert) vs locks (block) · SQL Database (PaaS) vs SQL Server on VM (IaaS) · Archive (cheapest, slowest) vs Hot (frequent access).
Advertisement