A branch has ample spare bandwidth and negligible loss, but sessions to a distant Azure region show a stable 210-ms RTT. Business requirements permit another host region. Which change best addresses the measured network constraint?

✓ Correct answer

• Deploy the workload in a suitable region closer to the branch

The measured constraint is latency rather than capacity. A closer suitable host region can reduce propagation delay; remeasure representative sessions afterward. Option explanations: A. Deploy the workload in a suitable region closer to the branch: Shortening the geographical path addresses the propagation component of RTT. B. Double the internet link's advertised bandwidth: More capacity does not remove distance-related delay when the existing link is not congested. C. Raise the host-pool session limit: Higher density does not correct network latency and could add host contention. D. Increase the profile-container maximum size: Profile capacity does not shorten the endpoint-to-host path. Sources: Prerequisites for Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/prerequisites; Network guidelines — https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/network-guidance

Read the source reference