Home / cloud-computing / Administering Windows Server (AZ-802) / Cheat Sheet
Administering Windows Server (AZ-802)

AZ-802 Cheat Sheet

AZ-802 Tests Hybrid Windows Server Judgment — Not On-Premises AD DS Alone

AZ-802 replaced AZ-800 and AZ-801, retired on 30 September 2026, as the single exam for Windows Server Administrator Associate. Expect scenarios mixing AD DS, Hyper-V, Azure Arc, Azure Files and Azure Monitor.

Check Your Readiness →
Among the harder certs
Avg: Not published by Microsoft
Pass: 750 / 1000
Most candidates understand Administering Windows Server (AZ-802) concepts — and still fail. This exam tests how you apply knowledge under pressure.

AZ-802 Domain Map (seven functional areas)

Seven domains merge the former AZ-800 administration and AZ-801 advanced topics. Scenarios state a constraint such as least privilege, a branch with poor physical security or users without VPN, and the answer is the feature built for it. 120 minutes; question count not published; general availability date unconfirmed.

  1. 01
    Deploy and manage AD DS (20–25%) — FSMO roles, RODCs, trusts, sites, gMSAs and Group Policy processing
  2. 02
    Hybrid instances and workloads (10–15%) — Windows Admin Center, JEA, PowerShell remoting, Azure Arc and Update Manager
  3. 03
    Manage virtual machines (10–15%) — Hyper-V features, checkpoints, Replica, Azure VM availability and secure access
  4. 04
    On-premises and hybrid networking (10–15%) — DNS zones and forwarders, DNS Private Resolver, DNSSEC, DHCP failover
  5. 05
    Storage and file services (15–20%) — Azure File Sync, Azure Files identity, DFS, Storage Spaces Direct, Storage Replica
  6. 06
    Secure Windows Server infrastructure (10–15%) — Windows LAPS, Credential Guard, App Control, PSOs, Protected Users
  7. 07
    Monitor and troubleshoot (15–20%) — Azure Monitor Agent and DCRs, AD object restore, SYSVOL recovery, Kerberos

Wrong instinct vs correct approach

A branch office has weak physical security and no IT staff but needs local sign-in
✕ Wrong instinct

Deploy a writable domain controller at the branch

✓ Correct approach

Deploy a Read-Only Domain Controller with a password replication policy that caches only branch users. A stolen RODC exposes far fewer credential hashes, and it never accepts writes, which are referred to a writable DC.

Remote staff need file shares without VPN, and security forbids exposing TCP 445
✕ Wrong instinct

Publish SMB on port 445 through the perimeter firewall

✓ Correct approach

Configure SMB over QUIC, which carries SMB over UDP 443 with TLS 1.3 and needs a server certificate. It gives VPN-less access without opening 445, a port many ISPs and security teams block.

Help desk operators must restart one service on several servers and do nothing else
✕ Wrong instinct

Add the help desk group to local Administrators

✓ Correct approach

Create a Just Enough Administration endpoint: a role capability file listing permitted cmdlets and a session configuration that uses a temporary virtual account. Operators run only those commands and never hold administrator rights themselves.

Nested PowerShell remoting fails when the second hop reaches a file server
✕ Wrong instinct

Enable CredSSP on every client and server

✓ Correct approach

Configure resource-based Kerberos constrained delegation on the target. It solves the double hop without sending reusable credentials to the intermediate server, which CredSSP does and a minimise-credential-exposure requirement rules out.

Two offices must both edit the same files, and branch servers should keep only hot data locally
✕ Wrong instinct

Replicate volumes between offices with Storage Replica

✓ Correct approach

Storage Replica is one-way and the destination is not accessible during replication. Azure File Sync, with one cloud endpoint per sync group, centralises data in Azure Files, and cloud tiering keeps only hot files on each server.

Know these cold

  • ▸ Forest-wide FSMO — chema and domain naming; per domain: PDC emulator, RID, infrastructure
  • ▸ Only the forest root PDC emulator syncs to external NTP; Kerberos tolerates five minutes of skew
  • ▸ An sMSA serves one computer; a gMSA serves many hosts and needs a KDS root key
  • ▸ AGDLP — ccounts into global groups, into domain local groups, which receive the permissions
  • ▸ Protected Users — o NTLM, delegation, DES or RC4, four-hour TGT; keep service accounts out
  • ▸ Availability set gives 99.95% in one data center; zones give 99.99% across two or more
  • ▸ DDA hands a whole PCIe device to one VM; GPU partitioning shares a GPU
  • ▸ Domain-joined DHCP servers lease nothing until they are authorized in AD DS
  • ▸ Hard quota blocks writes, soft quota only warns; Storage Spaces Direct requires a failover cluster
  • ▸ Broken trust — un Test-ComputerSecureChannel -Repair before rejoining, which loses group memberships

Can you answer these without checking your notes?

In this scenario: "A branch office has weak physical security and no IT staff but needs local sign-in" — what should you do first?
Deploy a Read-Only Domain Controller with a password replication policy that caches only branch users. A stolen RODC exposes far fewer credential hashes, and it never accepts writes, which are referred to a writable DC.
In this scenario: "Remote staff need file shares without VPN, and security forbids exposing TCP 445" — what should you do first?
Configure SMB over QUIC, which carries SMB over UDP 443 with TLS 1.3 and needs a server certificate. It gives VPN-less access without opening 445, a port many ISPs and security teams block.
In this scenario: "Help desk operators must restart one service on several servers and do nothing else" — what should you do first?
Create a Just Enough Administration endpoint: a role capability file listing permitted cmdlets and a session configuration that uses a temporary virtual account. Operators run only those commands and never hold administrator rights themselves.

Common Exam Mistakes — What candidates get wrong

Seizing a FSMO role when the holder is only down for patching

Seizure is for a holder that will never return; a recovering holder needs a transfer or a wait. Know the split: schema master and domain naming master are forest-wide, while PDC emulator, RID master and infrastructure master exist once per domain.

Linking a fine-grained password policy to an OU

Password Settings Objects apply only to users and global security groups, and the lowest precedence value wins when several apply. To give one department stricter rules, put its users in a global group and target the PSO at that group.

Expecting a domain-linked GPO to beat an OU-linked GPO

Processing runs local, site, domain, OU, and the last applied setting wins, so OU links override domain links. Only an Enforced link reverses that and also defeats Block Inheritance. Preferences set values users can change; policy settings lock them.

Installing Azure extensions before onboarding servers to Azure Arc

A server in a data center or another cloud appears in Azure only after the Connected Machine agent onboards it. Then Azure Monitor Agent, machine configuration and Azure Update Manager work; run azcmagent check before blaming extensions for errors.

Booting into DSRM to recover a deleted user when Recycle Bin is on

With the AD Recycle Bin enabled, Restore-ADObject returns the object online with all attributes and no downtime. Without it, restore in DSRM and mark objects authoritative with ntdsutil; a nonauthoritative restore lets partners replicate the deletion back.

Resources to help you pass Windows Server Administrator AZ-802 on your first attempt

Test your AD DS, Azure Arc and file services decisions against AZ-802 hybrid scenarios.