Which two storage technologies could an administrator use to set up a XenDesktop environment using Hyper-V? (Choose two)

Yusuf A.Jan 13, 2026

The correct answers are B, Local Disks, and D, Block Storage. My senior walked me through this one when we were setting up a lab, and the key thing she pointed out is that VMFS is a VMware file system so it has no business showing up in a Hyper-V environment, that rules out A right away. StorageLink is tied to XenServer specifically, not Hyper-V, so C is out too. Hyper-V plays nicely with local disk storage on the host and also with block-level storage like iSCSI or Fibre Channel SANs, which is exactly what the exam is testing here. Once you connect the hypervisor to the right storage type it makes sense why only those two fit.

Brenda K.Feb 15, 2026

Local Disks and Block Storage work here, but what made you rule out VMFS?

Jovan I.Jan 23, 2026

My first instinct was C because StorageLink sounds like it belongs in a Citrix stack, but then I remembered that StorageLink is a XenServer feature for offloading storage operations to third-party arrays, it has no place in a Hyper-V deployment at all. VMFS is VMware's proprietary filesystem and simply does not exist in any Hyper-V context, so A was out the moment I focused on which hypervisor the question actually names. With Hyper-V you are working with what that platform natively exposes, and that means local disks and block storage over iSCSI or Fibre Channel SAN, which lands you squarely on B and D. The trick here is that both wrong answers belong to real Citrix or VMware technologies, just not to Hyper-V, and the exam loves to cross those wires.

Dervla O.Jan 28, 2026

Saw this one on my actual exam and almost got burned by A, which is VMware's filesystem and has zero business in a Hyper-V question. Once I spotted that, eliminating C was easy too since StorageLink is a Citrix abstraction layer, not a storage technology you deploy under Hyper-V, leaving Local Disks and Block Storage as the only two that actually make sense in that environment.

Isolde G.Feb 3, 2026

B and D are the ones you want here, and the logic clicks once you think about what hypervisor you are actually dealing with. VMFS is VMware's own file system and has no place in a Hyper-V deployment, and StorageLink was a XenServer integration layer, so it does not apply when your hypervisor is Hyper-V. Local Disks work fine for smaller or POC setups where you are hosting VMs directly on the Hyper-V host, and Block Storage, think iSCSI or Fibre Channel, gives you the shared storage that a production XenDesktop environment on Hyper-V typically needs for live migration and HA. Knowing which storage type belongs to which hypervisor stack is the real skill being tested, not memorizing a list. Saw a version of this on my actual 1Y0-A19 sitting and I almost second-guessed myself on StorageLink because I remembered it being a Citrix thing, but then I caught myself and thought, StorageLink talks to XenServer storage APIs, Hyper-V has its own storage model entirely. That reminder got me to B and D without hesitation. If you go into the exam with a clear mental map of which features belong to XenServer versus Hyper-V versus ESX, these questions become quick points.