Desktops move to Horizon Cloud, but health-department phones still need enrollment, profiles, and compliance. Which statement is correct?
Select an answer to reveal the explanation.
Short Explanation
Moving the desks to Horizon Cloud does not turn phones into desktop pools. Cloud is VDI/DaaS; UEM still enrolls and complies the phones. Control Plane is not the Devices dashboard, and Boxer is email, not MDM.
Full Explanation
When desktops move to Horizon Cloud, health-department phones still need enrollment, profiles, and compliance on Workspace ONE UEM. Horizon Cloud is VDI and DaaS; phones remain on UEM even when desktops move to Horizon Cloud. Changing desktop hosting does not convert inspector phones into desktop pools or retire mobile device management. Horizon Cloud does not replace Workspace ONE UEM so that phones enroll as desktop pools. Horizon Cloud Control Plane is not the UEM Devices dashboard for iOS. Boxer does not become the MDM agent for phones once Horizon Cloud is licensed. Exam caveat: Hub, Access, UEM, and Horizon Cloud commonly coexist in city designs—moving desktops to the cloud does not retire mobile UEM for field inspectors. Operational check: after a Horizon Cloud pilot, enroll a health-department phone in UEM, confirm profiles and compliance still apply, launch a cloud desktop separately for the same user if entitled, document that Control Plane is not the iOS Devices console, and update the health-department EUC onboarding checklist. Keep civic diagrams labeled so help-desk and network teams do not swap these products during incidents. Document the successful test in the municipal runbook for the next change window.