cert-bank

Guides

이 글을 한국어로 읽기

AZ-900 Study Guide: Azure Fundamentals in Two Weeks, and the Look-Alike Services That Trip People Up

AZ-900 (Microsoft Azure Fundamentals) is the entry exam for Azure, and most of it can be learned in two weeks. What makes people fail is rarely a missing concept. It is the many pairs of Azure tools with similar names and overlapping jobs: Azure Policy and RBAC, the pricing calculator and the TCO calculator, Service Health and Azure Advisor. This guide gives you a two-week plan and a table of those look-alikes.

Study guide · Microsoft Azure Fundamentals (AZ-900)

AZ-900 Study Guide: Azure Fundamentals in Two Weeks, and the Look-Alike Services That Trip People Up

What you are walking into

  • Length: 45 minutes. Microsoft does not publish the number of questions.
  • Passing score: 700 on a scale of 1–1,000.
  • Question types: multiple choice, yes/no statement sets, drag and drop and hot area (click the right spot) items.
  • Skills measured: Describe cloud concepts (25–30%), Describe Azure architecture and services (35–40%), Describe Azure management and governance (30–35%).

Yes/no sets deserve a note: each statement is judged on its own, and they are where careless reading costs the most.

Two-week plan

Days 1–3: Cloud concepts

Capital versus operational expenditure and the consumption-based model; public, private and hybrid cloud; IaaS, PaaS and SaaS and who manages what in each (the shared responsibility model); high availability, scalability, elasticity, reliability, predictability, security and governance as cloud benefits. These questions are definitional, so learn the precise wording: scalability is adding resources, elasticity is adding and removing them automatically with demand.

Beginner tip: many Microsoft Learn modules for AZ-900 include a free sandbox: a temporary Azure subscription that needs no credit card and disappears after a few hours. Use it to create a resource group, a storage account and a small VM. Seeing the hierarchy of subscription, resource group and resource in the portal once makes the governance questions far easier.

Days 4–9: Architecture and services

  • Structure: regions, region pairs, availability zones, sovereign regions; the hierarchy management groups → subscriptions → resource groups → resources.
  • Compute: Virtual Machines, VM Scale Sets, availability sets, Azure Virtual Desktop, containers (Container Instances, AKS), Azure Functions, App Service.
  • Networking: virtual networks, subnets, peering, VPN Gateway versus ExpressRoute, Azure DNS, public and private endpoints.
  • Storage: Blob, Files, Queues, Disks; access tiers (hot, cool, cold, archive); redundancy options LRS, ZRS, GRS, GZRS; moving data with AzCopy, Storage Explorer, File Sync, Azure Migrate and Data Box.
  • Identity and security: Microsoft Entra ID, single sign-on, MFA, passwordless, Conditional Access, external identities (B2B), Zero Trust, defence in depth, Microsoft Defender for Cloud.

Days 10–12: Management and governance

Factors that affect cost, the pricing and TCO calculators, Cost Management and tags; Microsoft Purview, Azure Policy and resource locks; Azure Resource Manager, ARM templates and Bicep, Azure Arc; Azure Monitor, Log Analytics, Application Insights, Azure Advisor and Service Health.

Days 13–14: Mixed practice

Do mixed practice sets and, for every mistake, find which look-alike pair below caused it.

Where Azure's governance tools act in the resource hierarchy
Management groups
Azure Policy and RBAC assigned here apply to every subscription below
Subscriptions
Billing boundary · Cost Management budgets · Quotas
Resource groups
Lifecycle unit: deploy and delete together · Locks (CanNotDelete, ReadOnly) · Tags
Resources
VMs, storage accounts, VNets ... · Each inherits policy, roles and locks from above
Policy, RBAC and locks are inherited downwards: assign them as high as the rule really applies.

The look-alikes table

PairHow to tell them apart
Azure Policy vs Azure RBACRBAC controls who can do something. Policy controls what resources may look like, whoever creates them ("only these regions", "tags required").
Resource lock vs RBACA lock (CanNotDelete or ReadOnly) applies to everyone, even an Owner, until the lock is removed. It protects against accidents, not against people without permission.
Pricing calculator vs TCO calculatorPricing calculator: estimate the cost of Azure services you plan to use. TCO calculator: compare running workloads on premises with running them in Azure.
Service Health vs Azure Advisor vs Azure MonitorService Health: incidents and planned maintenance affecting your services and regions. Advisor: recommendations to improve cost, security, reliability and performance. Monitor: metrics and logs from your own resources.
Availability set vs availability zonesAn availability set spreads VMs across racks (fault and update domains) in one datacenter. Availability zones are separate datacenters in a region, so they also survive a datacenter failure.
VPN Gateway vs ExpressRouteVPN Gateway: encrypted tunnel over the public internet. ExpressRoute: private connection through a provider that does not go over the internet, with more predictable performance.
ZRS vs GRSZRS copies data across three zones in one region (survives a zone failure). GRS copies it to the paired region (survives a regional outage). GZRS does both.
Archive tier vs cool tierArchive is offline: a blob must be rehydrated, which can take hours, before it can be read. Cool and cold are online, just cheaper to store and dearer to access.
Microsoft Entra ID vs Active Directory Domain ServicesEntra ID is the cloud identity service for apps and Microsoft 365 (OAuth, SAML, OpenID Connect). AD DS is the on-premises directory with domains, Kerberos and Group Policy.
Azure Arc vs Azure Resource ManagerResource Manager is how every Azure resource is deployed and managed. Arc extends that management to servers and Kubernetes clusters outside Azure, on premises or in other clouds.
Going deeper: why region pairs exist

Most Azure regions are paired with another region in the same geography, usually a few hundred kilometres away. The pairing is not only a backup address. Microsoft rolls out platform updates to the two regions of a pair one after the other, so a faulty update is less likely to hit both. In a widespread outage, recovery of one region in each pair is prioritised. And geo-redundant storage (GRS and GZRS) copies data to the paired region.

Some newer regions have no pair; they rely on availability zones instead, and services that depend on pairing work differently there. For AZ-900 the rule is enough: zones protect against a datacenter failure, a paired region against a regional one.

Reading the questions

Among the 225 AZ-900 questions we wrote for this site, Virtual Machines, Azure Policy, Microsoft Entra ID, Resource Manager and Cost Management come up most often, and about one question in six asks you to pick two answers. Many questions describe a goal ("prevent anyone from creating resources outside Europe") rather than naming a tool. Translate the goal into who, what or where first: who → RBAC, what a resource may be → Policy, accidental deletion → lock.

Practise

Practise in the question bank: every question explains each option, right and wrong. Start with the domain you just studied, then take a timed mock exam.

Skills measured as listed in Microsoft's AZ-900 study guide; Microsoft updates the outline regularly, so check the current version before you book.