Study guide
13.4 BranchCache: Distributed Cache and Hosted Cache Modes
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
13.4 BranchCache: Distributed Cache and Hosted Cache Modes
Key Takeaways Explain This Topic AI
Only one BranchCache mode may be used per branch office, although different branches in the same organisation may each use a different mode.
Distributed cache mode operates within a single subnet; a multi-subnet branch requires hosted cache mode for clients on different subnets to share a cache.
A file server becomes a BranchCache content server through the BranchCache for Network Files role service, whereas web and BITS application servers use the BranchCache feature.
BranchCache client functionality for HTTP and SMB requires Enterprise or Education editions of Windows; Pro editions support BITS caching only.
Hosted cache servers running Windows Server 2012 or later need no server certificate and encrypt the cache by default; disabling Offline Files breaks BranchCache SMB caching.
Last updated: August 2026
BranchCache: Distributed Cache and Hosted Cache Modes
DFS Replication reduces WAN traffic by placing a writable replica of the data in the branch. BranchCache solves the same bandwidth problem without replicating anything: the authoritative copy stays in the main office or the cloud, and only the bytes a branch user has already downloaded are cached locally for the next user who asks for them. It works for content served over SMB , HTTP/HTTPS and BITS , and it never changes how authentication or authorisation happen.
1. What BranchCache Caches, and How It Finds It
BranchCache is a wide-area network bandwidth optimization technology that caches content from remote corporate web servers (HTTP/HTTPS) and file servers (SMB) locally in branch offices. +-----------------------------------------------------------------------------------+
- | BRANCHCACHE DEPLOYMENT MODES |
- | |
- | [DISTRIBUTED CACHE MODE] [HOSTED CACHE MODE] |
- | (Branch Office <= 50 Users) (Branch Office > 50 Users) |
- | |
- | +----------+ +----------+ +----------+ +------------+ |
- | | Client A | <--> | Client B | | Client A | ---> | Dedicated | |
- | +----------+ +----------+ +----------+ | Hosted | |
- | ^ ^ ^ | Cache Serv | |
- | | (WS-Discovery) | | | (TCP 443) | |
- | v v v +------------+ |
- | +----------+ +----------+ +----------+ ^ |
- | | Client C | <--> | Client D | | Client B | -----------+ |
- | +----------+ +----------+ +----------+ |
- | * Peer-to-peer (No Server) * Dedicated Server Required |
- +-----------------------------------------------------------------------------------+
- BranchCache Caching Modes Comparison
Feature / Metric Distributed Cache Mode Hosted Cache Mode
Target Environment Small branch offices ( ≤ 50 \le 50 ≤ 50 users) with no dedicated server Medium-to-large branch offices ( > 50 > 50 > 50 users)
Hardware Requirements Zero server hardware (Peer-to-peer among Windows clients) Requires a local Windows Server host
Discovery Protocol WS-Discovery (UDP port 3702 multicast across local subnet) Direct HTTPS connection to Hosted Cache Server ( TCP port 443 )
Cache Persistence Distributed across client workstations; cache lost when laptops go offline Centralized and persistent on dedicated server storage
Subnet Boundary Limited to a single Layer 2 broadcast subnet Multi-subnet capable across the entire branch network
- Pre-Loading Content Not supported Supported via Publish-BCFileContent and Export-BCCachePackage
- BranchCache Configuration via Group Policy
Configure the following Group Policy settings under Computer Configuration -> Policies -> Administrative Templates -> Network -> BranchCache :
Turn on BranchCache: Enabled.
Set BranchCache Distributed Cache mode OR Set BranchCache Hosted Cache mode (specifying the Hosted Cache Server FQDN).
Configure BranchCache for Network Files: Sets the round-trip network latency threshold (default is 80 ms) above which SMB shares utilize BranchCache caching.
2. Choosing a Mode
Microsoft's actual selection criterion is not a user count — it is whether the branch has a server and how many subnets the branch spans :
Distributed cache mode requires no additional hardware, which is why it suits branches with no local server. Its hard constraint is that it operates on a single subnet : a file downloaded onto one subnet cannot be discovered by clients on another subnet in the same branch, and those clients will fetch it across the WAN again.
Hosted cache mode places the cache on one or more local servers. Because clients contact the hosted cache server directly rather than multicasting to discover peers, all clients in a multi-subnet branch share one cache . The cache also survives laptops going offline, so cache hit rates are materially higher.
You may deploy both modes in the same organisation, but only one mode per branch office . Since Windows Server 2012 a branch may have more than one hosted cache server.
Note
The commonly quoted "50 users" threshold for choosing hosted cache mode is a planning rule of thumb, not a documented product limit. If the branch has a server, or spans more than one subnet, hosted cache mode is the correct choice regardless of headcount.
3. Enabling the Content Servers
BranchCache accelerates only content that originates on a BranchCache-enabled content server. Content pulled directly from an internet web server or from Windows Update is never cached and shared. Which component you install depends on the content server type:
Content server type Location Install
File server using SMB Main office or cloud datacenter BranchCache for Network Files role service (File and Storage Services role)
- Web server (IIS, HTTP or HTTPS) Main office or cloud datacenter BranchCache feature
- BITS-based application server (for example WSUS) Main office or cloud datacenter BranchCache feature
- Hosted cache server Branch office BranchCache feature, with hosted cache server mode enabled
- BranchCache client Branch office Nothing to install — enable BranchCache and a mode through Group Policy
For a file server, installing the role service is only half the job: hash generation must also be enabled on each share through the Hash Publication for BranchCache Group Policy setting or the share's BranchCache property. # Main-office SMB content server
- Install-WindowsFeature -Name FS-BranchCache -IncludeManagementTools
- Set-SmbShare -Name 'Finance' -CachingMode BranchCache -Force
- # Branch hosted cache server
- Install-WindowsFeature -Name BranchCache -IncludeManagementTools
- Enable-BCHostedServer -RegisterSCP # publishes a service connection point in AD DS
- Set-BCCache -Percentage 20 # size the local cache
- Get-BCStatus # verify the role and cache state
- # Branch client (usually set by Group Policy instead)
- Enable-BCDistributed # peer-to-peer mode
- Enable-BCHostedClient -ServerNames 'BR-CACHE-01.corp.contoso.com'
Clients are normally configured under Computer Configuration → Policies → Administrative Templates → Network → BranchCache : turn on BranchCache, then select either distributed cache mode or hosted cache mode (hosted cache clients can also discover the server automatically through the service connection point rather than a hard-coded name).
Content can be pre-staged into a branch during a maintenance window instead of being fetched on first use: # On the content server: generate hashes and export a cache package
- Publish-BCFileContent -Path 'D:\Shares\Deployments' -Recurse
- Export-BCCachePackage -Destination 'D:\Staging\branch-preload.zip'
- # On the hosted cache server: import the pre-generated package
- Import-BCCachePackage -Path 'E:\branch-preload.zip'
- 4. Versions, Editions and Security Behaviour
Three constraints regularly decide an exam answer:
Client edition matters. BranchCache client support for HTTP and SMB requires Enterprise or Education editions of Windows. Pro editions support BITS caching only — so a branch standardised on Windows Pro will never cache file share content no matter how the servers are configured.
Content information versions do not mix. V1 uses large fixed-size segments; V2 uses smaller variable-size segments that survive edits far better. A branch containing clients that negotiate V1 and clients that negotiate V2 will have those two populations not sharing cached content with each other in distributed cache mode.
Offline Files must stay enabled. If BranchCache is used for SMB caching and Offline Files is disabled, BranchCache SMB caching stops working correctly.
Security is hash-based rather than trust-based. The content server derives content information — a block hash list , a hash of data and a segment secret — using SHA-256 and a per-server server secret . A client must first be authenticated and authorised by the original content server to receive that content information; only then can it locate and decrypt blocks held by peers or by the hosted cache server. Blocks in transit are encrypted with a key derived from the segment secret, and any block that fails hash validation is discarded and refetched from the source. That is why BranchCache does not weaken NTFS permissions: possessing an encrypted block is useless without content information you were never authorised to receive.
Cache-at-rest behaviour differs by role. On distributed cache clients the local cache is protected only by file system ACLs, so BitLocker is recommended where physical security is weak. Hosted cache servers running Windows Server 2012 or later encrypt all cached data by default and, unlike Windows Server 2008 R2, require no server certificate .