1Y0-200 · Question #101
A Citrix Administrator creates a session printer for the Engineering group; however, engineers report that random characters are printed when they print. Which policy settings could be causing the…
The correct answer is B. Universal driver preference. See the full explanation below for the reasoning.
Question
A Citrix Administrator creates a session printer for the Engineering group; however, engineers report that random characters are printed when they print. Which policy settings could be causing the issue?
Options
- APrinter assignments
- BUniversal driver preference
- CWait for printers to be created
- DAuto-create generic universal printer
How the community answered
(21 responses)- A10% (2)
- B71% (15)
- C14% (3)
- D5% (1)
Community Discussion
8
Luis F.Jun 10, 2026B is your answer here. The Universal driver preference setting controls which driver gets used for session printers, and when it picks the wrong driver or falls back to a generic one that is not fully compatible with the printer, you end up with garbled output and random characters instead of clean print jobs.
Imani T.Jun 12, 2026Solid breakdown, and worth adding for the exam that this policy setting is found under Citrix Studio printing policies where you can actually reorder the driver preference list, so if the native driver is available and ranked first you can avoid the fallback to generic altogether.
Jovan I.May 28, 2026The Universal driver preference setting is the culprit here, because if the policy is forcing a native or EMF driver when the endpoint cannot support it, you get that garbled output instead of readable print. Flipping the preference to use the Citrix Universal Printer driver, or setting it to fallback to universal when native fails, clears this up every time.
Samuel O.Jun 9, 2026Saw this exact scenario on my exam and almost second-guessed myself into A, but then I remembered a job site where engineers were getting garbled output because the policy was set to prefer the native driver over the Universal Print Driver, and once we flipped that preference everything came out clean. B is your answer because when the UPD priority is misconfigured, the wrong driver gets used and you end up with those random character garbage prints that users hate.
Nina C.Jun 10, 2026That real-world story is a great way to lock in the concept, though I would add that it is worth double-checking the spool settings too, because a corrupted spool folder can produce that same garbled output and fool you into chasing a driver priority issue that was never there.
Nina C.Jun 16, 2026I actually went with D first because I figured the generic universal printer setup was the culprit, but then I remembered that garbled or random characters when printing usually points to a driver mismatch, and the Universal driver preference setting is what controls which driver gets used, so if it falls back to the wrong one you get exactly that garbage output.
Imani T.May 30, 2026The garbled output is a classic sign the wrong driver is being used, and Universal driver preference is exactly where you control whether Citrix tries native drivers before falling back to the universal one. If that preference order lands on a driver that does not match what the printer actually expects, you get garbage characters instead of readable output. Option C trips up a lot of people because "Wait for printers to be created" sounds timing-related and you might think a driver mismatch is a timing issue, but no, that setting just controls whether a session waits on printer creation before launching the desktop. Option D is tempting too since it mentions the universal printer, but auto-create generic universal printer just determines whether the generic printer object shows up at all, not which driver gets used for the session printer the admin already created manually. B is your answer.
Samuel O.May 31, 2026The only thing I would add is that on older Citrix versions the preference setting sometimes needs a policy refresh cycle before it takes effect, so if someone changes it and retests immediately they might think it did nothing.