Network Troubleshooting

486 soru

Soru 441Soru

A system administrator suspects a Windows workstation has been compromised and is sending outbound traffic to an unknown command-and-control server. The administrator opens Command Prompt to determine which local Process ID (PID) is responsible for establishing active outbound socket connections. Which command-line utility switch combination should the administrator execute to view numerical IP addresses, active connection states, and their corresponding process IDs?

Cevabı ve açıklamayı göster

Cevap: netstat -ano

Cevap

The command 'netstat -ano' accurately lists active network connections along with numerical IP addresses, port numbers, and owning Process IDs.
Executing 'netstat -ano' combines three flags: '-a' displays all active connections and listening ports, '-n' displays IP addresses and port numbers in numerical format (avoiding slow reverse-DNS lookups), and '-o' appends the owning Process ID (PID) column to the output. This gives security analysts and system administrators the exact data required to map suspicious network connections to running system processes.

Adım Adım Çözüm

1
Identify the diagnostic goal
The goal is to inspect active TCP/UDP connections and map them to local process identifiers (PIDs).
Correlating socket connections to PIDs allows the administrator to terminate or analyze suspicious software processes.
2
Evaluate command-line options for process and socket inspection
The 'netstat' command is designed to query network statistics and protocol connections on host OS platforms.
Other utilities like 'arp' or 'nslookup' operate on different OSI layers or perform external DNS lookup functions.
3
Select the correct combination of switches
The '-a' switch displays all connections and listening ports, '-n' prevents DNS name resolution for faster numerical viewing, and '-o' appends the Process ID (PID). Combining them yields 'netstat -ano'.
This output provides the exact PID needed to correlate network connections with active running processes in Task Manager or CLI toolsets.

Anahtar Kavram

Utilizing command-line network utilities (netstat) to inspect active connections and process identifiers.
Soru 442Soru

Users in a regional branch office report that their workstations can successfully communicate with local peers on their LAN segment but are unable to access centralized enterprise resources hosted at 10.50.0.0/2410.50.0.0/24. A network technician executes `ipconfig /all` on a affected workstation and receives the following output:

text
IPv4 Address. . . . . . . . . . . : 192.168.45.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.4.1
DHCP Server . . . . . . . . . . . : 192.168.45.1

Which of the following represents the root cause of the routing failure to external subnets?

Cevabı ve açıklamayı göster

Cevap: The configured default gateway address resides on a different IP subnet than the host address.

Cevap

The configured default gateway address resides on a different IP subnet than the host address.
The correct answer identifies that the default gateway (192.168.4.1) is misconfigured on a different subnet than the host (192.168.45.112/24). A default gateway must reside within the host's local IP subnet so the host can perform ARP resolution and send non-local packets to the gateway router.

Adım Adım Çözüm

1
Analyze host IP parameters from ipconfig output
Host IP is 192.168.45.112192.168.45.112 with subnet mask 255.255.255.0255.255.255.0 (/24), defining the local subnet range as 192.168.45.1192.168.45.1 to 192.168.45.254192.168.45.254.
Determines the boundaries of the local broadcast domain.
2
Evaluate the configured default gateway address
Default Gateway is set to 192.168.4.1192.168.4.1, which resides in the 192.168.4.0/24192.168.4.0/24 network range.
Identifies whether the gateway is directly reachable on the local layer 2 segment.
3
Determine the impact on traffic destined for remote networks
Because 192.168.4.1192.168.4.1 is not on the 192.168.45.0/24192.168.45.0/24 subnet, local ARP requests for the gateway's MAC address fail, rendering external subnets unreachable while local subnet traffic continues to function.
Explains why intra-subnet connectivity works but remote traffic fails.

Anahtar Kavram

Default Gateway Subnet Misconfiguration
Soru 443Soru

During a planned network maintenance window, an administrator installs a new central switch (Switch-Core) to serve as the core switching node. After connecting Switch-Core to the access switches, network traffic follows sub-optimal paths across the campus topology. Troubleshooting reveals that an old edge switch (Switch-Access-3) with a configured Spanning Tree Protocol (STP) bridge priority of 4096 has been elected as the STP root bridge because Switch-Core is using the default STP priority of 32768. Which configuration change on Switch-Core will resolve this issue and establish Switch-Core as the STP root bridge?

Cevabı ve açıklamayı göster

Cevap: Configure the STP bridge priority value on Switch-Core to a number lower than 4096, such as 0 or 2048.

Cevap

Configure the STP bridge priority value on Switch-Core to a number lower than 4096, such as 0 or 2048.
In 802.1D and 802.1w Spanning Tree Protocol, the switch with the lowest Bridge ID (BID) is elected as the root bridge. The BID begins with the bridge priority field. Because Switch-Access-3 has a priority of 4096 and Switch-Core is at the default value of 32768, Switch-Access-3 wins the election. Assigning Switch-Core a bridge priority lower than 4096 (such as 0 or 2048) guarantees it has the lowest BID and becomes the root bridge.

Adım Adım Çözüm

1
Identify the election criteria for Spanning Tree Protocol (STP) Root Bridge selection.
STP elects the root bridge based on the lowest Bridge ID (BID), which combines Bridge Priority and the switch MAC address.
Understanding BID comparison rules determines how to influence root bridge election.
2
Compare the current bridge priority of Switch-Access-3 (4096) with Switch-Core (32768).
Switch-Access-3 has a lower numerical priority (4096 < 32768), making it the current root bridge.
Lower numerical values take precedence in STP root bridge elections.
3
Determine the necessary configuration change on Switch-Core.
Setting Switch-Core's priority to a value lower than 4096 (e.g., 0 or 2048 in standard 4096 increments) forces Switch-Core to win the root bridge election.
Configuring a lower priority than 4096 ensures Switch-Core advertises the lowest BID across the broadcast domain.

Anahtar Kavram

STP Root Bridge Priority Election
Soru 444Soru

A network administrator is troubleshooting an issue where newly deployed host systems on a corporate subnet (10.100.40.0/2410.100.40.0/24) can communicate with local peers but fail to reach external subnets or internet services. Executing `ipconfig /all` on one of the affected hosts produces the following output:

text
IPv4 Address. . . . . . . . . . . : 10.100.40.88
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.100.4.1
DHCP Server . . . . . . . . . . . : 10.100.1.10

Which of the following options accurately identify the root cause of this connectivity failure and the appropriate corrective action? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: The assigned default gateway address (10.100.4.1) resides on a different IP subnet than the host's IPv4 address (10.100.40.88/24).; Reconfigure DHCP Scope Option 003 on the server to distribute a default gateway IP within the local 10.100.40.0/24 subnet.

Cevap

The host cannot reach remote networks because its default gateway (10.100.4.1) is on a different subnet than its assigned IP address (10.100.40.88/24). Reconfiguring DHCP Scope Option 003 on the DHCP server to distribute a gateway address on the 10.100.40.0/24 subnet resolves the issue.
The client host is assigned an IP address of 10.100.40.88 with a /24 subnet mask (255.255.255.0), placing it in the 10.100.40.0/24 network segment. The configured default gateway is 10.100.4.1, which resides on a completely different IP subnet (10.100.4.0/24). A host cannot route off-subnet traffic if its default gateway does not share its local subnet prefix. Because the configuration was provided dynamically, updating DHCP Option 003 on the DHCP server to supply a gateway address within 10.100.40.0/24 resolves the issue for all affected clients.

Adım Adım Çözüm

1
Analyze client IP configuration and subnet boundaries.
Host IP is 10.100.40.88 with subnet mask 255.255.255.0 (/24). The usable host IP range for this subnet is 10.100.40.1 through 10.100.40.254.
To send packets outside the local broadcast domain, a host must forward traffic to a gateway located within its local network prefix.
2
Compare default gateway address to host subnet.
The configured default gateway address is 10.100.4.1, which falls outside the 10.100.40.0/24 subnet prefix (it belongs to 10.100.4.0/24).
Because the gateway is not on the same broadcast domain, ARP resolution fails and remote packets cannot be forwarded.
3
Determine root source of misconfiguration and appropriate remedy.
The client received this configuration from DHCP Server 10.100.1.10. Reconfiguring DHCP Scope Option 003 (Router) for the 10.100.40.0/24 scope ensures clients automatically receive a gateway address within 10.100.40.0/24.
DHCP Option 003 dictates the default gateway IP address assigned to dynamic DHCP clients.

Anahtar Kavram

Default Gateway Subnet Alignment and DHCP Scope Option 003 Configuration
Soru 445Soru

A network administrator is systematically troubleshooting an end user's workstation that cannot access an internal web application located at `https://app.corp.local`. Place the command-line utility operations in the logical sequential order recommended for isolation, starting from basic local network interface validation up to upper-layer protocol testing.

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

Cevabı ve açıklamayı göster

Cevap

The correct order follows a structured bottom-up / progressive isolation approach: 1. Verify local IP settings (`ipconfig /all`), 2. Test ICMP loopback and default gateway reachability (`ping`), 3. Validate DNS name resolution (`nslookup`), 4. Identify network path failure points (`tracert`), 5. Verify transport layer port and service responsiveness (`netstat`/socket test).
The logical troubleshooting workflow progresses systematically from host interface verification (`ipconfig /all`), to local gateway reachability (`ping`), to application layer resolution (`nslookup`), to path routing analysis (`tracert`), and finally to service port level inspection (`netstat`).

Adım Adım Çözüm

1
Check local network interface status and assigned IP parameters using `ipconfig /all`.
Confirms the host has a valid IP address, subnet mask, gateway, and DNS server configuration.
Troubleshooting should start at Layer 1-3 local host verification before attempting remote target diagnosis.
2
Test ICMP ping to loopback (`127.0.0.1`) and default gateway.
Confirms the internal network stack functions and local segment connectivity is intact.
If the default gateway is unreachable, remote routing and DNS tests will fail.
3
Execute DNS lookup using `nslookup app.corp.local`.
Determines whether hostname resolution is functioning and yields the target destination IP.
Name resolution problems prevent applications from forming connections even if IP routing is fully operational.
4
Trace path hops to target server using `tracert`.
Identifies the exact intermediate router hop where latency spikes or packet loss occurs.
Path tracing isolates WAN or multi-router forwarding failures along the path to the server IP.
5
Verify target service port accessibility using transport/session tools (`netstat` / port socket check).
Distinguishes between network layer reachability and service-level firewall or application port blocks.
Upper-layer checks verify that TCP port 443 (HTTPS) is accepting connections once path reachability is confirmed.

Anahtar Kavram

Structured Command-Line Diagnostic Sequence for End-to-End Connectivity
Soru 446Soru

Match each physical layer cabling symptom or test result on the left with its most likely root cause on the right.

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

Öğeler

A wiremap tester indicates pin-to-pin continuity on pins 1 through 8, yet a cable certifier reports severe Near-End Crosstalk (NEXT) failure.
An optical power meter reveals abnormal insertion loss and high back reflection localized precisely at an LC patch panel junction.
A Category 6 cable run negotiates a link speed of only 100 Mbps instead of 1 Gbps, and a continuity test reveals an open circuit on pin 4.
A Power over Ethernet (PoE+) switch port shuts down due to excessive voltage drop, and a cable analyzer reports abnormally high DC resistance.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

1. Pin-to-pin continuity with severe NEXT matches Split pair wiring mistake. 2. Insertion loss and high back reflection at LC junction matches Contaminated fiber optic ferrule end-face. 3. 100 Mbps link fallback with open pin 4 matches Incomplete 4-pair connectivity for Gigabit. 4. High DC resistance and PoE voltage drop matches Use of Copper-Clad Aluminum (CCA) cabling.
Each physical cabling symptom maps directly to its specific physical layer failure mechanism: split pairs preserve pin continuity while causing NEXT due to untwisted pair pairing; fiber ferrule end-face debris scatters light causing insertion loss and return loss at connector junctions; pin 4 opens prevent 4-pair Gigabit autonegotiation and force a 100 Mbps fallback; and non-standard CCA cables introduce excessive DC resistance under PoE load.

Adım Adım Çözüm

1
Analyze the first scenario involving pin continuity accompanied by NEXT failure.
Identify that split pair cabling errors maintain straight-through electrical continuity but break pair twists, causing crosstalk.
Differential signaling in twisted-pair copper relies on tight twists to eliminate electromagnetic induction between adjacent pairs.
2
Analyze the second scenario involving attenuation and reflection localized at a fiber LC connector.
Determine that microscopic contamination on the ferrule surface impedes light transfer and reflects light back toward the transmitter.
Clean ferrule end-faces are essential to ensure glass-to-glass contact without air gaps.
3
Analyze the third scenario where a Cat 6 connection drops from 1 Gbps to 100 Mbps due to an open conductor on pin 4.
Recognize that 1000BASE-T autonegotiation requires all 4 pairs, whereas 100BASE-TX operates over only 2 pairs (1/2 and 3/6).
A break on pins 4, 5, 7, or 8 prevents 4-pair operation, causing the switch/NIC to downgrade the link.
4
Analyze the fourth scenario where PoE causes excessive voltage drop and high DC loop resistance.
Identify Copper-Clad Aluminum (CCA) as a non-compliant conductor material with higher DC resistance than solid copper.
Aluminum has lower conductivity than copper, leading to higher I^2R power loss and voltage drops when powering remote PoE devices.

Anahtar Kavram

Troubleshooting Physical Cabling and Connectors
Soru 447Soru

A network technician is troubleshooting an issue on a Linux host that cannot resolve the hostname of an internal server `app.corp.local`. The technician runs `dig app.corp.local` and receives a response indicating `STATUS: SERVFAIL` from the local recursive DNS server at `192.168.1.2`. To determine whether the issue is isolated to the local recursive server or affects the authoritative server directly, the technician wants to query the domain's designated authoritative DNS server at `10.0.5.50`. Which of the following command-line entries should the technician execute?

Cevabı ve açıklamayı göster

Cevap: dig @10.0.5.50 app.corp.local

Cevap

Executing `dig @10.0.5.50 app.corp.local` sends the query directly to the authoritative DNS server at `10.0.5.50`.
In the `dig` (Domain Information Groper) command-line utility, the `@` symbol followed by an IP address or hostname tells `dig` to send the query directly to that specific DNS server. Running `dig @10.0.5.50 app.corp.local` allows the technician to bypass the local recursive resolver (`192.168.1.2`) and evaluate the authoritative server's response.

Adım Adım Çözüm

1
Identify the goal of the CLI command.
The goal is to direct a DNS resolution query for `app.corp.local` specifically to the server at `10.0.5.50` instead of the local default resolver.
Bypassing intermediate recursive resolvers helps isolate whether DNS failures originate from local cache/forwarding or the authoritative name server.
2
Analyze the syntax requirements for the `dig` utility.
In BIND `dig`, directing a query to a specific DNS server requires specifying `@server` before or after the domain name.
The `@` sign tells `dig` to bypass `/etc/resolv.conf` defaults and direct UDP/TCP port 53 packets to the specified IP address.
3
Evaluate the correct command syntax.
`dig @10.0.5.50 app.corp.local` correctly targets `10.0.5.50` for the lookup.
This isolates the DNS troubleshooting path effectively.

Anahtar Kavram

Directing DNS lookup queries to specific name servers using the `dig` utility
Soru 448Soru

A network administrator is troubleshooting inter-switch communication between Switch-Alpha and Switch-Beta. Users on VLAN 20 attached to Switch-Alpha report complete loss of connectivity to servers on VLAN 20 attached to Switch-Beta. Additionally, syslog messages indicate that untagged management frames transmitted from Switch-Alpha on VLAN 10 are being received on VLAN 30 on Switch-Beta across trunk interface GigabitEthernet 0/1.

An inspection of the interface configuration reveals:
- Switch-Alpha (GigabitEthernet 0/1): Mode: Trunk, Native VLAN: 10, Allowed VLANs: 10, 20, 30
- Switch-Beta (GigabitEthernet 0/1): Mode: Trunk, Native VLAN: 30, Allowed VLANs: 10, 30

Which TWO configuration adjustments must be implemented on Switch-Beta to resolve both issues? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Reconfigure the native VLAN on interface GigabitEthernet 0/1 to VLAN 10.; Add VLAN 20 to the list of allowed VLANs on interface GigabitEthernet 0/1.

Cevap

The administrator must reconfigure the native VLAN on interface GigabitEthernet 0/1 to VLAN 10 and add VLAN 20 to the allowed VLAN list on interface GigabitEthernet 0/1.
The correct solution requires two actions on Switch-Beta: modifying the native VLAN on interface GigabitEthernet 0/1 to VLAN 10, and adding VLAN 20 to the trunk interface allowed list. Changing the native VLAN fixes the native VLAN mismatch between Switch-Alpha (VLAN 10) and Switch-Beta (VLAN 30), preventing untagged frame leakage. Adding VLAN 20 to the allowed list permits VLAN 20 tagged frames to pass across the trunk interface.

Adım Adım Çözüm

1
Analyze the syslog symptom regarding untagged traffic misdirection.
Identify that Switch-Alpha uses Native VLAN 10 while Switch-Beta uses Native VLAN 30 on the trunk link, creating a native VLAN mismatch that causes untagged VLAN 10 frames to drop into VLAN 30 on Switch-Beta.
802.1Q trunk ports do not tag frames belonging to the configured native VLAN. The receiving switch places untagged frames into its own configured native VLAN.
2
Analyze the VLAN 20 connectivity failure.
Determine that VLAN 20 is configured on Switch-Alpha's allowed trunk list (10, 20, 30) but is missing from Switch-Beta's allowed trunk list (10, 30).
Trunk interfaces prune and drop frames for VLANs that are not explicitly included in their allowed VLAN list.
3
Identify the required remedial commands on Switch-Beta.
Change the native VLAN on GigabitEthernet 0/1 to VLAN 10 and update the trunk allowed VLAN list to include VLAN 20.
These two steps align trunk parameter configurations on both ends, restoring VLAN 20 traffic flow and correcting untagged frame mapping.

Anahtar Kavram

802.1Q Trunk Parameter Matching (Native VLAN and Allowed VLAN List)
Soru 449Soru

A network technician is troubleshooting an existing Category 6 copper cable run that connects a workstation to a access switch. The link constantly fails to negotiate at Gigabit speed, dropping to 100 Mbps with frequent CRC frame errors under heavy traffic load. A wiremap test confirms that all eight conductors are properly pin-terminated at both ends according to TIA/EIA 568B standards with no open or short circuits. Which diagnostic instrument should the technician use to measure frequency-dependent parameters such as Near-End Crosstalk (NEXT) and return loss to determine if the run meets Category 6 specifications?

Cevabı ve açıklamayı göster

Cevap: Cable certifier

Cevap

The technician should use a cable certifier to measure frequency-dependent parameters such as Near-End Crosstalk (NEXT) and return loss against TIA/EIA Category 6 standards.
A cable certifier is specifically engineered to test copper runs at high frequencies according to TIA/EIA standards. It evaluates critical physical-layer electrical performance metrics—including Near-End Crosstalk (NEXT), attenuation, and return loss—which cause speed degradation and CRC errors even when basic pin continuity is intact.

Adım Adım Çözüm

1
Analyze the reported symptoms and initial test results
Basic continuity and wiremap testing verified proper pinouts and DC continuity, but link degradation (CRC errors and failed Gigabit auto-negotiation) persists.
Simple wiremap testers only confirm pin-to-pin DC continuity and cannot test high-frequency signal integrity.
2
Identify the required level of diagnostic measurement
Parameters like Near-End Crosstalk (NEXT), Equal-Level Far-End Crosstalk (ELFEXT), and return loss require broad frequency sweeps.
Gigabit Ethernet (1000BASE-T) relies on high-frequency signalling across all four pairs simultaneously, making it susceptible to noise and crosstalk.
3
Select the appropriate diagnostic tool
Choose a cable certifier.
Cable certifiers execute standardized test suites (ANSI/TIA-568) across specified frequencies to ensure physical copper infrastructure complies with category rating standards.

Anahtar Kavram

Copper Cable Certification vs. Basic Continuity Testing
Soru 450Soru

A network technician is deploying a new smart HVAC controller on VLAN 55 (172.16.55.0/24172.16.55.0/24). The corporate DHCP server is centralized on VLAN 10 (172.16.10.10/24172.16.10.10/24). Upon booting up the controller, running a network diagnostics command shows the following output:

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

Other existing hosts on VLAN 10 obtain their DHCP leases without issues. Which of the following is the MOST likely cause of the HVAC controller failing to acquire an IP address?

Cevabı ve açıklamayı göster

Cevap: The router interface servicing VLAN 55 lacks an IP helper address configured to forward broadcast DHCP requests.

Cevap

The router interface servicing VLAN 55 lacks an IP helper address configured to forward broadcast DHCP requests.
The client's self-assignment of an Automatic Private IP Address (169.254.108.42169.254.108.42) indicates that its DHCPDISCOVER broadcast was never answered. Since the host resides on VLAN 55 and the DHCP server resides on VLAN 10, the Layer 3 boundary router between these subnets drops the broadcast unless an IP helper address (DHCP Relay agent) is explicitly configured on the VLAN 55 interface to convert the broadcast to unicast.

Adım Adım Çözüm

1
Analyze the terminal output from the HVAC controller.
The host assigned itself an APIPA address of 169.254.108.42/16169.254.108.42/16, indicating it sent DHCPDISCOVER broadcasts but received no DHCPOFFER responses.
When a client configured for dynamic addressing receives no response from a DHCP server, automatic private IP addressing (APIPA) assigns an address in the 169.254.0.0/16169.254.0.0/16 range.
2
Evaluate the network topology context.
The client is on VLAN 55 (172.16.55.0/24172.16.55.0/24) while the DHCP server is located on VLAN 10 (172.16.10.10/24172.16.10.10/24).
Routers drop Layer 2 broadcast frames by default, preventing broadcast DHCPDISCOVER packets from traversing subnets unless relayed.
3
Determine the required resolution mechanism.
An IP helper address (`ip helper-address 172.16.10.10`) must be configured on the VLAN 55 Layer 3 interface.
The IP helper agent converts incoming broadcast DHCPDISCOVER messages into unicast requests sent directly to the centralized DHCP server on VLAN 10.

Anahtar Kavram

Troubleshooting DHCP Relay / IP Helper across Subnets and APIPA Diagnosis
Soru 451Soru

A network administrator is troubleshooting an issue on a Linux server hosting an internal HTTPS application. Users report that they cannot access the website from remote workstations, even though the server is powered on and reachable via `ping`. The administrator executes a command-line utility on the Linux server to inspect active network socket bindings and receives the following output:

State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 128 127.0.0.1:443 0.0.0.0:* users:(("httpd",pid=2048,fd=3))

Based on this output snippet, which of the following is the root cause preventing remote clients from accessing the web service?

Cevabı ve açıklamayı göster

Cevap: The web service daemon is bound exclusively to the local loopback interface rather than a physical network interface IP address.

Cevap

The web service daemon is bound exclusively to the local loopback interface rather than a physical network interface IP address.
The output snippet generated by socket troubleshooting commands (such as `ss` or `netstat`) reveals that the `httpd` process is listening on `127.0.0.1:443`. The IP address `127.0.0.1` is reserved for the host loopback interface, meaning the operating system will only accept socket connections originating from within the local machine. Remote workstations cannot reach the service until the daemon configuration is updated to bind to the server's actual interface IP address or all available network interfaces (`0.0.0.0`).

Adım Adım Çözüm

1
Analyze the command-line output socket binding table.
Identify that the process `httpd` is in the `LISTEN` state on `127.0.0.1:443`.
The `Local Address:Port` column indicates which network interface IP address and TCP port the daemon listens to for incoming traffic.
2
Evaluate the IP address scope for 127.0.0.1.
Recognize that `127.0.0.1` is reserved strictly for the local loopback interface.
Traffic directed to `127.0.0.1` is processed internally by the local host OS and cannot accept inbound IP packets arriving from external network adapters.
3
Determine the necessary corrective action for network accessibility.
The server configuration must be updated to listen on `0.0.0.0:443` (all interfaces) or the specific physical interface IP assigned to the server.
Binding to `0.0.0.0` or a public/private subnet IP allows the network stack to listen for incoming connections over the physical network interface.

Anahtar Kavram

Socket Binding and Loopback Interface Isolation in Network Troubleshooting CLI Utilities
Soru 452Soru

A network administrator connects a single-mode fiber optic patch cable to a newly installed patch panel module. Although physical link connectivity is established, optical testing shows exceptionally high optical return loss (back reflection), degrading signal quality. Upon visual inspection of the patch panel ports and connectors, the administrator notes that the patch cable has green LC connectors while the patch panel bulkhead coupler accepts blue LC connectors. Which of the following physical layer mismatched connection types is causing this issue?

Cevabı ve açıklamayı göster

Cevap: Mating an Angled Physical Contact (APC) connector with an Ultra Physical Contact (UPC) connector

Cevap

Mating an Angled Physical Contact (APC) connector with an Ultra Physical Contact (UPC) connector is causing the high optical return loss.
In fiber optic infrastructure, green connectors indicate Angled Physical Contact (APC), which features an 8-degree angled ferrule end-face designed to minimize back reflection. Blue connectors indicate Ultra Physical Contact (UPC), which features a flat or slightly dome-shaped ferrule end-face. Connecting an APC ferrule to a UPC ferrule creates an air gap between the fiber cores, causing severe signal reflection (high optical return loss) and potential physical damage to the glass end-faces.

Adım Adım Çözüm

1
Identify the connector color coding standards for optical fiber polish types.
Green bodies/boots signify Angled Physical Contact (APC), while blue bodies/boots signify Ultra Physical Contact (UPC).
Industry standards mandate strict color coding to prevent improper mating of differing physical contact geometries.
2
Analyze the physical ferrule interface differences between APC and UPC connectors.
APC ferrules are polished at an 8-degree angle to direct reflected light into the cladding, whereas UPC ferrules are polished with a flat/spherical surface.
Joining an 8-degree angled ferrule (green) to a flat/spherical ferrule (blue) prevents complete glass-to-glass contact.
3
Determine the impact of mating APC with UPC connectors.
The physical gap causes severe optical signal reflection (high return loss) and can permanently damage the fiber end-faces.
Matching physical polish types is essential for maintaining physical layer transmission integrity.

Anahtar Kavram

Fiber Optic Polish Types (APC vs. UPC Connector Mismatch)
Tahmini Süre:1m 30s
Soru 453Soru

A network technician is investigating degraded performance and intermittent packet drops on a newly terminated Category 6 UTP cable run. When tested with a basic wiremap continuity tester, all eight pins pass with direct 1-to-1 pin mapping. However, the link experiences severe performance issues under load. Which of the following test results or physical characteristics indicate that a split pair condition is the root cause of this failure? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: A basic wiremap continuity tester reports that pin 1 connects to pin 1, pin 2 to pin 2, up to pin 8 to pin 8.; A cable certifier measures excessively high Near-End Crosstalk (NEXT) along the cable run.

Cevap

The correct characteristics indicating a split pair are that a basic wiremap tester reports full 1-to-1 pin continuity, while a cable certifier measures excessively high Near-End Crosstalk (NEXT).
A split pair condition happens when individual wires from separate twisted pairs are improperly paired together at both RJ-45 terminations. Because the pinout sequence is mirrored at both ends, a basic continuity wiremap tester shows a valid 1-to-1 connection. However, breaking the geometric pairing cancels the noise rejection mechanism inherent to twisted-pair cabling, causing severe Near-End Crosstalk (NEXT) that requires a full cable certifier to detect.

Adım Adım Çözüm

1
Understand the physical nature of a split pair fault.
A split pair occurs when two individual conductors from different twisted pairs are mistakenly swapped at both cable ends during termination (e.g., pin 3 and pin 4 swapped on both ends).
Because the miswiring is mirrored at both ends, electrical continuity is maintained from end to end.
2
Evaluate how basic continuity testers interact with split pairs.
Basic wiremap testers only verify DC continuity and pin-to-pin mapping, so they report the cable as correctly wired.
Continuity testers do not check signal frequency, phase cancellation, or crosstalk.
3
Analyze high-frequency signal interference caused by split pairs.
Twisting two specific conductors together cancels out electromagnetic interference. Splitting those pairs disrupts the cancellation effect, causing high Near-End Crosstalk (NEXT) and Far-End Crosstalk (FEXT).
Advanced cable certifiers testing high-frequency signal integrity detect this elevated NEXT noise.

Anahtar Kavram

Split Pair Diagnosis in Twisted-Pair Cabling
Tahmini Süre:1m 30s
Soru 454Soru

A network administrator is troubleshooting a connectivity failure between two switches connected via an 802.1Q trunk link. Host devices assigned to VLAN 10 on Switch-A are unable to communicate with servers on VLAN 10 connected to Switch-B. Inspection of the switch port configurations indicates that port GigabitEthernet 0/1 on Switch-A is configured with VLAN 10 as its native VLAN, while port GigabitEthernet 0/1 on Switch-B uses default VLAN 1 as its native VLAN. Which of the following best explains why VLAN 10 traffic fails to reach its destination across the trunk?

Cevabı ve açıklamayı göster

Cevap: Switch-A transmits VLAN 10 traffic untagged over the trunk, causing Switch-B to receive the frames and place them into VLAN 1 rather than VLAN 10.

Cevap

Switch-A transmits VLAN 10 traffic untagged over the trunk, causing Switch-B to receive the frames and place them into VLAN 1 rather than VLAN 10.
The correct answer correctly identifies that an 802.1Q trunk sends frames belonging to its configured native VLAN without adding an 802.1Q VLAN tag. Because Switch-A has native VLAN 10 and Switch-B has native VLAN 1, Switch-A sends VLAN 10 frames untagged. Switch-B receives those untagged frames and places them into its own native VLAN (VLAN 1), preventing VLAN 10 hosts on Switch-A from reaching VLAN 10 servers on Switch-B.

Adım Adım Çözüm

1
Analyze how 802.1Q trunks handle native VLAN traffic.
Frames associated with the native VLAN configured on a switch interface are sent across the trunk link without an IEEE 802.1Q VLAN tag.
802.1Q standard behavior dictates that native VLAN traffic remains untagged for backward compatibility.
2
Trace the path of untagged frames sent from Switch-A to Switch-B.
Switch-A sends VLAN 10 frames untagged because VLAN 10 is configured as native on Switch-A's trunk interface. Upon arrival at Switch-B, Switch-B receives untagged frames and assigns them to its native VLAN, which is configured as VLAN 1.
Switches assign all incoming untagged frames received on a trunk port to whichever VLAN is configured locally as the native VLAN.
3
Determine the operational impact on VLAN 10 connectivity.
VLAN 10 frames from Switch-A end up on VLAN 1 on Switch-B, preventing end-to-end Layer 2 communication between VLAN 10 hosts across the switches.
Traffic is misrouted into a different broadcast domain, breaking intra-VLAN communication.

Anahtar Kavram

802.1Q Native VLAN Tagging and Mismatch Behavior
Soru 455Soru

Match each command-line network troubleshooting command to its primary diagnostic function.

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

Öğeler

ping -f -l 1472
nslookup -type=TXT
ss -tulpn
traceroute -n

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Matching pairs: ping -f -l 1472 corresponds to testing path MTU with the Don't Fragment flag; nslookup -type=TXT corresponds to querying DNS TXT records; ss -tulpn corresponds to displaying listening TCP/UDP sockets with PIDs without resolving names; traceroute -n corresponds to tracing the Layer 3 path without hostname resolution.
Each utility switch targets a specific diagnostic capability: 'ping -f -l' checks MTU size limits, 'nslookup -type=TXT' retrieves text verification records, 'ss -tulpn' lists listening sockets and process IDs numerically on Linux, and 'traceroute -n' identifies route hops without performing time-consuming reverse DNS lookups.

Adım Adım Çözüm

1
Analyze ping switches '-f' and '-l'
Identify '-f' as Don't Fragment flag and '-l' as payload size, indicating Path MTU Discovery (PMTUD).
Setting the DF flag causes routers to drop packets exceeding MTU size and return ICMP Fragmentation Needed messages.
2
Analyze nslookup option '-type=TXT'
Recognize record type targeting domain text entries.
TXT records store descriptive text data, frequently utilized for email authentication mechanisms like SPF and DKIM.
3
Analyze ss command flags '-tulpn'
Decode Linux socket statistics options.
'-t' (TCP), '-u' (UDP), '-l' (listening), '-p' (processes), and '-n' (numeric output without DNS resolution) inspect open ports and ownership.
4
Analyze traceroute flag '-n'
Identify suppression of reverse DNS lookups.
Instructing traceroute not to perform DNS resolution speeds up execution when identifying network path hops.

Anahtar Kavram

Utilizing command-line utilities and flags for specific network troubleshooting diagnostics
Soru 456Soru

A workstation on VLAN 30 (192.168.30.0/24192.168.30.0/24) fails to receive an IP address automatically and shows an APIPA address of 169.254.14.88169.254.14.88. A network administrator must systematically isolate the issue from the local host to the centralized network services. Place the troubleshooting steps in the correct logical sequence.

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

Cevabı ve açıklamayı göster

Cevap

The correct troubleshooting sequence starts at the local client host (`ipconfig /all`), moves to verifying the local router's DHCP relay configuration (`ip helper-address`), tests Layer 3 reachability to the server (`ping`), and finishes with inspecting DHCP scope activity and pool capacity on the server.
Structured network troubleshooting follows a logical path from local host diagnostics (`ipconfig /all`), to local gateway relay verification (`ip helper-address`), inter-device reachability testing (`ping`), and finally centralized service health checks (DHCP scope status).

Adım Adım Çözüm

1
Verify client interface state and IP configuration.
Confirms host link status and verifies APIPA (169.254.x.x169.254.x.x) autoconfiguration state.
Establishes baseline host status before analyzing upstream infrastructure.
2
Verify DHCP relay agent settings on the local gateway.
Ensures client DHCP broadcast frames are converted to unicast packets directed to the server.
Routers drop broadcasts by default; missing relay configuration stops DHCP requests at the gateway.
3
Test Layer 3 IP reachability between gateway and DHCP server.
Confirms routing and network path functionality between relay agent and server.
Relay agents cannot deliver unicast DHCPDISCOVER packets if routing to the server is down.
4
Audit server scope status and lease pool availability.
Verifies that the DHCP server can generate valid DHCPOFFER responses for the requested subnet.
Exhausted pools or disabled scopes prevent lease issuance even when requests arrive successfully.

Anahtar Kavram

DHCP Relay and IP Address Troubleshooting Sequence
Soru 457Soru

A network administrator receives reports that mobile devices connecting to the guest Wi-Fi network (VLAN 85, subnet 172.20.85.0/24172.20.85.0/24) are failing to access internet resources. Inspecting a network details page on an affected device reveals an IP address of 169.254.41.19169.254.41.19 with a subnet mask of 255.255.0.0255.255.0.0. Reviewing the DHCP server statistics shows that the active pool for VLAN 85 currently has 00 available IP addresses remaining out of the 254254 allocated pool entries. Which of the following actions should the administrator take to resolve the root cause of this issue?

Cevabı ve açıklamayı göster

Cevap: Expand the DHCP scope for VLAN 85 by modifying the subnet mask to a /23/23 or shortening the DHCP lease duration.

Cevap

Expanding the DHCP scope for VLAN 85 (such as by modifying the subnet mask to a /23) or reducing the lease duration will resolve the address pool exhaustion issue.
The client receiving an APIPA address (169.254.x.x169.254.x.x) combined with the DHCP server showing 00 available addresses indicates DHCP scope exhaustion. To remediate scope exhaustion in high-turnover guest wireless networks, administrators should expand the address pool (for example, expanding a /24/24 subnet to a /23/23) or decrease the DHCP lease duration so inactive leases expire sooner.

Adım Adım Çözüm

1
Analyze the client symptom and IP address output.
The IP address 169.254.41.19169.254.41.19 is an Automatic Private IP Addressing (APIPA) address, indicating the client failed to obtain a DHCP lease.
When a client cannot reach a DHCP server or receive an available lease, it self-assigns an APIPA address in the 169.254.0.0/16169.254.0.0/16 range.
2
Examine the DHCP server pool statistics.
The server logs show 00 available addresses remaining out of 254254 total entries in the scope.
This confirms DHCP scope exhaustion, where all usable host addresses have been leased out to existing clients.
3
Identify the appropriate remediation strategy.
Shortening lease times allows inactive leases to expire faster, while expanding the subnet mask to /23/23 increases usable addresses from 254254 to 510510.
Increasing scope capacity or accelerating lease turnover directly resolves scope exhaustion in high-density or guest wireless environments.

Anahtar Kavram

DHCP Scope Exhaustion and APIPA Diagnosis
Tahmini Süre:1m 30s
Soru 458Soru

A network administrator is investigating a database connection issue on a host machine. The administrator needs to query the designated internal DNS server at 10.0.0.5310.0.0.53 directly for the record `db1.corp.internal` rather than relying on local resolver cache settings, and also inspect all active TCP socket connections along with listening ports on the local system. Which of the following command-line entries will successfully achieve these goals? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Run `nslookup db1.corp.internal 10.0.0.53` to direct the name resolution query to the specific internal server.; Run `netstat -an` to display all active connections and numerical port bindings.

Cevap

The correct actions are running `nslookup db1.corp.internal 10.0.0.53` to query the specific DNS server directly and running `netstat -an` to inspect active socket connections and listening ports numerically.
Directing an `nslookup` request to a specific server IP address (such as `nslookup db1.corp.internal 10.0.0.53`) bypasses local DNS caches to query that server directly. Additionally, `netstat -an` provides a detailed list of all listening ports and established socket connections using numerical IP addresses and port numbers.

Adım Adım Çözüm

1
Identify the CLI tool syntax required to bypass local resolver settings and query a designated DNS server directly.
Executing `nslookup <hostname> <server_ip>` sends the lookup query explicitly to the specified server IP address (10.0.0.5310.0.0.53).
Default `nslookup` queries rely on configured system resolvers unless an explicit server address parameter is provided.
2
Identify the CLI utility suited for displaying open network ports and active TCP sessions.
`netstat -an` outputs all active TCP/UDP connections and open listening ports in numerical format.
The `-a` flag includes listening ports and the `-n` flag suppresses hostname/service resolution for faster numerical rendering.

Anahtar Kavram

Utilizing command-line network utilities (`nslookup`, `netstat`, `dig`, `arp`) for protocol inspection and reachability troubleshooting.
Soru 459Soru

During a fiber optic cabling deployment between two network racks, a technician notes high optical signal attenuation on a multi-mode fiber patch cord. The technician suspects a physical micro-fracture or excessive bend radius near one of the connector terminations where light is escaping through the buffer. Which tool should the technician use to visually locate the exact spot where light is leaking?

Cevabı ve açıklamayı göster

Cevap: Visual Fault Locator (VFL)

Cevap

The Visual Fault Locator (VFL) is the appropriate diagnostic tool to visually identify escaping light at a bend or fracture in a fiber optic cable.
The Visual Fault Locator (VFL) uses a visible red laser that bleeds through jacket damage, tight bends, or cracked fibers, enabling instant visual detection of physical fault locations.

Adım Adım Çözüm

1
Analyze the physical layer symptom
Light loss (attenuation) is occurring on a fiber patch cord due to a suspect bend or fracture emitting light.
Identifying whether light is escaping requires a visible light source operating in the visible spectrum.
2
Evaluate candidate optical troubleshooting tools
The Visual Fault Locator (VFL) injects a visible red laser (635-650 nm) into the fiber core.
Escaping red light illuminates faults through the jacket or connector buffer.
3
Select the correct diagnostic instrument
Choose the VFL over copper tools or non-visual meters.
OPMs measure loss quantitatively without pinpointing location, while TDRs and tone probes apply to copper media.

Anahtar Kavram

Fiber Optic Visual Fault Locators
Tahmini Süre:1m 0s
Soru 460Soru

A network technician executes a command-line DNS query on a workstation to troubleshoot host resolution. The technician receives the following terminal output:

text
Server: resolver.lab.corp
Address: 192.168.1.254

Non-authoritative answer:
Name: fileserver.lab.corp
Address: 10.1.50.12

Which of the following statements correctly interprets the 'Non-authoritative answer' header in this CLI output?

Cevabı ve açıklamayı göster

Cevap: The responding DNS server provided the IP address from its local cache rather than holding the master zone file for the domain.

Cevap

The responding DNS server provided the IP address from its local cache rather than holding the master zone file for the domain.
The 'Non-authoritative answer' designation indicates that the DNS server fulfilling the query obtained the host mapping from its cached memory (or via recursive queries to other name servers) rather than maintaining the original authoritative zone database for the domain.

Adım Adım Çözüm

1
Analyze the CLI output header and response structure.
The terminal shows that server resolver.lab.corp (192.168.1.254) processed the request for fileserver.lab.corp.
Identifying the responding server verifies that network DNS resolution took place rather than a local file lookup.
2
Evaluate the meaning of the 'Non-authoritative answer' designation in DNS diagnostic tools.
A non-authoritative response indicates the server answered from cached records retrieved from another server.
Authoritative answers only come from the primary or secondary DNS servers hosting the official zone database file for that specific domain.
3
Select the option matching the correct interpretation of DNS cache operations.
The statement explaining that the server answered using cached data from a recursive lookup is correct.
This directly aligns with standard DNS resolver behavior when fulfilling client queries for domains outside their hosted zones.

Anahtar Kavram

Interpreting nslookup and DNS command-line utility outputs
ÖncekiSayfa 23 / 25Sonraki
Network Troubleshooting Alıştırma Soruları — CompTIA Network+ — Sayfa 23 | Examkin