Network Troubleshooting

486 soru

Soru 401Soru

A network administrator attempts to configure Core-Switch-01 to serve as the Spanning Tree Protocol (STP) root bridge for VLAN 50. The administrator executes the command to set the bridge priority for VLAN 50 to 61440. Shortly after, a newly provisioned access switch with factory default settings is connected to the network and unexpectedly assumes the root bridge role for VLAN 50. Which of the following best explains why the access switch became the root bridge instead of Core-Switch-01?

Cevabı ve açıklamayı göster

Cevap: The bridge priority assigned to Core-Switch-01 is numerically higher than the default priority of 32768 on the access switch, and STP prefers the lowest numerical priority value.

Cevap

The bridge priority assigned to Core-Switch-01 is numerically higher than the default priority of 32768 on the access switch, and STP prefers the lowest numerical priority value.
In Spanning Tree Protocol (802.1D / 802.1w), the root bridge election is determined by the lowest Bridge ID (BID). The default bridge priority for switches is 32768 (plus the VLAN ID extension). When the administrator set the core switch priority to 61440, the numerical value was increased instead of decreased. As a result, the newly attached switch with its default priority of 32768 had a lower numerical BID and won the root bridge election.

Adım Adım Çözüm

1
Analyze Spanning Tree Protocol (STP) root bridge selection criteria.
STP elects the switch with the lowest Bridge Identifier (BID) as the root bridge. The BID consists of Bridge Priority (2 bytes) + System ID Extension/VLAN ID + MAC Address (6 bytes).
Lower numerical priority values take precedence over higher numerical values.
2
Compare the configured priority value against the factory default priority.
Core-Switch-01 priority = 61440. Access switch default priority = 32768.
Because 32768 < 61440, the access switch has a superior (lower) priority value.
3
Determine why the access switch assumed the root bridge role.
Configuring a priority of 61440 made Core-Switch-01 less preferred than any switch running default settings (32768). To guarantee root bridge status, the priority should have been set to a lower value such as 4096 or 0.
Correcting the misconfiguration requires assigning a lower numerical priority to the designated core switch.

Anahtar Kavram

Spanning Tree Protocol (STP) Root Bridge Election and Priority Mechanics
Soru 402Soru

A network technician provisions a new database server on VLAN 50 (10.50.0.0/2410.50.0.0/24). Upon booting up, running `ip addr show` reveals that the host interface has acquired an IP address of 169.254.88.12/16169.254.88.12/16. The technician manually assigns a static address of 10.50.0.50/2410.50.0.50/24 to the interface and verifies that the host can successfully ping its default gateway at 10.50.0.110.50.0.1. The centralized DHCP server resides on VLAN 10 (10.10.0.5/2410.10.0.5/24).

Which of the following are the MOST likely causes of the host initially receiving an APIPA address? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: The router interface serving VLAN 50 is missing an IP helper address pointing to the DHCP server at 10.10.0.510.10.0.5.; The centralized DHCP server does not have an active IP scope configured for the 10.50.0.0/2410.50.0.0/24 network segment.

Cevap

The host received an APIPA address because the router interface for VLAN 50 lacks an IP helper address pointing to the remote DHCP server, or the DHCP server lacks an active scope for the 10.50.0.0/24 subnet.
An APIPA address (169.254.x.x) confirms that the client failed to receive a response from a DHCP server. Since static IP configuration proves local VLAN 50 Layer 2 and Layer 3 connectivity to the default gateway is operational, the failure stems from cross-VLAN DHCP transport or pool availability. First, routers block broadcast traffic by default; thus, the router interface on VLAN 50 must have an IP helper address configured to forward DHCP broadcasts as unicast traffic to the DHCP server on VLAN 10. Second, the DHCP server must have an active address scope for the 10.50.0.0/24 network segment to lease addresses to clients on that relay pool.

Adım Adım Çözüm

1
Analyze the client IP address symptom
The host obtained 169.254.88.12/16, which is an APIPA address indicating that the client sent DHCP DISCOVER frames but never received a valid DHCP OFFER/ACK.
Identifying APIPA establishes that DHCP negotiation failed completely rather than succeeding with bad option settings.
2
Evaluate local Layer 2 connectivity
Static configuration of 10.50.0.50/24 successfully pings the gateway at 10.50.0.1.
This rules out physical cable failure, switch port VLAN misassignment, or default gateway interface shutdown.
3
Diagnose cross-subnet DHCP forwarding and scope availability
Because the DHCP server is located on VLAN 10 (10.10.0.5) while the host is on VLAN 50 (10.50.0.0/24), the router interface for VLAN 50 must act as a DHCP relay agent using `ip helper-address 10.10.0.5`. Furthermore, the DHCP server must hold an active pool matching the 10.50.0.0/24 network.
Without the relay agent, broadcast DISCOVER messages cannot cross Layer 3 boundaries. Without an active scope, the server cannot offer an address for that subnet.

Anahtar Kavram

DHCP Relay and Scope Configuration in Multi-VLAN Environments
Soru 403Soru

A system administrator is troubleshooting an inability to establish a secure remote administration session via SSH to a Linux server located at 192.168.1.50192.168.1.50. The administrator executes the command `netstat -an` directly on the server to inspect active network socket states and receives the following truncated output:

Proto Local Address Foreign Address State
TCP 0.0.0.0:23 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING

Based on the utility output, which condition explains why remote SSH connections to this server are failing?

Cevabı ve açıklamayı göster

Cevap: The SSH daemon is not running or is not bound to listen on standard TCP port 22.

Cevap

The SSH daemon is not running or is not bound to listen on standard TCP port 22.
Secure Shell (SSH) operates over TCP port 22 by default. In the provided `netstat -an` output, the server lists active listening services on TCP ports 23 (Telnet), 80 (HTTP), and 443 (HTTPS), but TCP port 22 is completely missing. This indicates the SSH daemon process is not running or is not listening on its default port, causing incoming connection attempts to fail.

Adım Adım Çözüm

1
Analyze the utility and parameters used
The `netstat -an` command displays all active network connections and listening ports (`-a`) using numerical IP addresses and port numbers (`-n`).
Numerical display prevents DNS lookup delays and shows exact port numbers being monitored.
2
Inspect listening TCP ports in the command output
The server has active listeners on TCP port 23 (Telnet), TCP port 80 (HTTP), and TCP port 443 (HTTPS).
To accept incoming connections for a protocol, a service daemon must be bound and listening on its designated port.
3
Evaluate incoming connection request requirements against active listeners
SSH relies on TCP port 22 by default. Since port 22 is absent from the LISTENING socket table, incoming SSH connection requests will be rejected by the TCP stack.
The SSH service process is either stopped or configured to use a non-standard port not shown in the listening table.

Anahtar Kavram

Port and protocol monitoring using netstat/ss utilities
Tahmini Süre:1m 30s
Soru 404Soru

A network technician is investigating a report that a Windows client workstation cannot load an internal intranet application hosted on a distant subnet (`172.16.10.50`). The technician decides to perform a bottom-up command-line diagnostic workflow to isolate the point of failure. In what sequence should the technician execute the following commands to logically isolate the issue from local IP configuration to remote network path routing?

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct troubleshooting sequence is: 1) `ipconfig /all` to inspect local IP settings, 2) `ping 127.0.0.1` to test the internal TCP/IP stack, 3) `ping 192.168.1.1` to verify default gateway reachability, and 4) `tracert 172.16.10.50` to isolate route failures across remote hops.
A structured bottom-up command-line diagnostic process begins at the local host and moves outward: first inspecting local IP settings (`ipconfig /all`), testing the internal protocol stack (`ping 127.0.0.1`), validating local gateway reachability (`ping 192.168.1.1`), and finally tracing path hops to remote destinations (`tracert`).

Adım Adım Çözüm

1
Verify local IP configuration using `ipconfig /all`.
Displays client network adapter settings, DHCP status, assigned IP, subnet mask, default gateway, and DNS servers.
Establishes baseline configuration and identifies basic issues like missing default gateways or APIPA address assignments.
2
Test local TCP/IP stack functionality using `ping 127.0.0.1`.
Receives ICMP echo replies from the local loopback interface.
Confirms the protocol stack and driver software are bound properly to the local adapter.
3
Test local subnet reachability by pinging the default gateway IP (`192.168.1.1`).
Verifies ARP resolution and ICMP packet transport across the immediate Layer 2 network segment.
Ensures the workstation can successfully transmit packets to its local router interface.
4
Trace the path to the remote host using `tracert 172.16.10.50`.
Displays hop-by-hop latency and identifies the specific router interface where packets are dropped.
Isolates inter-subnet routing or firewall policy failures further along the path beyond the local gateway.

Anahtar Kavram

Standard Command-Line Bottom-Up Network Troubleshooting Sequence
Soru 405Soru

A network administrator is troubleshooting an issue where workstations assigned to VLAN 30 on Switch-1 cannot communicate with servers on VLAN 30 attached to Switch-2. An audit of interface GigabitEthernet0/1 on Switch-1 reveals that it was mistakenly configured with static access mode (`switchport mode access`). Additionally, the trunk configuration documentation indicates VLAN 30 must be explicitly allowed, but the interface allowed list is currently restricted to VLANs 10 and 20 (`switchport trunk allowed vlan 10,20`).

Which TWO configuration commands must the administrator execute on Switch-1 interface GigabitEthernet0/1 to establish an 802.1Q trunk link and permit VLAN 30 traffic to pass across it?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: switchport mode trunk; switchport trunk allowed vlan add 30

Cevap

The correct commands are 'switchport mode trunk' and 'switchport trunk allowed vlan add 30'.
To establish proper Layer 2 trunking for VLAN 30, the port operational mode must first be changed from access to trunk using the trunk mode command. Secondly, because the trunk has an explicit allowed list restricting traffic, VLAN 30 must be added to the allowed VLAN list on the interface using the add keyword so it does not overwrite current allowed VLANs.

Adım Adım Çözüm

1
Identify the trunking mode status
The interface is operating in static access mode rather than trunking mode.
An access port strips VLAN tags and restricts traffic to a single VLAN, preventing multi-VLAN trunking.
2
Enable 802.1Q trunking on the interface
Interface mode switches to trunking.
Running 'switchport mode trunk' forces the switchport into permanent trunking mode.
3
Modify the trunk allowed VLAN list
VLAN 30 is appended to the allowed VLANs list on the trunk link.
Using 'switchport trunk allowed vlan add 30' allows frames tagged with VLAN 30 to cross the trunk interface without removing existing allowed VLANs.

Anahtar Kavram

802.1Q Trunking Mode Configuration and Allowed VLAN List Management
Soru 406Soru

A network administrator is troubleshooting an existing Category 6 UTP cabling run between a floor switch and a wall outlet. Although a basic wiremapper confirms full pin-to-pin continuity and proper TIA/EIA 568B wire map alignment, connected devices experience frequent Frame Check Sequence (FCS) errors and link degradation during heavy traffic. Which of the following diagnostic tools should the administrator use to locate the exact position of the physical cable damage along the run?

Cevabı ve açıklamayı göster

Cevap: Time-Domain Reflectometer (TDR)

Cevap

Time-Domain Reflectometer (TDR)
A Time-Domain Reflectometer (TDR) transmits electrical pulses along metallic copper conductors and measures signal reflections caused by impedance discontinuities. By measuring the round-trip time of the reflected wave, the TDR accurately calculates the distance to cable kinks, breaks, or severe NEXT/crosstalk points.

Adım Adım Çözüm

1
Analyze the symptoms and current test results.
Basic wiremapping confirms pin continuity, but physical layer frame corruption (FCS errors) indicates physical damage or impedance mismatches along the copper cable run.
Standard continuity testers only verify basic pin-to-pin connections and cannot detect signal degradation or locate internal conductor flaws.
2
Select the appropriate physical diagnostic tool for copper media.
A Time-Domain Reflectometer (TDR) is selected because it transmits electrical signals down copper conductors and calculates fault distance based on reflection timing.
TDR technology accurately measures distance to impedance changes, cable kinks, or partial breaks in copper twisted-pair cabling.

Anahtar Kavram

Selecting copper cabling diagnostic tools for distance-to-fault analysis
Tahmini Süre:1m 0s
Soru 407Soru

A network administrator deploys a new workstation on VLAN 35 (10.35.0.0/2410.35.0.0/24). Upon booting up, the workstation cannot access internal servers or the internet. Executing `ipconfig /all` on the workstation yields the following output:

IPv4 Address. . . . . . . . . . . : 169.254.14.88
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : Yes

The central DHCP server is located on VLAN 10 (10.10.0.0/2410.10.0.0/24) and actively provides IP address leases to clients on VLAN 10. Which of the following represents the most likely cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The Layer 3 interface serving VLAN 35 lacks an IP helper address pointing to the DHCP server.

Cevap

The Layer 3 interface serving VLAN 35 lacks an IP helper address pointing to the DHCP server.
The client address 169.254.14.88169.254.14.88 indicates that the workstation failed to receive a response to its DHCP DISCOVER broadcast and fell back to Automatic Private IP Addressing (APIPA). Because the DHCP server is on a different subnet (VLAN 10), the router interface serving VLAN 35 must be configured with a DHCP Relay Agent (`ip helper-address`) to forward client broadcast requests to the unicast IP address of the DHCP server.

Adım Adım Çözüm

1
Analyze host network configuration output.
The workstation has an IPv4 address of 169.254.14.88169.254.14.88 with a /16/16 mask (255.255.0.0255.255.0.0) and no default gateway.
Addresses in the range 169.254.0.1169.254.0.1 through 169.254.255.254169.254.255.254 represent Automatic Private IP Addressing (APIPA), indicating the client tried and failed to contact a DHCP server.
2
Evaluate network topology and DHCP traffic flow boundaries.
The host is on VLAN 35 (10.35.0.0/2410.35.0.0/24), while the DHCP server resides on VLAN 10 (10.10.0.0/2410.10.0.0/24).
DHCP discovery messages are sent as Layer 2 broadcast packets (255.255.255.255255.255.255.255). Routers do not forward Layer 2 broadcasts across subnets by default.
3
Identify missing relay component.
A DHCP Relay Agent (such as `ip helper-address` on a router or Layer 3 switch interface) is required on VLAN 35 to forward broadcast requests as unicast packets to the DHCP server on VLAN 10.
Without an IP helper address configured on VLAN 35's default gateway interface, DHCP DISCOVER broadcasts are dropped by the router.

Anahtar Kavram

DHCP Relay Agent and APIPA Diagnosis
Tahmini Süre:1m 15s
Soru 408Soru

A network technician is investigating performance issues on several newly installed cabling runs connecting a distribution switch to server racks. The technician needs to identify appropriate diagnostic procedures and remedies for physical layer faults. Which of the following actions and tool selections correctly resolve these physical layer problems? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Use an Optical Power Meter (OPM) to measure signal power loss across a fiber optic patch link suspect of excessive attenuation.; Reterminate an RJ-45 connector on a Category 6 UTP cable using consistent T568B pinouts on both ends to resolve a split pair condition.

Cevap

The correct responses are using an Optical Power Meter (OPM) to measure light attenuation across a fiber link, and reterminating Category 6 UTP cable connectors with consistent T568B pinouts to correct split pairs.
Measuring fiber power loss requires an Optical Power Meter (OPM) to test light intensity, while resolving split pairs on twisted-pair cables requires reterminating connectors consistently to a standard such as T568B so that signals travel along paired twists.

Adım Adım Çözüm

1
Evaluate fiber optic diagnostic requirement
Identify that light loss / attenuation along a fiber link is directly measured in dB or dBm using an Optical Power Meter combined with a light source.
OPM is the standard instrument for validating fiber optic power levels and decibel loss.
2
Identify corrective action for split pairs on copper twisted-pair cabling
Recognize that split pairs result from incorrect pin assignment configurations across twisted pairs and require proper retermination according to TIA/EIA-568 standards.
Reterminating both ends to standard T568B ensures corresponding signals travel along correctly twisted pairs, minimizing NEXT.
3
Analyze incorrect tool selection choices
Distinguish between wire tracing tools (tone probe), basic continuity testers (wiremapper), and distance/performance diagnostics (TDR / Cable Certifier).
Tone probes trace cables and wiremappers check simple continuity, but neither locate fault distances or measure high-frequency noise.

Anahtar Kavram

Selecting accurate testing equipment (OPM vs TDR vs tone probe) and applying standard cable termination (T568A/B) to resolve copper and fiber physical layer faults.
Tahmini Süre:1m 30s
Soru 409Soru

A network administrator is troubleshooting an issue where a newly connected Linux host receives an IP address via DHCP but cannot communicate with hosts on external subnets. Arrange the following diagnostic and troubleshooting steps into the correct chronological order according to standard Network+ troubleshooting methodology.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct troubleshooting sequence begins with verifying physical link status, inspecting the local IP address and routing table for the default gateway, pinging the local default gateway, pinging a remote public IP address, and finally testing DNS domain name resolution.
Following standard CompTIA troubleshooting methodology, network diagnostics proceed logically from Layer 1 to higher layers: verify physical link integrity, inspect local IP and routing parameters (default gateway), test local subnet gateway reachability via ICMP, test external path routing via IP ping, and finally test higher-layer application services like DNS name resolution.

Adım Adım Çözüm

1
Check physical layer connectivity
Confirmed physical link integrity
Lower-layer physical connectivity issues must be ruled out before inspecting protocol-layer configuration.
2
Inspect IP configuration and default gateway entry
Identified configured IP address, subnet mask, and default gateway router address
Determines if the DHCP server supplied valid addressing details including the default gateway route.
3
Ping the local default gateway
Verified local subnet Layer 3 communication
Tests basic local packet forwarding and ARP resolution to the local router interface.
4
Ping a remote external IP address
Verified remote IP routing past the local gateway
Isolates network layer routing path issues from higher-level application/DNS issues.
5
Test DNS resolution with dig or nslookup
Verified full end-to-end service availability
Ensures domain names resolve to IP addresses after underlying IP reachability is established.

Anahtar Kavram

Standardized bottom-up IP addressing and DHCP service troubleshooting sequence
Soru 410Soru

A network administrator is conducting a comprehensive network analysis on a workstation experiencing connectivity and resolution issues. Match each command-line utility command on the left with its primary diagnostic function on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

pathping 192.168.10.1
arp -a
netstat -ano
dig -x 10.0.0.50

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

pathping 192.168.10.1 matches with measuring packet loss and latency per hop; arp -a matches with displaying local MAC address mappings; netstat -ano matches with listing active connections, listening ports, and Process IDs; dig -x 10.0.0.50 matches with performing reverse DNS lookups.
Each command-line tool maps directly to its intended OSI layer and operational troubleshooting purpose: pathping measures per-hop packet loss over time, arp -a displays Layer 2 MAC cache tables, netstat -ano correlates listening sockets to Process IDs, and dig -x performs reverse DNS resolution.

Adım Adım Çözüm

1
Identify pathping functionality
pathping combines ICMP echo requests with route tracking over several minutes to report specific hop-by-hop packet loss stats.
This pinpoints intermittent link degradation across intermediate routers.
2
Identify arp -a functionality
arp -a queries the ARP cache on local interfaces.
ARP operates between Layer 2 and Layer 3 to resolve IP addresses to hardware MAC addresses.
3
Identify netstat -ano functionality
netstat with flags -a (all sockets), -n (numerical format), and -o (owning Process ID) outputs active network transport sockets.
This allows administrators to identify which local running processes are holding open listening ports or connections.
4
Identify dig -x functionality
dig -x executes a PTR record query against the configured DNS resolver.
The -x flag specifies a reverse lookup parameter to translate an IP address into a domain hostname.

Anahtar Kavram

Command-Line Network Diagnostic Utilities
Soru 411Soru

A network administrator is troubleshooting connectivity for a workstation on a newly configured VLAN 25 (172.16.25.0/24172.16.25.0/24). The central DHCP server is located on VLAN 10 (172.16.10.100172.16.10.100). Running `ipconfig /all` on the workstation yields the following output snippet:

IPv4 Address. . . . . . . . . . . : 169.254.88.12
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . :

Which of the following is the most likely cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The router interface serving VLAN 25 lacks a configured IP helper address pointing to the central DHCP server.

Cevap

The router interface serving VLAN 25 lacks a configured IP helper address pointing to the central DHCP server.
DHCP clients broadcast DHCPDISCOVER messages on their local subnet. Because routers do not forward Layer 3 broadcast traffic by default, clients on subnets separate from the central DHCP server cannot obtain an IP address unless an IP helper address (DHCP relay) is configured on the router gateway interface. Without a relay, the client times out and assigns itself an APIPA address (169.254.x.x169.254.x.x).

Adım Adım Çözüm

1
Analyze the `ipconfig /all` output snippet provided for the workstation.
The workstation has self-assigned an APIPA address (169.254.88.12169.254.88.12) with no Default Gateway or DHCP Server listed.
When a client configured for dynamic IP addressing fails to receive a response to its DHCPDISCOVER broadcast, operating systems default to Automatic Private IP Addressing (APIPA).
2
Evaluate the network topology details.
The client resides on VLAN 25 (172.16.25.0/24172.16.25.0/24), whereas the DHCP server resides on a different subnet, VLAN 10 (172.16.10.100172.16.10.100).
Layer 3 routers block broadcast traffic by default, preventing DHCPDISCOVER broadcasts on VLAN 25 from reaching VLAN 10.
3
Identify the required network configuration for cross-subnet DHCP.
An IP helper address (DHCP relay agent) must be configured on the router's VLAN 25 interface.
The DHCP relay agent intercepts local DHCP broadcasts and forwards them as unicast packets across the router to the central DHCP server address.

Anahtar Kavram

DHCP Relay (IP Helper) Configuration across VLAN boundaries
Tahmini Süre:1m 15s
Soru 412Soru

Match each switch log message or port status indicator on the left with its corresponding root cause on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

%CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on GigabitEthernet0/1 (10), with Switch-B GigabitEthernet0/1 (20).
Interface GigabitEthernet0/2 status shows increasing late collisions and FCS frame check sequence errors under high load.
%SPAN-4-PORT_BLOCKING: Port GigabitEthernet0/24 blocked by Spanning Tree Protocol due to receiving a superior BPDU.
Access port FastEthernet0/5 is assigned to VLAN 40, but connected hosts cannot communicate and show interface down/line protocol down (inactive VLAN).

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The CDP native VLAN mismatch log corresponds to mismatched untagged VLAN IDs across a trunk link. Increasing late collisions and FCS errors correspond to a duplex mismatch between connected interfaces. The STP superior BPDU blocked port log corresponds to an unexpected switch advertising a lower STP priority. The inactive access port condition corresponds to a missing VLAN definition in the local switch VLAN database.
Each switch log or status symptom maps directly to a distinct Layer 2 misconfiguration: CDP warning logs pinpoint native VLAN mismatches, late collisions indicate duplex mismatches, superior BPDU logs indicate STP priority conflicts, and inactive port assignments indicate uncreated local VLANs.

Adım Adım Çözüm

1
Analyze the CDP native VLAN mismatch syslog notification
Identified explicit native VLAN mismatch (VLAN 10 vs VLAN 20) on trunk interface GigabitEthernet0/1.
802.1Q trunks must agree on the native VLAN ID to prevent cross-VLAN traffic leaks and CDP error logging.
2
Analyze the interface error counters showing late collisions and FCS errors
Identified classic duplex mismatch diagnostic indicators.
Half-duplex interfaces listen before transmitting, but when connected to a full-duplex port, collisions occur late in frame transmission.
3
Analyze the Spanning Tree Protocol port blocking message
Associated superior BPDU receipt with STP root bridge election dynamics.
A superior BPDU contains a lower Bridge ID (Priority + MAC), causing STP to block or re-evaluate path priorities to prevent loops.
4
Analyze the inactive access port state for assigned VLAN 40
Correlated the inactive port symptom with missing database configuration.
Access ports assigned to a non-existent VLAN cannot forward traffic until the VLAN is defined in the VLAN database.

Anahtar Kavram

Troubleshooting Layer 2 switching issues including native VLAN mismatches, duplex misconfigurations, STP topology dynamics, and missing VLAN database entries.
Soru 413Soru

A network technician is troubleshooting a high optical insertion loss issue on a 10Gbps multimode fiber optic link connecting two distribution switches. An optical power meter indicates a lower-than-expected power level, but no complete signal break is detected along the cable span. The technician suspects physical contamination on the connector ferrule. Which tool should the technician use to visually inspect the connector end-face for microscopic dirt, scratches, or oil?

Cevabı ve açıklamayı göster

Cevap: Fiber inspection scope

Cevap

The technician should use a fiber inspection scope to examine the cleanliness and physical surface condition of the connector ferrule.
A fiber inspection scope (or fiber microscope) is specifically designed to magnify the polished end-face of a fiber optic connector ferrule. This tool allows technicians to inspect the optical core for surface dirt, dust, scratches, or fingerprints that impair light transmission.

Adım Adım Çözüm

1
Analyze the reported symptom and target physical component.
The link exhibits high signal loss, and contamination on the fiber ferrule end-face is suspected.
Debris or oils on the optical core obstruct light transmission and cause significant signal attenuation.
2
Select the appropriate diagnostic tool designed for surface inspection.
A fiber inspection scope (fiber microscope) provides high optical magnification of the connector ferrule surface.
Visual examination under magnification is required to verify contamination prior to cleaning.
3
Differentiate from reflectometers and copper testing tools.
Reflectometers analyze signal reflections to calculate distance and loss metrics, while tone probes trace copper wiring, but neither tool can display physical surface images.
Choosing the specialized tool intended for ferrule surface inspection ensures precise diagnostic accuracy.

Anahtar Kavram

Fiber Optic Ferrule Inspection and Tool Selection
Soru 414Soru

A network administrator is troubleshooting an issue where client machines on the subnet 10.0.50.0/2410.0.50.0/24 cannot establish connections to an internal HTTPS portal hosted at 10.0.50.20010.0.50.200. The administrator runs the `netstat -an` utility directly on the destination server hosting the portal and receives the following output snippet:

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 10.0.50.200:443 10.0.50.45:51204 ESTABLISHED
UDP 0.0.0.0:500 *:*

To verify local network layer mapping on a client machine (10.0.50.4510.0.50.45) that is experiencing intermittent timeouts, which command-line utility should the technician use to inspect the cached IP-to-MAC address bindings?

Cevabı ve açıklamayı göster

Cevap: arp -a

Cevap

The correct command to inspect cached IP-to-MAC address bindings on a local subnet is `arp -a`.
The `arp -a` command displays the host's Address Resolution Protocol cache table, which contains the dynamic and static mappings of IPv4 addresses to physical MAC addresses on the local network segment.

Adım Adım Çözüm

1
Analyze the troubleshooting objective
The requirement asks for a tool to examine local IP-to-MAC address (Layer 3 to Layer 2) resolution cache on a workstation.
Address resolution issues on a local Ethernet segment involve evaluating Layer 2 physical address mapping.
2
Evaluate the capabilities of the listed CLI utilities
`arp -a` displays the Address Resolution Protocol table containing mapped IP and MAC addresses.
ARP is specifically responsible for mapping IPv4 addresses to Ethernet MAC addresses on the local link.

Anahtar Kavram

Utilizing ARP and Diagnostic Utilities for Layer 2 / Layer 3 Boundary Verification
Soru 415Soru

A network technician is troubleshooting a performance issue on a newly installed network switch port connected to a high-volume server. Monitoring tools report low overall throughput, a high count of frame check sequence (FCS) errors, and a constantly incrementing late collision counter on the switch port interface. The interface status shows the link is operational at 100 Mbps. Which of the following is the most likely cause of this issue?

Cevabı ve açıklamayı göster

Cevap: A duplex mismatch where one side of the connection is operating in full-duplex mode and the other in half-duplex mode

Cevap

A duplex mismatch where one side of the connection is operating in full-duplex mode and the other in half-duplex mode
The correct answer identifies a duplex mismatch. When one port is configured for full-duplex and the connected port is operating in half-duplex, the full-duplex end sends traffic without performing carrier sensing. The half-duplex end senses a collision mid-transmission, registering late collisions and causing packet corruption that registers as FCS errors.

Adım Adım Çözüm

1
Analyze the physical and Layer 2 error indicators described in the scenario
Identified specific interface symptom indicators: 100 Mbps link speed with late collisions and FCS (Frame Check Sequence) errors
Late collisions occur when a device detects a collision after transmitting the first 64 bytes of a frame, which strongly indicates a timing or mode mismatch in media access control.
2
Evaluate the mechanism causing late collisions
Determined that full-duplex devices send data without checking for carrier sense, while half-duplex devices wait for clear channels and detect collisions during full-duplex transmissions
When auto-negotiation fails or manual configuration is inconsistent, one side defaults to half-duplex and the other to full-duplex, causing late collisions on the half-duplex node and FCS/CRC errors on the full-duplex node.
3
Differentiate from alternative Layer 2 misconfigurations
Ruled out native VLAN mismatches, missing Layer 3 routing, and STP root priority misconfigurations
VLAN and STP misconfigurations affect frame tagging, path forwarding, or spanning-tree topology, but do not produce physical late collision counters.

Anahtar Kavram

Duplex Mismatch Symptoms and Troubleshooting
Tahmini Süre:1m 15s
Soru 416Soru

Match each physical layer cabling issue or task with the diagnostic tool best suited to identify or resolve it.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Locating the exact distance to a severed conductor along a 75-meter UTP cable run
Detecting a split pair condition caused by incorrect wire positions on pins 3, 4, 5, and 6
Measuring optical signal attenuation across a single-mode fiber patch link to verify budget compliance
Tracing an unlabeled horizontal cable run from an office wall jack to its patch panel port

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

1. Locating the exact distance to a severed conductor -> Time-Domain Reflectometer (TDR); 2. Detecting a split pair condition -> Cable Certifier; 3. Measuring optical signal attenuation -> Optical Power Meter (OPM) and Light Source; 4. Tracing an unlabeled horizontal cable run -> Tone Generator and Inductive Probe.
Each diagnostic tool maps to its specific troubleshooting capability: TDR calculates distance to physical copper breaks via signal reflections; Cable Certifier measures high-frequency metrics to detect split pairs; Optical Power Meter with light source measures light loss in fiber links; Tone Generator and Probe traces unlabeled cable runs.

Adım Adım Çözüm

1
Analyze the physical cable distance fault requirement.
Determined that finding distance to a break requires analyzing signal reflections over time.
A Time-Domain Reflectometer (TDR) sends pulses along copper wire and measures reflection delay to pinpoint distance to an open or short fault.
2
Analyze the split pair wiring defect scenario.
Identified that split pairs maintain pin-to-pin continuity but break twist geometry.
Basic wiremappers show pin-to-pin continuity even when pairs are split; high-frequency testing using a Cable Certifier is required to detect the resulting crosstalk and impedance issues.
3
Analyze the fiber attenuation measurement requirement.
Determined that light loss across fiber must be quantified.
An Optical Power Meter (OPM) combined with a continuous light source measures optical loss in dB to compare against loss budget standards.
4
Analyze the unlabeled cable identification task.
Identified the need to trace signal paths non-destructively through wall spaces.
A Tone Generator places an analog signal onto the wire pair, and an inductive probe picks up the audio signal wirelessly to identify the cable endpoint.

Anahtar Kavram

Selecting Appropriate Physical Layer Diagnostic Tools for Copper and Fiber Cable Troubleshooting
Soru 417Soru

A network administrator is investigating a name resolution issue where workstations can reach an internal server via IPv4, but fail to resolve its IPv6 address using the internal DNS server at 10.0.10.510.0.10.5. The administrator needs to query the specified DNS server directly to verify if an IPv6 mapping exists for `app.lab.internal`.

Which TWO of the following command-line diagnostic utilities and syntax options will successfully query the targeted DNS server specifically for the host's IPv6 (AAAAAAAA) record? (Select TWO)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: dig @10.0.10.5 app.lab.internal AAAA; nslookup -type=AAAA app.lab.internal 10.0.10.5

Cevap

The commands 'dig @10.0.10.5 app.lab.internal AAAA' and 'nslookup -type=AAAA app.lab.internal 10.0.10.5' are both valid CLI invocations to query a specific DNS server for IPv6 AAAA records.
To diagnose IPv6 DNS lookup issues directly against a specific DNS server, network administrators use dedicated name resolution utilities (dig or nslookup). In dig, the syntax requires specifying the targeted DNS server with an '@' prefix (e.g., @10.0.10.5) followed by the domain name and record type AAAA. In nslookup, the '-type=AAAA' option specifies IPv6 record requests, and appending the target DNS server IP address at the end overrides the default local DNS resolver.

Adım Adım Çözüm

1
Identify the required record type for IPv6 resolution.
IPv6 domain address resolution uses AAAA (quad-A) records, whereas IPv4 uses A records.
The scenario explicitly specifies diagnosing IPv6 resolution failure.
2
Identify command-line parameters for targeting a specific DNS server.
In 'dig', specifying '@server_ip' directs the lookup to that server. In 'nslookup', adding the server IP as a positional trailing argument targets that server.
The administrator must test the internal DNS server at 10.0.10.5 rather than relying on default system resolver configuration.
3
Evaluate the choices for syntax correctness and functionality.
Both 'dig @10.0.10.5 app.lab.internal AAAA' and 'nslookup -type=AAAA app.lab.internal 10.0.10.5' meet all criteria.
Both command structures correctly specify the record type and direct query target.

Anahtar Kavram

DNS Command-Line Diagnostics for IPv6 (AAAA Records)
Soru 418Soru

A network administrator is troubleshooting an 802.1Q trunk link between Switch-A and Switch-B. Host computers on VLAN 20 attached to Switch-B are unable to communicate with the default gateway located on Switch-A. Inspection of the trunk configuration reveals two issues: Switch-A is configured with native VLAN 20 while Switch-B is configured with native VLAN 1, and VLAN 20 is currently missing from the allowed VLAN list on Switch-B's trunk interface. Which TWO of the following statements accurately explain the technical causes of the communication failure in this setup? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Untagged frames transmitted from VLAN 20 on Switch-A will be associated with VLAN 1 when received by Switch-B.; Tagged frames for VLAN 20 sent from Switch-A will be dropped by Switch-B's trunk interface.

Cevap

The two correct technical causes are that untagged frames transmitted from VLAN 20 on Switch-A will be associated with VLAN 1 when received by Switch-B, and tagged frames for VLAN 20 sent from Switch-A will be dropped by Switch-B's trunk interface.
The issue stems from two distinct trunking misconfigurations. First, a native VLAN mismatch (VLAN 20 on Switch-A vs. VLAN 1 on Switch-B) causes untagged frames sent from VLAN 20 on Switch-A to be incorrectly assigned to VLAN 1 upon arrival at Switch-B. Second, because VLAN 20 is missing from Switch-B's allowed VLAN list on the trunk, any tagged VLAN 20 frames arriving at or traversing Switch-B are dropped.

Adım Adım Çözüm

1
Analyze the impact of mismatched native VLAN configurations across the 802.1Q trunk link.
Switch-A transmits VLAN 20 traffic untagged because VLAN 20 is configured as its native VLAN. Switch-B receives untagged traffic and places it into VLAN 1 (its configured native VLAN), creating a native VLAN mismatch error and misdirecting traffic.
802.1Q trunks do not tag frames belonging to the configured native VLAN.
2
Evaluate the impact of the allowed VLAN list configuration on Switch-B.
Any tagged frames sent for VLAN 20 that reach Switch-B will be filtered out and dropped at the trunk interface because VLAN 20 is absent from Switch-B's allowed list.
Trunk interfaces only prune or permit traffic explicitly matched in their configured allowed VLAN list.

Anahtar Kavram

802.1Q Trunking Native VLAN Mismatch and Allowed List Filtering
Soru 419Soru

A network technician is troubleshooting a newly installed Category 6A UTP cable run that is failing performance certification tests due to excessive Near-End Crosstalk (NEXT). A visual inspection of the patch panel terminations reveals that all eight conductors are connected to their corresponding pin positions according to the T568B standard. Which of the following installation flaws is the most likely cause of the excessive NEXT?

Cevabı ve açıklamayı göster

Cevap: Untwisting the wire pairs more than 0.5 inches (13 mm) prior to punching them down onto the block

Cevap

Untwisting the wire pairs more than 0.5 inches (13 mm) prior to punching them down onto the block is the primary cause of excessive Near-End Crosstalk (NEXT).
Twisted-pair Ethernet cabling relies on the precise twisting of wire pairs to provide mutual cancellation of electromagnetic interference. When terminating Category 6 or Category 6A cabling onto a patch panel or RJ-45 jack, standards mandate that wire pairs should not be untwisted more than 0.5 inches (13 mm). Excessive untwisting removes this noise cancellation capability right at the connector, causing signal energy to leak between adjacent pairs and resulting in Near-End Crosstalk (NEXT) failure on cable certification tests.

Adım Adım Çözüm

1
Analyze the physical cable failure symptom
The cabling run fails certification specifically due to Near-End Crosstalk (NEXT), while pin mapping is verified correct.
Crosstalk occurs when signals traveling through one wire pair bleed into adjacent wire pairs near the transmitting end.
2
Evaluate physical termination factors that affect pair isolation
Twisted-pair cables rely on precise twists along the conductor length to cancel out electromagnetic interference and crosstalk.
Exceeding the maximum recommended untwist distance (0.5 inches or 13 mm for Cat 6/6A) degrades pair isolation at the termination point.
3
Identify the corrective action
Re-terminate the patch panel connections while keeping pair untwisting to a minimum.
Preserving twists close to the IDC punch-down block eliminates NEXT and allows the link to pass certification.

Anahtar Kavram

Near-End Crosstalk (NEXT) and Twisted-Pair Termination Limits
Tahmini Süre:1m 15s
Soru 420Soru

A network technician is troubleshooting connectivity for a VoIP desk phone on VLAN 80 (10.80.0.0/2410.80.0.0/24). The phone boots up and receives an IP address lease, but it cannot register with the central PBX server located on VLAN 10 (10.10.0.10/2410.10.0.10/24). Running a network status command on the phone reveals the following output:

text
IPv4 Address . . . . . . . . . . . : 10.80.0.45
Subnet Mask . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . : 10.80.1.1
DHCP Server . . . . . . . . . . . . : 10.80.0.1
DHCP Option 066 (TFTP Server) . . . : 10.10.0.10

Which of the following is the primary cause of the registration failure?

Cevabı ve açıklamayı göster

Cevap: The DHCP server configured Option 003 (Default Gateway) with an IP address on a different subnet than the host.

Cevap

The DHCP server provided a Default Gateway address (Option 003) that resides on a different subnet (10.80.1.110.80.1.1) than the client's assigned address (10.80.0.45/2410.80.0.45/24), preventing off-subnet routing.
The client received an IP address of 10.80.0.4510.80.0.45 with a /24/24 subnet mask (255.255.255.0255.255.255.0), placing it on the 10.80.0.0/2410.80.0.0/24 subnet. The DHCP server provided Option 003 (Default Gateway) with the IP address 10.80.1.110.80.1.1, which belongs to the 10.80.1.0/2410.80.1.0/24 subnet. A host cannot forward packets to a default gateway that does not reside on its local IP subnet, which prevents the VoIP phone from routing traffic to the PBX server on VLAN 10.

Adım Adım Çözüm

1
Analyze the assigned IP address and subnet mask of the host
The host address is 10.80.0.4510.80.0.45 with a subnet mask of 255.255.255.0255.255.255.0 (/24/24). The local subnet range is 10.80.0.110.80.0.1 to 10.80.0.25410.80.0.254.
Determines the boundaries of the host's local Layer 3 broadcast domain.
2
Compare the Default Gateway IP address against the local subnet boundaries
The gateway is configured as 10.80.1.110.80.1.1, which falls outside the 10.80.0.0/2410.80.0.0/24 network range.
Hosts must send traffic destined for external networks (such as the PBX at 10.10.0.1010.10.0.10) to a default gateway located on their own local subnet.
3
Determine the impact of the subnet mismatch
The client host cannot resolve the Layer 2 MAC address of the default gateway via ARP, causing all off-subnet transmission to fail.
Identifies why communication to the PBX server on VLAN 10 fails despite receiving an IP lease.

Anahtar Kavram

DHCP Option 003 Default Gateway Subnet Mismatch Troubleshooting
ÖncekiSayfa 21 / 25Sonraki
Network Troubleshooting Alıştırma Soruları — CompTIA Network+ — Sayfa 21 | Examkin