Question 10
In the Cedarview Engineering pilot environment, a controlled verification is required for: An acquired branch connects through an undersized VPN and the team projects total desktop bandwidth using only average traffic per connected user. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter. This is an independently observable result of the targeted change: Plan capacity against observed high-percentile bandwidth and bursty sign-ins, incorporating headroom for concurrent Microsoft Teams meetings. It closes the specific Cedarview Engineering failure: An acquired branch connects through an undersized VPN and the team projects total desktop bandwidth using only average traffic per connected user.
Incorrect Answers
A simulated afternoon peak shows reduced packet loss and stable interactive response without changing healthy session host capacity. This is evidence for a DIFFERENT remediation: Measure endpoint-to-service latency, packet loss, and concurrent session throughput, then resize or prioritize the constrained network path. That remediation addresses: A remote call center's AVD sessions become unresponsive each afternoon even though session host CPU is healthy and the WAN link is saturated. It does not establish resolution of the Cedarview Engineering problem: An acquired branch connects through an undersized VPN and the team projects total desktop bandwidth using only average traffic per connected user. The required outcome here is: A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter.
A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures. This is evidence for a DIFFERENT remediation: Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path. That remediation addresses: A session host reports Available yet RDP Shortpath remains inactive; engineers troubleshoot only Azure VM power state rather than the connection transport. It does not establish resolution of the Cedarview Engineering problem: An acquired branch connects through an undersized VPN and the team projects total desktop bandwidth using only average traffic per connected user. The required outcome here is: A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter.
A busy-hour pilot with representative display and media workloads stays within the measured link headroom and user latency objectives. This is evidence for a DIFFERENT remediation: Estimate concurrent session bandwidth by workload, multimedia usage, latency tolerance, and peak concurrency before choosing network capacity. That remediation addresses: A new Azure Virtual Desktop office supports 480 concurrent users, but network sizing was estimated from the number of physical desks and omits session bandwidth. It does not establish resolution of the Cedarview Engineering problem: An acquired branch connects through an undersized VPN and the team projects total desktop bandwidth using only average traffic per connected user. The required outcome here is: A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter.