Instant-clone 311 desktops need HA, DRS, and vMotion. Which product actually provides those virtualization features under Horizon?
Select an answer to reveal the explanation.
Short Explanation
Horizon books the session; vSphere owns the building. HA, DRS, and vMotion are hypervisor-cluster features, not something Connection Server, UEM, or DEM pretend to be. 311 clones are just VMs living on vSphere.
Full Explanation
Instant-clone 311 desktops that need HA, DRS, and vMotion depend on vSphere, the virtualization platform that hosts Horizon desktop VMs and supplies those high-availability and mobility features for civic call-center workloads. Horizon sits on vSphere; it does not replace the hypervisor’s cluster services. Horizon Connection Server is the broker, not the hypervisor for desktop VMs. Workspace ONE UEM does not vMotion enrolled phones between clusters as a substitute for vSphere HA and DRS. Dynamic Environment Manager applies user-environment settings and does not live-migrate settings as a host-mobility feature in place of vMotion. Exam caveat: on-prem Horizon availability is tightly coupled to vSphere cluster health—broker health alone cannot place desktop VMs without a healthy hypervisor layer underneath the pod. Operational check: validate the 311 desktop cluster has HA and DRS configured in vCenter, put a host in maintenance mode and confirm clones vMotion as expected, document that Connection Server and UEM are not providers of those virtualization features, and attach the result to the facilities maintenance runbook. Keep civic diagrams labeled so help-desk and network teams do not swap these products during incidents.