A help-desk technician is investigating performance complaints from remote users who access their work environment through the company's virtual desktop infrastructure (VDI). The users connect with thin clients and report that applications hesitate before opening and typed characters do not appear on the screen for almost a second. Local diagnostic tools on the thin clients show no CPU, RAM, or storage bottlenecks. Which client-side resource should the technician examine first to address the sluggish VDI experience?
Local SSD health and remaining lifespan on the thin client
Amount of free local RAM on the thin client
CPU clock speed of the thin client's processor
Available network bandwidth and latency between the thin client and the data center
VDI sessions run on virtual machines in the data center; the thin client mainly forwards keyboard, mouse, and display information. Because processing and storage occur on the host server, local CPU speed, memory, and drive health have minimal impact on session responsiveness. Slow screen refreshes and delayed keystrokes are classic symptoms of insufficient bandwidth or high latency between the client and the VDI host. Verifying network performance to the data center is therefore the most logical first step. The other resources listed are far less likely to cause these real-time interaction delays in a VDI environment.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is latency, and how does it affect network performance?
Open an interactive chat with Bash
How can network bandwidth impact VDI performance?
Open an interactive chat with Bash
Why do thin clients rely on data center resources in a VDI setup?