Printer Alert Light and Pausing After Jobs
An office's network printer frequently pauses after completing print jobs. Other identical printers on the same network are functioning well. The printer displays an alert light, but the screen provides no further information. Which of the following is the most effective first step to resolve the issue?
Community Insight
The question tests the CompTIA printer troubleshooting order — physical checks before software or connectivity — and the common trap is jumping to drivers, logs, or the network cable because the printer is network-connected.
When a network printer repeatedly pauses after finishing jobs while identical printers on the same network work fine, the problem is almost certainly physical rather than driver- or network-related. The page establishes that the correct first step is checking for and clearing paper jams or obstructions, since an alert light with an uninformative display typically points to a hardware condition inside the device.
Learners most often pick B, updating drivers, because the printer is on the network; but other identical printers on that network are fine, and driver issues do not trigger an alert light or an in-job pause.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option A follows the A+ troubleshooting methodology: rule out the most obvious, most accessible physical cause first. An alert light that stays lit while the display shows nothing is the classic indicator of a paper jam, a small scrap of paper, a stuck document guide, or a mis-seated tray — conditions that make the printer halt or pause mid-cycle after ejecting a page. Because the failing printer is a single unit and other identical printers on the same segment are healthy, a device-local obstruction is the most probable fault. Clearing the jam also resets the sensor state, so the alert clears immediately and confirms the diagnosis at no cost. Per objective 5.6, physical and mechanical checks precede driver, log, and cabling analysis.Why the Other Options Are Wrong
Option B, updating drivers, addresses rendering and data-stream problems; a driver fault would not illuminate the hardware alert light or mechanically interrupt job completion, and identical printers using the same drivers are working fine. Option C, analyzing event logs, is a reasonable later step but is undermined here by the stated fact that the screen provides no further information, and log review is less direct than a ten-second visual inspection. Option D, swapping the network cable, tests connectivity; a bad cable would cause timeouts, queue backups, or offline status on the print server, not a repeating pause pattern with a local alert light on one device.Community Comment Notes
One community comment agrees with this verdict, noting "490. A — Check for paper jams or obstructions" and reasoning that an "Alert light + printer keeps pausing" combination means you should "first physically check for something stuck inside." That comment's reasoning matches the official troubleshooting sequence, so it supports the answer chosen here.Official Reference
Exam Strategy
When a printer symptom includes an alert or warning light, treat it as a hardware condition and start with physical inspection — paper path, trays, and toner seating — before considering drivers or cabling. Eliminate any option that addresses a shared resource when the problem is isolated to a single device.
Frequently Asked Questions
Why isn't updating the driver the right first step for a printer that pauses with an alert light?
Driver problems cause garbled output or failed jobs, not a hardware alert light or repeated pauses. Other identical printers on the same network using the same drivers work fine, so the fault is device-local.
When would analyzing the printer's event logs be the correct troubleshooting step?
Use logs after physical checks pass and the device offers diagnostic data — for example, recurring error codes, intermittent connectivity drops, or memory/firmware faults. The question states the display provides no further information.
Related Analysis
Practice All 220-1201 Questions
Access 105 questions with complete answers and detailed explanations.
View Full 220-1201 Practice Test →