1Y1-300 · Question #62
Scenario: A Citrix Engineer has updated the XenDesktop master image, which the head office users connect to in order to use Personal vDisk. When testing the new image, the engineer discovers that…
The correct answer is A. Ensure that the Update Inventory process is NOT interrupted. See the full explanation below for the reasoning.
Question
Scenario: A Citrix Engineer has updated the XenDesktop master image, which the head office users connect to in order to use Personal vDisk. When testing the new image, the engineer discovers that the Personal vDisk feature stopped working. What could the engineer do to prevent this issue from occurring during future updates?
Options
- AEnsure that the Update Inventory process is NOT interrupted.
- BEnsure the master image and Personal vDisk are on the same storage type.
- CEnsure that neither updates nor applications are placing binaries in the administrator user
- DEnsure that the installed data on the Personal vDisk does NOT exceed more than 50% of the
How the community answered
(52 responses)- A73% (38)
- B4% (2)
- C10% (5)
- D13% (7)
Community Discussion
4
Prof. SaraNov 7, 2025Answer A is correct. The Update Inventory process is what synchronizes the master image changes with the Personal vDisk configuration, and interrupting it is the single most common cause of Personal vDisk breaking after a master image update. When that process does not complete cleanly, the vDisk driver loses its mapping to the updated image layers, which is exactly the failure mode described in this scenario. The fix going forward is procedural discipline: always let Update Inventory run to completion, confirm it finishes without errors before you hand the environment back to users, and build that verification step into your standard change process. The other options describe real housekeeping practices but none of them are the root cause of a broken Personal vDisk after a routine image update.
Giselle K.Nov 8, 2025That covers the main failure path well, though I would add that the vDisk driver mapping loss can also surface if the Citrix XenDesktop Setup wizard ran a catalog update concurrently with Update Inventory, so in shared environments it is worth serializing those operations and not just watching for the inventory job itself to finish.
Giselle K.Nov 16, 2025Sat this one in early 2019 and almost overthought it, because B sounds plausible when you first read it, but the Update Inventory process is literally the handshake between the new master image and the PvD layer, so if that gets cut short you end up with the vDisk driver mismatch that kills the whole feature. Once I remembered what actually happens during a catalog update with PvD enabled, A was the only answer that made sense.
Grace U.Nov 23, 2025I remember staring at this one during my own exam and feeling that small panic when none of the options jumped out immediately, but once I reminded myself that Personal vDisk depends on a clean inventory sync to reconcile what belongs to the base image versus what belongs to the user layer, A became the only answer that made sense. If that Update Inventory process gets cut short, the system loses track of which binaries are whose, and the whole feature falls apart on next connection.