nerdexam
Citrix

1Y0-A15 · Question #3

Scenario: A Citrix Engineer implementing the new virtualization design for Nether Tech Inc. must configure XenApp for dynamic delivery by using Provisioning Services. Provisioning Services already…

The correct answer is C. Boot Device Manager (BDM). See the full explanation below for the reasoning.

Question

Scenario: A Citrix Engineer implementing the new virtualization design for Nether Tech Inc. must configure XenApp for dynamic delivery by using Provisioning Services. Provisioning Services already exists in the environment; however, due to company policies, neither using DHCP nor Citrix 1Y0-A15 Exam modifying the DHCP scope options to include options 66 and 67 or using PXE are possible. Which configuration method should the engineer recommend in order for the virtual XenApp servers to boot from their assigned vDisk?

Options

  • ATFTP Service
  • BBoot from SAN
  • CBoot Device Manager (BDM)
  • DStatic IP Address Assignment

How the community answered

(67 responses)
  • A
    1% (1)
  • B
    10% (7)
  • C
    82% (55)
  • D
    6% (4)

Community Discussion

4
Hiroshi T.Hiroshi T.Feb 21, 2026

The correct answer is C, Boot Device Manager (BDM). When DHCP options 66 and 67 are off the table and PXE is blocked by policy, BDM is the designed fallback for Provisioning Services bootstrap delivery. BDM works by writing the bootstrap directly to a small partition on the local disk or a USB device, so the target machine can locate the PVS server and boot from its assigned vDisk without relying on DHCP scope options or a PXE server at all. Citrix documents BDM specifically for environments where network-based boot methods are restricted, which matches the Nether Tech scenario exactly.

13
Jovan I.Jovan I.Feb 19, 2026

C is the right call here. When DHCP options 66 and 67 are off the table and PXE is blocked by policy, Boot Device Manager solves the problem by writing a small bootstrap partition directly to a local disk or a USB drive on the target machine, so the box does not need to rely on the network broadcast chain at all. The BDM bootstrap holds the IP address of the PVS server and the relevant store information, and when the target powers on it reads that partition first, then reaches out directly to Provisioning Services to stream the vDisk. TFTP Service alone, option A, still depends on the PXE handshake to get the bootstrap to the target, so that is a non-starter under these constraints. I actually hit this exact scenario on my 1Y0-A15 sitting in 2011. I knew PXE was out but I second-guessed myself on TFTP and almost marked A before I caught myself and remembered that TFTP is just the delivery mechanism for the bootstrap file, it does not replace the need for PXE to initiate the process. Wrote BDM down, moved on, and it came back correct. The exam likes to test whether you understand that BDM is specifically the workaround for locked-down DHCP environments, so if you see any language about DHCP options being restricted or PXE being prohibited, go straight to C.

0
Prof. SaraProf. SaraFeb 18, 2026

TFTP handles the boot file delivery directly, no DHCP options needed.

-1
Hiroshi T.Hiroshi T.Feb 19, 2026

Prof. Sara, the RFC 2132 and vendor documentation are clear that DHCP option 66 (TFTP server name) and option 67 (bootfile name) are required to tell the client where to reach the TFTP server and which file to request, so the client cannot initiate the TFTP transfer without those options being delivered first. C is correct because DHCP carries those pointers before TFTP ever enters the picture.

0
Full 1Y0-A15 Practice