1Y0-204 App and Desktop Image Management Practice Question
An administrator utilizing Citrix Provisioning observes that target devices fail to boot, hanging indefinitely at the initializing network step with a 'No boot filename received' error message. Which configuration issue is the most likely cause of this failure?
⚠ Common exam trap
Candidates frequently blame firewall rules or the PVS server service itself, overlooking the specific DHCP scope options that are mandatory for the PXE boot process to locate the bootstrap file.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The DHCP options 66 and 67 are misconfigured or missing on the local network infrastructure.
The 'No boot filename received' error indicates that the target device successfully contacted a DHCP server but the DHCP options 66 (Boot Server Host Name) and 67 (Boot File Name, such as ARDBP32.BIN) were not correctly provided. Without these parameters, the client device cannot locate the PVS bootstrap file required to continue the PXE boot process.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The vDisk version being targeted is currently locked in maintenance mode by another admin.
Why it's wrong here
VDisk locking issues manifest later in the provisioning boot sequence after the device has successfully established network contact and loaded the bootstrap file. A failure at the network initialization step points directly to DHCP or PXE service misconfiguration.
- ✓
The DHCP options 66 and 67 are misconfigured or missing on the local network infrastructure.
Why this is correct
Citrix Provisioning target devices relying on PXE boot depend heavily on DHCP options 66 and 67 to identify the boot server address and file name. If these options are missing or incorrect, the target device halts its network boot sequence immediately.
- ✗
The Citrix Provisioning SOAP service has stopped running on the primary delivery controller.
Why it's wrong here
The SOAP service on the delivery controller handles provisioning operations after the target has booted and contacted the server; it plays no part in delivering the initial PXE boot filename. That error arises earlier, from DHCP scope options or TFTP/bootstrap configuration, so a stopped SOAP service would surface as streaming or console failures instead.
- ✗
The write-cache disk attached to the target device has reached maximum capacity limits.
Why it's wrong here
A full write-cache disk causes write failures or target shutdown, not a PXE boot stall. 'No boot filename received' indicates the target never obtained a boot file, so the fault lies in DHCP options, TFTP or bootstrap configuration, not local cache capacity. Write-cache sizing matters for steady-state streaming performance.
Visual reference
About these practice questions
This 1Y0-204 question is part of Courseiva's 216-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Citrix exam blueprint
This 1Y0-204 practice question is part of Courseiva's free Citrix certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 1Y0-204 exam.