AZ-900 — Microsoft Azure Fundamentals Quick Review

Quick Review for Microsoft Azure Fundamentals (AZ-900): cloud concepts, Azure services, security, governance, pricing, and practice focus areas.

Quick Review focus

This independent Quick Review is for candidates preparing for the real Microsoft Azure Fundamentals (AZ-900) exam from Microsoft. Use it to refresh high-yield concepts before moving into topic drills, mock exams, and detailed explanations.

AZ-900 is a recognition-and-understanding exam. You usually need to identify the best Azure service, pricing concept, security control, governance tool, or cloud model from short scenarios. The main challenge is not deep configuration; it is choosing the correct concept quickly and avoiding similar-sounding distractors.

What to know at a glance

AreaHigh-yield review target
Cloud conceptsIaaS, PaaS, SaaS; public, private, hybrid; CapEx vs OpEx; elasticity, scalability, high availability
Azure architectureRegions, availability zones, subscriptions, resource groups, management groups, Azure Resource Manager
ComputeVirtual Machines, App Service, Azure Functions, containers, Azure Kubernetes Service
NetworkingVirtual networks, subnets, NSGs, VPN Gateway, ExpressRoute, Azure Bastion, load balancing options
StorageBlob, Files, Queue, Table, Disk Storage; access tiers; redundancy options
Identity and accessMicrosoft Entra ID, users, groups, tenants, MFA, Conditional Access, RBAC
SecurityShared responsibility, defense in depth, Key Vault, Microsoft Defender for Cloud, Microsoft Sentinel
GovernanceAzure Policy, resource locks, tags, management groups, Azure Blueprints conceptually if encountered
Cost and supportPricing calculator, TCO calculator, Cost Management, reservations, Azure Advisor
MonitoringAzure Monitor, Log Analytics, Application Insights, Service Health, Resource Health

Cloud concepts

Cloud service models

ModelYou manageProvider managesBest clue in a question
IaaSOS, runtime, apps, data, many security settingsPhysical datacenter, hosts, networking foundation“Lift and shift,” custom OS control, virtual machines
PaaSApp code and dataOS, runtime platform, scaling platform, patching foundation“Deploy code without managing servers”
SaaSConfiguration and data usageApplication and underlying platform“Use a complete application” such as email or CRM

Common trap: Virtual Machines are IaaS, even when hosted in Azure. Azure App Service and Azure Functions are PaaS-style services because you do not manage the underlying server OS.

Deployment models

ModelMeaningExam clue
Public cloudCloud resources delivered over the public internet and shared provider infrastructureFast provisioning, consumption-based pricing
Private cloudCloud-like environment dedicated to one organizationMore direct control, often on-premises or dedicated hosting
Hybrid cloudCombines public and private environmentsIntegration between on-premises and Azure
Multi-cloudUses more than one cloud providerAvoid vendor concentration or use specialized provider features

Core cloud benefits

ConceptMeaningCandidate mistake to avoid
High availabilitySystem remains accessible despite failuresDo not confuse with backup
ScalabilityAbility to increase or decrease capacityScaling can be vertical or horizontal
ElasticityAutomatic or rapid scaling based on demandUsually tied to variable workloads
ReliabilityAbility to recover from failureOften supported by redundancy and resilient design
PredictabilityMore consistent performance and cost planningIncludes both performance and financial predictability
SecurityTools and controls to protect systemsCloud does not remove customer security responsibilities
GovernanceEnforcing standards and complianceThink policy, tagging, locks, and scope
ManageabilityAbility to deploy, monitor, and control resourcesIncludes portal, CLI, PowerShell, templates, automation

CapEx vs OpEx

TermMeaningAzure exam angle
Capital expenditureUp-front spending on assets such as datacenters and serversTraditional on-premises purchasing
Operational expenditureOngoing pay-as-you-go operating costCloud consumption model
Consumption-based pricingPay for what you useHelps avoid overprovisioning

Shared responsibility model

The shared responsibility model is one of the most frequently tested AZ-900 concepts. The more managed the service, the more responsibility Microsoft carries for the platform, but the customer still owns identity decisions, data, access, and configuration choices.

ResponsibilityIaaSPaaSSaaS
Physical datacenterMicrosoftMicrosoftMicrosoft
Physical networkMicrosoftMicrosoftMicrosoft
Physical hostsMicrosoftMicrosoftMicrosoft
Operating systemCustomerMicrosoftMicrosoft
Application runtimeCustomerMicrosoftMicrosoft
ApplicationCustomerCustomerMicrosoft
DataCustomerCustomerCustomer
Identities and accessCustomerCustomerCustomer
Endpoint devicesCustomerCustomerCustomer

High-yield rule: Microsoft secures the cloud infrastructure; customers secure what they put in the cloud and how they allow access to it.

Azure architecture and resource organization

Management hierarchy

LevelPurposeExam clue
Management groupOrganize multiple subscriptionsApply governance across subscriptions
SubscriptionBilling, access, and resource boundarySeparate environments, departments, or billing
Resource groupLogical container for resourcesManage lifecycle of related resources
ResourceIndividual service instanceVM, storage account, virtual network, database

Important rules:

  • A resource belongs to one resource group.
  • A resource group belongs to one subscription.
  • Resources in the same resource group do not have to be in the same Azure region.
  • Role assignments and policies can be applied at multiple scopes and inherited downward.
  • Tags help with organization and cost reporting, but tags do not enforce compliance by themselves.

Regions and availability

ConceptMeaningWatch for
RegionGeographic area containing Azure datacentersChoose for latency, compliance, availability, cost
Availability zonePhysically separate datacenter location within a regionProtects against datacenter-level failure
Region pairAzure pairs many regions for resilience planningUseful for disaster recovery design
Sovereign/specialized cloudIsolated cloud for specific government or regulatory needsDo not assume every service is available everywhere

Common trap: Availability zones are inside a region. They are not the same as regions, and they are not the same as resource groups.

Azure Resource Manager

Azure Resource Manager, often called ARM, is the deployment and management layer for Azure resources.

FeatureWhy it matters
Consistent management layerPortal, CLI, PowerShell, templates, and SDKs use ARM
Role-based access control integrationAccess can be controlled by scope
Declarative deploymentARM templates and Bicep define desired infrastructure
Tagging and policy supportGovernance is applied through the management plane

Compute services

ServiceUse whenDo not confuse with
Azure Virtual MachinesNeed OS-level control, custom software, lift-and-shiftApp Service
Virtual Machine Scale SetsNeed many identical VMs that scaleManual VM creation
Azure App ServiceHost web apps, APIs, or mobile back ends without managing serversAzure Functions
Azure FunctionsRun event-driven, serverless codeAlways-on web hosting
Azure Container InstancesRun containers quickly without orchestrating a clusterAKS
Azure Kubernetes ServiceOrchestrate containerized applications at scaleSimple single-container jobs
Azure Virtual DesktopProvide cloud-hosted desktops and appsVM Scale Sets

Compute decision rules

Scenario phraseLikely answer
“Full control over the operating system”Azure Virtual Machines
“Deploy a web app without managing infrastructure”Azure App Service
“Run code in response to an event”Azure Functions
“Run a container quickly without managing servers”Azure Container Instances
“Manage many containers with orchestration”Azure Kubernetes Service
“Provide remote desktops from Azure”Azure Virtual Desktop

Common trap: “Serverless” does not mean no servers exist. It means the customer does not manage the servers.

Storage services

Core storage types

ServiceBest forExam clue
Blob StorageUnstructured object data such as images, videos, backups, logs“Object storage” or “unstructured data”
Azure FilesManaged file shares using SMB/NFS-style access“Lift-and-shift file share”
Queue StorageSimple message queue“Decouple application components”
Table StorageNoSQL key-value style data“Structured NoSQL data”
Disk StoragePersistent disks for Azure VMs“Attach storage to a VM”

Blob access tiers

TierUse caseKey idea
HotFrequently accessed dataHigher storage cost, lower access cost
CoolInfrequently accessed dataLower storage cost, higher access cost
ArchiveRarely accessed dataLowest storage cost, rehydration required before access

Common trap: Archive is not for data that must be immediately readable.

Storage redundancy

OptionProtects againstQuick interpretation
LRSLocal hardware failure within a datacenterLowest redundancy scope
ZRSDatacenter/zone failure within a regionReplicates across availability zones
GRSRegional outage using paired region replicationCross-region protection
GZRSZone redundancy plus geo-replicationStronger regional and zone resilience
RA-GRS / RA-GZRSRead access to secondary copyReadable secondary endpoint

Decision rule: If the question says protect against datacenter failure within the same region, think ZRS. If it says protect against regional outage, think GRS/GZRS.

Networking

Foundational networking concepts

ConceptPurposeCandidate mistake
Virtual networkPrivate network boundary in AzureNot the same as a subnet
SubnetSegment inside a virtual networkUsed to organize and isolate resources
Network security groupAllow/deny inbound and outbound trafficWorks at subnet or NIC level
Route tableControls traffic routingDifferent from NSG filtering
Public IP addressInternet-reachable addressMay increase exposure if misused
Private IP addressInternal network communicationUsed inside VNets and private connectivity

Connectivity services

ServiceUse whenWatch for
VPN GatewayEncrypted connection over the public internetSite-to-site, point-to-site, VNet-to-VNet
ExpressRoutePrivate connection to Microsoft cloud servicesDoes not travel over the public internet
Azure BastionSecure browser-based RDP/SSH to VMsAvoids exposing RDP/SSH public IPs
Azure DNSHost DNS domains and recordsDNS hosting, not web hosting
Private LinkPrivate access to supported Azure servicesKeeps traffic off public endpoint path

Load balancing and traffic distribution

ServiceLayer / purposeBest clue
Azure Load BalancerLayer 4 TCP/UDP load balancingLow-level network load distribution
Application GatewayLayer 7 HTTP/HTTPS routingWeb traffic, URL routing, WAF
Azure Front DoorGlobal HTTP/HTTPS entry pointGlobal web acceleration and routing
Traffic ManagerDNS-based traffic distributionRoutes by DNS responses
Content Delivery NetworkCache static content near usersImprove delivery of static assets

Common trap: Traffic Manager does not directly proxy application traffic; it uses DNS to direct clients.

Identity, access, and security

Microsoft Entra ID

Microsoft Entra ID is Microsoft’s cloud identity and access management service. AZ-900 questions often test whether you can distinguish identity authentication from Azure resource authorization.

ConceptMeaning
TenantDedicated identity instance for an organization
UserIdentity assigned to a person or workload
GroupCollection of users for easier access management
MFARequires additional verification beyond a password
Conditional AccessEnforces access decisions based on signals such as user, device, location, or risk
Single sign-onSign in once to access multiple applications
External identitiesCollaborate with users outside the organization

Authentication vs authorization

TermQuestion it answersExample
Authentication“Who are you?”Sign in with password and MFA
Authorization“What are you allowed to do?”RBAC role assignment on a resource group

Common trap: Microsoft Entra ID authenticates identities. Azure RBAC authorizes management access to Azure resources.

Azure role-based access control

RBAC conceptMeaning
Security principalUser, group, service principal, or managed identity
Role definitionSet of allowed actions
ScopeWhere the role applies: management group, subscription, resource group, or resource
Role assignmentPrincipal + role + scope

High-yield rule: Grant access at the least broad scope that satisfies the requirement.

Security tools

ToolPurposeExam clue
Microsoft Defender for CloudSecurity posture management and workload protectionRecommendations, secure score, threat protection
Microsoft SentinelCloud-native SIEM/SOARSecurity analytics, incidents, automated response
Azure Key VaultStore secrets, keys, and certificatesProtect passwords, API keys, cryptographic keys
Azure FirewallManaged network firewallCentralized network filtering
DDoS ProtectionProtect against distributed denial-of-service attacksNetwork-level attack mitigation
Network security groupsBasic network traffic filteringAllow/deny by protocol, port, source, destination

Defense in depth

Defense in depth means using layered controls rather than relying on a single security mechanism.

LayerExample controls
Physical securityMicrosoft datacenter controls
Identity and accessMFA, Conditional Access, RBAC
PerimeterDDoS Protection, Azure Firewall
NetworkNSGs, segmentation, private endpoints
ComputeEndpoint protection, patching, hardening
ApplicationSecure development, WAF
DataEncryption, Key Vault, access control

Governance and compliance

Governance tools

ToolUse forCommon trap
Azure PolicyEnforce or audit rulesPolicy can deny noncompliant deployments
InitiativeGroup of policiesUseful for broader compliance goals
Resource locksPrevent deletion or modificationLocks are not access permissions
TagsOrganize resources and costsTags do not enforce resource configuration
Management groupsOrganize subscriptionsGood for enterprise governance
Azure ArcManage resources across Azure, on-premises, and other cloudsExtends Azure management

Policy vs RBAC vs locks

NeedBest fit
Prevent creation of resources in disallowed regionsAzure Policy
Allow a user to read but not change resourcesAzure RBAC
Prevent accidental deletion of a resourceResource lock
Track department or cost centerTags
Apply governance across many subscriptionsManagement groups

Common trap: If the scenario says “ensure resources can only be created in approved regions,” choose Azure Policy, not tags.

Compliance and trust resources

ResourcePurpose
Microsoft PurviewData governance, risk, and compliance capabilities
Service Trust PortalCompliance reports, audit information, trust documents
Azure compliance offeringsInformation about Microsoft cloud compliance coverage
Privacy and security documentationUnderstand how Microsoft handles security, privacy, and compliance responsibilities

Pricing, cost management, and service levels

Cost drivers

Cost factorReview point
Resource typeDifferent services have different pricing models
RegionPricing can vary by region
Usage amountCompute time, storage volume, transactions, operations
Data transferInbound is often treated differently from outbound; watch wording
Support planSupport level can affect monthly cost
Reservations/savingsCommitment-based discounts can reduce predictable workload costs
Storage tierHot, cool, and archive trade storage cost against access cost

Cost tools

ToolBest use
Pricing calculatorEstimate cost of planned Azure resources
TCO calculatorCompare on-premises costs with Azure costs
Microsoft Cost ManagementMonitor, analyze, and control current Azure spend
Budgets and alertsNotify when spending approaches thresholds
Azure AdvisorRecommendations for cost, performance, reliability, security, and operational excellence

Common trap: Use the pricing calculator before deployment to estimate Azure service costs. Use Cost Management after resources exist to monitor and manage spending.

Service level concepts

ConceptMeaning
SLAMicrosoft’s service-level commitment for a service or configuration
Composite SLACombined availability of multiple dependent services
Preview serviceFeature not generally available; may have limitations
Public previewAvailable for testing by customers
General availabilityProduction-ready release status

For composite availability, multiply the availability of dependent components when every component is required for the solution to work:

\[ \text{Composite availability} = A_1 \times A_2 \times A_3 \times \cdots \]

Common trap: Adding more required dependencies can reduce composite availability unless the architecture adds redundancy.

Monitoring and management

Monitoring tools

ToolUse forExam clue
Azure MonitorCollect and analyze telemetry across Azure resourcesMetrics, logs, alerts
Log AnalyticsQuery logs using a workspaceAnalyze log data
Application InsightsApplication performance monitoringWeb app performance, failures, dependencies
Azure Service HealthAzure service incidents affecting youRegional/service outage communication
Azure Resource HealthHealth of a specific resourceDiagnose whether a resource is affected
AlertsNotify or trigger actionsThresholds, metrics, logs

Management tools

ToolBest for
Azure portalBrowser-based graphical management
Azure PowerShellScripted management using PowerShell cmdlets
Azure CLICross-platform command-line management
Azure Cloud ShellBrowser-based shell with Azure tools preinstalled
ARM templatesJSON declarative infrastructure deployment
BicepSimpler declarative language for Azure resources
Azure mobile appMonitor and manage resources from mobile devices

Common trap: PowerShell and CLI can often perform similar management tasks, but they use different syntax and are preferred by different administrator workflows.

Scenario decision map

    flowchart TD
	    A[Read the scenario requirement] --> B{Need identity or access?}
	    B -->|Sign-in, MFA, SSO| C[Microsoft Entra ID]
	    B -->|Permissions on Azure resources| D[Azure RBAC]
	    B -->|Prevent noncompliant deployments| E[Azure Policy]
	    A --> F{Need compute hosting?}
	    F -->|OS control| G[Azure Virtual Machines]
	    F -->|Web app without server management| H[Azure App Service]
	    F -->|Event-driven code| I[Azure Functions]
	    F -->|Container orchestration| J[AKS]
	    A --> K{Need connectivity?}
	    K -->|Encrypted over internet| L[VPN Gateway]
	    K -->|Private circuit| M[ExpressRoute]
	    K -->|Secure VM admin without public RDP/SSH| N[Azure Bastion]
	    A --> O{Need cost planning?}
	    O -->|Estimate before deployment| P[Pricing calculator]
	    O -->|Compare on-premises to Azure| Q[TCO calculator]
	    O -->|Analyze current spend| R[Cost Management]

Common AZ-900 traps

TrapCorrect thinking
“Cloud means Microsoft handles all security.”Responsibility is shared; customer still manages data, identity, and access.
“Resource groups are physical locations.”Resource groups are logical containers. Regions are physical/geographic.
“Tags enforce compliance.”Tags organize and report; Azure Policy enforces rules.
“RBAC controls network traffic.”RBAC controls management access; NSGs and firewalls control traffic.
“Availability zones are separate regions.”Zones are separate datacenter locations within a region.
“Archive storage is instantly available.”Archive data must be rehydrated before access.
“ExpressRoute is a VPN.”ExpressRoute is private connectivity; VPN uses encrypted tunnels over the internet.
“Traffic Manager is a load balancer proxy.”Traffic Manager is DNS-based routing.
“App Service gives full OS control.”Use Virtual Machines when full OS control is required.
“Azure Monitor and Service Health are the same.”Azure Monitor tracks telemetry; Service Health reports Azure service issues affecting you.

How to use practice questions effectively

After this Quick Review, use IT Mastery practice to turn recognition into exam-speed decision making.

  1. Start with topic drills for one area at a time, such as identity, pricing, storage, or networking.
  2. Review every missed item with detailed explanations, especially when two Azure services seemed plausible.
  3. Build a short “confusion list” of pairs you mix up, such as Azure Policy vs RBAC or VPN Gateway vs ExpressRoute.
  4. Move to mixed original practice questions once individual topics feel familiar.
  5. Use mock exams to practice pacing, wording recognition, and elimination.

A strong AZ-900 question bank should help you explain why the right answer is right and why the distractors are wrong.

Final quick checklist

Before your next practice set, confirm you can answer these without notes:

  • Which responsibilities remain with the customer in IaaS, PaaS, and SaaS?
  • When should you choose VMs, App Service, Functions, containers, or AKS?
  • What is the difference between a region, availability zone, resource group, and subscription?
  • Which storage service fits blobs, files, queues, tables, and VM disks?
  • When do you choose LRS, ZRS, GRS, or GZRS?
  • How do Microsoft Entra ID, MFA, Conditional Access, and Azure RBAC differ?
  • When should you use Azure Policy, tags, locks, or management groups?
  • Which tool estimates cost before deployment, compares TCO, or monitors current spend?
  • Which monitoring tool fits logs, app performance, service incidents, or resource health?

Next step: take a focused AZ-900 topic drill from the question bank, review the detailed explanations, and repeat this Quick Review for any topic where you miss more than a few questions.

Continue in IT Mastery

Use this Quick Review as a final concept map, then move into IT Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original IT Mastery practice items; they are not official Microsoft questions, copied live-exam content, or exam dumps.

Browse Certification Practice Tests by Exam Family