Scenario: A user informs a Citrix Administrator that audio quality has degraded on their virtual desktop that uses personal vDisk. Audio was functioning correctly the previous day. Which action…

Orla P.Jun 26, 2026

D is your answer here. When audio quality degrades suddenly on a virtual desktop, the fastest place to start is Citrix Director because it gives you live session details for that specific user, including latency, bandwidth, and protocol metrics that can point directly at whether this is a network issue, a session configuration problem, or something with the HDX audio channel itself. The other options are not useless, but they are second steps, not first steps. Checking Receiver logs on the client (A) or the event log on the desktop (C) requires you to know what you are looking for already, and reviewing audio redirection policy (B) would only make sense if audio never worked or stopped working for everyone, not just one user on one day. Director gets you to the problem faster because it correlates session health data in one place without you having to bounce between the client and the VDA.

Giselle K.Jun 16, 2026

D is right, though I would argue B is where your instincts will naturally pull you since audio redirection policies are the first thing most of us touch when audio breaks, but the question is asking how to investigate an issue that was working yesterday, not reconfigure something, and Director session details will show you bandwidth, latency, and ICA channel data for that specific session in real time without you guessing. Start in Director, let the data tell you where to dig next.

Mei-Ling H.Jun 26, 2026

Got D on my real exam by remembering Director shows live session audio metrics.

Isolde G.Jun 22, 2026

C is the right call here because the audio was working fine the day before, which rules out a policy misconfiguration right away. If the Citrix audio redirection policy had changed, it would have broken for multiple users or immediately after a policy push, not just quietly degraded overnight for one person on a personal vDisk. The personal vDisk layer is key in this scenario, because changes written to that disk, driver updates, application installs, or a corrupted vDisk layer, can absolutely surface as device-level errors, and those show up in the Windows event log on the desktop itself, not in Director or Receiver logs. Director is great for session bandwidth and latency stats but it does not expose the guest OS internals that would point you to a vDisk-related audio driver fault, so pulling the event log from that desktop is the most direct path to a root cause here.

Brenda K.Jun 26, 2026

D is right, Director shows live session audio details fast.