Scenario: A Citrix Administrator needs to reduce costs by limiting users' printing sources. The administrator needs to stop automatic creation of all client printers in a session and map printers…

Viktor S.Jun 26, 2026

B and D. Auto-create client printers lets you shut off the default behavior that maps every client printer automatically, and Session printers lets you define exactly which network printers get mapped based on filters like Active Directory site or IP range, which is how you target by floor. Together they replace the spray-and-pray approach with deliberate, location-aware printer assignment.

Nina C.Jun 26, 2026

Yes, B and D are the right ones here. You set "Auto-create client printers" to disable automatic creation so no random client printers pop up in sessions, then use "Session printers" to map specific network printers based on filters like the user's IP subnet or location, which is exactly how you would tie printers to a floor.

Hiroshi T.Jun 26, 2026

I initially thought Direct connections to print servers (C) had to be in the mix since the scenario mentions floor-based mapping, but that policy only controls whether the client routes jobs directly to the print server rather than through the VDA, which is a bandwidth setting, not an assignment setting. What sealed it for me was going back to the Citrix Virtual Apps and Desktops 7 1912 LTSR documentation, which is the reference for the 1Y0-204 blueprint, and confirming that Auto-create client printers (B) is exactly what controls whether client printers get auto-created at session launch, and Session printers (D) is the policy that lets you assign specific network printers based on filters like subnet or Active Directory OU, which is how you map printers per building floor.

Ola B.Jun 26, 2026

I almost went with A, but session printers lets you map by location and auto-create controls the rest.

Jovan I.Jun 26, 2026

Saw this exact combo on my exam, B kills autocreation, D maps by location policy.