Council is told HA means two Connection Servers. How should the EUC technician separate the terms?
Select an answer to reveal the explanation.
Short Explanation
Two different safety nets get called HA in hallway talk. vSphere HA restarts a VM when a host dies; a second Connection Server is a spare front desk if one broker dies. Do not let council treat those as the same switch.
Full Explanation
vSphere HA restarts VMs after host failure; extra Connection Servers are application-level broker redundancy—two different "HA" ideas. 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: Two Connection Servers are not vSphere HA and do not restart ESXi hosts after a broker crash. Distractor concept: DRS alone is not the Horizon broker high-availability control. Distractor concept: UEM compliance plus two Hub installs is not farm HA for desktops. Exam caveat: Separate host/VM HA from broker redundancy; hallway "HA" talk mixes them. Operational check: Document both: cluster HA settings for desktop VMs and a second Connection Server for broker survivability. 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: Two different safety nets get called HA in hallway talk. vSphere HA restarts a VM when a host dies; a second Connection Server is a spare front desk if one broker dies. Do not let council treat those as the same switch.