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
  76% (25)
• B
  3% (1)
• C
  6% (2)
• D
  15% (5)

Explanation

Citrix Provisioning (PVS) streams a single read-only vDisk to multiple virtual machines, meaning the base OS image is never written to - only a small write cache per VM handles changes, dramatically reducing total storage writes. This is achievable with minimal effort because write caching is a built-in PVS feature requiring no additional infrastructure.

B is wrong because MCS I/O Optimization does reduce some writes via RAM cache, but it's tied to MCS-provisioned machines and requires more configuration overhead than PVS - it's not the minimal effort solution here.

C is wrong because Personal vDisk was designed to separate user-installed apps and data from the base image, not to reduce write I/O on storage - it actually adds a layer of disk activity.

D is wrong because a SAN is a storage infrastructure investment that improves performance and availability but does nothing to reduce the number of writes; it also requires significant hardware and administrative effort.

Memory tip: Think of PVS as a "read-only Netflix stream" - many VMs watch the same movie (vDisk) but only scribble their personal notes (write cache) locally, so the main storage barely gets touched.

No community discussion yet for this question.