A charter city with a dark site and no outbound SaaS is told the UEM console must stay in the civic data center. Which deployment model is that?
Select an answer to reveal the explanation.
Short Explanation
A dark site is a building with no skybridge to a vendor cloud. On-premises UEM keeps the console in the civic data center; that is not Horizon Cloud.
Full Explanation
A dark site that must keep the UEM console in the civic data center is on-premises Workspace ONE UEM with a customer-hosted control plane. 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: Vendor-hosted Horizon Cloud control plane is the opposite hosting model and is about Horizon. Distractor concept: UEM SaaS with no local console contradicts the dark-site residency requirement. Distractor concept: Intelligence SaaS dashboards alone are analytics, not the full UEM console residency need. Exam caveat: Dark site / no outbound SaaS / console must stay local → on-premises UEM. Operational check: Validate isolation assumptions, size local UEM infrastructure, and confirm enrollment works without SaaS console dependency. 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.