Why Do Copies and Scans Show a Vertical Line but Prints Do Not?

Why the Answer Is Correct

The decisive clue is the split in behavior: copies and scans are bad, but printed jobs and received faxes are perfect. Copies and scans both pull the original through the automatic document feeder and image it through the scanner glass, so they exercise the input subsystem; a plain print job or an incoming fax never touches that path at all. A narrow streak of dust, toner, correction fluid, or a scratch on the ADF scan strip produces exactly this symptom — a consistent vertical line at the same position on every imaged page. Because the fault follows the scanning path and not the print engine, the document feeder (C) is where the technician should look. As colemajo29 puts it, the key is "to isolate the subsystem where the error occurs."

Why the Other Options Are Wrong

The drum assembly (D) is the strongest distractor, and BurningIce6699's instinct that "lines on papers it's usually the drum" is a fair rule of thumb for print defects — but it cannot explain output that is clean on print and fax jobs. 351199f captures the logic precisely: "a dirty drum assembly would affect everything, not just normal printing." The corona wire (B) is a print-engine component that transfers toner to paper, so a defect there would also mark every printed page, not only scanned images. Pickup rollers (A) only lift and feed media; a worn roller causes jams, misfeeds, or skew, never a perfectly straight vertical line confined to scanned output. Each of these lives on the output side, which the scenario has already cleared.

Community Comment Notes

The community is strongly aligned on C, and the reasoning converges on the same subsystem-isolation argument. Elle notes the line is "often caused by dirt or debris on the scanner glass or in the document feeder—specifically on the narrow strip of glass" used by the ADF, which is the concrete physical cause worth checking first. dengelkes makes the elimination argument explicit: if the drum were at fault "it would affect all print jobs," so the problem must sit in the ADF path. CyberKH states flatly that the answer "should be a document feeder, not a drum assembly," and acf9805 summarizes it as a scanning/feed-side problem rather than a printing-side one. The lone dissenter, BurningIce6699, offers a generic drum-wear explanation that the scenario's own evidence contradicts.