Municipal court clerks share counters. IT wants any clerk to walk up, authenticate, and get a clean desktop rather than a PC full of the previous shift's bookmarks and cached case PDFs. Which VDI approach fits?
Select an answer to reveal the explanation.
Short Explanation
A shared court counter should feel like a freshly wiped chalkboard at the start of each shift. Non-persistent pooled VDI hands every clerk a clean desktop and leaves yesterday's bookmarks behind.
Full Explanation
Non-persistent or pooled virtual desktops support shared civic counters because the session is reset or discarded at logoff. The next authenticated clerk does not inherit cached case files or personal browser state. Dedicated always-on PCs, local browser caches, and replaying another shift's writable volume keep leftover data on the counter.