SK0-004 · Question #190
A user in the accounting department reports that print jobs are not printing. A user in the software development department also cannot print to the same printer, but can print to two other printers…
The correct answer is B. Check whether the print spooler service has started. When multiple users from different workstations cannot print to a single printer, the root cause is on the print server, and verifying the Print Spooler service is the correct first diagnostic step.
Question
A user in the accounting department reports that print jobs are not printing. A user in the software development department also cannot print to the same printer, but can print to two other printers on different print servers. Which of the following should be the administrator's FIRST step?
Options
- ADetermine whether the server is out of virtual memory.
- BCheck whether the print spooler service has started.
- CReboot the print server.
- DHave the users reboot their workstations.
How the community answered
(25 responses)- A4% (1)
- B92% (23)
- C4% (1)
Why each option
When multiple users from different workstations cannot print to a single printer, the root cause is on the print server, and verifying the Print Spooler service is the correct first diagnostic step.
Virtual memory exhaustion would degrade overall server performance and impact many services simultaneously, not a single printer queue in isolation.
The Print Spooler service queues and manages all print jobs sent to a printer; if it has stopped or crashed, no jobs will be processed regardless of the submitting workstation. Because the problem is isolated to one printer and affects users from separate departments on different machines, checking whether this service is running targets the shared server-side component before escalating to more disruptive actions.
Rebooting the server is a corrective action of last resort, not a diagnostic step, and should only follow confirmation of the underlying cause.
Because the issue affects multiple users on separate workstations, the problem is server-side and rebooting individual client machines would have no effect.
Concept tested: Print Spooler service troubleshooting on Windows Server
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/printing/print-spooler-service-overview
Topics
Community Discussion
No community discussion yet for this question.