Study guide

9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations

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

9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations

Key Takeaways Explain This Topic AI

Host caching must follow the I/O pattern: Read/Write for the OS disk, ReadOnly for read-heavy database data files, and None for transaction log and write-heavy disks.

Setting host caching to ReadOnly or Read/Write on a SQL Server log disk risks write reordering and is the single most common Azure IaaS storage misconfiguration on the exam.

Credit-based bursting lets smaller Premium SSD v1 disks reach 3,500 IOPS and 170 MB/s for up to 30 minutes at no extra cost once credits have accumulated.

Ephemeral OS disks live on the host cache or local temp storage, cost nothing in storage transactions, and reimage in seconds, but every byte is lost on deallocation or host reallocation.

Managed disks can be expanded online on supported configurations but can never be shrunk; exceeding a single disk's IOPS ceiling requires striping several disks into one Storage Spaces volume in the guest.

Last updated: August 2026

  • Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations
  • 1. Host Disk Caching Strategies for Windows Workloads

Azure VM host caching utilizes the physical hypervisor host's high-speed RAM and local NVMe storage to accelerate disk reads and writes. Misconfiguring host caching can cause severe database corruption during ungraceful host failovers. +-----------------------------------------------------------------------------+

  • | AZURE VM HOST CACHING ARCHITECTURE |
  • | |
  • | +---------------------------------------------------------------------+ |
  • | | AZURE HYPERVISOR HOST | |
  • | | | |
  • | | +--------------------+ +----------------------------+ | |
  • | | | Host RAM / NVMe | | Windows Guest OS | | |
  • | | | Read Cache | <---------- | - OS Disk (C:) | | |
  • | | +--------------------+ | (Cache: Read/Write) | | |
  • | | | | | |
  • | | +--------------------+ | - SQL Data Disk (.mdf) | | |
  • | | | Host RAM / NVMe | <---------- | (Cache: ReadOnly) | | |
  • | | | Write Buffer | | | | |
  • | | +--------------------+ | - SQL Log Disk (.ldf) & | | |
  • | +------------------------------------ | AD NTDS.dit | | |
  • | | | (Cache: NONE) | | |
  • | v +----------------------------+ | |
  • | +---------------------------------------------------------------------+ |
  • | | REMOTE AZURE MANAGED DISK STORAGE SUBSYSTEM | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+

Caching Modes and Workload Mapping:

Read/Write Caching (Default on OS Disks):

Mechanism: Reads are served from host memory; writes are acknowledged once written to the host cache before being flushed asynchronously to remote Azure Storage.

Usage: Standard for OS Disks ( C: ) to accelerate operating system boot times, software installation, and temporary registry operations.

Restriction: NEVER use Read/Write caching for database transaction log files.

ReadOnly Caching:

Mechanism: Reads are cached in high-speed host RAM/local SSD. Writes bypass the cache and commit synchronously to remote persistent storage.

Usage: Highly recommended for SQL Server data files ( .mdf ) , reporting databases, and read-heavy application data where repeated queries benefit from zero-latency memory cache hits.

None Caching (Host Caching Disabled):

Mechanism: All reads and writes bypass the host cache and commit directly and synchronously to the remote managed disk storage subsystem.

Usage: MANDATORY for SQL Server transaction log files ( .ldf ) , Active Directory database and log files ( NTDS.dit , edb.log ) , and transactional queue systems.

Integrity Rule: If an Azure physical host experiences a power failure while uncommitted writes reside in host RAM cache, uncommitted database transactions are lost, causing Update Sequence Number (USN) rollbacks in AD DS and transaction chain corruption in SQL Server.

Caution

The Volatile Temporary Disk ( D: ) Rule: Most Azure VM sizes include a local temporary scratch disk assigned as drive letter D: . This drive is physically located on the hypervisor host and is completely erased during VM resizing, planned hardware maintenance, or VM deallocation. Never store user data, AD DS directory partitions, or SQL database data/log files on D: . It is only suitable for the Windows pagefile ( pagefile.sys ) or SQL Server tempdb (when configured to recreate directories upon startup).

2. Disk Bursting: Credit-Based vs On-Demand Bursting

Disk bursting allows managed disks to exceed their baseline provisioned IOPS and throughput limits to handle sudden, unexpected traffic spikes or batch jobs. +-----------------------------------------------------------------------------+

  • | DISK BURSTING MODES COMPARISON |
  • | |
  • | FEATURE CREDIT-BASED BURSTING ON-DEMAND BURSTING |
  • | ---------------+----------------------------+-----------------------------|
  • | Applicability | Premium SSD <= 512 GiB | Premium SSD > 512 GiB |
  • | | (Tiers P1 to P20) | (Tiers P30+ and all sizes) |
  • | Mechanics | Accumulates credits when | Bursts dynamically whenever |
  • | | I/O is below baseline | workload exceeds baseline |
  • | Burst Max | Up to 3,500 IOPS / 170 MB/s| Up to 30,000 IOPS / 1,000 MB|
  • | Duration | Up to 30 minutes continuous| Unlimited (uncapped) |
  • | Cost | Free (included in tier) | Hourly enablement fee + |
  • | | | per-burst transaction fee |
  • +-----------------------------------------------------------------------------+

Credit-Based Bursting: When a small disk (such as a P10 OS disk) operates below its baseline IOPS and throughput, it accumulates burst credits in a bucket. When demand surges (e.g., during OS boot, patch installation, or initial application load), the disk consumes credits to burst up to 3,500 IOPS and 170 MB/s for a maximum of 30 minutes at no additional cost.

On-Demand Bursting: Designed for larger production workloads where burst durations cannot be constrained by credit buckets. When enabled on Premium SSD disks (such as P30 or P40), the disk bursts whenever demanded by the OS, up to 30,000 IOPS and 1,000 MB/s, with charges applied per burst transaction.

3. Ephemeral OS Disks

Traditional Azure VMs store the operating system disk on remote Azure Storage, requiring network hops across the datacenter fabric for OS reads and writes. Ephemeral OS Disks provision the operating system virtual hard disk directly on the local VM host hypervisor storage (using either the VM's local temporary NVMe disk or the VM's OS cache allocation). +-----------------------------------------------------------------------------+

  • | PERSISTENT MANAGED DISK VS EPHEMERAL OS DISK |
  • | |
  • | PERSISTENT MANAGED OS DISK EPHEMERAL OS DISK |
  • | +--------------------------+ +--------------------------+ |
  • | | Compute Host Hypervisor | | Compute Host Hypervisor | |
  • | | (VM Core + RAM) | | +----------------------+ | |
  • | +--------------------------+ | | VM Core + RAM | | |
  • | | | +----------------------+ | |
  • | (Network Fabric) | | Local Temp NVMe / | | |
  • | v | | Cache: OS Disk (C:) | | |
  • | +--------------------------+ | +----------------------+ | |
  • | | Remote Azure Storage | +--------------------------+ |
  • | | - Persistent OS Disk | (Zero Remote Storage Hop) |
  • | +--------------------------+ (Instant Re-imaging & Fast Reset) |
  • +-----------------------------------------------------------------------------+

Key Architectural Features of Ephemeral OS Disks:

Zero Storage Cost: Storage capacity and transactional I/O operations for ephemeral OS disks are free; billing is tied strictly to the underlying compute VM size.

Extreme Performance: Delivers sub-millisecond read/write latency and maximum IOPS matching the physical NVMe drive on the host.

Rapid Re-imaging & Provisioning: VM re-imaging takes seconds rather than minutes because no remote disk copying or storage fabric registration is involved.

Workload Suitability: Perfect for stateless applications, Virtual Machine Scale Sets (VMSS) running web farms, batch processing workers, and Azure Kubernetes Service (AKS) agent nodes.

Key Constraints:

The VM size's local cache or temp disk must be equal to or larger than the OS image size (typically 127 GiB for Windows Server).

Data on the OS disk is lost immediately if the VM is stopped/deallocated or moved to another host due to maintenance.

Does not support Azure Backup VM-level snapshots, disk capturing, or customer-managed disk encryption sets.

  • 4. Attaching, Resizing & Aggregating Managed Disks with PowerShell
  • Expanding Managed Disks Online

Azure supports online expansion of managed data disks without stopping the VM on modern VM sizes. Managed disks can only be expanded ; they cannot be shrunk . # 1. Update the managed disk size in Azure to 512 GiB

  • $VirtualMachine = Get-AzVM -ResourceGroupName 'RG-Production' -Name 'AZ-APP01'
  • $Disk = Get-AzDisk -ResourceGroupName 'RG-Production' -DiskName 'AZ-APP01-Data01'
  • $Disk.DiskSizeGB = 512
  • Update-AzDisk -ResourceGroupName 'RG-Production' -Disk -DiskName 'AZ-APP01-Data01'

# 2. Inside the Windows Server Guest OS (via PowerShell Remoting or Run Command):

  • # Scan for disk changes and extend the volume to maximum available size
  • Update-HostStorageCache
  • $Size = (Get-PartitionSupportedSize -DiskNumber 2 -PartitionNumber 2)
  • Resize-Partition -DiskNumber 2 -PartitionNumber 2 -Size $Size.SizeMax
  • Aggregating Disk IOPS with Storage Spaces Striping

When an application's I/O requirements exceed the maximum limits of a single Premium SSD v1 disk (20,000 IOPS / 900 MB/s), administrators attach multiple managed disks to the VM and configure a striped Storage Space (RAID-0 / Simple Resiliency) inside the Windows guest OS. # Inside Windows Server: Initialize disks and create a striped Storage Pool

$PhysicalDisks = Get-PhysicalDisk -CanPool $true

  • # Create the Storage Pool
  • New-StoragePool `
  • FriendlyName 'DataStoragePool' `
  • StorageSubsystemFriendlyName 'Windows Storage*' `
  • PhysicalDisks $PhysicalDisks
  • # Create a Striped (Simple) Virtual Disk across all pooled managed disks
  • New-VirtualDisk `
  • StoragePoolFriendlyName 'DataStoragePool' `
  • FriendlyName 'StripedDataVolume' `
  • ResiliencySettingName 'Simple' `
  • NumberOfColumns $PhysicalDisks.Count `
  • UseMaximumSize
  • # Initialize and format the new striped volume with 64KB allocation unit for SQL
  • Initialize-Disk -VirtualDisk (Get-VirtualDisk -FriendlyName 'StripedDataVolume') -PartitionStyle GPT
  • New-Partition -DiskNumber (Get-Disk -FriendlyName '*StripedDataVolume*').Number -UseMaximumSize -DriveLetter F
  • Format-Volume -DriveLetter F -FileSystem NTFS -AllocationUnitSize 65536 -NewFileSystemLabel 'SQLData'

Tip

Why Simple Resiliency in Azure? Because Azure Managed Disks are already protected by underlying three-way locally redundant storage (LRS), configuring Mirroring or Parity inside Windows Server Storage Spaces introduces redundant software overhead without additional availability benefits. Simple (Striped) resiliency aggregates IOPS and throughput linearly across all attached disks up to the VM's compute-level I/O capping limits.

Loading diagram... Azure IaaS Host Caching and Disk Layout for Windows SQL Server Workload