During enrollment week, 400 parks tablets pull the same Intelligent Hub package. What happens without a CDN or edge cache?
Select an answer to reveal the explanation.
Short Explanation
Four hundred tablets grabbing the same Hub package at once is rush hour on a one-lane bridge to the SaaS origin. A CDN puts copies at the edge so the civic internet pipe does not melt. Connection Server, App Volumes, and DHCP are not what those tablets are talking to for the installer.
Full Explanation
Without a CDN or edge cache, 400 parks tablets pulling the same Intelligent Hub package can saturate the SaaS origin and civic internet pipe; with a CDN, devices hit nearby caches. 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: Connection Server does not refuse enrollments for lack of a CDN. Distractor concept: App Volumes writable volumes failing is a different failure domain. Distractor concept: DHCP running out of "Blast ports" is not a coherent enrollment-week CDN symptom. Exam caveat: Enrollment stampede without edge cache hurts origin/WAN; CDN mitigates—don't blame Horizon/App Volumes/DHCP myths. Operational check: Load-test or review metrics from enrollment week showing origin vs cache hits after CDN enablement. 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.