Network Troubleshooting

486 soru

Soru 141Soru

A network technician is performing RF site troubleshooting in a manufacturing facility to resolve persistent wireless connectivity issues. Match each observed wireless symptom or environmental phenomenon on the left with its correct physical root cause or signal behavior on the right.

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

Öğeler

Multipath distortion causing high frame retransmissions
RF attenuation causing rapid reduction in RSSI
Non-802.11 ambient interference causing localized signal degradation
Antenna polarization mismatch causing severe signal loss

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Multipath distortion matches signal reflection out of phase off metal surfaces; RF attenuation matches absorption by dense building materials; Non-802.11 interference matches RF noise from unshielded industrial microwave equipment; Antenna polarization mismatch matches orthogonal spatial antenna orientations.
Each wireless troubleshooting phenomenon is accurately matched to its underlying RF physical characteristic: reflection out of phase causes multipath, physical absorption by building materials causes attenuation, non-Wi-Fi electromagnetic emitters cause non-802.11 interference, and mismatched spatial alignment of antennas causes polarization loss.

Adım Adım Çözüm

1
Analyze the physical behavior of signal reflections.
Identify that bounced radio waves arriving out of phase represent multipath distortion.
Reflected signals arrive at slightly different intervals, creating inter-symbol interference.
2
Analyze signal loss caused by physical barriers.
Identify that RSSI reduction due to concrete or masonry wall absorption represents RF attenuation.
Physical obstacles absorb and diminish RF energy as waves travel through them.
3
Analyze noise generated by non-Wi-Fi electronics.
Identify that 2.4 GHz interference from microwave appliances represents non-802.11 ambient interference.
Industrial and consumer appliances generate electromagnetic noise outside the 802.11 protocol rules.
4
Analyze spatial orientation issues with wireless antennas.
Identify that orthogonal antenna positioning represents polarization mismatch.
Maximum signal transfer requires transmitter and receiver antennas to share the same physical plane.

Anahtar Kavram

Physical and Environmental RF Troubleshooting Mechanisms
Tahmini Süre:1m 30s
Soru 142Soru

A network technician is addressing severe voice quality degradation on an enterprise VoIP network following a core router firmware update. Place the technician's troubleshooting procedures in the correct sequence according to the official CompTIA troubleshooting methodology.

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence follows the official CompTIA troubleshooting methodology: 1. Identify the problem (gather information and replicate symptoms), 2. Establish a theory of probable cause (hypothesize QoS reset), 3. Test the theory (check queue statistics to confirm root cause), 4. Establish a plan of action (formulate change request and evaluate impact), 5. Verify full system functionality (place test calls to confirm resolution), 6. Document findings, actions, and outcomes (log the issue and update documentation).
The CompTIA troubleshooting methodology follows a strict 6-step lifecycle: 1) Identify the problem, 2) Establish a theory of probable cause, 3) Test the theory to determine the cause, 4) Establish a plan of action to resolve the problem and identify potential effects, 5) Verify full system functionality and, if applicable, implement preventive measures, and 6) Document findings, actions, and outcomes. The sequence correctly places problem identification and replication first, followed by hypothesis generation, theory testing, change planning, system verification, and final documentation.

Adım Adım Çözüm

1
Identify the problem
Gathered user reports, checked error counters, and successfully replicated the voice degradation symptoms.
Troubleshooting must begin by defining the exact symptoms and establishing a clear problem scope.
2
Establish a theory of probable cause
Formulated a hypothesis that the recent firmware update removed the customized QoS configuration.
After gathering problem details, the technician considers potential causes, questioning the obvious factors like recent maintenance.
3
Test the theory to determine the cause
Confirmed that voice packets were incorrectly classified into the best-effort queue.
Testing validates whether the hypothesis is correct before taking disruptive corrective actions.
4
Establish a plan of action to resolve the problem and identify potential effects
Drafted a plan and change ticket to re-apply the LLQ QoS policy while evaluating potential network impact.
A structured plan ensures that changes are systematically planned, approved, and mitigated against unintended side effects.
5
Verify full system functionality and implement preventive measures
Confirmed clear voice calls and verified no dropouts or secondary issues occurred.
Fixes must be verified in the actual environment to ensure the problem is completely resolved without introducing new issues.
6
Document findings, actions, and outcomes
Recorded the issue summary, root cause, and updated baseline documentation.
Documenting creates historical references for future incidents and maintains accurate network records.

Anahtar Kavram

CompTIA 6-Step Network Troubleshooting Methodology
Tahmini Süre:1m 30s
Soru 143Soru

A system administrator notices that a newly provisioned server cannot reach destinations outside its local subnet. Arrange the diagnostic actions in the correct logical sequence following standard CompTIA troubleshooting methodology.

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

Cevabı ve açıklamayı göster

Cevap

The proper troubleshooting sequence begins with verifying local host network settings, testing reachability to the local default gateway via ping, performing a traceroute to isolate the path failure hop, and inspecting the gateway router's routing table and access control lists.
Logical network troubleshooting flows systematically from the local host up through the network path. First, local interface configurations must be verified. Second, connectivity to the immediate gateway is tested. Third, traceroute isolates where remote forwarding fails. Finally, deep analysis of router ACLs and routing tables is performed at the point of failure.

Adım Adım Çözüm

1
Inspect local network configuration
Confirms the host IP, subnet mask, and default gateway address are correctly configured.
Eliminates local host misconfigurations before testing network infrastructure.
2
Ping local default gateway
Validates functional ICMP communication across the local switch fabric to the router interface.
Ensures the host can reach its local gateway before attempting off-subnet diagnostics.
3
Run traceroute to target destination
Determines whether packets stop at the local gateway or at a downstream hop.
Isolates the specific network device responsible for packet loss.
4
Examine router configuration
Identifies root causes such as missing default static routes or explicit/implicit ACL deny statements.
Enables targeted remediation on the affected network device.

Anahtar Kavram

Troubleshooting Gateway and Routing Path Issues
Soru 144Soru

A network technician needs to identify which port on a patch panel inside a wiring closet connects to an unlabelled wall outlet in a conference room. Which of the following tools is best suited to trace and locate this cable run?

Cevabı ve açıklamayı göster

Cevap: Tone generator and probe

Cevap

The tone generator and probe is the appropriate tool for tracing and locating an unlabelled cable run.
A tone generator emits an analog audio tone onto copper conductors, while an inductive probe senses the signal without physical metal contact. This allows a technician to sweep the probe across patch panel ports to quickly pinpoint the matching cable end.

Adım Adım Çözüm

1
Determine the troubleshooting requirement
The objective is to trace an unlabelled physical copper cable from a wall jack to its patch panel termination point.
Identifying unlabelled cable runs requires a tool designed for cable tracing rather than performance certification or fault distance measurement.
2
Select the correct physical diagnostic tool
Connecting the tone generator to the wall outlet sends an audible signal down the cable, which can then be detected at the patch panel using the inductive probe.
Tone generators and probes (often called fox and hound kits) are explicitly built to locate specific wires within bundles or unlabelled patch panels.

Anahtar Kavram

Cable Tracing and Location Tools
Soru 145Soru

A network technician terminates a custom Category 6A unshielded twisted-pair (UTP) cable run between a high-density patch panel and an enterprise core switch. A basic LED wiremapper confirms pin-to-pin continuity on all eight conductors (pins 1 through 8 match identically on both ends). However, when connected to 10 Gbps10\text{ Gbps} switch interfaces, the link fails to auto-negotiate above 100 Mbps100\text{ Mbps} and generates a rapid accumulation of Cyclic Redundancy Check (CRC) errors and Near-End Crosstalk (NEXT) violations under traffic load. Which of the following physical layer faults is the root cause of this failure, and which instrument must be used to diagnose it accurately?

Cevabı ve açıklamayı göster

Cevap: A split pair condition caused by mispairing conductors across different twisted pairs, requiring a cable certifier or high-frequency TDR to detect NEXT failure.

Cevap

The root cause is a split pair condition, which preserves pin-to-pin DC continuity but destroys noise cancellation, requiring a cable certifier or high-frequency Time-Domain Reflectometer (TDR) capable of measuring Near-End Crosstalk (NEXT) to diagnose.
A split pair occurs when individual conductors are wired to the correct pin locations on both ends of a cable run, but are physically taken from different twisted pairs (for example, placing pin 3 and pin 4 onto the same physical twisted pair). Because continuity remains 1-to-1, simple DC wiremappers register a pass. However, at high frequencies such as 10 Gbps10\text{ Gbps} Ethernet, the lack of pair twisting mutual cancellation generates extreme Near-End Crosstalk (NEXT) and packet corruption, causing auto-negotiation fallbacks and CRC errors. A cable certifier or TDR capable of measuring parameter performance across frequencies is required to detect and pinpoint this condition.

Adım Adım Çözüm

1
Analyze the diagnostic data from the basic wiremapper test
Basic LED wiremappers send low-voltage DC signals down each conductor individually to verify pin-to-pin continuity (e.g., Pin 1 to Pin 1, Pin 2 to Pin 2). Passing this test rules out open circuits, short circuits, and reversed pinouts.
Establishing what a basic continuity tester can and cannot measure isolates the category of cable fault.
2
Correlate link performance symptoms with physical twisted-pair physics
Twisted-pair Ethernet relies on differential signaling across dedicated pairs (e.g., pins 1/2, 3/6, 4/5, 7/8 in T568B) to cancel electromagnetic interference and crosstalk. In a split pair, individual wires are connected to the correct pins on both ends, but conductors from different physical pairs are paired together.
DC current flows through the correct pin numbers, so DC continuity passes, but the AC differential signals travel along non-twisted physical partners, eliminating noise cancellation and creating severe NEXT and CRC errors at high frequencies (10 Gbps10\text{ Gbps}).
3
Select the appropriate diagnostic instrument
Identifying split pairs and high-frequency crosstalk requires a cable certifier or advanced Time-Domain Reflectometer (TDR) that measures AC signal parameters, NEXT, return loss, and impedance discontinuities.
Simple continuity testers or tone probes cannot analyze signal phase, crosstalk, or high-frequency performance metrics.

Anahtar Kavram

Split Pair Faults & Advanced Cable Certification
Soru 146Soru

A network engineer is systematically troubleshooting a client workstation that is experiencing intermittent domain name resolution failures for internal corporate servers. Arrange the troubleshooting steps in the correct, logical order—beginning with local client configuration verification and progressing outward to network transport validation.

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

Cevabı ve açıklamayı göster

Cevap

The correct systematic order begins with verifying client IP configuration settings (ipconfig /all), followed by inspecting local DNS cache entries (ipconfig /displaydns), checking static mapping overrides in the HOSTS file, issuing an explicit query directly to the DNS server (nslookup), and finally inspecting network path firewalls for UDP/TCP port 53 traffic blocking.
Systematic DNS troubleshooting follows a logical progression from local client endpoint configuration (verifying IP settings, clearing local cache, inspecting static HOSTS file entries) to direct server querying (nslookup), and finally to network path transport verification (UDP/TCP port 53 firewall inspection).

Adım Adım Çözüm

1
Verify client IP configuration settings.
Confirmed assigned Primary/Secondary DNS IP addresses and DNS search suffixes.
Incorrect server IPs or missing domain suffixes prevent queries from reaching the intended server.
2
Inspect local endpoint DNS resolver cache.
Identified whether previously resolved names or stale negative cache entries are causing failures.
Operating systems check memory cache before sending outbound network queries.
3
Review local static HOSTS file overrides.
Checked for misconfigured IP-to-hostname mappings on the local filesystem.
HOSTS file entries supersede DNS server lookup requests in standard host name resolution order.
4
Execute explicit nslookup targeting the DNS server.
Determined whether the DNS server responds to direct FQDN queries.
Direct queries bypass client-side caching and isolate client configuration from server responsiveness.
5
Verify network transport layer rules on UDP/TCP port 53.
Isolated intermediate network firewalls blocking DNS traffic.
If client configuration is valid but queries time out, intermediate network firewalls or ACLs are blocking UDP/TCP port 53.

Anahtar Kavram

Troubleshooting DNS and Name Resolution Services
Tahmini Süre:2m 0s
Soru 147Soru

A network administrator receives a report that a newly assigned workstation on VLAN 25 (10.25.0.0/2410.25.0.0/24) cannot access remote intranet services. Upon inspecting the workstation, the administrator observes an auto-configured IPv4 address of 169.254.42.10169.254.42.10. Place the following diagnostic and remediation steps in the correct logical sequence to systematically troubleshoot and resolve this DHCP relay issue from client verification to final resolution.

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

Cevabı ve açıklamayı göster

Cevap

The correct logical sequence begins with client-side verification (`ipconfig /all`), followed by testing local subnet connectivity using a static IP, checking the router's DHCP relay (`ip helper-address`) configuration, confirming DHCP server scope availability for VLAN 25, and finally releasing and renewing the client's lease.
Following the structured troubleshooting methodology, an administrator must first verify client symptoms (APIPA confirmation), isolate local physical and VLAN connectivity using a temporary static IP, verify that the Layer 3 boundary device is properly configured with a DHCP relay agent (`ip helper-address`), ensure the remote DHCP server has an active scope for that subnet, and finally test dynamic acquisition on the client.

Adım Adım Çözüm

1
Confirm client symptom and network stack state
Identify that the client holds an APIPA address (169.254.42.10169.254.42.10), proving DHCP DISCOVER messages failed to receive an OFFER.
CompTIA troubleshooting methodology mandates verifying the problem and gathering initial symptoms on the affected client first.
2
Isolate local Layer 2/3 network path
Confirming ping to 10.25.0.110.25.0.1 works under a temporary static IP proves local cabling, NIC, and switch VLAN configuration are functional.
Eliminates basic physical and local link issues before troubleshooting higher-level services across subnets.
3
Audit gateway DHCP relay configuration
Identify if `ip helper-address` is missing or pointing to an incorrect IP on the gateway interface for VLAN 25.
DHCP broadcasts cannot cross routers without a relay agent forwarding unicast requests to the DHCP server.
4
Audit central DHCP server scope state
Ensure the server scope for 10.25.0.0/2410.25.0.0/24 is active, not scope-exhausted, and configured with correct options.
Even with a working relay agent, an unactivated or exhausted scope prevents IP assignment.
5
Verify resolution on client
Client successfully receives an IP address in the 10.25.0.0/2410.25.0.0/24 range via dynamic lease renewal.
Confirms full end-to-end functionality of the DHCP process.

Anahtar Kavram

DHCP Relay and APIPA Troubleshooting Methodology across Subnets
Soru 148Soru

An IT technician is troubleshooting severe throughput degradation and excessive frame retransmissions on a newly configured 2.4 GHz wireless network in an office suite. A site survey reveals that three nearby access points serving the area are operating on channels 1, 3, and 5. Which of the following modifications should the technician make to resolve the interference?

Cevabı ve açıklamayı göster

Cevap: Reconfigure the access points to operate on channels 1, 6, and 11.

Cevap

Reconfigure the access points to operate on channels 1, 6, and 11.
The 2.4 GHz Wi-Fi spectrum uses 20 MHz channel widths spaced 5 MHz apart. To avoid adjacent-channel interference (ACI), access points must be configured on non-overlapping channels (1, 6, and 11). Operating APs on channels 1, 3, and 5 results in overlapping frequency ranges that cause heavy packet corruption and retransmissions.

Adım Adım Çözüm

1
Analyze the reported symptoms and current channel assignment
Identified that channels 1, 3, and 5 overlap with one another in the 2.4 GHz band, leading to adjacent-channel interference (ACI).
Channels 1, 3, and 5 share frequency ranges, causing RF energy from one channel to corrupt signals on adjacent channels.
2
Determine the standard non-overlapping channel scheme for 2.4 GHz Wi-Fi
Channels 1, 6, and 11 provide 20 MHz spacing with no frequency overlap.
20 MHz wide channels require 25 MHz of separation between center frequencies to prevent overlapping boundaries.
3
Select the appropriate remedial action
Reassigning the access points to channels 1, 6, and 11 resolves ACI.
Proper channel separation eliminates adjacent channel interference and restores normal wireless throughput.

Anahtar Kavram

2.4 GHz Non-Overlapping Channel Selection
Soru 149Soru

During a post-maintenance outage, voice over IP (VoIP) endpoints on a newly provisioned voice VLAN fail to register with the local SIP call manager. A network engineer formulates a hypothesis that a newly applied transport layer security (TLS) certificate authority (CA) bundle is missing on the automated provisioning server payload. To test this theory, the engineer sets up an isolated test bench, captures the boot traffic of a test phone via switch port mirroring, and inspects the packet trace. The trace confirms that the phone aborts the session during the TLS handshake due to an untrusted certificate authority, successfully validating the root cause. Which of the following actions should the engineer perform NEXT according to the CompTIA troubleshooting methodology?

Cevabı ve açıklamayı göster

Cevap: Develop a plan of action to update the CA trust store on the provisioning server and assess potential side effects on active handsets before applying the change.

Cevap

Develop a plan of action to update the CA trust store on the provisioning server and assess potential side effects on active handsets before applying the change.
In the CompTIA 7-step troubleshooting methodology, the steps are: 1. Identify the problem, 2. Establish a theory of probable cause, 3. Test the theory to determine cause, 4. Establish a plan of action to resolve the problem and identify potential effects (then implement the solution), 5. Verify full system functionality and implement preventive measures, and 6. Document findings, actions, and outcomes. Because packet capture analysis on the isolated test bench confirmed the root cause (untrusted CA certificate), Step 3 is complete. The required next step is Step 4: establishing a plan of action and evaluating potential side effects before implementing the resolution.

Adım Adım Çözüm

1
Analyze current phase in CompTIA 7-step methodology
The engineer confirmed the hypothesis through packet inspection on an isolated test bench, completing Step 3 (Test the theory to determine cause).
Confirming the root cause concludes the theory testing phase.
2
Determine the next logical step in the CompTIA sequence
Step 4 of the methodology requires establishing a plan of action to resolve the problem and identifying potential effects.
Before executing changes in production, a plan must be structured and risk mitigation assessed.
3
Select the option that aligns with Step 4
Developing a plan of action to update the CA trust store while identifying potential impacts directly matches Step 4.
This maintains strict compliance with standard CompTIA troubleshooting framework rules.

Anahtar Kavram

CompTIA 7-Step Troubleshooting Methodology Sequence (Step 3 to Step 4 transition)
Soru 150Soru

A network technician is testing connectivity on a workstation that fails to load external websites. The technician executes `nslookup portal.vendor.com` in the command prompt and receives the following output:

text
C:\> nslookup portal.vendor.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.50

*** Request to UnKnown timed out

Which of the following is the most likely reason for this DNS resolution failure?

Cevabı ve açıklamayı göster

Cevap: The local workstation cannot reach or receive a response from the configured DNS server at 192.168.1.50.

Cevap

The local workstation cannot reach or receive a response from the configured DNS server at 192.168.1.50.
The correct option correctly identifies that a request timeout in `nslookup` occurs when the client sends a query to the designated DNS server (192.168.1.50) but receives no reply before the timer expires. This typically points to an unreachable DNS server, network path interruption, or blocked port 53 traffic.

Adım Adım Çözüm

1
Analyze the nslookup command output.
Identified that the client queried DNS server 192.168.1.50 and encountered 'DNS request timed out.'
Understanding the error message pinpointed the exact stage of the failure.
2
Differentiate between name resolution failure types.
Recognized that timeouts signify network transport or service availability issues rather than record misconfigurations (which return NXDOMAIN or SERVFAIL).
A request timeout means the server never responded back to the client's UDP/TCP port 53 query.
3
Select the option describing network reachability or service unresponsiveness.
Determined that 192.168.1.50 is unreachable or not responding to DNS requests.
This directly matches the observed timeout symptom.

Anahtar Kavram

DNS Timeout vs. Resolution Error Diagnosis
Soru 151Soru

A network administrator receives a ticket stating that a newly deployed application server at 192.168.20.5/24192.168.20.5/24 cannot reach a remote database server located on a different subnet at 10.1.50.10/2410.1.50.10/24. Place the following diagnostic and remediation steps in the correct logical troubleshooting sequence to isolate and resolve the issue.

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

Cevabı ve açıklamayı göster

Cevap

The correct logical order begins with checking local host IP configuration (item 1), testing local gateway reachability (item 2), tracing the path to isolate the failing hop (item 3), inspecting the routing table and ACLs at that hop (item 4), and finally applying the fix and verifying end-to-end connectivity (item 5).
Standard network troubleshooting proceeds methodically from the host level outward: verify host parameters, test local gateway reachability, perform path analysis to locate the failing hop, evaluate routing and ACL configurations on that device, and verify resolution.

Adım Adım Çözüm

1
Verify local host IP configuration
Ensures the host has a valid IP address, mask, and default gateway setting
Rule out basic local misconfigurations before investigating network infrastructure.
2
Ping the local default gateway
Confirms Layer 2 and Layer 3 reachability within the local broadcast domain
Isolates whether the problem is on the local LAN segment or across routed bounds.
3
Perform path tracing using traceroute
Pinpoints the exact intermediate router or firewall hop where ICMP/IP packets stop
Narrows the scope of investigation to a specific network device.
4
Analyze routing entries and ACL statements on the target hop device
Determines if packets are dropped due to a missing static/dynamic route or blocked by an implicit/explicit deny rule
Identifies the precise root cause of the forwarding failure.
5
Implement corrective configuration and conduct end-to-end validation
Restores bidirectional IP communication and verifies solution effectiveness
Confirms resolution without leaving unverified changes in production.

Anahtar Kavram

CompTIA Troubleshooting Methodology applied to Routing, Default Gateways, and ACLs
Soru 152Soru

A network administrator is investigating connectivity issues where branch office users report that cloud-hosted file transfers repeatedly stall and disconnect over an IPsec VPN tunnel. The administrator tests a hypothesis by sending ICMP packets with the Don't Fragment (DF) bit set, confirming that an maximum transmission unit (MTU) mismatch across the WAN interface is causing packet fragmentation drops. According to the CompTIA troubleshooting methodology, which action should the administrator perform NEXT?

Cevabı ve açıklamayı göster

Cevap: Establish a plan of action to modify the interface MTU and TCP MSS values while identifying potential impacts on overall network traffic.

Cevap

Establish a plan of action to modify the interface MTU and TCP MSS values while identifying potential impacts on overall network traffic.
The CompTIA troubleshooting methodology follows a strict sequence: 1. Identify the problem, 2. Establish a theory of probable cause, 3. Test the theory to determine cause, 4. Establish a plan of action to resolve the problem and identify potential effects, 5. Verify full system functionality and implement preventive measures, and 6. Document findings, actions, and outcomes. Because the administrator has already tested the theory and confirmed the MTU mismatch (Step 3), the immediate next step is Step 4: Establishing a plan of action to resolve the issue while considering potential side effects.

Adım Adım Çözüm

1
Identify the current step in the CompTIA 6-step troubleshooting process based on the scenario details.
The scenario describes that the administrator has tested the hypothesis (ICMP ping with DF bit set) and confirmed the cause (MTU mismatch), completing Step 3: Test the theory to determine cause.
CompTIA troubleshooting requires following a strict sequential workflow.
2
Determine the next sequential phase required by the methodology.
The step immediately following Step 3 (Test theory) is Step 4: Establish a plan of action to resolve the problem and identify potential effects.
Changes must be planned and evaluated for side effects before implementation.
3
Select the choice that corresponds to establishing a plan of action.
Developing a plan to adjust MTU/TCP MSS settings while considering traffic impacts correctly represents Step 4.
Planning actions and assessing potential effects ensures structured change management.

Anahtar Kavram

CompTIA Troubleshooting Methodology Step Sequence
Tahmini Süre:1m 15s
Soru 153Soru

A network administrator runs the following command on a host experiencing name resolution failures:

C:\> nslookup app.corp.local 192.168.1.10
Server: dns01.corp.local
Address: 192.168.1.10

*** dns01.corp.local can't find app.corp.local: Non-existent domain

Based on the output, which TWO of the following represent plausible root causes for this error? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: An A record for the hostname app.corp.local is missing from the forward lookup zone on the DNS server.; The queried hostname app.corp.local contains a typographical error or does not match the configured domain name record.

Cevap

The correct root causes are that an A record for app.corp.local is missing from the DNS server's forward lookup zone, and that the queried hostname contains a typographical error or does not match the record.
The nslookup utility successfully established contact with DNS server 192.168.1.10, but received an NXDOMAIN response. This demonstrates that network layer connectivity is operational, but the DNS zone database lacks an A/AAAA record for the queried name, or the user queried a misspelled domain name.

Adım Adım Çözüm

1
Analyze the nslookup command output.
The command successfully communicated with the specified DNS server at IP address 192.168.1.10192.168.1.10.
The output returns the server name and address, indicating network connectivity to the DNS service on port 53 is functional.
2
Evaluate the specific error message returned by the resolver.
The server responded with 'can't find app.corp.local: Non-existent domain' (NXDOMAIN).
NXDOMAIN confirms the DNS server processed the query but could not find a matching host record in its database.
3
Identify valid causes for an NXDOMAIN response.
The missing host record (A record) on the DNS zone or an incorrect host name query are the correct explanations.
Both causes directly explain why an authoritative DNS server returns a non-existent domain error.

Anahtar Kavram

Troubleshooting DNS NXDOMAIN Errors and Host Record Misconfigurations
Soru 154Soru

A user's workstation is assigned a static IPv4 address of 192.168.1.50192.168.1.50 with a subnet mask of 255.255.255.0255.255.255.0. The default gateway is configured as 192.168.2.1192.168.2.1. The user cannot access any external resources or communicate outside the local network segment. Which of the following best explains why the workstation cannot reach the default gateway?

Cevabı ve açıklamayı göster

Cevap: The host IP address and the default gateway reside on different IP subnets.

Cevap

The host IP address and the default gateway reside on different IP subnets.
For a workstation to forward traffic off its local network segment, its default gateway must share the same IP subnet. With a subnet mask of 255.255.255.0255.255.255.0, the workstation at 192.168.1.50192.168.1.50 belongs to the 192.168.1.0/24192.168.1.0/24 network, while the configured gateway 192.168.2.1192.168.2.1 belongs to the 192.168.2.0/24192.168.2.0/24 network. Because they reside on separate subnets, local ARP requests to locate the gateway will fail.

Adım Adım Çözüm

1
Determine the host's IP network ID based on its assigned IP address and subnet mask.
An IP address of 192.168.1.50192.168.1.50 with subnet mask 255.255.255.0255.255.255.0 places the host on network 192.168.1.0/24192.168.1.0/24.
The subnet mask 255.255.255.0255.255.255.0 defines the first 24 bits (three octets) as the network prefix.
2
Determine the network ID of the configured default gateway address.
A gateway address of 192.168.2.1192.168.2.1 with subnet mask 255.255.255.0255.255.255.0 places the gateway on network 192.168.2.0/24192.168.2.0/24.
For host-to-gateway Layer 2 frame resolution, the gateway must reside on the same IP subnet as the host.
3
Compare the host network ID with the gateway network ID to establish the root cause.
Network 192.168.1.0/24192.168.1.0/24 does not match 192.168.2.0/24192.168.2.0/24.
A host cannot resolve ARP requests or forward frames to a default gateway configured on a different subnet.

Anahtar Kavram

Default Gateway Subnet Misconfiguration
Soru 155Soru

A network technician is troubleshooting DNS resolution issues on a branch office workstation. The workstation is configured to use the local branch gateway router (192.168.10.1192.168.10.1) as its primary DNS server, which should forward requests for internal corporate resources to the core DNS server (10.100.1.510.100.1.5).

When attempting to resolve an internal hostname, the technician runs the following command-line queries from the workstation:

text
$ nslookup intranet.corp.local
Server: 192.168.10.1
Address: 192.168.10.1#53

** server can't find intranet.corp.local: SERVFAIL

$ nslookup intranet.corp.local 10.100.1.5
Server: 10.100.1.5
Address: 10.100.1.5#53

Name: intranet.corp.local
Address: 10.100.20.50

Based on the output, which TWO of the following are the most likely root causes for the initial resolution failure? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: The DNS forwarder configuration on the local router (192.168.10.1) is specified with an incorrect or unreachable upstream DNS server IP address.; An Access Control List (ACL) or firewall rule is blocking port 53 UDP/TCP traffic originating from the router's IP address to the core DNS server.

Cevap

The initial resolution failure is most likely caused by either an incorrect upstream DNS server IP address configured in the local router's DNS forwarder settings, or an Access Control List (ACL) / firewall rule blocking DNS port 53 traffic sourcing from the router's IP address to the core DNS server.
The output demonstrates that the workstation can directly query the core DNS server at 10.100.1.5 and receive an authoritative A record response. However, querying the local router at 192.168.10.1 yields a SERVFAIL error. This error occurs when a DNS server cannot fulfill a query due to an upstream failure. This indicates either that the router is attempting to forward requests to an incorrect/unreachable upstream IP address configured in its forwarding list, or that intermediate network security controls (ACLs/firewalls) are blocking port 53 traffic originating specifically from the router's IP address.

Adım Adım Çözüm

1
Analyze the first command output (`nslookup intranet.corp.local`).
The query sent to the local gateway (192.168.10.1192.168.10.1) returns a `SERVFAIL` error response.
`SERVFAIL` indicates that the DNS server received the request but encountered an internal failure (such as an inability to communicate with upstream recursive/authoritative servers) while attempting to process it.
2
Analyze the second command output (`nslookup intranet.corp.local 10.100.1.5`).
Direct query to the core DNS server (10.100.1.510.100.1.5) successfully resolves `intranet.corp.local` to IP address 10.100.20.5010.100.20.50.
This confirms that the host record exists, the core DNS server is operational, and the workstation itself has IP connectivity to port 53 on 10.100.1.510.100.1.5.
3
Deduce why querying the router fails while querying the core server directly succeeds.
Identify issues specific to the relay path between 192.168.10.1192.168.10.1 and 10.100.1.510.100.1.5.
Because the workstation can reach 10.100.1.510.100.1.5, any path failure must affect traffic originating from 192.168.10.1192.168.10.1 specifically (such as router-sourced ACL restrictions) or an internal misconfiguration on 192.168.10.1192.168.10.1 (such as an incorrect forwarder destination IP address).

Anahtar Kavram

DNS Forwarder and Relay Troubleshooting
Soru 156Soru

A network technician is troubleshooting a workstation that can ping other local hosts on the 192.168.10.0/24192.168.10.0/24 subnet but cannot access any remote servers on external networks. Running an IP configuration utility displays the following settings:

- IP Address: 192.168.10.45192.168.10.45
- Subnet Mask: 255.255.255.0255.255.255.0
- Default Gateway: 192.168.20.1192.168.20.1

Which of the following configuration issues is preventing the workstation from reaching external networks?

Cevabı ve açıklamayı göster

Cevap: The default gateway IP address is located on a different subnet than the workstation.

Cevap

The default gateway IP address is located on a different subnet than the workstation.
A host needs a default gateway configured on its own local IP subnet so it can resolve the gateway's MAC address via ARP and deliver off-subnet frames. Because the workstation resides in 192.168.10.0/24192.168.10.0/24 while the gateway address is configured as 192.168.20.1192.168.20.1, the host considers the gateway unreachable and cannot transmit packets to external destinations.

Adım Adım Çözüm

1
Analyze the host network configuration parameters.
Host IP address is 192.168.10.45192.168.10.45 with mask 255.255.255.0255.255.255.0 (/24), defining the local subnet as 192.168.10.0192.168.10.0 to 192.168.10.255192.168.10.255.
Determining the local subnet boundaries is necessary to evaluate local address validity.
2
Compare the default gateway IP address against the host subnet range.
The gateway 192.168.20.1192.168.20.1 belongs to the 192.168.20.0/24192.168.20.0/24 network, which is outside the host's local subnet.
For a host to forward non-local traffic, the default gateway's IP address must be directly reachable on the local Layer 2 segment.
3
Identify the root cause of the external unreachability.
The workstation cannot send ARP requests or Ethernet frames directly to a gateway that resides on a foreign subnet.
Mismatched gateway subnets prevent out-of-subnet routing.

Anahtar Kavram

Default Gateway Subnet Alignment
Soru 157Soru

A network technician is troubleshooting an issue where a newly deployed application server (10.40.20.50/2410.40.20.50/24) in VLAN 20 cannot connect to an off-site database cluster at 172.16.100.25/24172.16.100.25/24. Hosts in VLAN 20 can reach local resources and the internet, but cannot communicate with the 172.16.100.0/24172.16.100.0/24 network. Following the standard CompTIA network troubleshooting methodology, place the diagnostic and remediation steps in the correct sequential order from first to last.

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

Cevabı ve açıklamayı göster

Cevap

The correct sequential order for troubleshooting routing, gateway, and ACL issues is: 1) Verify local host configuration and gateway reachability (`item_1`), 2) Trace the path to locate the failure hop (`item_2`), 3) Check the router's routing table for destination routes (`item_3`), 4) Audit interface ACLs for filtering or implicit deny statements (`item_4`), and 5) Apply the configuration fix and verify end-to-end connectivity (`item_5`).
Following the structured CompTIA troubleshooting methodology, network diagnostics move logically from local host checks (ping default gateway), to path isolation (traceroute), to device routing tables (`show ip route`), to access control list inspection (`show ip access-lists`), and finally to implementing and verifying the solution.

Adım Adım Çözüm

1
Test local stack and default gateway connectivity.
Confirms Layer 1–3 network interface functionality and local subnet communication.
Always eliminate local client and gateway configuration issues prior to inspecting remote network infrastructure.
2
Run path isolation diagnostics (`traceroute`).
Identifies the exact hop where packets are dropped.
Isolates whether the failure occurs within the local network, at a core routing boundary, or across a WAN/VPN link.
3
Verify routing table contents on the target router.
Determines if the router possesses a valid exit interface or next-hop route for 172.16.100.0/24172.16.100.0/24.
A missing route causes the router to drop packets or send them to an incorrect default route.
4
Audit interface Access Control Lists (ACLs).
Reveals whether traffic is permitted or inadvertently dropped by rule sequence or implicit deny.
Even with a valid route, interface ACLs evaluate traffic before or after routing lookup and can block communication.
5
Modify the configuration and conduct final verification.
Restores full connectivity and documents resolution.
Testing service reachability after applying configuration changes confirms complete problem resolution.

Anahtar Kavram

Structured Network Troubleshooting Methodology for Routing and ACLs
Soru 158Soru

A network administrator is analyzing console log messages and packet captures between two Layer 2 switches, Switch-A and Switch-B, connected via an 802.1Q trunk on port GigabitEthernet0/1. Switch-A has GigabitEthernet0/1 configured with 'switchport trunk native vlan 10', whereas Switch-B has GigabitEthernet0/1 configured with 'switchport trunk native vlan 20'. Cisco Discovery Protocol (CDP) alerts report a %CDP-4-NATIVE_VLAN_MISMATCH error. Hosts on Switch-A in VLAN 10 report unexpected cross-talk and data leaks to hosts on Switch-B in VLAN 20, while tagged VLAN 30 traffic functions normally. Which of the following correctly explains the underlying root cause of this behavior and the required resolution?

Cevabı ve açıklamayı göster

Cevap: The native VLAN mismatch causes untagged frames sent from Switch-A (VLAN 10) to be received and ingested as untagged frames on Switch-B and assigned to its local native VLAN (VLAN 20); configuring matching native VLAN numbers on both trunk endpoints resolves the cross-VLAN leakage.

Cevap

The native VLAN mismatch causes untagged frames sent from Switch-A (VLAN 10) to be received and ingested as untagged frames on Switch-B and assigned to its local native VLAN (VLAN 20); configuring matching native VLAN numbers on both trunk endpoints resolves the cross-VLAN leakage.
In 802.1Q trunking, traffic belonging to the native VLAN is sent untagged across the link. When Switch-A sends VLAN 10 traffic untagged (due to native VLAN 10 configuration), Switch-B receives those untagged frames and implicitly assigns them to its own native VLAN (VLAN 20). This results in untagged broadcast domain leakage across VLAN boundaries. Matching the native VLAN settings across both switches resolves the issue.

Adım Adım Çözüm

1
Analyze the 802.1Q trunking protocol behavior for native VLAN traffic.
IEEE 802.1Q trunks transmit frames belonging to the designated native VLAN without an explicit 4-byte 802.1Q header tag.
Native VLAN frames are unencapsulated for backward compatibility with non-trunking devices.
2
Trace frame egress from Switch-A and ingress on Switch-B.
Switch-A transmits VLAN 10 traffic untagged because VLAN 10 is its native VLAN. Switch-B receives untagged frames on GigabitEthernet0/1 and maps all incoming untagged frames to its own native VLAN, which is VLAN 20.
Trunk interfaces do not carry native VLAN identification metadata inside untagged frame headers.
3
Determine the necessary administrative resolution.
Aligning the native VLAN configurations on both Switch-A and Switch-B (e.g., setting both to VLAN 10 or both to an unused VLAN like VLAN 99) eliminates the native VLAN mismatch log and prevents untagged traffic leakage.
Both switches must agree on the native VLAN ID on trunk links for symmetrical handling of untagged frame encapsulation.

Anahtar Kavram

Native VLAN Mismatch Behavior on IEEE 802.1Q Trunk Links
Soru 159Soru

A network administrator configures a workstation with IP address 172.20.30.45172.20.30.45 and subnet mask 255.255.255.192255.255.255.192. The workstation can successfully ping local hosts, but fails to reach any external subnets. Reviewing `ipconfig /all` reveals the following output:

IPv4 Address. . . . . . . . . . . : 172.20.30.45
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . : 172.20.30.65

Which of the following identifies the root cause of the connectivity failure?

Cevabı ve açıklamayı göster

Cevap: The default gateway IP address resides outside the workstation's local subnet range.

Cevap

The default gateway IP address resides outside the workstation's local subnet range.
The workstation IP address (172.20.30.45172.20.30.45) with subnet mask 255.255.255.192255.255.255.192 (/26) belongs to the subnet 172.20.30.0/26172.20.30.0/26, which spans addresses 172.20.30.0172.20.30.0 through 172.20.30.63172.20.30.63. The configured default gateway (172.20.30.65172.20.30.65) lies within the adjacent subnet 172.20.30.64/26172.20.30.64/26. Because a host's default gateway must reside on the same local subnet as the host interface, the host cannot send local ARP queries for the gateway, breaking all outbound non-local traffic.

Adım Adım Çözüm

1
Calculate the subnet boundaries for the workstation using the given CIDR mask
A subnet mask of 255.255.255.192255.255.255.192 corresponds to a /26/26 prefix, giving a block size of 256192=64256 - 192 = 64 addresses per subnet.
Subnet ranges increment by 64 in the fourth octet: Subnet 0 (172.20.30.0172.20.30.63172.20.30.0 - 172.20.30.63) and Subnet 1 (172.20.30.64172.20.30.127172.20.30.64 - 172.20.30.127).
2
Determine the host's subnet and valid host range
The host address 172.20.30.45172.20.30.45 falls into Subnet 0 (172.20.30.0/26172.20.30.0/26), where usable IPs are 172.20.30.1172.20.30.1 through 172.20.30.62172.20.30.62.
Devices must have a default gateway configured within their own local subnet boundary to enable ARP resolution for off-subnet forwarding.
3
Evaluate the configured default gateway address
The configured gateway IP is 172.20.30.65172.20.30.65, which falls into Subnet 1 (172.20.30.64/26172.20.30.64/26).
Because 172.20.30.65172.20.30.65 is on a different subnet, the host cannot ARP for its gateway address directly on the local link.

Anahtar Kavram

Default Gateway Subnet Alignment
Tahmini Süre:1m 30s
Soru 160Soru

A network technician is investigating a connectivity issue where a host with IP address 172.16.5.25/24172.16.5.25/24 cannot access services on a remote subnet 10.10.1.0/2410.10.1.0/24. Local ping tests confirm the host can communicate with other devices on 172.16.5.0/24172.16.5.0/24. Which of the following misconfigurations could cause this issue? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: The host is configured with a default gateway address (172.16.4.1172.16.4.1) that resides outside its assigned subnet; An Access Control List (ACL) applied to the egress router interface drops traffic due to an implicit deny rule

Cevap

The host is configured with a default gateway address outside its subnet (172.16.4.1172.16.4.1), and an Access Control List (ACL) drops the traffic due to an implicit deny rule.
For a host to reach remote networks, its default gateway must be on the local subnet (172.16.5.0/24172.16.5.0/24). A gateway address of 172.16.4.1172.16.4.1 prevents routing. Furthermore, network traffic passed to a router will be dropped if an applied ACL lacks a permit entry due to the default implicit deny clause.

Adım Adım Çözüm

1
Analyze local vs. remote connectivity symptoms
The host communicates locally on 172.16.5.0/24172.16.5.0/24, confirming Layer 1/2 functionality and local switchport settings, but fails to reach remote networks.
Traffic destined for off-link addresses (10.10.1.0/2410.10.1.0/24) must be sent to a valid local Layer 3 default gateway.
2
Evaluate default gateway IP configuration
An IP of 172.16.4.1172.16.4.1 is on a different subnet than 172.16.5.25/24172.16.5.25/24.
Hosts cannot resolve ARP for a default gateway that is not on their local IP subnet, preventing remote packet delivery.
3
Evaluate router ACL behavior
Traffic matching no explicit permit rule on a router interface is blocked.
Access Control Lists filtering traffic implement an implicit deny rule at the end of the list.

Anahtar Kavram

Troubleshooting Default Gateways and Router ACL Placement
ÖncekiSayfa 8 / 25Sonraki
Network Troubleshooting Alıştırma Soruları — CompTIA Network+ — Sayfa 8 | Examkin