A transit authority compares Horizon 8 pods it operates on city vSphere with Horizon Cloud, where the vendor hosts the control plane. What is the associate-level distinction?
Select an answer to reveal the explanation.
Short Explanation
Both deliver a desktop; the argument is who owns the front desk. City vSphere pods keep the broker on-site; Horizon Cloud puts that control plane with the vendor.
Full Explanation
Horizon 8 on city vSphere and Horizon Cloud share delivered-desktop intent; the associate distinction is where the broker/control plane is hosted. 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: Horizon Cloud is not an NSX Tier-1 gateway. Distractor concept: On-premises Horizon 8 can run on vSphere; denying that is false. Distractor concept: Horizon Cloud does not remove the need for identity or Windows desktops. Exam caveat: Same desktop idea, different control-plane hosting—do not redefine Horizon Cloud as NSX or "no Windows/identity." Operational check: Diagram both options showing control-plane location, identity still required, and desktop VMs still present. 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: Both deliver a desktop; the argument is who owns the front desk. City vSphere pods keep the broker on-site; Horizon Cloud puts that control plane with the vendor.