City permitting clerks keep permit PDFs on tower PCs. The EUC technician wants desktops that live in the civic data center so a stolen clerk PC does not hold the only copy of an application file. Which VDI benefit addresses that goal?

For city permitting clerks, the correct VDI benefit is keeping the Windows desktop and permit files in the civic data center so a stolen tower is only a session display, not the sole copy of application PDFs. In municipal EUC terms, treat the endpoint as a window into city systems when the architecture says so, not as the system of record for the files or apps in the stem. Distractor concept: Copying permit folders to USB in the treasurer's safe is removable-media backup, not centralized VDI, and it still creates portable copies that walk out of city hall. Distractor concept: Installing a thicker local image on every tower keeps files on the endpoint and increases theft exposure instead of solving it. Distractor concept: Replacing Horizon with an NSX overlay confuses network virtualization with desktop delivery; NSX does not relocate the desktop OS into the data center. Exam caveat: Associate stems often mix Horizon, NSX, and USB backup—choose the control that matches keeping files off the stolen PC. Operational check: Confirm clerk sessions land on data-center VMs with civic storage paths, and verify a wiped endpoint cannot open permit PDFs without an authenticated brokered session. Record the chosen control and the rejected failure modes in the civic change ticket or runbook so on-call staff and auditors share the same rationale after the next maintenance window. Re-validate after personnel or image changes that the same control still meets the city's continuity, security, and support expectations for this service.