Network Troubleshooting

486 questions

Question 341Question

A network engineer is analyzing a packet capture (pcap) collected from a client workstation that is unable to authenticate with a RADIUS server. The trace shows the workstation sending UDP datagrams to port 1812 on the server IP address, followed immediately by ICMP Type 3, Code 3 (Destination Unreachable - Port Unreachable) response messages from the server. Which of the following conclusions is best supported by the packet analyzer output?

Show answer & explanation

Answer: The destination server host received the IP datagram, but no active RADIUS service is listening on the target UDP port, or a firewall actively rejected the port.

Answer

The destination server host received the IP datagram, but no active RADIUS service is listening on the target UDP port, or a firewall actively rejected the port.
In packet capture analysis, receiving an ICMP Type 3 Code 3 (Port Unreachable) message directly from the target host proves that Layer 1 through Layer 3 network paths are functioning properly. The error explicitly confirms that the destination host received the packet, but no daemon or service was listening on UDP port 1812 (or an endpoint firewall explicitly blocked and rejected the port).

Step-by-Step Solution

1
Analyze the packet capture protocol types and control response codes.
Identified outgoing UDP packets addressed to destination port 1812 and returning ICMP Type 3, Code 3 packets originating from the target server.
ICMP Type 3 Code 3 specifically translates to 'Destination Unreachable: Port Unreachable'.
2
Correlate ICMP error feedback with OSI layer transport functionality.
Concluded that network connectivity up through Layer 3 is operational, but Layer 4 service binding failed on the target host.
An ICMP Port Unreachable message is generated by the destination host's network stack when an IP packet arrives for a port that has no active application listening on it.

Key Concept

Packet Analyzer Interpretation & ICMP Port Unreachable Response Diagnosis
Question 342Question

A network administrator has just completed testing a theory and confirmed that an incorrect Maximum Transmission Unit (MTU) setting on an edge router interface is causing packet fragmentation and dropping encrypted site-to-site IPsec VPN traffic. Following the CompTIA troubleshooting methodology, the administrator is now preparing to transition to the phase of establishing a plan of action and implementing the solution. Which of the following specific tasks should be performed during this phase? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Assess potential side effects and impacts on downstream network services before applying configuration modifications.; Draft a step-by-step implementation procedure alongside a roll-back contingency plan in case issues arise during execution.

Answer

The technician must assess potential side effects on downstream network services and draft a detailed step-by-step implementation plan with rollback contingency steps.
According to the CompTIA troubleshooting methodology, after a theory is confirmed in Step 3, the technician proceeds to Step 4: 'Establish a plan of action to resolve the problem and implement the solution.' This step explicitly requires identifying potential effects on existing systems, designing a clear step-by-step implementation procedure, and formulating a rollback contingency plan.

Step-by-Step Solution

1
Identify current phase in CompTIA Troubleshooting Methodology
The technician has confirmed the theory (Step 3 complete) and is entering Step 4: Establish a plan of action to resolve the problem and implement the solution.
Once a theory of probable cause is verified, the technician moves to planning and implementation.
2
Differentiate tasks belonging strictly to Step 4 from subsequent steps
Step 4 encompasses identifying potential side effects, creating an action plan, writing rollback procedures, and executing the solution.
Proper change management requires risk analysis and rollback plans before implementation.
3
Select valid Step 4 actions
Assessing impact on downstream services and creating step-by-step rollout and fallback procedures belong in Step 4.
System testing (Step 5) and documentation logging (Step 6) occur later in the troubleshooting process.

Key Concept

CompTIA Troubleshooting Methodology - Plan of Action & Implementation
Question 343Question

A network administrator provisions a new VLAN at a remote office site, routing inter-VLAN traffic through a local Layer 3 switch. Clients connected to the new VLAN are unable to access network resources and receive self-assigned IP addresses starting with 169.254.x.x169.254.x.x. The centralized DHCP server located at the main headquarters has a valid, non-exhausted scope created for the new subnet. Which of the following is the most likely cause of this issue?

Show answer & explanation

Answer: The Layer 3 switch interface serving the new VLAN lacks a DHCP relay agent configuration.

Answer

The Layer 3 switch interface serving the new VLAN lacks a DHCP relay agent configuration.
DHCP DISCOVER messages are sent as Layer 2 broadcast frames. Because routers and Layer 3 switches do not forward broadcast traffic, a DHCP relay agent (or IP helper address) must be enabled on the client-facing gateway interface to convert broadcasts into unicast traffic directed to the remote DHCP server. Without this relay, clients fail to reach the server and fall back to Automatic Private IP Addressing (APIPA).

Step-by-Step Solution

1
Analyze client symptoms and network topology.
Clients receive 169.254.x.x169.254.x.x (APIPA) addresses, indicating DHCP DISCOVER messages are failing to receive a DHCP OFFER from the server across the Layer 3 boundary.
DHCP broadcasts (Layer 2 broadcast destination address FF:FF:FF:FF:FF:FF) are restricted to their local broadcast domain and cannot traverse Layer 3 devices by default.
2
Evaluate the state of the centralized DHCP server.
The server has a configured, active, and unexhausted scope for the target subnet, ruling out server-side scope exhaustion.
If the scope is available and valid, the delivery mechanism between the client broadcast domain and the unicast DHCP server is broken.
3
Identify the required network service to bridge Layer 2 broadcasts across Layer 3 boundaries.
A DHCP relay agent (such as the `ip helper-address` directive) must be configured on the gateway interface to forward broadcast requests as unicast packets to the remote server.
Without a relay agent, DHCP DISCOVER broadcasts are dropped by the Layer 3 interface.

Key Concept

DHCP Relay / IP Helper Operation across Layer 3 Boundaries
Question 344Question

An infrastructure engineer is investigating an incident where telemetry data feeds from an edge gateway fail to reach a central monitoring cluster. After analyzing packet captures, the engineer successfully confirms that an MTU mismatch along the GRE tunnel path is causing fragmented packets to be dropped. Which action represents the next step the engineer should take according to the CompTIA troubleshooting methodology?

Show answer & explanation

Answer: Formulate a plan of action to rectify the tunnel MTU configuration while considering impact, and apply the required changes.

Answer

Formulate a plan of action to rectify the tunnel MTU configuration while considering impact, and apply the required changes.
The scenario describes a technician who has already established a theory and tested it to confirm the cause (Step 3). According to the CompTIA methodology, the immediate next step (Step 4) is to establish a plan of action to resolve the issue while identifying potential side effects, and then implement the solution.

Step-by-Step Solution

1
Identify the current phase of the troubleshooting process.
The scenario states that packet capture analysis confirmed the MTU mismatch as the root cause. This completes Step 3: Test the theory to determine cause.
Recognizing the completed step allows determination of the proper sequence.
2
Determine the next sequential step in the CompTIA 6-step troubleshooting methodology.
Following Step 3 (Test the theory), the next phase is Step 4: Establish a plan of action to resolve the problem and identify potential effects, then implement the solution.
CompTIA standards mandate establishing a structured plan and considering side effects before executing changes.

Key Concept

CompTIA Troubleshooting Methodology Step Order
Estimated Time:1m 30s
Question 345Question

A network technician terminates a new Category 6A horizontal cable run between a patch panel and a modular wall jack using T568B standards. When testing the link, a basic wiremapper confirms that all eight conductors have proper 1-to-1 pin continuity. However, when connected to a multi-gigabit switch, the link fails to negotiate a 10Gbps connection and experiences high frame error rates. A cable certifier reveals severe Near-End Crosstalk (NEXT). Which TWO of the following physical installation faults are the most likely causes of this issue? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Untwisting the conductor pairs excessively at the patch panel or wall jack termination points; Accidentally wiring a split pair condition while maintaining straight-through pin continuity

Answer

Excessive untwisting of conductor pairs at termination points and split pair wiring configurations are the primary causes of severe Near-End Crosstalk (NEXT) when 1-to-1 pin continuity is verified.
Excessive untwisting of wire pairs during termination disrupts pair geometry and reduces mutual noise cancellation, directly causing Near-End Crosstalk (NEXT). Additionally, split pair configurations swap conductors between pairs while preserving 1-to-1 pin continuity; basic continuity testers will report the cable as good, but high-frequency signals suffer catastrophic crosstalk.

Step-by-Step Solution

1
Analyze the reported symptoms and diagnostic tool capabilities.
The basic wiremapper passes 1-to-1 continuity, but the certifier detects severe NEXT interference.
Basic continuity wiremappers only check DC continuity (pin 1 to pin 1, etc.) and cannot detect high-frequency AC crosstalk or pair separation errors.
2
Identify physical termination factors that destroy pair cancellation.
Excessive untwisting of pairs (> 0.5 inches / 13 mm) destroys mutual inductive and capacitive noise cancellation at high frequencies.
Maintaining tight pair twisting up to the point of termination is critical for differential signal noise rejection.
3
Identify pinout errors that pass continuity checks but fail frequency certification.
Split pairs maintain end-to-end 1-to-1 pin continuity but split twisted pairs across non-paired conductors.
Because the signal and return paths are no longer twisted with each other, differential mode noise cancellation fails completely, resulting in high Crosstalk.

Key Concept

Causes of Near-End Crosstalk (NEXT) and Split Pairs in Twisted-Pair Cabling
Question 346Question

A network administrator is troubleshooting an issue where hosts on the 10.10.10.0/2410.10.10.0/24 management subnet cannot establish secure web connections to a server at 10.20.30.5010.20.30.50. Upon reviewing the inbound interface settings on the router, the administrator inspects the following Access Control List (ACL):

text 10 permit tcp 10.10.10.0 0.0.0.255 host 10.20.30.50 eq 80 20 deny ip any any

When attempting to access the server's web control portal via `https://10.20.30.50`, connection attempts time out. Which of the following identifies the root cause of this failure?

Show answer & explanation

Answer: The ACL permits HTTP traffic on port 80 rather than HTTPS traffic on port 443, causing HTTPS packets to match the deny rule.

Answer

The ACL rule permits TCP port 80 (HTTP) instead of TCP port 443 (HTTPS), causing secure web connections to be blocked by the subsequent deny rule.
The correct option correctly identifies that HTTPS uses TCP port 443. Because rule 10 specifically matches `eq 80` (HTTP), packets destined for port 443 skip rule 10 and hit rule 20 (`deny ip any any`), resulting in a connection timeout.

Step-by-Step Solution

1
Analyze the requested service protocol and target port.
Secure web traffic (`https://`) utilizes TCP port 443.
Identifying the target port is essential when evaluating ACL transport-layer matching rules.
2
Examine rule 10 of the active Access Control List.
Rule 10 permits TCP traffic targeting `eq 80` (HTTP).
Port 80 is for unencrypted HTTP traffic, not encrypted HTTPS traffic.
3
Evaluate how HTTPS traffic is processed through the ACL sequence.
HTTPS traffic (port 443) does not match rule 10 and falls through to rule 20 (`deny ip any any`).
ACLs process rules sequentially until a match is found; unmatched traffic falls through to subsequent deny rules.

Key Concept

ACL Port Filtering and Sequence Evaluation
Estimated Time:1m 30s
Question 347Question

A workstation connected to an enterprise network fails to reach internal network resources. A network technician is assigned to troubleshoot the host's IP addressing and DHCP service connectivity. Arrange the diagnostic and troubleshooting steps in the correct order according to standard bottom-up network troubleshooting methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence starts with inspecting physical network cabling and NIC link status, running `ipconfig /all` to evaluate the host IP configuration, verifying switch port VLAN assignment, checking `ip helper-address` (DHCP relay) settings on the default gateway, and finally checking central DHCP server scope statistics for pool exhaustion.
Following standard bottom-up network troubleshooting methodology, a technician verifies physical link connectivity (Layer 1) first, inspects host IP details (`ipconfig /all`) to identify APIPA assignment, checks access switch port VLAN configuration (Layer 2), verifies default gateway DHCP relay (`ip helper-address`) parameters (Layer 3), and finally inspects central DHCP server scope health and lease pool utilization.

Step-by-Step Solution

1
Inspect Layer 1 physical link connectivity
Confirmed physical media connection and link signal LED activity on the NIC and switch port.
Rule out physical Layer 1 disconnects or faulty patch cables before analyzing protocol configurations.
2
Check local host IP address configuration
Determined the client has auto-assigned an APIPA address (169.254.x.x169.254.x.x).
Identify host-level IP parameters and establish that dynamic IP lease acquisition failed.
3
Verify access switch Layer 2 VLAN assignment
Confirmed the access switch port is assigned to the intended workstation VLAN.
Ensure client traffic resides within the proper broadcast domain and access control segment.
4
Inspect Layer 3 DHCP relay configuration
Verified `ip helper-address` is configured correctly on the gateway subinterface.
Ensure DHCP broadcast requests (255.255.255.255255.255.255.255) are relayed as unicast to the central DHCP server.
5
Verify central DHCP server scope utilization
Confirmed server scope health and available lease pool capacity.
Rule out server-level DHCP scope exhaustion or service failure preventing lease issuance.

Key Concept

Structured OSI bottom-up troubleshooting methodology applied to IP addressing and DHCP service failures
Question 348Question

A client workstation requests the IP address for an external hostname (app.sub.example.com) that is not in any local DNS cache. Arrange the steps of the recursive DNS lookup process in the correct order from initial query to final response.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for recursive DNS resolution is: 1) Client sends recursive query to local resolver, 2) Resolver queries root server for .com TLD, 3) Resolver queries .com TLD server for example.com authoritative server, 4) Resolver queries authoritative server for app.sub.example.com host record, 5) Resolver caches the record and returns the IP address to the client.
The correct order follows standard hierarchical DNS resolution: the client workstation issues a recursive request to its local configured resolver. When the resolver's cache is clear, it queries a root name server to find the TLD server, then queries the .com TLD server to locate the authoritative server for example.com, and finally queries the authoritative server for the specific A record before caching and returning the answer to the client.

Step-by-Step Solution

1
Identify the initial query trigger
The client sends a recursive request to its assigned local resolver.
Resolvers handle the full lookup process on behalf of stub clients.
2
Trace top-down DNS hierarchy resolution
The resolver contacts root servers (.), TLD servers (.com), and domain authoritative servers (example.com) sequentially.
Hierarchical DNS resolution proceeds from the root zone downward toward specific authoritative servers.
3
Identify the completion of resolution
The resolver returns the final A record to the client and caches the result.
Caching reduces subsequent query latency and network load across the DNS hierarchy.

Key Concept

Iterative and Recursive DNS Name Resolution Hierarchy
Question 349Question

A network technician is deploying IP VoIP phones on VLAN 30 (172.16.30.0/24172.16.30.0/24). The centralized DHCP server is located on VLAN 10 (172.16.10.5172.16.10.5). While devices assigned static IP addresses on VLAN 30 communicate across subnets normally, all phones set to acquire addresses automatically receive IPs in the 169.254.x.x169.254.x.x subnet and fail to register. Inspecting the Layer 3 switch shows that inter-VLAN routing is active and operational. Which of the following is the most likely cause of this problem?

Show answer & explanation

Answer: The interface for VLAN 30 on the Layer 3 switch is missing an IP helper address pointing to the DHCP server.

Answer

The interface for VLAN 30 on the Layer 3 switch is missing an IP helper address pointing to the DHCP server.
DHCP discovery messages are sent as Layer 2 and Layer 3 broadcasts, which routers and Layer 3 switches do not forward across subnets by default. Because the DHCP server is on VLAN 10 and the clients are on VLAN 30, the Layer 3 switch interface serving VLAN 30 requires an IP helper address configured to relay DHCP broadcast requests as unicast traffic to the server.

Step-by-Step Solution

1
Analyze the symptom and client IP assignment
Phones fail to receive a dynamic IP lease and auto-assign an APIPA address (169.254.x.x169.254.x.x).
APIPA assignment occurs when a host sends a DHCP DISCOVER broadcast but receives no response before timing out.
2
Evaluate the network topology and broadcast boundaries
Clients reside on VLAN 30 (172.16.30.0/24172.16.30.0/24), whereas the DHCP server resides on a separate broadcast domain, VLAN 10 (172.16.10.5172.16.10.5).
Layer 3 boundaries (routers/switches) drop broadcast traffic like DHCP DISCOVER frames by default.
3
Identify the missing network service configuration
A DHCP Relay Agent (`ip helper-address`) must be configured on the VLAN 30 interface of the Layer 3 switch.
The relay agent converts client DHCP broadcast requests into unicast packets and forwards them directly to the DHCP server on VLAN 10.

Key Concept

DHCP Relay Agent and IP Helper Address Placement across Subnets
Estimated Time:1m 30s
Question 350Question

A network administrator is investigating user reports of severe performance degradation and file transfer timeouts when accessing a local backup server connected to Switch-A. The administrator reviews the interface statistics on switch port GigabitEthernet0/1 and observes a rapidly increasing counter for late collisions, FCS errors, and runts, despite the physical link showing up/up at 100 Mbps. Which of the following is the primary cause of this connectivity issue?

Show answer & explanation

Answer: A duplex mismatch between switch port GigabitEthernet0/1 and the backup server network interface card

Answer

A duplex mismatch between switch port GigabitEthernet0/1 and the backup server network interface card
The combination of high late collision counters, FCS errors, and runts on a connected link is a classic indicator of a duplex mismatch. This commonly occurs when one device is manually set to full-duplex while the connecting switch port is left on auto-negotiation, causing the switch port to fall back to half-duplex.

Step-by-Step Solution

1
Analyze the reported interface symptoms and error counters
Identified high late collisions, FCS errors, and runts on an operational link.
Late collisions occur when a device detects a collision after transmitting the first 64 bytes (512 bits) of a frame.
2
Correlate error counters with Layer 1/2 configuration mismatch types
Determined that half-duplex devices listen for collisions during transmission while full-duplex devices transmit continuously without checking for carrier sense.
When one end is full-duplex and the other is half-duplex, the full-duplex end sends data whenever ready, causing the half-duplex end to detect collisions mid-frame and log late collisions.
3
Select the root cause that matches the physical error profile
Confirmed duplex mismatch as the correct root cause.
Only a duplex mismatch produces late collisions; trunk mismatches or routing failures result in dropped packets or log warnings without collision counter increments.

Key Concept

Duplex Mismatch Symptom Identification
Question 351Question

A network administrator is troubleshooting an unbundled Category 6 copper cable run passing through a ceiling plenum that suddenly lost connectivity. The administrator suspects the cable was damaged or cut at an unknown point along its 85-meter length. Which diagnostic instrument should be utilized to measure the exact distance to the cable fault?

Show answer & explanation

Answer: Time-Domain Reflectometer (TDR)

Answer

Time-Domain Reflectometer (TDR)
A Time-Domain Reflectometer (TDR) sends an electrical pulse down a copper cable and records signal reflections caused by impedance anomalies. By measuring the time delay of the returned signal, the device calculates the precise distance to a physical break or open circuit.

Step-by-Step Solution

1
Identify the primary diagnostic requirement from the scenario.
The goal is to determine the exact distance along a copper cable run where a physical break or severance occurred.
The cable run is 85 meters long and hidden behind ceiling plenum spaces, making visual inspection inefficient.
2
Evaluate testing tools based on their operating principles.
A Time-Domain Reflectometer (TDR) sends signal pulses down copper conductors and analyzes the timing of reflected signals to calculate distance to impedance disruptions (opens or shorts).
Only a TDR (or OTDR for optical fiber) provides distance-to-fault measurements.

Key Concept

Using TDR to locate physical copper cabling faults
Estimated Time:1m 0s
Question 352Question

A network technician is troubleshooting an issue where client machines on the local network cannot access an internal secure web application hosted at `https://app.corp.local`. The technician executes `nslookup app.corp.local` on a client machine, which successfully resolves `app.corp.local` to IP address `10.10.20.15`. The technician then connects remotely to the server at `10.10.20.15` and runs the `netstat -ano` command, obtaining the following output snippet:

Proto Local Address Foreign Address State PID
TCP 10.10.20.15:80 0.0.0.0:0 LISTENING 2044
TCP 10.10.20.15:8080 0.0.0.0:0 LISTENING 3112
UDP 10.10.20.15:53 *:* 1088

Based on the command output and scenario details, which of the following is the primary cause of the connection failure?

Show answer & explanation

Answer: The web application service on the server is not bound or listening on TCP port 443.

Answer

The web application service on the server is not bound or listening on TCP port 443.
Secure HTTP (HTTPS) communication requires a web server process listening on TCP port 443. The netstat command output indicates that the server at 10.10.20.15 has active listening sockets for TCP port 80 (HTTP), TCP port 8080, and UDP port 53 (DNS), but no service bound to TCP port 443. Consequently, incoming HTTPS connection attempts to HTTPS default port 443 are rejected by the host OS.

Step-by-Step Solution

1
Analyze DNS lookup results
The domain name `app.corp.local` successfully resolves to IPv4 address `10.10.20.15`, confirming DNS name resolution is functioning properly.
Rule out DNS resolution failure as the root cause of the connection error.
2
Analyze netstat output protocol and port bindings
The netstat snippet lists active listening sockets on TCP port 80 (HTTP), TCP port 8080 (alternate HTTP), and UDP port 53 (DNS).
Identify which network services and transport ports are currently active on the destination server.
3
Correlate client request protocol with server listening ports
The client is attempting an HTTPS connection (`https://app.corp.local`), which requires a listening socket on TCP port 443. No process on the server is listening on TCP port 443.
HTTPS operates over TCP port 443 by standard convention; without a service listening on this port, TCP handshake attempts will be refused.

Key Concept

Analyzing Command-Line Utility Output (netstat socket state and port bindings)
Question 353Question

A network administrator is investigating connectivity complaints from users on a newly deployed subnet (10.20.50.0/2410.20.50.0/24). An affected workstation displays an IP address of 169.254.112.45169.254.112.45 and a subnet mask of 255.255.0.0255.255.0.0. The organization's central DHCP server is located on a separate administrative segment (10.20.10.1010.20.10.10). Which of the following issues could cause the client to receive this address? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The local router interface serving as the default gateway for 10.20.50.0/2410.20.50.0/24 is missing a DHCP relay agent (ip helper-address) configuration.; The DHCP scope designated for the 10.20.50.0/2410.20.50.0/24 subnet on the central server has exhausted all available IP addresses.

Answer

The client receiving an Automatic Private IP Addressing (APIPA) address indicates a failure to communicate with or obtain an IP lease from a DHCP server. The two valid root causes are: 1) missing DHCP relay (IP helper) configuration on the local default gateway router interface, which prevents broadcast discovery frames from reaching the remote DHCP server, and 2) scope exhaustion on the DHCP server for that specific subnetwork pool.
An APIPA address (169.254.0.1 through 169.254.255.254) indicates that the client attempted to obtain an IP lease via DHCP but received no response. When a DHCP server resides on a different IP subnet than the client, broadcast DHCPDISCOVER packets require a Layer 3 relay agent (such as ip helper-address on network routers) to unicast the request to the central DHCP server. Without this relay, requests are dropped by the default gateway. Alternatively, if the relay is functioning but the DHCP server has run out of available addresses in its scope pool for that subnet, no lease can be granted, resulting in APIPA self-assignment.

Step-by-Step Solution

1
Analyze the reported IP address signature.
The host IPv4 address 169.254.112.45169.254.112.45 with mask 255.255.0.0255.255.0.0 is an APIPA address assigned when a DHCP client gets no reply to DHCPDISCOVER broadcasts.
Identifying APIPA establishes that the core problem is DHCP request/response failure rather than an inline routing or Layer 1 hardware failure.
2
Evaluate subnetwork boundaries between client and DHCP server.
The client is on 10.20.50.0/2410.20.50.0/24 while the DHCP server is on 10.20.10.1010.20.10.10. Broadcasts do not traverse routers without a relay agent.
If the local router interface lacks an ip helper-address directive, DHCPDISCOVER packets are dropped at the Layer 3 boundary.
3
Evaluate server-side scope availability.
If the relay agent is active but the DHCP server scope has zero available leases, the server cannot offer an address.
Scope exhaustion produces the identical APIPA symptom on client machines.

Key Concept

APIPA Diagnosis and DHCP Relay Configuration
Question 354Question

A network technician is troubleshooting connectivity issues for several newly provisioned workstations on the finance VLAN (10.15.30.0/24). While the workstations can communicate with each other on the local switch, none of them can access corporate servers on external subnets or reach the internet. An inspection of `ipconfig /all` on one of the affected clients yields the following output:

IPv4 Address. . . . . . . . . . . : 10.15.30.45
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.15.40.1
DHCP Server . . . . . . . . . . . : 10.15.10.10

Which of the following is the most likely cause of the routing failure?

Show answer & explanation

Answer: The DHCP scope option for the default gateway specifies an IP address located outside the local subnet.

Answer

The DHCP scope option for the default gateway specifies an IP address located outside the local subnet.
For a workstation to communicate with remote networks, its configured default gateway must share the same network identifier as defined by the host IP address and subnet mask. In this scenario, the host IP (10.15.30.45/24) belongs to the 10.15.30.0/24 subnet, but the gateway (10.15.40.1) resides on 10.15.40.0/24. This subnet mismatch prevents ARP resolution for the default gateway, resulting in failed off-subnet routing while allowing local switch traffic.

Step-by-Step Solution

1
Analyze the IP address and subnet mask from the command output.
The host IP is 10.15.30.45 with subnet mask 255.255.255.0 (/24). The local network boundary is 10.15.30.0 to 10.15.30.255.
Determines which IP addresses reside on the local broadcast domain.
2
Compare the configured default gateway address against the local subnet range.
The default gateway is configured as 10.15.40.1, which falls into the 10.15.40.0/24 subnet rather than 10.15.30.0/24.
A default gateway must reside on the same IP subnet as the client host to receive local Layer 2 frames.
3
Determine the root cause of off-subnet unreachability.
Because the gateway IP is non-local, client traffic destined for external networks cannot be delivered to the gateway router.
Confirms why local switch traffic functions properly while external/internet routing fails.

Key Concept

Default Gateway Subnet Alignment in DHCP Scope Configurations
Question 355Question

Match each network diagnostic requirement or scenario to the most appropriate hardware testing tool or protocol analyzer function.

Click a left item, then click its matching right item

Items

Locating the precise distance to a bend or reflective break along a 1.5 km single-mode optical fiber link.
Identifying which unlabelled RJ-45 wall jack in an office area corresponds to a specific port on a 110 punch-down block.
Verifying pin-to-pin wiring continuity, opens, shorts, and swapped wires on a newly terminated Cat 6 patch cable.
Filtering captured frame traffic to isolate TCP window size changes and packet retransmission events during file transfer degradation.

Matches

Show answer & explanation

Answer

1. Distance fault on optical fiber links to Optical Time-Domain Reflectometer (OTDR). 2. Tracing unlabelled wall jack runs to Tone generator and inductive probe kit. 3. Checking pin continuity and wire pairing to Wiremap tester. 4. Filtering TCP window size and retransmissions to Packet analyzer display filter (`tcp.analysis.flags`).
Each diagnostic scenario maps directly to its intended hardware tool or packet analyzer syntax based on operational layer and physical medium: OTDR for fiber reflection faults, tone probe for cable tracing, wiremap tester for twisted-pair pinouts, and packet display filters for transport-layer performance analysis.

Step-by-Step Solution

1
Analyze physical medium characteristics and required measurements for cable testing.
Fiber optic distance-to-fault detection requires optical pulse reflection measurement (OTDR). Unlabelled copper path tracing requires signal injection and pickup (tone generator and probe). Copper pinout verification requires pin-to-pin continuity testing (wiremap tester).
Matching physical medium symptoms to appropriate hardware tester operating principles ensures proper tool selection.
2
Evaluate protocol analysis requirements for packet capture inspection.
Transport layer issue inspection (TCP retransmissions and window size tracking) requires frame-level packet capture filtering syntax.
Packet analyzers evaluate frame contents across OSI Layers 2 through 7 using display filters to isolate specific network phenomena.

Key Concept

Selecting Appropriate Network Diagnostics Tools and Packet Analyzer Syntax
Estimated Time:1m 30s
Question 356Question

A network administrator is troubleshooting an issue where servers on VLAN 40 (subnet 172.20.40.0/24) can successfully synchronize time with an internal NTP server (192.168.1.50), but fail to retrieve software updates from an HTTP repository located on the same server (192.168.1.50:80).

Inspection of the router's inbound ACL on the VLAN 40 interface reveals the following configuration:

ip access-list extended VLAN40_IN
10 permit tcp 172.20.40.0 0.0.0.255 host 192.168.1.50 eq 443
20 permit udp 172.20.40.0 0.0.0.255 host 192.168.1.50 eq 123

Which of the following TWO statements correctly identify the root cause of the failure and the necessary corrective action? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: HTTP traffic on TCP port 80 is denied because it matches the unwritten implicit deny rule at the end of the access control list.; A new entry explicitly permitting TCP port 80 traffic from the 172.20.40.0/24 network to 192.168.1.50 must be appended to the access control list.

Answer

HTTP traffic on TCP port 80 is denied by the implicit deny rule at the end of the access control list, and adding an explicit rule permitting TCP port 80 traffic from 172.20.40.0/24 to 192.168.1.50 resolves the issue.
Access Control Lists process traffic sequentially and evaluate unmatched traffic against an unwritten implicit deny all statement. Because the ACL only permits TCP port 443 and UDP port 123, HTTP traffic destined for TCP port 80 is implicitly blocked. To permit HTTP updates, an administrator must add an explicit permit rule for TCP port 80.

Step-by-Step Solution

1
Analyze the Access Control List entries against the application layer ports in use.
Rule 10 explicitly permits TCP port 443 (HTTPS) and rule 20 permits UDP port 123 (NTP). The repository application relies on unencrypted HTTP (TCP port 80).
Traffic directed to TCP port 80 does not match any explicit permit rule in the access control list.
2
Evaluate the implicit behavior of standard and extended Access Control Lists.
Traffic not explicitly permitted by an earlier rule hits the unwritten implicit deny statement at the bottom of the ACL and is dropped.
This explains why NTP traffic (port 123) succeeds while HTTP traffic (port 80) is dropped.
3
Formulate the required configuration change to resolve the connectivity issue.
Add an explicit permit rule for TCP port 80 from source subnet 172.20.40.0/24 to destination host 192.168.1.50.
An explicit permit statement takes precedence over the implicit deny rule for HTTP requests.

Key Concept

Troubleshooting Access Control Lists (ACLs) and Implicit Deny Behavior
Estimated Time:1m 30s
Question 357Question

A network administrator is diagnosing two distinct layer 2 issues on Switch-A. First, syslog logs display repeated `%CDP-4-NATIVE_VLAN_MISMATCH` messages for trunk link interface GigabitEthernet0/1 connected to Switch-B. Second, interface statistics for GigabitEthernet0/2 connected to a local database server show a high number of late collisions and alignment errors during heavy transfer periods. Which of the following actions should the administrator take to resolve these issues? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Reconfigure the native VLAN configuration on Switch-B's trunk interface to match the native VLAN setting on Switch-A.; Manually set matching speed and duplex settings on both Switch-A's GigabitEthernet0/2 interface and the database server's network interface card.

Answer

The administrator should align the native VLAN configurations on both trunk ends (matching Switch-B to Switch-A) and ensure speed/duplex settings match on both Switch-A and the connected database server.
Correct troubleshooting requires addressing both specific symptoms reported: matching the native VLAN setting across the trunk link stops CDP mismatch alerts and frame misdirection, while hardcoding or autonegotiating matching duplex settings on both sides of the host interface eliminates late collisions.

Step-by-Step Solution

1
Analyze the CDP log message `%CDP-4-NATIVE_VLAN_MISMATCH`.
Identified an 802.1Q trunk misconfiguration where untagged frames are interpreted as belonging to different VLANs on opposite ends of the link.
802.1Q trunks must share identical native VLAN numbers on both interconnected switchports to prevent traffic misrouting and switchport error states.
2
Analyze interface statistics showing late collisions on GigabitEthernet0/2.
Identified a duplex mismatch between Switch-A (operating at half-duplex) and the connected server (operating at full-duplex).
Late collisions happen when a node detects a collision after transmitting the first 64 bytes of a frame, which occurs when one side ignores CSMA/CD rules due to full-duplex configuration while the other side uses half-duplex.
3
Select the appropriate remedial actions.
Reconfigure the trunk native VLAN on Switch-B and configure identical speed/duplex settings on GigabitEthernet0/2 and the server interface.
These steps address the root causes of trunk mismatches and duplex mismatches directly.

Key Concept

Troubleshooting 802.1Q Native VLAN Mismatches and Ethernet Duplex Mismatches
Question 358Question

A network technician is investigating performance degradation on a desktop host connected to switch port FastEthernet 0/12. The switch port speed and duplex settings were manually configured to 100 Mbps and Full Duplex, while the desktop network adapter was left on auto-negotiation. Running the `show interface fastEthernet 0/12` command reveals a rapidly incrementing counter for late collisions and Frame Check Sequence (FCS) errors.

Which of the following is the root cause of this connectivity issue?

Show answer & explanation

Answer: A duplex mismatch caused by the desktop adapter auto-negotiating to Half Duplex while the switch port is fixed at Full Duplex.

Answer

The root cause is a duplex mismatch resulting from the host network adapter auto-negotiating to Half Duplex while the switch interface is manually hardcoded to Full Duplex.
The correct answer identifies a duplex mismatch caused by mismatched negotiation modes. Standard IEEE auto-negotiation rules state that if one endpoint is manually set to fixed speed and duplex (e.g. 100/Full) and the other is set to auto-negotiate, the auto-negotiating side can sense speed but cannot detect duplex mode, defaulting to Half Duplex. The resulting collision domain mismatch causes late collisions and FCS errors on the switch interface.

Step-by-Step Solution

1
Analyze the switch port interface configuration and error counters.
The switch interface is statically set to 100/Full, and the interface counter shows high numbers of late collisions and FCS errors.
Late collisions occur when a device detects a collision after transmitting the first 64 bytes (512 bits) of a frame, characteristic of half-duplex operation.
2
Evaluate auto-negotiation behavior on Ethernet links.
The host NIC uses auto-negotiation, but because the switch port does not send auto-negotiation pulses, the host falls back to the IEEE default of Half Duplex.
When speed/duplex auto-negotiation fails to receive response pulses, speed is detected via link pulses, but duplex defaults to half-duplex for backward compatibility.
3
Identify the cause of frame corruption and late collision errors.
The switch port sends frames at will (Full Duplex) while the host listens for quiet wire before sending (Half Duplex). When the switch transmits while the host is sending, the host detects a late collision.
This physical mismatch leads to frame aborts, retransmissions, FCS alignment errors, and significant throughput loss.

Key Concept

Duplex Mismatch Diagnosis and IEEE Auto-Negotiation Fallback Rules
Question 359Question

A network administrator is configuring a workstation in a newly provisioned subnet with the IPv4 address 172.16.45.50/25172.16.45.50/25. The host can successfully ping other devices on the 172.16.45.0/25172.16.45.0/25 local network, but cannot reach any external subnets or the internet. Executing `ipconfig` reveals the default gateway is configured as 172.16.45.130172.16.45.130. Which of the following is the root cause of the connectivity failure?

Show answer & explanation

Answer: The default gateway IP address resides outside the host's assigned IP subnet range.

Answer

The default gateway IP address resides outside the host's assigned IP subnet range.
For a host to communicate with remote networks, its configured default gateway must reside on the exact same local IP subnet. A /25 prefix (subnet mask 255.255.255.128) provides usable host addresses from 172.16.45.1 to 172.16.45.126 with a broadcast address of 172.16.45.127. The configured default gateway IP address (172.16.45.130) belongs to the next block (172.16.45.128/25), making it unreachable via Layer 2 ARP requests.

Step-by-Step Solution

1
Calculate the subnet boundaries for 172.16.45.50/25172.16.45.50/25.
A /25/25 subnet mask (255.255.255.128255.255.255.128) divides the block into subnets of 128 addresses each: Subnet 1 spans 172.16.45.0172.16.45.0 to 172.16.45.127172.16.45.127 (usable host IPs: 172.16.45.1172.16.45.1172.16.45.126172.16.45.126), and Subnet 2 spans 172.16.45.128172.16.45.128 to 172.16.45.255172.16.45.255.
Subnet bounds determine which IP addresses belong to the local broadcast domain versus remote networks requiring routing.
2
Evaluate the configured default gateway address (172.16.45.130172.16.45.130).
The IP 172.16.45.130172.16.45.130 lies within the second subnet (172.16.45.128/25172.16.45.128/25).
A host must have a default gateway configured on its local IP subnet to send frames directly to the gateway's MAC address via ARP.
3
Identify the root cause of the failure.
Because the default gateway IP is on a separate IP subnet, the workstation cannot resolve the gateway's Layer 2 address, causing all off-subnet traffic destined for external networks to fail.
Hosts cannot send traffic off-subnet without a valid, locally reachable default gateway.

Key Concept

Default Gateway Subnet Mismatch Diagnosis
Question 360Question

A network administrator is troubleshooting an unexpected link outage on a 2 km single-mode fiber optic backbone connecting two enterprise distribution switches. While both optical transceivers are functioning properly, no signal reaches the remote end. The administrator needs to pinpoint the exact location of a suspected physical break along the cable run within an underground conduit. Which diagnostic tool should the administrator use?

Show answer & explanation

Answer: Optical Time-Domain Reflectometer (OTDR)

Answer

An Optical Time-Domain Reflectometer (OTDR) is the correct tool because it measures light reflections along a fiber optic strand to calculate the exact distance to a physical break or defect.
An Optical Time-Domain Reflectometer (OTDR) is designed specifically to trace fiber optic cable runs. By transmitting pulses of light into the fiber and analyzing the backscattered light, it calculates time-of-flight reflections to display a trace showing the exact distance to splices, excessive bends, or complete breaks along the cable.

Step-by-Step Solution

1
Identify the physical cabling medium
The infrastructure uses single-mode fiber optic cable.
Diagnostic tools are media-specific (optical vs. electrical).
2
Determine the diagnostic requirement
The goal is to calculate the distance to a cable fault inside a conduit run.
A tool that only measures overall pass/fail loss is insufficient when fault location is required.
3
Select the appropriate optical diagnostic tool
The Optical Time-Domain Reflectometer (OTDR) sends light pulses down the fiber and evaluates backscatter reflectivity to map distance to attenuation events and breaks.
An OTDR is specifically designed for characterization and distance-to-fault analysis in optical fiber runs.

Key Concept

Optical Time-Domain Reflectometer (OTDR) fault localization
PreviousPage 18 / 25Next
Network Troubleshooting Practice Questions — CompTIA Network+ — Page 18 | Examkin