Free Microsoft AZ-140 Actual Exam Questions - Question 4 Discussion
Windows Server and is deployed to the West US Azure region.
You deploy a new Azure Virtual Desktop host pool named HostPool1 to the East US Azure region.
You need to ensure that all the traffic between HostPool1 and Server1 is routed via the Microsoft
backbone network.
What should you use?
B vs A, but service endpoints are mostly for Azure PaaS, so B fits cross-region VNet communication better.
This one seems pretty clear to me: B, virtual network peering. Since Server1 and HostPool1 are in different regions, peering their VNets ensures traffic uses the Microsoft backbone. Service endpoints (A) work within the same region, so they don’t really help here. Routing tables (C) just control routing but can’t force traffic onto Microsoft’s network, and Traffic Manager (D) is more for load balancing across endpoints, not controlling routing paths. So for cross-region secure traffic inside Azure, peering is the way to go.
B, virtual network peering is the only option that guarantees Microsoft backbone routing cross-region.
Not C, routing tables control traffic flow but don’t guarantee it stays on Microsoft’s backbone. Virtual network peering (B) is designed exactly for private cross-region traffic within Azure.
It’s A because service endpoints extend your virtual network private address space, keeping traffic on the Microsoft backbone without needing peering. Peering isn’t always necessary if you just want secure regional access.
It’s B, because peering connects VNets privately without internet traffic.
This one seems pretty straightforward if you’ve worked with AVD before. First, you’d get the RD connection info with the Azure CLI. Then download the RDP file from that output, and finally, open that file with mstsc.exe to connect. So, looks like it’s: run the Azure CLI command to get the RDP file, save/download it, and then use Remote Desktop Connection to open that RDP file. Not too complicated once you know the flow.