Microsoft Updated AZ-800 Exam Questions and Answers by delia

The hybrid connectivity chapter explains Azure Relay (Hybrid Connections/WebSockets) as a service that lets on-premises apps be securely exposed without opening inbound firewall ports. The server initiates an outbound connection to Azure Relay, and Internet clients connect to Azure Relay, which relays traffic over WebSockets to the on-premises listener. The guide emphasizes: “Azure Relay enables exposing services behind firewalls without inbound port openings, supporting WebSockets for bidirectional communication.” Alternatives either require inbound exposure or additional infrastructure: ARR (reverse proxy) and Web Application Proxy run on-premises and would need inbound ports. Azure Application Gateway can proxy HTTP(S) and supports WebSockets pass-through, but to reach an on-prem server you’d typically need VPN/ExpressRoute and corresponding inbound allowances. Since the requirement is to minimize inbound ports on Firewall1 while supporting WebSockets, Azure Relay is the correct solution.

The Windows Server Data Deduplication section of the Administering Windows Server Hybrid Core Infrastructure course explains that deduplicated volumes require the deduplication components on any system that needs to read them: “Data Deduplication is implemented as a filter driver. To access a deduplicated volume on another server, you must install the Data Deduplication role service; otherwise files may appear as reparse points and cannot be opened.” It also clarifies that “when the role is present, the system transparently rehydrates data on access without requiring a restore.” In your scenario, Disk2 was deduplicated on Server1 and is now attached to Server2. To regain immediate access to all files as quickly as possible, install the Data Deduplication role service on Server2 so the filter can interpret the chunk store and metadata and make the files readable instantly. Creating a storage pool is irrelevant because the disk already exists and is readable; FSRM does not interpret dedup data; and restoring from Azure Backup would be slower and unnecessary since the original deduplicated volume is intact. Hence, the fastest, correct action is to install Data Deduplication on Server2.https://docs.microsoft.com/en-us/windows-server/storage/data-deduplication/overview

In the context of Windows Server Hybrid Core Infrastructure and container networking, choosing the correct network driver is critical for application deployment. According to official documentation, the l2bridge (Layer 2 Bridge) network mode is used when container hosts are connected to the same IP subnet. In this configuration, each container is assigned an IP address from the same prefix as the container host. All container traffic is bridged to the physical network through an external Hyper-V Virtual Switch. Because the containers share the same underlying network infrastructure as the host, they are visible to the rest of the physical network without requiring Network Address Translation (NAT).

The documentation specifies that for multi-node clusters or deployments where containers must be directly reachable on the physical network via their own IP addresses, l2bridge is the standard choice. This differs from NAT, which uses a private internal IP range and translates traffic through the host's IP, and Transparent mode, which is often used for individual hosts where the container is directly connected to the physical network but can have complexities in virtualized environments. l2tunnel is specifically used for Microsoft Cloud Stack (Azure Stack HCI) and SDN scenarios, typically involving encapsulation, which is not the standard requirement for a general multi-container application deployment on a single server unless specified. Therefore, for a high-performance, direct-access network that bridges traffic at Layer 2, l2bridge is the verified architectural choice for Windows containers.

The Administering Windows Server Hybrid Core Infrastructure content for Azure IaaS VMs explains that Azure VMs include a temporary disk (commonly D:) that is ephemeral and not persisted; by default, the Windows paging file (pagefile.sys) is placed on this temporary disk. The guidance states that the temporary disk must not be used for application data and that if you need to reclaim the D: letter for a persistent data disk, you must first relocate the paging file to another drive (typically C:), and then change the drive letters so the data disk can assume D:. Stopping/deallocating the VM is not required for drive-letter changes inside the guest, and expanding the temporary disk is irrelevant because it remains non-persistent.

In this scenario, to make the persistent data disk use D:, the first step is to move pagefile.sys off the temporary storage (D:) to the OS drive (C:). After that, you can change the temporary disk to another letter (for example, F:), and then change the existing data disk from E: to D:, meeting the requirement that App1’s data reside on a persistent disk assigned to D:.