Study guide
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV)
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV)
Key Takeaways Explain This Topic AI
Windows Server Failover Clustering (WSFC) provides high availability and fault tolerance for Hyper-V workloads, requiring passing all cluster validation tests via Test-Cluster for Microsoft production support.
Dynamic Quorum dynamically adjusts node voting weights, while quorum witnesses (Disk Witness, File Share Witness, and Cloud Witness in Azure Blob Storage) provide tie-breaking votes for even-node clusters.
Cluster Shared Volumes (CSV) deliver active-active multi-node concurrent read/write storage access to a shared NTFS or ReFS volume mounted uniformly under C:\ClusterStorage\VolumeX across all cluster nodes.
CSV I/O operates in Direct I/O mode for high-performance direct SAN/SAS storage operations, automatically transitioning to Block Redirected I/O over the SMB 3.0 cluster network during storage path degradation or metadata updates.
Virtual machine migration options include Live Migration (zero downtime with Kerberos/CredSSP and TCP/Compression/SMB Direct transports), Storage Live Migration (relocating VHDXs without VM interruption), and Shared Nothing Live Migration (migrating compute and storage between non-clustered hosts).
Last updated: August 2026
Hyper-V Failover Clustering & Cluster Shared Volumes (CSV)
In enterprise private and hybrid cloud architectures, running business-critical virtualized workloads requires zero unplanned downtime, high resilience against host hardware failures, and dynamic workload mobility. Windows Server Failover Clustering (WSFC) integrated with Hyper-V provides the foundational high-availability clustering tier for Windows Server environments. By grouping multiple physical Hyper-V hosts into a unified cluster managed through Failover Cluster Manager or PowerShell, organizations achieve automated virtual machine failover, live workload balancing, and non-disruptive host maintenance.
1. Windows Server Failover Clustering (WSFC) Architecture & Prerequisites
A Hyper-V Failover Cluster is a group of independent physical servers (nodes) that work together to increase the availability of virtualized roles and applications. If a physical node experiences hardware failure, power loss, or operating system failure, the virtual machines hosted on that node are automatically restarted on remaining healthy nodes within seconds. +-----------------------------------------------------------------------------------------+
- | HYPER-V FAILOVER CLUSTER ARCHITECTURE |
- | |
- | +------------------------------------+ +------------------------------------+ |
- | | Hyper-V Cluster Node 1 (Active) | | Hyper-V Cluster Node 2 (Active) | |
- | | - Role: VM-SQL-01 [Running] | | - Role: VM-APP-01 [Running] | |
- | | - Heartbeat / Cluster Network | | - Heartbeat / Cluster Network | |
- | | - Live Migration Network (RDMA) | | - Live Migration Network (RDMA) | |
- | +------------------------------------+ +------------------------------------+ |
- | \ / |
- | \ / |
- | =====================\===========================/================================= |
- | STORAGE FABRIC (iSCSI / FC / SAS / SMB 3.0) |
- | =================================================================================== |
- | | |
- | +-------------------+-------------------+ |
- | | Cluster Shared Volume (CSV LUN) | |
- | | Path: C:\ClusterStorage\Volume1 | |
- | | Holds: VM Configs, VHDX Virtual Disks| |
- | +---------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
- Core Prerequisites for Hyper-V Clustering
Hardware Homogeneity: While mixed-processor generations can run clustered VMs using Hyper-V Processor Compatibility Mode, identical CPU models (Intel VT-x or AMD-V) and matching BIOS/UEFI settings are strongly recommended for seamless Live Migration.
Network Topology: A minimum of two distinct physical network adapters per host is required, though enterprise environments deploy redundant 10GbE/25GbE adapters segregated into distinct subnets or VLANs:
Management Network: Host administration, Active Directory domain traffic, and RDP/SSH.
Cluster / Heartbeat Network: Inter-node cluster communication, health monitoring, and state replication.
Live Migration Network: Dedicated high-speed network for memory state replication during migrations (preferably configured with RDMA / SMB Direct).
Storage Network: Dedicated iSCSI or SMB 3.0 traffic if not using Fibre Channel.
VM Traffic Network: Hyper-V Virtual Switch carrying tenant guest traffic.
Active Directory Domain Services: All cluster nodes must be joined to the same Active Directory Domain Services (AD DS) forest/domain.
Shared Storage: Accessible to all cluster nodes simultaneously via Fibre Channel (FC), Fibre Channel over Ethernet (FCoE), iSCSI, Shared Serial Attached SCSI (SAS), or Storage Spaces Direct (S2D).
Cluster Validation Testing ( Test-Cluster )
Before forming a cluster, administrators must execute the Cluster Validation Wizard or the Test-Cluster PowerShell cmdlet. Running cluster validation tests hardware, network latency, storage failover reservations (SCSI-3 Persistent Reservations), and Hyper-V virtual switch configurations. # Execute a full cluster validation across candidate Hyper-V nodes
- Test-Cluster -Node "HV-NODE01", "HV-NODE02", "HV-NODE03" `
- Include "Hyper-V Configuration", "Storage", "Network", "System Configuration", "Inventory" `
- ReportFilePath "C:\Reports\HyperVClusterValidation.html"
- # Create the Failover Cluster after all validation tests pass
- New-Cluster -Name "HV-PROD-CLUST" `
- Node "HV-NODE01", "HV-NODE02", "HV-NODE03" `
- StaticAddress "10.10.10.50" `
- NoStorage
Important
Microsoft Support Policy Requirement: To receive full Microsoft production support for a Failover Cluster, the environment must pass all validation tests in Test-Cluster without blocking errors. A validation report with "Warnings" is acceptable if documented, but "Failures" must be remediated prior to putting the cluster into production.
2. Quorum Models & Dynamic Quorum Architecture
Quorum is the consensus mechanism that ensures a cluster maintains integrity and avoids split-brain conditions—a catastrophic scenario where a communication breakdown causes cluster partitions to simultaneously assume volume ownership and write conflicting data to shared disks.
Voting Architecture & Dynamic Quorum
Modern Windows Server Failover Clustering implements Dynamic Quorum . Under Dynamic Quorum, the cluster dynamically recalculates the total votes required for quorum when nodes gracefully shut down or fail sequentially. As long as nodes drop one by one with sufficient time for the cluster to recalculate voting weights, a cluster can survive down to a single remaining node and a witness. +-----------------------------------------------------------------------------------------+
- | QUORUM MODELS COMPARISON |
- | |
- | QUORUM WITNESS TYPE BEST USE CASE REQUIREMENTS / MECHANISM |
- | -----------------------+--------------------------------+-----------------------------|
- | Node Majority | Odd number of nodes (3, 5, 7) | No witness needed; 50%+1 |
- | (No Witness) | in a single datacenter | active nodes maintain quorum|
- | -----------------------+--------------------------------+-----------------------------|
- | Disk Witness | Multi-site or even-node SAN | Dedicated shared LUN (512MB)|
- | | environments | with SCSI-3 reservations |
- | -----------------------+--------------------------------+-----------------------------|
- | File Share Witness | Multi-site stretched clusters | SMB file share on a separate|
- | (FSW) | or non-SAN environments | independent server host |
- | -----------------------+--------------------------------+-----------------------------|
- | Cloud Witness | All modern 2-node or even-node | Azure Blob Storage account |
- | | clusters (Standard Practice) | Outbound HTTPS port 443 |
- +-----------------------------------------------------------------------------------------+
- Cloud Witness in Azure Blob Storage
Cloud Witness is the recommended witness type for modern Windows Server clusters. Instead of provisioning an on-premises physical file server or shared SAN LUN, Cloud Witness uses a lightweight Azure Blob Storage account as an arbitration point. # Configure an Azure Cloud Witness for the Hyper-V Cluster
- Set-ClusterQuorum -Cluster "HV-PROD-CLUST" `
- CloudWitness `
- AccountName "stghvclusterwitness" `
- AccessKey "A1b2C3d4E5f6G7h8I9j0K1L2M3N4O5P6Q7R8S9T0U1V2W3X4Y5Z6=="
Why Cloud Witness is Superior:
Zero Compute Costs: Uses standard Azure Blob Storage; no virtual machine hosting or OS patching required.
Multi-Site Resiliency: Operates outside local datacenter failure domains, making it ideal as a third-party tiebreaker in stretched multi-datacenter clusters.
Negligible Storage: Maintains a tiny 0-byte blob file containing only timestamp tokens for arbitration.
3. Cluster Shared Volumes (CSV) Architecture & I/O Flow
Prior to Cluster Shared Volumes (CSV), a clustered shared disk (LUN) could only be mounted and accessed by a single node at any given time. If multiple VMs resided on the same LUN, all those VMs had to run on the same cluster host.
Cluster Shared Volumes (CSV) revolutionizes Hyper-V storage by providing an active-active, multi-node shared namespace. Multiple cluster nodes can simultaneously read from and write to the same shared NTFS or ReFS volume. CSV exposes shared volumes as subdirectories under a uniform local namespace on every node: C:\ClusterStorage\VolumeX . +-----------------------------------------------------------------------------------------+
- | CLUSTER SHARED VOLUMES (CSV) I/O PATHWAYS |
- | |
- | [COORDINATOR NODE (Node 1)] [NON-COORDINATOR NODE (Node 2)] |
- | +------------------------+ +------------------------+ |
- | | VM 1 (Reads/Writes) | | VM 2 (Reads/Writes) | |
- | | | | | |
- | | NTFS / ReFS Metadata | | Direct I/O (Data Reads)| |
- | | Manager & Coordinator | | | |
- | +-----------+------------+ +-----------+------------+ |
- | | (Direct SAN) | (Direct SAN) |
- | | | |
- | v v |
- | +--------------------------------------------------------------------------+ |
- | | SHARED STORAGE FABRIC (SAN LUN / CSV VOLUME) | |
- | +--------------------------------------------------------------------------+ |
- | |
- | === BLOCK REDIRECTED I/O FALLBACK PATH (If Node 2 loses physical storage link) === |
- | [Node 2 Guest VM] ---> [Node 2 CSVFS] === SMB 3.0 Cluster Net ===> [Node 1] ---> [SAN] |
- +-----------------------------------------------------------------------------------------+
- Direct I/O vs Block Redirected I/O
CSV handles storage input/output using two distinct operational modes:
I/O Mode Operational Mechanism When It Occurs
Direct I/O The cluster node communicates directly with the underlying storage fabric (FC/iSCSI/SAS) through its local HBA/NIC. Delivers full native storage performance and lowest latency. Standard virtual disk read and write operations when storage paths are fully operational.
Block Redirected I/O Storage I/O is intercepted at the CSV Filter Driver ( csvfs.sys ) and rerouted over the cluster network via SMB 3.0 to the CSV Coordinator Node , which performs the physical write on behalf of the requesting node. Occurs when: (1) A node loses physical connectivity to the storage fabric, (2) Storage snapshots or volume maintenance are active, or (3) Volume metadata updates take place (file creation, dynamic expansion). # Convert a standard cluster disk to a Cluster Shared Volume (CSV)
Add-ClusterSharedVolume -Name "Cluster Disk 2" -Cluster "HV-PROD-CLUST"
# Inspect CSV volume state and owner (Coordinator) node
Get-ClusterSharedVolume | Select-Object Name, State, OwnerNode, @{N='Path';E={$_.SharedVolumeInfo.FriendlyVolumeName}}
Tip
Exam Trap: ReFS vs NTFS on CSV: Starting with Windows Server 2019 and Windows Server 2022/2025, ReFS (Resilient File System) is fully supported on CSV alongside NTFS. ReFS offers near-instantaneous fixed-size VHDX creation and checkpoint merge operations via Block Cloning (allocate-on-write) technology.
Loading diagram... CSV Direct I/O vs Redirected I/O Traffic Flow
4. Virtual Machine Migration Technologies
Hyper-V provides multiple migration mechanisms to transfer virtual machine compute, memory, and storage states between hosts without service interruption. +-----------------------------------------------------------------------------------------+
- | VIRTUAL MACHINE MIGRATION MODES COMPARISON |
- | |
- | MIGRATION TYPE DOWNTIME STORAGE REQUIREMENT APPLICABILITY |
- | ------------------------+----------+----------------------+---------------------------|
- | Clustered Live Migration | Zero | Shared Storage (CSV) | Nodes in same cluster |
- | Storage Live Migration | Zero | Independent Storage | Any host (moves VHDX files|
- | Shared Nothing Live Mig. | Zero | Independent Storage | Non-clustered hosts |
- | Quick Migration | Brief | Shared Storage | Clustered hosts (pause/res|
- +-----------------------------------------------------------------------------------------+
- 1. Clustered Live Migration (Compute Only)
Clustered Live Migration moves the execution state and RAM of a running virtual machine from one cluster node to another while keeping the underlying virtual disk (VHDX) stationary on shared CSV storage. The process transfers memory pages iteratively, pauses the VM for milliseconds during final CPU register transfer, and announces the VM's MAC address on the new switch port via Gratuitous ARP.
Live Migration Performance & Transport Protocols:
TCP: Default transport; transfers uncompressed memory pages over standard TCP connections. Higher network utilization.
Compression: Compresses memory pages using host CPU cycles before transmission across the network. Recommended for 1GbE or saturated 10GbE networks.
SMB 3.0 / SMB Direct (RDMA): Transfers memory data over SMB 3.0 utilizing RDMA (Remote Direct Memory Access) adapters (iWARP or RoCE). Delivers line-rate throughput (25GbE/100GbE) with near-zero host CPU overhead.
Authentication Protocols:
Kerberos: Requires configuring Active Directory Constrained Delegation for the cifs and Microsoft Virtual System Migration Service services on the computer accounts of all Hyper-V hosts. Enables initiating Live Migrations remotely via Windows Admin Center, PowerShell remoting, or Hyper-V Manager.
CredSSP (Credential Security Support Provider): Avoids configuring Kerberos constrained delegation but requires the administrator to log in directly via local interactive desktop session on the source host. Remote PowerShell Live Migration triggers fail under CredSSP due to the "double-hop" authentication barrier.
2. Storage Live Migration
Storage Live Migration relocates a virtual machine's virtual hard disks ( .vhdx ), checkpoints, and configuration files from one storage location to another without stopping the running VM. While the VM continues executing, Hyper-V performs a baseline file copy, uses a write mirror to log all incoming disk writes to both the source and target locations, synchronizes deltas, and switches file handles upon completion. # Perform Storage Live Migration of a running VM to a new CSV volume
- Move-VMStorage -VMName "VM-APP-01" `
- DestinationStoragePath "C:\ClusterStorage\Volume2\VM-APP-01"
- 3. Shared Nothing Live Migration
Shared Nothing Live Migration simultaneously transfers both the memory state and the virtual disk storage of a running VM between two independent, non-clustered Hyper-V hosts connected only by an Ethernet network cable or LAN. # Migrate a running VM and its storage between non-clustered Hyper-V hosts
- Move-VM -Name "VM-DEV-01" `
- DestinationHost "HV-STANDALONE-02" `
- IncludeStorage `
- DestinationStoragePath "D:\Hyper-V\Virtual Hard Disks\VM-DEV-01"
- 5. Host Maintenance: Node Pause and Role Draining
Performing planned host maintenance (e.g., applying Windows cumulative updates or updating physical server firmware) requires evacuating clustered VM workloads without downtime. # Step 1: Pause the cluster node and drain all hosted VM roles automatically
Suspend-ClusterNode -Name "HV-NODE01" -Drain
# Step 2: Perform host patching, hardware maintenance, or OS reboot
# ... Host reboot occurs here ...
- # Step 3: Resume the cluster node and fail back original workloads
- Resume-ClusterNode -Name "HV-NODE01" -Failback Immediate
Suspend-ClusterNode -Drain : Sets the node state to Paused and systematically initiates Live Migrations of all running virtual machines to remaining active nodes, taking node capacity and memory constraints into account.
Resume-ClusterNode -Failback Immediate : Re-enables the node ( Up state) and immediately Live Migrates preferred workloads back to the host if configured in failback policies.