City laptops for social workers ship with full Windows, Office, and Intelligent Hub. Which statement about client type is correct?

City social-worker laptops with full Windows, Office, and Intelligent Hub are fat clients that can still connect to Horizon when a specialized VDI session is required. 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: Intelligent Hub does not make them zero clients. Distractor concept: SaaS Office does not make them thin clients. Distractor concept: A local OS does not disqualify them as Horizon endpoints; fat clients commonly run Horizon Client. Exam caveat: Full PC + optional Horizon Client = fat client, still a valid Horizon endpoint. Operational check: Confirm Hub/Office local presence and a successful Horizon launch from the same laptop for specialized pools. 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: A city laptop is still a fat client even if Hub and Office live on it — it is a full PC that can also knock on a Horizon door when a specialized desktop is needed. Hub does not magically make it a zero client, and a local OS is exactly what a fat endpoint has.