220-1102 Question 212
Single answerScannersA small law office replaced an old flatbed scanner with a new network-connected multifunction scanner. Staff can print to the device without issues, but when they try to scan from their Windows 11 PCs using the vendor's scan utility, the software does not detect the scanner. The scanner's web interface opens successfully in a browser, and the office firewall recently began blocking unnecessary legacy services. Which action is the MOST likely to restore scanning functionality while keeping the environment secure?
- A
Enable the scanner's WSD or install the vendor's TWAIN/WIA scan driver on the PCs, and configure the scan application to use that method instead of relying on older discovery protocols
- B
Open inbound SMB file sharing ports on each Windows 11 PC so the scanner can push scanned images directly to user desktops
- C
Disable Windows Defender Firewall on all affected PCs to allow the scanner software to discover the device
- D
Reinstall the printer driver on each PC because printing and scanning use the same driver package and protocol
Show answer and explanation
Correct answer: A
Explanation
This question tests the ability to separate printing functionality from scanning functionality on a multifunction device. In real environments, users often assume that if printing works, scanning should also work automatically, but scan features typically depend on separate drivers and protocols such as TWAIN, WIA, or WSD. Because the device's web interface is reachable, IP connectivity is already confirmed. The clue about blocking legacy services suggests the scanner software may have depended on older discovery methods that are no longer permitted. The best practice is to use supported, current vendor scan drivers or WSD where appropriate rather than weakening security controls. Microsoft documentation for Windows scanning commonly references WIA and WSD support, and vendor documentation frequently specifies whether TWAIN, WIA, ICA, or proprietary discovery components are required for desktop scanning.
- A. Correct.
Correct. If users can print and reach the scanner's web interface, basic network connectivity is working. The problem is more likely related to scan discovery or scan-specific drivers/protocols. On Windows, scanners commonly use WIA, TWAIN, or WSD-based discovery/communication, depending on the device and software. In an environment where legacy discovery services are restricted, using the vendor's current scan driver or WSD support is the most practical and secure fix.
- B. Incorrect.
Incorrect. SMB may be used for scan-to-folder workflows, but that is a different feature from scanning from a desktop scan utility. Opening file sharing ports on every workstation increases attack surface and does not address why the vendor's scan application cannot detect the scanner.
- C. Incorrect.
Incorrect. Disabling the firewall is not a best-practice troubleshooting step in a production office and is broader than necessary. The scenario specifically mentions a security-conscious environment. A targeted configuration change for supported scan protocols or drivers is more appropriate than removing host-based firewall protection.
- D. Incorrect.
Incorrect. Printing working does not prove scanning is properly configured. Printers and scanners often use different drivers, services, and protocols even when they are part of the same multifunction device. Reinstalling only the print driver is unlikely to resolve scanner detection issues.