Question 650
In the Redwood Media Group pilot environment, a controlled verification is required for: An administrator tries to diagnose an app hang but cannot identify which AVD session and host belongs to the affected user. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
The support record links the correct user session ID to its host and the remediation avoids interrupting a healthy colleague. This is an independently observable result of the targeted change: Use AVD session management and host pool diagnostics to locate the specific user session and host before taking any action. It closes the specific Redwood Media Group failure: An administrator tries to diagnose an app hang but cannot identify which AVD session and host belongs to the affected user.
Incorrect Answers
The corrected host registration or broker issue resolves the failures without unnecessarily increasing VM count. This is evidence for a DIFFERENT remediation: Correlate host status, connection diagnostics, and AVD agent events before deciding whether capacity expansion is appropriate. That remediation addresses: One host pool has high connection failure rates but acceptable resource use, so an operator adds more VM capacity without inspecting agent health. It does not establish resolution of the Redwood Media Group problem: An administrator tries to diagnose an app hang but cannot identify which AVD session and host belongs to the affected user. The required outcome here is: The support record links the correct user session ID to its host and the remediation avoids interrupting a healthy colleague.
An intentionally delayed test sign-in shows its problematic stage and associated performance counters in the monitoring view. This is evidence for a DIFFERENT remediation: Configure Azure Monitor diagnostics for AVD connections and host performance, then correlate user logon phases with host metrics. That remediation addresses: AVD users report long logon times, but the support dashboard includes only Azure VM CPU metrics and cannot identify connection stage delays. It does not establish resolution of the Redwood Media Group problem: An administrator tries to diagnose an app hang but cannot identify which AVD session and host belongs to the affected user. The required outcome here is: The support record links the correct user session ID to its host and the remediation avoids interrupting a healthy colleague.
The orphaned session is cleared and the assigned personal VM and its retained user data remain intact. This is evidence for a DIFFERENT remediation: Use supported AVD session disconnect or logoff management with a documented profile and data-preservation procedure. That remediation addresses: A disconnected session continues consuming a personal desktop for days and the help desk is unsure whether removing the session deletes the user VM. It does not establish resolution of the Redwood Media Group problem: An administrator tries to diagnose an app hang but cannot identify which AVD session and host belongs to the affected user. The required outcome here is: The support record links the correct user session ID to its host and the remediation avoids interrupting a healthy colleague.