1Y0-A19 · Question #47
A customer needs to configure a XenDesktop environment so that an end user has the best experience when launching a virtual desktop. The environment needs to be configured with fault tolerance so…
The correct answer is C. Cache on the target device and redirect the cache on a share within the Fibre Channel. See the full explanation below for the reasoning.
Question
A customer needs to configure a XenDesktop environment so that an end user has the best experience when launching a virtual desktop. The environment needs to be configured with fault tolerance so that when a XenServer goes down for maintenance the target device can still be deployed by any XenServer with the least load. Currently, the customer has a XenServer pool consisting of 16 XenServer hosts with 8 GB of memory and a 2 TB SATA hard disk. A 2 TB Fibre Channel Storage Area Network is attached to the XenServer. The Provisioning services host is configured on a stand-alone server with 8 GB of memory and three 500 GB SCSI hard disks configured as a RAID 5 configuration. What is the best write caching method for deploying 800 target devices within a XenServer pool?
Options
- ACache on the target device and redirect to the RAM of the target device.
- BCache on the Provisioning services host and redirect the cache on the local file system.
- CCache on the target device and redirect the cache on a share within the Fibre Channel
- DCache on the Provisioning services host and redirect the cache on a share within the Fibre
How the community answered
(27 responses)- A4% (1)
- B11% (3)
- C81% (22)
- D4% (1)
Community Discussion
5
Mei-Ling H.Jun 11, 2026The answer is C. Caching on the target device and redirecting to the Fibre Channel SAN gives you high-speed shared storage that every XenServer in the pool can reach, so when one host goes down for maintenance the target device can still be deployed by any other host with the least load, which is exactly the fault tolerance requirement here. Option B and D both funnel 800 devices through the Provisioning Services host local file system or single server, which becomes a bottleneck, and option A is limited by each target device RAM size alone without the persistent shared storage benefit the FC SAN provides.
Yusuf A.May 29, 2026Picked C, the FC SAN cache redirect, after our senior drew it on a whiteboard last week. That stuck with me when I saw this one on the actual exam.
Brenda K.Jun 21, 2026Cache on the target device with redirect to the Fibre Channel SAN is the right call here, and here is why it holds up under pressure: the FC SAN gives you the high-speed, low-latency shared storage that 800 target devices need so the write cache stays accessible no matter which XenServer in the pool picks up the load after a host goes down for maintenance. Caching locally on the device RAM (A) vanishes on reboot, the PVS host RAID 5 options (B and D) bottleneck at the server, and that 1 GB SCSI array was not built to absorb 800 concurrent write streams anyway.
Nina C.Jun 9, 2026Definitely D, the PVS host redirecting to FC SAN handles 800 devices.
Brenda K.Jun 12, 2026Nina, the answer is C because a fiber channel SAN requires HBAs on the host, not redirection through the PVS host, and C correctly identifies the component that enables direct SAN access for that scale of devices.