End User Computing Fundamentals
The End User Computing Fundamentals domain tests how you choose and operate an endpoint delivery model for different user groups. Expect questions on personas, device ownership, thick/thin/VDI/DaaS trade-offs, the endpoint lifecycle, network dependencies, data locality, peripherals, and service levels. The exam rewards decisions that match user workload and connectivity, not product name recognition.
Core rules
- Start with the persona: task, mobility, latency tolerance, data sensitivity, and connectivity. A call-center agent, a field engineer, and a designer need different compute.
- Map delivery to constraints: local compute works offline; VDI centralizes data but depends on network and broker capacity; published apps reduce image sprawl; DaaS shifts infrastructure but not identity or policy design.
- Treat the lifecycle as provision, configure, secure, patch, support, and retire. Asset ownership and wipe rights differ for corporate, BYOD, and shared devices.
- Design for failure: offline policy caching, local encrypted data where required, fallback access, and clear support boundaries.
Worked example
A sales team of 200 uses laptops in low-connectivity areas and needs CRM plus local Office files. A proposal to move everyone to nonpersistent VDI fails the connectivity test and adds latency. The better design is managed laptops with disk encryption, local Office, SSO to CRM, and policy sync when online. VDI remains for office-based contractors who need centralized data.
Traps
Do not equate VDI with app virtualization; VDI delivers a desktop, app publishing delivers a session. Do not assume BYOD means unmanaged. Do not ignore licensing, peripherals, or print. Do not size only by user count; profile I/O and latency matter.