A parks clerk snapshot is offered as the city's Horizon disaster-recovery plan. What should the technician say belongs in recoverability instead?

Recoverability needs backup of Horizon and UEM configuration plus golden images—not one parks clerk VM snapshot as the civic DR strategy. 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: One clerk VM snapshot is not pod-wide DR. Distractor concept: Backing up only the Horizon Client installer on USB does not recover Connection Server. Distractor concept: Deleting the clerk VM weekly does not preserve Horizon configuration. Exam caveat: Config + golden images (+ documented restore) beat single-user snapshots as recoverability. Operational check: Back up Connection Server/UEM config and golden images, store offsite, and tabletop a restore without relying on one user snapshot. 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. Helpdesk coaching tip aligned to the conversational brief: Snapshotting one clerk desktop is like photographing one desk and calling city hall backed up. Recoverability means Horizon and UEM config plus golden images. A USB copy of Horizon Client does not rebuild the brokers.