Home AZ-104 Final Prep
Exam: tomorrow

The night-before AZ-104 guide

You already know VMs and infrastructure, so this guide spends its time on the questions that catch experienced admins: RBAC scope logic, storage rules and limits, backup vault details, and networking edge cases. Take the full practice exam first, then use the sections below on the domains where you scored lowest.

01 · Format

What you're walking into

700passing score out of 1000 (scaled, not a %)
40–60questions, typically about 50
~100 minfor questions; plan on ~2 hours total
No penaltyfor wrong answers, so answer every question
  • Question types: single choice, multi-select ("choose two"), drag-and-drop ordering, hot-area (select values in a dropdown or diagram), and one or two case studies with a long scenario and several questions.
  • Yes/No series: the same goal with a different proposed solution each time. You can't go back to these. Judge each solution only on whether it meets the stated goal.
  • Case studies are timed as their own section. When you leave one, you can't return. Read the requirements tab first, then the questions, then look things up in the scenario.
  • Microsoft Learn is available during the exam (the "open book" feature on role-based exams). It's slow, so use it only to check a specific number or a role name, and only on questions you've flagged.
  • Pacing: about 1.5 minutes per question. Flag anything that takes more than 2 minutes and come back to it.
02 · Weighting

Your risk map

The domain weights come from the published skills outline. The risk ratings are my estimate based on what you told me: strong on VMs and infrastructure, and you've built S2S tunnels by following documentation.

DomainWeightYour riskWhy
Manage Azure identities & governance20–25%HighRBAC scope logic, locks, Policy effects, and Entra licensing are exam favorites that infrastructure work rarely exercises.
Implement & manage storage15–20%HighQuestions here test exact rules: which tier or SKU, which redundancy, which SAS type, minimum retention days.
Deploy & manage compute20–25%Low–MedYour VM experience covers most of this. Review App Service tiers and slots, ACI and Container Apps, and ARM/Bicep.
Implement & manage virtual networking15–20%MediumExpect NSG rule evaluation, peering transit, private vs service endpoints, DNS zones, and load balancer choice.
Monitor & maintain resources10–15%MediumRecovery Services vault vs Backup vault, alert processing rules, data collection rules, and basic KQL.

VPN Gateway isn't listed by name in the current skills outline. Peering with gateway transit and hybrid connectivity questions still come up, so the S2S section below covers what you need without spending the whole night on it.

03 · Schedule

Tonight and tomorrow

Tonight · 0:00–1:45

Take the full practice exam

Use timed conditions: no Microsoft Learn, no pausing. Don't look anything up during the exam. The results screen shows which domains you missed.

Tonight · 1:45–2:45

Review every miss

Read each explanation, then the matching cheat sheet below. Run "Retry missed" once. Stop there.

Tonight · then stop

Sleep

Another hour of cramming is worth less than being rested. A tired brain misreads "NOT" and "least privilege" in question stems.

Morning · 20 min

Numbers & traps

Read "Numbers to memorize" and "Classic traps" only. Do a 10-question practice round in your weakest domain.

04 · Identity & governance · 20–25%

Identity & governance cheat sheet

RBAC scope logic

  • Scope: Management group → Subscription → Resource group → Resource. Assignments inherit downward and are additive.
  • NotActions is not a deny. It only subtracts from that one role, so another role can still grant the same permission.
  • Actual deny assignments are created only by the platform (deployment stacks, managed apps). You can't create one directly.
  • Creating a custom role needs roleDefinitions/write (Owner or User Access Administrator). AssignableScopes controls where the role can be assigned.
  • Management group hierarchy: up to 6 levels below the root, not counting the root and subscription levels.

Roles to know cold

  • Owner: full control plus role assignment.
  • Contributor: full control, can't assign roles.
  • User Access Administrator: assigns roles only. RBAC Administrator: assigns roles, optionally limited by conditions.
  • VM Contributor: manages VMs, with no login access and no rights on the VNet or storage the VM connects to.
  • Storage Account Contributor can list keys, which effectively gives data access. Storage Blob Data * roles are data plane.
  • An Entra Global Admin can elevate to User Access Administrator at root scope (/), under Properties → "Access management for Azure resources".

Locks

  • CanNotDelete (Delete): resources can be changed but not deleted. ReadOnly: no changes and no deletion.
  • Locks apply to everyone, including Owners. An Owner or User Access Administrator can remove the lock first.
  • Locks are inherited by child resources. When locks conflict, the most restrictive one wins.
  • Locks are control plane only. A ReadOnly lock on a storage account blocks listKeys (a POST), so portal access that uses a key fails, but Entra data-plane access still works.

Azure Policy

  • Effects: Deny, Audit, Append, Modify, DeployIfNotExists, AuditIfNotExists, Disabled.
  • Deny blocks only new creates and updates. Existing resources are flagged non-compliant and keep running.
  • Fixing existing resources needs a remediation task (Modify or DINE effects, using a managed identity).
  • An initiative is a set of policies. Exemptions and exclusions remove scopes from an assignment.
  • Tags are not inherited. Use the "Inherit a tag from the resource group" policy (Modify effect) plus remediation.

Entra ID

  • Group types: Security or Microsoft 365. Membership: Assigned, Dynamic user, or Dynamic device (device rules work on security groups only).
  • Dynamic groups and group-based licensing need Entra ID P1.
  • External partners: invite as guests (B2B), one at a time or by bulk CSV. They sign in with their own credentials.
  • SSPR: None / Selected / All. "Selected" scopes it to a group. Admin accounts always have SSPR with a stricter two-method policy.
  • Administrative units scope Entra admin roles to a subset of users or devices.

Cost & moves

  • Budgets only alert (and can trigger action groups). They never stop resources on their own.
  • Moving resources: resource IDs change. Role assignments made directly on the resource don't move. Source and target RGs are locked for writes during the move; the resources keep running.
  • Moving across subscriptions requires the same Entra tenant and the resource provider registered in the target subscription.
  • Advisor gives cost, security, reliability, and performance recommendations. Reservations and Azure Hybrid Benefit reduce cost.
05 · Storage · 15–20%

Storage cheat sheet

RedundancyCopiesSurvivesRead from secondary?
LRS3 in one datacenterDisk / rack failureNo
ZRS3 across availability zonesZone failureNo
GRSLRS + LRS in paired regionRegion failure (after failover)No (RA-GRS: yes)
GZRSZRS + LRS in paired regionZone and region failureNo (RA-GZRS: yes)

Tiers & lifecycle

  • Minimum days before early-deletion charges: Hot none, Cool 30, Cold 90, Archive 180.
  • Archive is offline. To read a blob you rehydrate it (change its tier or copy it): up to 15 h at standard priority, under 1 h at high priority for blobs under 10 GB.
  • The Archive tier isn't supported on ZRS, GZRS, or RA-GZRS accounts.
  • Lifecycle management policy rules filter by prefix or blob index tags and act on days since modification, creation, or last access (last access needs access tracking enabled).

Access

  • Two account keys. Rotating a key invalidates every SAS signed with it.
  • Account SAS: multiple services. Service SAS: one service. User delegation SAS: signed with Entra credentials, Blob/ADLS only, recommended.
  • Stored access policy: lets you revoke a service SAS without rotating keys. Up to 5 per container.
  • Data-plane RBAC: Storage Blob Data Reader / Contributor / Owner. Shared Key authorization can be turned off.

Network

  • The firewall allows selected VNets (needs the Microsoft.Storage service endpoint on the subnet) and public IP ranges (not private IPs).
  • A private endpoint gives the account a private IP in your VNet and is reachable from on-prem over VPN/ER. It needs the privatelink.blob.core.windows.net DNS zone.
  • The "Allow trusted Microsoft services" exception covers services like Azure Backup and Event Grid.

Data protection

  • Blob soft delete and container soft delete: 1–365 days.
  • Versioning keeps prior versions automatically when a blob is overwritten.
  • Point-in-time restore needs versioning, change feed, and soft delete.
  • Object replication needs versioning on both accounts and change feed on the source. Not supported with hierarchical namespace (HNS).
  • Immutable storage: a time-based retention policy (WORM, can be locked) or a legal hold (no end date).

Azure Files & File Sync

  • SMB uses port 445, which many ISPs block. NFS requires premium file shares.
  • Premium file shares (FileStorage accounts) support LRS and ZRS only.
  • Identity sources: on-prem AD DS, Entra Domain Services, or Entra Kerberos (hybrid users). Share-level roles: SMB Share Reader / Contributor / Elevated Contributor (Elevated can change NTFS ACLs).
  • File Sync: Storage Sync Service → sync group → 1 cloud endpoint plus multiple server endpoints. Each server registers with only one Sync Service. Cloud tiering frees local disk space.

Tools & encryption

  • AzCopy: azcopy copy / azcopy sync, authenticated with Entra or a SAS. Storage Explorer is the GUI. Data Box is for offline transfers of many TB.
  • Encryption at rest is always on, with Microsoft-managed or customer-managed keys (Key Vault with soft delete and purge protection).
  • Infrastructure (double) encryption can only be enabled when the account is created.
06 · Compute · 20–25%

Compute cheat sheet

App Service tierCustom domain / TLSScale outSlotsAutoscale
Free / SharedShared: domain only———
BasicYesManual, up to 3——
StandardYesUp to 105Yes
Premium v3YesUp to 3020Yes
Isolated (ASE)YesUp to 10020Yes

VM availability

  • SLAs: VMs across zones 99.99%, availability set 99.95%, single VM on Premium SSD 99.9%.
  • Availability set: up to 3 fault domains (rack, power) and 20 update domains (default 5). Planned maintenance takes down one UD at a time.
  • You can't add an existing VM to an availability set. You have to recreate it.
  • Resizing a running VM restarts it. If the new size isn't on the current hardware cluster, deallocate first.

Disks & encryption

  • The temp disk (D: on Windows, /dev/sdb on Linux) is lost on deallocate or redeploy.
  • SSE (default; platform- or customer-managed key) encrypts at rest. Encryption at host also covers the temp disk and caches.
  • ADE (BitLocker / DM-Crypt) needs a Key Vault in the same region and subscription with "Azure Disk Encryption for volume encryption" enabled.
  • Moving a VM across regions: Azure Resource Mover or ASR.

Scale sets

  • Orchestration modes: Uniform or Flexible. Autoscale is configured as rules in a profile with Min / Max / Default instance counts.
  • Default is used when metrics can't be read. If the current count is below Default, autoscale scales out to Default.
  • Default cooldown is 5 minutes. Scale-in policies: Default, NewestVM, OldestVM.
  • Post-deploy configuration: Custom Script Extension, Run Command, or cloud-init.

ARM & Bicep

  • Template sections: parameters, variables, resources, outputs. dependsOn sets deployment order.
  • Deployment scopes: az deployment group|sub|mg|tenant create. Creating an RG requires subscription scope.
  • Modes: Incremental (default) leaves other resources alone. Complete deletes RG resources that aren't in the template.
  • Decorators like @allowed, @minLength, and @secure() are checked at validation, before anything deploys.

Containers

  • ACR SKUs: Basic, Standard, Premium (geo-replication, private link). Prefer a managed identity with AcrPull over the admin user.
  • ACI: containers in a group share lifecycle, network (localhost), and volumes. Multi-container groups are Linux-only. Restart policies: Always / OnFailure / Never.
  • Container Apps: serverless, with revisions, ingress, and KEDA scale rules (HTTP, queue, and others). Scales to zero.

App Service details

  • A web app must be in the same region as its plan. All apps on a plan share its instances and scale together.
  • Settings marked as a deployment slot setting stay with the slot during a swap. Everything else moves with the code.
  • Custom domain: verify with a TXT record (asuid) plus a CNAME or A record. Free managed certificates are available.
  • Backup is available on Basic and higher. VNet integration handles outbound traffic; private endpoints handle inbound.
07 · Networking · 15–20%

Networking cheat sheet

Service endpointPrivate endpoint
Target IPService keeps its public IPPrivate IP in your subnet
Reachable from on-prem over VPN/ERNoYes
ScopeEntire service in the regionOne specific resource
DNS changesNoneprivatelink.* private zone
CostFreeHourly plus data processed

VNets & peering

  • Azure reserves 5 IPs per subnet (first 4 plus the last). The smallest subnet is /29.
  • Peering is non-transitive, and peered address spaces can't overlap. Global (cross-region) peering works.
  • Gateway transit: on the hub side, "Allow gateway transit". On the spoke side, "Use remote gateways".
  • Spoke-to-spoke traffic: peer the spokes directly, or route through a hub NVA or firewall (UDR plus "allow forwarded traffic").

NSG & ASG

  • Priority 100–4096. Lower number wins, and the first match stops evaluation.
  • Default inbound rules: AllowVnetInBound, AllowAzureLoadBalancerInBound, DenyAllInBound (65500).
  • Inbound traffic is checked by the subnet NSG, then the NIC NSG. Both must allow it. Outbound is NIC first, then subnet.
  • ASG members must all be NICs in the same VNet. Use "Effective security rules" on the NIC to see the combined result.

Routing

  • Next hop types: Virtual appliance, Virtual network gateway, Virtual network, Internet, None.
  • Longest prefix match wins. On a tie, UDR beats BGP, which beats system routes.
  • Forcing traffic through an NVA: UDR on the source subnet, plus IP forwarding enabled on the NVA's NIC (and in its OS).

DNS

  • Azure-provided DNS is at 168.63.129.16.
  • Private zones are linked to VNets. Auto-registration can be enabled for only one zone per VNet. A VNet can be linked to many zones for resolution only.
  • Public zone: delegate by changing the NS records at the registrar. A CNAME can't sit at the zone apex; use an alias record instead.

Load balancing: pick the right one

  • Load Balancer: layer 4, regional. Application Gateway: layer 7 path/host routing, TLS termination, WAF, needs its own subnet.
  • Traffic Manager: global, DNS-based. Front Door: global, layer 7, CDN plus WAF.
  • Standard LB requires a Standard public IP. Zone-redundant. Backend pool must be in one VNet. Closed by default (needs an NSG to allow traffic).
  • LB components: frontend IP, backend pool, health probe, LB rule, inbound NAT rule, outbound rule. Session persistence: None, Client IP, or Client IP and protocol.
  • Basic LB and Basic public IP were retired on Sept 30, 2025.

Bastion & Network Watcher

  • Bastion needs a subnet named AzureBastionSubnet, /26 or larger. Native client and IP-based connection need the Standard SKU or higher.
  • IP flow verify: which NSG rule allows or denies a packet. Next hop: where a packet is routed. Connection troubleshoot: one-off end-to-end test.
  • Connection monitor: ongoing reachability and latency checks with alerts. VPN troubleshoot: gateway and connection diagnostics. Flow logs: VNet flow logs.
08 · Hybrid

Site-to-site VPN, built from memory

You've done this by following the docs. These are the steps in order, with the detail on each that tends to show up in exam questions.

  1. VNet with a subnet named exactly GatewaySubnet, /27 or larger. Don't put VMs or an NSG on it.
  2. Public IP (Standard SKU, static) for the gateway.
  3. Virtual network gateway: type VPN (not ExpressRoute), VPN type route-based (needed for P2S, VNet-to-VNet, multiple S2S tunnels, and IKEv2). Choose an SKU (VpnGw1–5, AZ variants for zones). It takes 30–45 minutes to deploy.
  4. Local network gateway: represents on-prem. It holds the on-prem VPN device's public IP (or FQDN) and the on-prem address prefixes. When on-prem adds a subnet, update the prefixes here (or use BGP).
  5. Connection: type Site-to-site (IPsec), linking the VNet gateway to the local network gateway, with a shared key (PSK) that must match the on-prem device.
  6. Configure the on-prem device (download its configuration script from the connection), then confirm the connection status shows Connected.

Variants

  • P2S (point-to-site): individual clients connect, authenticating with a certificate, Entra ID, or RADIUS. Needs a route-based gateway.
  • VNet-to-VNet: a gateway on each side. Peering is usually the better choice today.
  • ExpressRoute: private circuit through a provider that doesn't cross the internet. A VPN can be used as a backup path.
  • Active-active gateways give two tunnels for high availability.

Troubleshooting

  • Mismatched PSK → the connection never comes up.
  • Wrong prefixes on the local network gateway → the tunnel is up but some subnets are unreachable.
  • Spokes can't reach on-prem → gateway transit or "Use remote gateways" isn't set on the peering.
  • Diagnose with Network Watcher VPN troubleshoot.
09 · Monitor & maintain · 10–15%

Monitoring & backup cheat sheet

VaultProtects
Recovery Services vaultAzure VMs, SQL Server / SAP HANA in VMs, Azure Files, on-prem through the MARS agent or MABS. Also Site Recovery.
Backup vaultAzure Blobs, Azure Disks, Azure Database for PostgreSQL, AKS.

Azure Backup

  • The vault must be in the same region as the resources it backs up.
  • Set the vault's storage redundancy (LRS/ZRS/GRS) before the first backup. Cross Region Restore requires GRS.
  • VM restore options: create a new VM, restore disks, replace existing, or File Recovery (a script mounts the recovery point so you can copy individual files).
  • Soft delete keeps deleted backup data for 14 days. A vault can't be deleted while soft-deleted items remain.

Site Recovery

  • Replicates VMs to a secondary region. The Recovery Services vault goes in the target region.
  • Test failover runs in an isolated VNet without affecting production replication.
  • Sequence: failover → commit → re-protect → fail back.

Alerts

  • An alert rule has a scope, a condition (metric, log search, or activity log), an action group, and a severity (Sev0–4).
  • Action groups send notifications (email, SMS, push, voice) and run actions (runbook, Function, Logic App, webhook, ITSM).
  • Alert processing rules suppress notifications or add action groups on a schedule, for example during maintenance windows.

Data collection

  • Azure Monitor Agent plus a data collection rule (DCR). The legacy Log Analytics (MMA) agent is retired.
  • Metrics are kept 93 days. The Activity log (who did what at the control plane) is kept 90 days. Send it to a workspace to keep it longer.
  • Resource logs need a diagnostic setting to send them to Log Analytics, Storage, or Event Hubs.
  • Insights: VM insights, Storage insights, Network insights.

KQL you should recognize

Event
| where TimeGenerated > ago(24h)
| where EventLevelName == "Error"
| summarize count() by Computer
| sort by count_ desc

Heartbeat
| summarize LastSeen = max(TimeGenerated) by Computer
| where LastSeen < ago(15m)

Perf
| where CounterName == "% Processor Time"
| summarize avg(CounterValue) by bin(TimeGenerated, 5m)
| render timechart
Syntax · CLI, PowerShell, Bicep & CIDR

Commands, templates, and subnet math

Candidates report CLI and PowerShell snippets, Bicep, subnetting and CIDR, and Private Link on the real exam. You need to recognize the right command and parameters, not recite every flag.

TaskAzure CLIPowerShell
Resource groupaz group createNew-AzResourceGroup
VMaz vm createNew-AzVM
Resize / deallocate a VMaz vm resize / az vm deallocateUpdate-AzVM after changing the size / Stop-AzVM (deallocates by default)
VNet, then subnetaz network vnet create, az network vnet subnet createNew-AzVirtualNetwork, Add-AzVirtualNetworkSubnetConfig, then Set-AzVirtualNetwork
Storage accountaz storage account create --sku Standard_ZRS --kind StorageV2New-AzStorageAccount -SkuName Standard_ZRS -Kind StorageV2
User delegation SASaz storage blob generate-sas --auth-mode login --as-userNew-AzStorageBlobSASToken with a context from -UseConnectedAccount
Role assignmentaz role assignment create --assignee … --role Reader --scope …New-AzRoleAssignment -SignInName … -RoleDefinitionName Reader -ResourceGroupName …
Custom roleaz role definition create --role-definition role.jsonNew-AzRoleDefinition -InputFile role.json
Lockaz lock create --lock-type CanNotDeleteNew-AzResourceLock -LockLevel CanNotDelete
Policy assignmentaz policy assignment createNew-AzPolicyAssignment
Deploy a templateaz deployment group|sub|mg|tenant createNew-AzResourceGroupDeployment (group), New-AzSubscriptionDeployment (subscription)

Bicep

  • Building blocks: param, var, resource, module, output. targetScope = 'subscription' lets one file create resource groups.
  • existing references a resource you didn't deploy in this file. Add scope: resourceGroup('RG2') if it lives elsewhere.
  • Referencing another resource's symbolic name creates an implicit dependency. Use dependsOn only when there's no reference.
  • az bicep build: Bicep → ARM JSON. az bicep decompile: ARM JSON → Bicep (may need manual fixes).
  • az deployment group what-if previews what a deployment would change without deploying.
  • Decorators @allowed, @minLength, @secure() are checked at validation.

Private Link names & Arc

  • Blob: privatelink.blob.core.windows.net. Files: privatelink.file.core.windows.net.
  • Azure SQL: privatelink.database.windows.net. Key Vault: privatelink.vaultcore.azure.net.
  • The private DNS zone must be linked to the VNet, or clients still resolve the public IP.
  • On-prem name resolution for Azure private zones: Azure DNS Private Resolver inbound endpoint plus a forwarder on-prem.
  • Azure Arc-enabled servers: install the Connected Machine agent on an on-prem or other-cloud server to manage it with Azure Policy, RBAC, and Monitor.

Subnet math

PrefixAddressesUsable in Azure (minus 5)
/2983
/281611
/273227
/266459
/25128123
/24256251
/23512507
/221,0241,019

A /23 is two /24 blocks: 10.0.0.0/23 spans 10.0.0.0 to 10.0.1.255. A /25 is half a /24, split at .128. Two ranges overlap when one sits inside the other, and VNets with overlapping spaces can't be peered. Subnets in one VNet can't overlap either.

10 · Recall

Numbers to memorize

ItemValue
Availability set fault domains / update domainsmax 3 / max 20 (default 5)
VM SLA: zones / availability set / single Premium SSD99.99 / 99.95 / 99.9%
Early deletion: Cool / Cold / Archive30 / 90 / 180 days
Archive rehydration, standard priorityup to 15 hours
Stored access policies per container5
Blob / container soft delete range1–365 days
Backup soft delete retention14 days
Activity log retention90 days
Reserved IPs per subnet5
GatewaySubnet / AzureBastionSubnet minimum/27 / /26
NSG custom rule priority range100–4096
Management group depth (excluding root)6 levels
App Service Standard: instances / slots10 / 5
Tags per resource50
11 · Traps

Classic traps

"Least privilege" in the question rules out Owner. Find the narrowest built-in role that still does the job.
"Minimize administrative effort" usually points to a policy, a dynamic group, or a management group assignment, not a script.
NotActions isn't a deny. A second role can still grant the same permission.
Locks stop Owners too. And a ReadOnly lock on a storage account breaks key listing.
Policy Deny doesn't touch existing resources. They're only marked non-compliant.
Peering is non-transitive. Hub-and-spoke doesn't give spoke-to-spoke connectivity for free.
Subnet NSG allows it, but the NIC NSG has only default rules → inbound internet traffic is denied.
The vault must be in the same region as the VM. Blobs and disks go in a Backup vault, not a Recovery Services vault.
Deployment slots and autoscale start at Standard. Basic doesn't have them.
ACI multi-container groups are Linux-only.
Budgets never shut anything down unless you attach automation through an action group.
Service endpoints aren't reachable from on-prem. Private endpoints are.
Yes/No series: each proposed solution is judged separately, and you can't go back.