A council member asks whether a content delivery network is how inspectors reach VDI from home. What contrast should the operator draw?

A CDN distributes apps, updates, and media at scale; it is not how inspectors reach VDI from home, and it is not Connection Server, UAG, or Workspace ONE Access. 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: A CDN is not the Horizon Connection Server. Distractor concept: A CDN is not Unified Access Gateway in the DMZ. Distractor concept: A CDN is not Workspace ONE Access, the identity broker. Exam caveat: Contrast content distribution versus VDI access and identity services clearly for council questions. Operational check: Explain the home VDI path (client→UAG→broker) separately from CDN edge caches used for app/media bits. 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: A CDN is a magazine distributor, not the front desk and not the ID badge. It pushes bits (apps, updates, videos) out to the edge. Inspectors still reach VDI through UAG and Connection Server, and they still sign in through Access.