Match each network diagnostic requirement or operational anomaly to the most appropriate diagnostic hardware tool or packet analyzer syntax.
- Locating the precise distance to a high-reflectance mechanical splice break along a 12 km single-mode fiber-optic backbone.Optical Time-Domain Reflectometer (OTDR)
- Isolating an unmapped RJ45 wall jack inside a dense, fully patched telecommunications closet without disrupting active switch links.Tone generator and inductive probe
- Detecting an unauthorized secondary DHCP server on a local VLAN by analyzing mirrored frame payloads for DHCPOFFER messages.Wireshark with filter `bootp.option.dhcp == 2`
- Measuring real-time voltage and verifying negotiated 802.3at Power over Ethernet (PoE+) draw at an endpoint deployment location prior to connecting a PTZ camera.Hardware PoE inline analyzer
Answer
The correct pairings match: (1) Long-distance single-mode fiber splice fault distance to an Optical Time-Domain Reflectometer (OTDR); (2) Unmapped cable identification in dense patch panels without disconnection to a tone generator and inductive probe; (3) Rogue DHCP server identification in packet captures to Wireshark filtering on BOOTP message type 2 (DHCPOFFER); and (4) Endpoint PoE voltage and IEEE 802.3at load validation to a hardware PoE inline analyzer.
Each diagnostic requirement requires a tool operating at the correct OSI layer and physical media type: OTDRs characterize optical fiber reflection and attenuation; tone generators with inductive probes trace unshielded or shielded copper cabling non-intrusively; Wireshark DHCP display filters capture Layer 7 application bootstrap options; and PoE inline analyzers assess negotiated power delivery under load.
Step-by-Step Solution
Key Concept
Selecting target hardware diagnostic tools and packet analyzer display filters based on physical medium and protocol layer analysis requirements.