220-1102 Operating Systems Practice Question
A technician is supporting a clinic workstation. The immediate goal is to identify where network path latency or failure begins. Which tool, control, or procedure is the best fit?
⚠ Common exam trap
The trap here is that candidates might confuse Event Viewer's network-related error logs with the ability to trace the exact network path, but Event Viewer only shows local machine logs and cannot map the sequence of routers or measure per-hop latency.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
tracert/traceroute
Tracert (Windows) and traceroute (Linux/macOS) use ICMP Echo packets with incrementing TTL values to map each hop along a network path. By analyzing where packets time out or latency spikes, the technician can pinpoint the exact router or segment where the network path degrades or fails, making it the ideal tool for diagnosing path latency or failure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
tracert/traceroute
Why this is correct
Traceroute sends packets with incrementing TTL values and reports each hop's response time, revealing precisely where latency rises or forwarding stops along the path. That hop-by-hop visibility directly identifies the point where network path latency or failure begins, which ping alone cannot localise.
- ✗
Local Users and Groups
Why it's wrong here
Local Users and Groups manages local account and group membership, holding no network diagnostic capability. It is tempting as a general workstation administration console, and would be correct for granting a clinic user local administrator rights, but tracing path latency requires hop-by-hop probing such as tracert.
- ✗
System Restore
Why it's wrong here
System Restore reverts local system files and registry to an earlier restore point, altering no network path. It is tempting as a general remediation step after a fault, and would be correct for recovering from a bad driver or update, but identifying where latency begins needs hop-by-hop probing.
- ✗
Event Viewer
Why it's wrong here
Event Viewer records local system, application and security events; it does not measure latency or reveal which network hop fails. It is tempting because logs often explain connectivity errors, and would suit diagnosing a service crash, but path latency requires active probing with tracert or pathping.
Go deeper
Related to this question
Learn chapter
Linux Users and File Permissions
Key term
Linux
Linux is an open-source operating system that manages computer hardware and software, widely used in servers, desktops, and embedded systems.
Key term
Windows
Windows is a family of operating systems developed by Microsoft that manages computer hardware and software, providing a graphical user interface for users to interact with their devices.
About these practice questions
One of 925 original 220-1102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1102 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1102 exam.