1Y0-204 · Question #229
A Citrix Administrator needs to reduce supply overhead by limiting users' printing sources. The administrator needs to stop automatic creation of all client printers in a session and map printers…
The correct answer is A. Auto-Create Client Printers D. Session Printer. Disabling Auto-Create Client Printers prevents all local printers from being mapped, while Session Printer policies allow printers to be assigned dynamically based on location.
Question
A Citrix Administrator needs to reduce supply overhead by limiting users' printing sources. The administrator needs to stop automatic creation of all client printers in a session and map printers based on the floor of the building from which the user's session connects. Which two policies should the administrator configure? (Choose two.)
Options
- AAuto-Create Client Printers
- BDirect Connections to Print Servers
- CPrinter Properties Retention
- DSession Printer
How the community answered
(37 responses)- A81% (30)
- B14% (5)
- C5% (2)
Explanation
Disabling Auto-Create Client Printers prevents all local printers from being mapped, while Session Printer policies allow printers to be assigned dynamically based on location.
Topics
Community Discussion
6
Nina C.Mar 4, 2026The answer is A and D, because you set Auto-Create Client Printers to stop the automatic creation of all client printers in a session, then use the Session Printer policy to map specific printers based on a filter like the client IP range, which is how you target users by building floor. Those two work together, one removes the noise and the other puts back only what you want.
Ola B.Mar 6, 2026Nina nailed the pairing, but worth noting that the Session Printer policy filter works cleanest when you have your IP subnets cleanly carved per floor, so spin up a quick lab with two subnets and confirm your filters resolve before you push that to production.
Ola B.Feb 17, 2026I have been back and forth on this one but I keep landing on B and D as the pair that makes the most sense here. Direct Connections to Print Servers is doing real work in this scenario because when you bypass the data collector and connect directly, you cut out a layer of overhead that the question is specifically asking you to address. Spin up a quick lab with a XenApp or CVAD site, enable that policy, and watch the difference in spool traffic during session launch, it is pretty eye-opening. Session Printer then lets you define exactly which printer maps based on a filter like subnet or worker group, which lines up perfectly with the floor-based mapping requirement in the question. Auto-Create Client Printers and Printer Properties Retention just do not target the problem at the right layer, one floods the session with every client device printer and the other is just about where settings get saved.
Nina C.Feb 19, 2026Ola, you nailed the Session Printer piece, but the answer is actually A and D, because Auto-Create Client Printers is what controls whether printers are mapped in the first place during session launch, and Direct Connections to Print Servers is more about routing than about which printers get created or filtered. A and D together handle both the creation side and the floor-level targeting the question is going for.
Anjali D.Feb 22, 2026Okay so our group was split on this one but I keep coming back to C and D as my picks, and here is why I think Printer Properties Retention belongs in the answer. When you are mapping printers by floor or building location, the whole point is that the right printer shows up with the right settings every time a user connects from that area, and Printer Properties Retention is what controls whether those configured printer properties are held in the user profile or on the client device. Without locking that down alongside your Session Printer policy, users on the same floor could end up with inconsistent printer behavior between sessions because the properties are not being retained in the way the admin intends. I feel like a lot of people jump straight to Auto-Create and Session Printer without thinking about what actually persists the mapping configuration after it is set. Would love to hear if anyone in the group sees it differently, especially if you think A replaces C here rather than pairing with D.
Nina C.Feb 24, 2026Anjali, the pairing is actually A and D, because Auto-Create Client Printers is what drives the automatic creation of location-based printers in the session alongside the Session Printer policy, and Printer Properties Retention is a separate retention setting that does not control which printers get mapped to which users or locations. Think of it this way, A handles the "which printer shows up" part, and D handles "which one is assigned by location," so C ends up being out of scope for what the question is actually testing.