A metro IT planner compares hosting models. Which statement correctly distinguishes Horizon Cloud environment types from a self-managed on-prem pod?
Select an answer to reveal the explanation.
Short Explanation
Two families: bake your own Horizon 8 pod on civic vSphere, or consume Horizon Cloud on a public cloud such as AWS or Azure. They are not the same Connection Server screen, and Cloud still delivers desktops.
Full Explanation
Horizon Cloud can target public clouds such as AWS or Azure, while a self-managed Horizon 8 pod runs on civic vSphere. That distinction is how metro IT planners should separate Horizon Cloud environment types from an on-premises Connection Server pod operated under municipal control in the city data center. It is false that Horizon Cloud exists only on civic vSphere and that AWS and Azure are not listed environment types. Horizon 8 on-prem and Horizon Cloud are not the same console on Connection Server. Horizon Cloud on AWS does not replace Workspace ONE Access and still delivers virtual desktops rather than abandoning desktop delivery. Exam caveat: Access, UEM, and Horizon Cloud often integrate in a full digital workspace, but hosting-model questions focus on where desktops run and which control plane applies. Operational check: draw two columns—Horizon Cloud on AWS or Azure versus Horizon 8 on civic vSphere—list consoles, ownership, and failure domains, confirm planners are not told that Cloud and on-prem share one Connection Server UI, and file the comparison with the architecture board. Keep civic diagrams labeled so help-desk and network teams do not swap these products during incidents.