An organization wants to implement a virtual desktop infrastructure (VDI) solution on their vSAN storage. They also need to store their applications running inside the VDI environment on vSAN…

Question

Options

• AApp Volumes
• BWorkspace ONE Access
• CHorizon
• DWorkspace ONE UEM
• EDynamic Environment Manager

• A
  44% (22)
• B
  32% (16)
• D
  16% (8)
• E
  8% (4)

Explanation

Horizon (C) is VMware's core VDI platform that deploys and manages virtual desktops, and it integrates directly with vSAN as its underlying storage. App Volumes (A) complements Horizon by delivering applications as virtual disks (AppStacks) stored on vSAN, meaning the applications themselves live on the vSAN datastore rather than being baked into the desktop image - satisfying both requirements together.

The distractors are wrong because they serve different purposes: Workspace ONE Access (B) is an identity/SSO portal that authenticates users to apps but has no role in hosting desktops or storing apps on storage. Workspace ONE UEM (D) is a Unified Endpoint Management tool for managing physical and mobile devices, not a VDI or application storage solution. Dynamic Environment Manager (E) handles user personalization and policies within a desktop session (wallpapers, drive mappings, etc.) but does not provision desktops or store application packages on vSAN.

Memory tip: Think of the two-layer VDI stack - Horizon = the desktop (the virtual machine running on vSAN), App Volumes = the apps (virtual disks also sitting on vSAN). The other three (Access, UEM, DEM) are "management and policy" tools that work around the desktop, not underneath it.

No community discussion yet for this question.