Scenario: A Citrix Enterprise engineer is tasked with deploying XenDesktop pooled desktops for an insurance company with 10 remote users using Provisioning Services. The design document requires…

Carlos M.Jun 20, 2026

D is the move here. When the target device does not have enough RAM for write cache and you cannot add more, you shift the cache type to "Cache on device hard disk in Standard Image Access Mode." Standard Image mode is what you need for Provisioning Services pooled desktops since it lets multiple targets stream from the same vDisk simultaneously, and caching to the local HD gives you a persistent write cache location without touching RAM. Private Image mode would lock the vDisk to a single device, which defeats the whole point of a pooled desktop deployment for those 10 remote users. So the phrase that completes the sentence is cache type to Cache on device HD in Standard Image Access Mode.

Kemal J.Jun 14, 2026

D, obviously, though "Cache on device HD" making you pick Standard mode is the part that trips people, not the cache type itself.

Orla P.May 28, 2026

D is the right call here. When RAM is off the table for write cache, you fall back to the device hard drive, and that only works in Standard Image Access Mode because pooled desktops run in Standard, not Private, which is reserved for dedicated one-to-one assignments.

Jovan I.Jun 2, 2026

D, though "device HD" is Citrix's clunky way of saying local disk write cache in Standard Image mode.

Samuel O.Jun 27, 2026

I keep coming back to B on this one and here is my thinking. In the field when you hit a memory ceiling with no hardware path forward, the logical move is to shift how the disk image itself is structured, and Difference Disk Image mode lets the target device track changes in a layered way that offloads what RAM would have otherwise had to handle. I spent a good chunk of time on a hospital rollout where we hit a similar wall, and changing the access mode was always the first lever we pulled before touching cache type settings, because cache type is downstream of how the image is being accessed in the first place. The way I read this question, they are pointing you toward the vDisk access mode specifically, not the cache type, which rules out C and D right away since those are completing the sentence with cache type language. And Private Image in option A would break the pooled model entirely since you cannot share a Private Image across 10 simultaneous users, so B is the only one that keeps the pooled architecture intact while addressing the memory problem.