1Y0-A20 · Question #105
Scenario: For users at remote offices, network printers are defined on their workstations. A print server is located in each remote office. The WAN link speed to the datacenter varies and the…
The correct answer is B. Disable the direct connections to print servers policy. See the full explanation below for the reasoning.
Question
Scenario: For users at remote offices, network printers are defined on their workstations. A print server is located in each remote office. The WAN link speed to the datacenter varies and the administrator would like to ensure the best possible printing performance for these XenApp users. Which step should the administrator take to address the group of users with minimal required effort?
Options
- AEnable the session printers policy.
- BDisable the direct connections to print servers policy.
- CReconfigure the network printers as local printers on the workstations.
- DEnsure that the vendor printer driver is installed on all XenApp servers in the farm.
How the community answered
(37 responses)- A14% (5)
- B76% (28)
- C3% (1)
- D8% (3)
Community Discussion
7
Giovanna H.Jun 26, 2026Exam section: XenApp Printing Policies, specifically optimizing print routing across variable-bandwidth WAN links. Mnemonic to lock this in, "Direct OFF keeps data off the WAN." The correct answer is B. When direct connections to print servers is enabled, the XenApp server in the datacenter attempts to send the print job straight across the WAN to the remote office print server, which hammers that variable-speed link. Disabling that policy forces print jobs to travel back through the ICA session to the client workstation, and from there the job moves over the local LAN to the nearby print server, which is the shortest, fastest path and requires no driver changes or printer reconfiguration on any workstation.
Ingrid P.Jun 27, 2026The mnemonic is solid but make sure your card has a second field showing the specific registry path or policy node name so you can recognize it in exhibit-based questions, not just recall the concept.
Yusuf A.Jun 26, 2026Option A tricked me at first because "session printers policy" sounds like exactly what you want for remote users, but that just controls which printers get mapped into the session, it does not fix the WAN bottleneck. Disabling direct connections to print servers (B) is the right move because it routes print jobs through the local print server instead of hauling data across that variable WAN link, which is the whole problem the scenario describes.
Giovanna H.Jun 27, 2026Yusuf nails the distinction, and the mnemonic I give students is "session policy picks the printer, UPS picks the path," because disabling direct connections hands the job to the Universal Print Server component, which is the actual mechanism the CCA-V blueprint tests under the Printing section when the scenario specifies a high-latency or variable WAN link.
Ingrid P.Jun 26, 2026The session printers policy is exactly what this scenario is calling for. It lets you centrally define which printers get mapped for users based on filters like client IP subnets or AD groups, so you can scope it to the remote office users specifically without touching individual workstation configs one by one. That "minimal effort" phrasing in the question is the tell, because rolling out a single policy from the farm covers the whole group at once rather than reconfiguring local settings or messing with driver installs across every XenApp server. The WAN variability detail is there to remind you that you want printing to route through the local print server, and session printers policy is how you enforce that routing for exactly this user population without a lot of manual overhead.
Carlos M.Jun 26, 2026Saw this one on my exam and almost went with D out of habit because driver issues are always the first thing that comes to mind with printing problems, but the scenario is specifically calling out a variable WAN link and a local print server at each site, so B is the play. Disabling direct connections to print servers forces jobs to route through that local print server instead of crawling back across the WAN to the datacenter, which is exactly the performance fix they're describing with minimal config change.
Ingrid P.Jun 28, 2026Carlos is right that B is the correct call, but worth noting for your cards that the underlying principle is print job locality, not just "disable direct connections," since that framing helps you recognize the same fix when it shows up disguised in a cloud-hosted print spooler question.