Scenario: A Citrix Administrator maintains a Citrix Virtual Apps and Desktops Site with local storage that contains several logical disk space locations. The administrator would like to reduce the…

Question

Options

• ACitrix Provisioning
• BMachine Creation Services input/output optimization
• CPersonal vDisk
• DStorage Area Network (SAN)

• A
  71% (10)
• B
  7% (1)
• C
  7% (1)
• D
  14% (2)

Explanation

Citrix Provisioning (PVS) is correct because it streams a single read-only master disk image to multiple virtual machines over the network, meaning VMs write only to a small, isolated write cache rather than generating full disk write I/O for each machine - dramatically reducing total writes on local storage with minimal ongoing effort once configured.

B is wrong because MCS I/O Optimization improves performance but still relies on per-VM delta disks that accumulate writes; it reduces storm effects but doesn't minimize total write volume the way streaming does. C is wrong because Personal vDisk adds a per-user persistent virtual disk, which increases writes rather than reducing them - and the feature was deprecated by Citrix anyway. D is wrong because a SAN doesn't reduce the number of write operations; it only changes where writes go, and migrating from local storage to a SAN is a significant infrastructure project, not minimal effort.

Memory tip: Think of PVS as "one image, many readers" - because VMs stream from a shared read-only vDisk, only tiny write-cache files are generated per VM, making it the go-to solution when the goal is write reduction on storage.

No community discussion yet for this question.