Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CompTIA Exam 220-1102 Topic 1 Question 40 Discussion

Actual exam question for CompTIA's 220-1102 exam
Question #: 40
Topic #: 1
[All 220-1102 Questions]

A workstation does not recognize a printer. However, the previous day. the printer successfully received a job from the workstation. Which of the following tools should a technician use to see what happened before the failure?

Show Suggested Answer Hide Answer
Suggested Answer: D

When troubleshooting a printer that was previously working but is no longer recognized by a workstation, Event Viewer is the most appropriate tool to check for historical logs and events related to the printer and the system.

Option A: Performance Monitor Performance Monitor is used for monitoring system performance and resources in real-time and does not provide specific historical event logs related to device failures.

Option B: Devices and Printers Devices and Printers show the status and properties of connected devices but do not provide a historical log of events or errors.

Option C: Task Scheduler Task Scheduler manages and monitors scheduled tasks but does not log hardware events or errors.

Option D: Event Viewer Event Viewer logs system events, including errors, warnings, and information related to hardware and software. It is ideal for checking what happened prior to the printer failure.


CompTIA A+ 220-1102 Objective 3.1 (Troubleshoot common Windows OS problems), particularly using Event Viewer for diagnosing issues.

Contribute your Thoughts:

Portia
2 months ago
Event Viewer, for sure. It's the CSI of the tech world. You'll find all the clues you need to solve this printer mystery.
upvoted 0 times
...
Glory
2 months ago
Hmm, Task Scheduler? Nah, that's for scheduling tasks, not troubleshooting printer issues. Event Viewer is the way to go. It's like reading a mystery novel, but with more tech jargon.
upvoted 0 times
Kristal
1 months ago
Let's check Event Viewer to see what caused the issue.
upvoted 0 times
...
Silvana
2 months ago
Yeah, Event Viewer can help us figure out what went wrong.
upvoted 0 times
...
Truman
2 months ago
I think Event Viewer is the best option here.
upvoted 0 times
...
...
Lili
2 months ago
Task Scheduler might have some clues too, but I think Event Viewer is the best option.
upvoted 0 times
...
Amber
3 months ago
I'm voting for Event Viewer. That's where you'll find all the dirty laundry on what caused the printer to stop working. Plus, it's way more exciting than Devices and Printers.
upvoted 0 times
Cary
1 months ago
Let's check Event Viewer to see what caused the printer to stop working.
upvoted 0 times
...
Glenn
1 months ago
I agree, Event Viewer will give us the information we need to troubleshoot the issue.
upvoted 0 times
...
Brianne
2 months ago
I think Event Viewer is the way to go. It shows all the details of what went wrong.
upvoted 0 times
...
...
Teddy
3 months ago
I think Devices and Printers could also be useful to check the printer status.
upvoted 0 times
...
Lyndia
3 months ago
Dude, Performance Monitor? Really? How is that gonna help with a printer issue? I mean, I know it's a powerful tool, but not for this problem.
upvoted 0 times
...
Bambi
3 months ago
I agree with Kenny, Event Viewer can help diagnose the issue.
upvoted 0 times
...
Nicolette
3 months ago
Event Viewer is the way to go. I bet the technician can find some juicy details about what went wrong in the logs.
upvoted 0 times
Sherell
3 months ago
Yeah, Event Viewer will definitely provide some insight into what caused the printer issue.
upvoted 0 times
...
Millie
3 months ago
I agree, Event Viewer is the best option to check for any errors or issues.
upvoted 0 times
...
...
Kenny
3 months ago
I think the technician should use Event Viewer to see what happened.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77