Clerks cannot resolve horizon.city.example after a DNS outage even though Connection Server is running. What does that demonstrate?

If clerks cannot resolve horizon.city.example after a DNS outage while Connection Server still runs, DNS is a Horizon dependency—clients and components must resolve brokers and UAG. 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: DNS is not optional merely because someone bookmarked a Connection Server IP. Distractor concept: DHCP failure is not the only name-resolution problem in a pod. Distractor concept: Workspace ONE Intelligence does not replace DNS for VDI hostnames. Exam caveat: Name resolution is a hard dependency; running brokers without DNS still fail clients. Operational check: Break/fix DNS for the broker name in lab, confirm failure, restore DNS, and document DNS as a Horizon dependency. 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: If the street signs disappear, knowing the building is open does not help — clerks still cannot find horizon.city.example. DNS is a Horizon dependency for clients and components. Bookmarking raw IPs is not the design, and Intelligence is analytics, not name lookup.