Study guide
1.5 Active Directory Sites, Subnets & Site Link Topology
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
1.5 Active Directory Sites, Subnets & Site Link Topology
Key Takeaways Explain This Topic AI
DEFAULTIPSITELINK ships with a cost of 100, a replication interval of 180 minutes and a 24x7 schedule; the interval minimum is 15 minutes and the maximum is 10,080 minutes.
The KCC always routes over the lowest total site link cost, so cost should be assigned inversely to link speed rather than left at the default everywhere.
"Bridge all site links" is enabled by default and makes site links transitive; disable it and build explicit site link bridges only when the IP network is not fully routed.
A client whose IP address matches no subnet object has no site affinity and may authenticate across the WAN; create one site per Azure region and map every VNet address space to it.
Universal Group Membership Caching lets a site without a global catalog complete logons by caching universal group membership and refreshing it every eight hours.
Last updated: August 2026
Active Directory Sites, Subnets & Site Link Topology
In hybrid and enterprise multi-site environments, Active Directory Domain Services must balance rapid directory consistency against wide-area network (WAN) bandwidth consumption. The site topology is the map that makes that balance possible: it tells domain controllers which replication partners are cheap to reach, and it tells clients which domain controller is physically nearest. Get the site and subnet design wrong and every symptom that follows — slow logons, authentication crossing an ExpressRoute circuit, Azure IaaS virtual machines authenticating against an on-premises domain controller — looks like a network problem when it is really a directory-configuration problem.
1. Active Directory Sites, Subnets & Site Links Architecture
An Active Directory Site represents a well-connected physical location defined by high-bandwidth, low-latency IP subnets (typically a local datacenter or campus LAN). +-----------------------------------------------------------------------------+
- | AD DS SITES AND SUBNETS ARCHITECTURE |
- | |
- | [SITE: HQ-Dallas] [SITE: Branch-Chicago] |
- | Subnets: 10.10.0.0/16, 10.20.0.0/16 Subnets: 192.168.1.0/24 |
- | +--------------------------+ +--------------------------+ |
- | | DC-DAL-01 | DC-DAL-02 | | BR-CHI-01 (RODC) | |
- | +--------------------------+ +--------------------------+ |
- | \ / |
- | +========= [SITE LINK: DAL-CHI] ==+ |
- | Cost: 50 |
- | Replication Frequency: 30 mins |
- | Schedule: 24x7 Available |
- +-----------------------------------------------------------------------------+
Core Components:
IP Subnets: IP subnet objects (e.g., 10.10.1.0/24 , fe80::/64 ) are created in Active Directory Sites and Services and explicitly associated with a Site. When a domain-joined client boots, the Netlogon service matches the client's current IP address against the subnet objects to determine its local site, querying DNS for site-specific SRV records (e.g., _ldap._tcp.HQ-Dallas._sites.dc._msdcs.corp.contoso.com ).
Site Links: Site links connect two or more sites, modeling the WAN connectivity between them. Site links use the IP transport (RPC over IP) for all intra-forest replication. (The legacy SMTP transport is restricted to asynchronous inter-site replication across non-contiguous forests without RPC connectivity and cannot replicate the Domain directory partition).
Site Link Cost: A relative integer cost metric (range: 1 to 32767 , default: 100 ). Active Directory uses Dijkstra's shortest-path algorithm to calculate the lowest cumulative cost path between sites.
Replication Frequency & Schedule:
Frequency: Defines how often inter-site replication is attempted during allowable hours (default: 180 minutes , minimum configurable: 15 minutes ).
Schedule: A 7-day, 24-hour bitmap grid determining the specific hours when replication across the WAN is permitted.
2. Site Links: Cost, Schedule and Replication Interval
A site link is the object that says two or more sites can replicate with each other and how expensive that path is. Every new forest ships with one site link named DEFAULTIPSITELINK in the IP (RPC over IP) transport container, and every site you create is placed into it unless you move it.
Site link attribute Default value What it controls
Cost 100 Relative expense of the path. The KCC always prefers the lowest total cost route between two sites.
Replication interval 180 minutes How often bridgehead servers poll across the link. Minimum 15 minutes, maximum 10,080 minutes (one week).
Schedule 24 × 7 (always available) The windows during which replication may occur at all. A closed schedule beats a short interval — replication simply waits.
Transport IP RPC over IP. The legacy SMTP transport cannot replicate the domain partition and is effectively obsolete.
Cost is relative , not a unit of bandwidth. A common design assigns cost inversely to link speed — a 1 Gbps metro fibre link might be cost 10, a 100 Mbps MPLS circuit cost 50, and a satellite branch cost 500 — so the KCC naturally routes through the fast paths. Two competing routes with identical cost cause the KCC to choose by the site link's globally unique identifier (GUID), which is effectively arbitrary; if you care which path wins, make the costs different. # Create a site, a subnet mapped to it, and a costed site link
- New-ADReplicationSite -Name 'AzureEastUS'
- New-ADReplicationSubnet -Name '10.20.0.0/16' -Site 'AzureEastUS' -Location 'Azure East US VNet'
- New-ADReplicationSiteLink -Name 'HQ-to-AzureEastUS' `
- SitesIncluded 'HQ-Seattle','AzureEastUS' `
- Cost 30 -ReplicationFrequencyInMinutes 15 -InterSiteTransportProtocol IP
- # Tighten an existing link and confirm the values that are actually stored
- Set-ADReplicationSiteLink -Identity 'DEFAULTIPSITELINK' -Cost 100 -ReplicationFrequencyInMinutes 60
- Get-ADReplicationSiteLink -Filter * -Properties Cost,ReplicationFrequencyInMinutes,SitesIncluded |
- Format-Table Name,Cost,ReplicationFrequencyInMinutes
- Site Link Bridging and Transitivity
By default the forest has Bridge all site links enabled on the IP transport, which makes every site link transitive: if HQ links to Branch-A and HQ links to Branch-B, the KCC treats Branch-A and Branch-B as reachable through HQ even though no link joins them directly. That is the correct setting for a fully routed IP network. You disable bridging — and then build explicit site link bridge objects — only when the physical network is not fully routed, for example when two branch networks can each reach the hub but cannot reach each other.
3. Bridgehead Servers and Automatic Site Coverage
Inter-site replication never happens between arbitrary pairs of domain controllers. In each site, the Intersite Topology Generator nominates one bridgehead server per directory partition per transport, and all inter-site traffic funnels through it. You can nominate a preferred bridgehead server manually in Active Directory Sites and Services, but doing so is a trap the exam likes: if every preferred bridgehead you designated is offline, Active Directory does not fall back to an unlisted domain controller, and inter-site replication for that partition stops entirely.
Automatic site coverage solves the opposite problem — a site with subnets and users but no domain controller. Domain controllers in the next-lowest-cost site register site-specific SRV records in DNS on behalf of the empty site, so clients there still find a sensible domain controller instead of a random one. Where a site has no local domain controller and slow WAN links, enable Universal Group Membership Caching (UGMC) on the site: a domain controller caches a user's universal group memberships at first logon and refreshes them every eight hours, which allows logon without contacting a global catalog across the WAN.
4. Subnet-to-Site Mapping, DC Locator and Hybrid Design
The DC Locator process is what turns the site topology into real client behaviour. A client sends its IP address to a domain controller during the initial DsGetDcName call; the domain controller compares that address against the subnet objects in the directory, returns the name of the site the client belongs to, and the client then queries DNS for site-specific SRV records under _tcp.<SiteName>._sites.dc._msdcs.<domain> . Any subnet that is not defined in Active Directory produces a client with no site affinity, which then authenticates against whichever domain controller answers first — frequently one across the WAN. :: Which site does this machine believe it is in, and which DC did it choose?
- nltest /dsgetsite
- nltest /dsgetdc:corp.contoso.com /force
:: Log unmapped subnets: NETLOGON writes entries to %SystemRoot%\debug\netlogon.log
Important
Hybrid rule: create one Active Directory site per Azure region that hosts domain controllers, and register every Azure virtual network address space as a subnet object mapped to that site. Without it, Azure IaaS virtual machines have no site affinity and will authenticate over the VPN or ExpressRoute circuit back to on-premises domain controllers — the single most common cause of "slow logon in Azure" tickets.
Moving a domain controller between sites is a directory operation, not a reinstall: Move-ADDirectoryServer -Identity 'DC-AZ-01' -Site 'AzureEastUS'