Free Microsoft AZ-140 Actual Exam Questions - Question 5 Discussion
You identify the network latency between the locations where users reside and the planned
deployment.
What should you use to identify the best Azure region to deploy the host pool?
It’s B because Experience Estimator predicts user experience before deployment, unlike Traffic Manager.
Actually, B makes more sense here since the Experience Estimator is designed to simulate user experience and latency before deploying, unlike Traffic Manager which handles live traffic routing after deployment.
A vs B? I’d drop D and C for sure—Advisor is more about cost/performance tweaks, and Monitor is for after things are up. Between Traffic Manager and Experience Estimator, Traffic Manager is more for routing traffic and failover, not really for picking the best region based on user latency before deployment. The Experience Estimator actually simulates user experience including latency, so it fits better for planning. So B seems like the more targeted tool here.
B/D? I’m ruling out C because Azure Monitor is more post-deployment monitoring, not for initial region choice. D could be tempting since Azure Advisor gives recommendations, but those are usually about cost and best practices, not latency specifics. Between A and B, B fits better since it’s built to estimate user experience based on latency before deployment, while Traffic Manager is more about managing traffic after you’ve set things up. So I’d go with B for planning the right Azure region upfront.
Maybe A since Traffic Manager measures real-time latency between regions.
B. The Experience Estimator is designed specifically for assessing Azure Virtual Desktop performance, including network latency, so it’s better suited than Traffic Manager or Monitor for picking the right region before deployment.
Option A makes sense because Azure Traffic Manager can direct users to the endpoint with the lowest latency, helping pick the best Azure region for deployment.
Not sure about all the steps, but think you have to first create the MSIX package, then upload it to Share1, register the app for MSIX app attach, and finally assign it to Pool1. Seems like a logical order.