Examkin

Network Troubleshooting

486 questions

All types486Multiple choice248Multiple select111Matching61Ordering66
Question 81Question →

A network technician is configuring a workstation with the IP address 192.168.1.45 and a subnet mask of 255.255.255.0. The technician manually sets the workstation's default gateway address to 192.168.2.1. The workstation can communicate with other hosts on the 192.168.1.0/24 subnet but cannot reach any internet destinations. Which of the following is the most likely cause of this issue?

Show answer & explanation

Answer: The default gateway address is configured on a different IP subnet than the workstation.

Answer

The default gateway address is configured on a different IP subnet than the workstation.
For a workstation to send traffic to external networks, its default gateway must be on the same local IP subnet. With an IP of 192.168.1.45/24, the gateway must be an address within 192.168.1.0/24 (such as 192.168.1.1). Configuring 192.168.2.1 makes the gateway unreachable at Layer 2.

Step-by-Step Solution

1
Determine the host subnet boundaries.
An IP of 192.168.1.45 with mask 255.255.255.0 (/24) belongs to the 192.168.1.0/24 subnet with usable host IPs from 192.168.1.1 through 192.168.1.254.
Host IP configuration determines which addresses are considered local (on-link).
2
Compare the default gateway IP to the host subnet.
The IP address 192.168.2.1 belongs to the 192.168.2.0/24 subnet.
To route off-subnet traffic, the host must be able to send Ethernet frames directly to the gateway's IP address on the local segment.
3
Identify the connectivity impact.
Because 192.168.2.1 is off-link, the workstation cannot send ARP requests directly to resolve the gateway's MAC address, preventing remote communication.
Default gateways must be local host neighbors on the same IP subnet.

Key Concept

Default Gateway Subnet Alignment
Estimated Time:45s
Question 82Question →

A network administrator is investigating four separate wireless connectivity issues across an enterprise site. Match each observed wireless symptom or telemetry anomaly to its primary root cause.

Click a left item, then click its matching right item

Items

High frame retransmissions occur when legacy 802.11b802.11\text{b} clients at the facility perimeter transmit simultaneously with newer 802.11n802.11\text{n} clients operating closer to the access point.
Signal strength drops significantly from −62 dBm-62\text{ dBm} to −84 dBm-84\text{ dBm} immediately after interior drywall partitions are replaced with reinforced cinder block walls.
Access points operating on 5 GHz5\text{ GHz} channel 100 near a coastal harbor experience periodic, sudden 60-second transmission silences and channel changes.
Clients experience high frame corruption and packet loss inside a metallic storage room despite maintaining a strong received signal strength indicator (RSSI) of −52 dBm-52\text{ dBm}.

Matches

Show answer & explanation

Answer

1 matches Hidden node problem; 2 matches RF Absorption; 3 matches Dynamic Frequency Selection (DFS) clearing event; 4 matches Multipath delay spread.
Each observed wireless symptom directly corresponds to a specific physical propagation phenomenon or protocol-level behavior: collisions between distant stations stem from the hidden node problem; signal loss through masonry walls is caused by RF absorption; radar detection on 5 GHz UNII-2 channels triggers DFS channel changes; and signal reflections in metal-heavy spaces create multipath delay spread.

Step-by-Step Solution

1
Analyze collision issues between legacy and modern clients at differing distances.
Identify that clients out of RF range of each other transmit simultaneously, causing frame corruption at the access point.
This behavior defines the hidden node problem, which can be mitigated using Request to Send / Clear to Send (RTS/CTS) mechanisms.
2
Assess the impact of structural changes on signal propagation metrics.
Determine that high-density masonry absorbs RF energy, sharply decreasing signal power (RSSI).
RF absorption by dense materials reduces signal intensity and coverage area.
3
Evaluate intermittent outages occurring specifically on 5 GHz UNII-2 channels near radar sources.
Recognize mandatory 60-second channel availability check silences associated with DFS radar detection.
802.11 standards require APs on DFS channels to yield priority to primary radar signals.
4
Diagnose high packet corruption occurring in highly reflective environments with high RSSI.
Identify multipath delay spread, where reflected signals cause inter-symbol interference.
Strong RSSI measures overall power but does not guarantee signal phase alignment or quality.

Key Concept

RF environmental propagation phenomena and 802.11 protocol troubleshooting
Question 83Question →

A network engineer is troubleshooting a 75-meter Category 6 (Cat6) unshielded twisted-pair (UTP) link connecting a core switch to a distribution switch. Under load, the interface experiences high frame corruption and periodic link dropping. A basic wiremapper confirms that all eight conductors are pinned correctly according to TIA/EIA-568B with continuous electrical connectivity and no open circuits or shorts. The engineer suspects a structural wire break or severe impedance anomaly located inside the building conduit between floors. Which diagnostic instrument must the engineer use to determine the exact distance along the cable run where the physical defect is located?

Show answer & explanation

Answer: A Time-Domain Reflectometer (TDR), because it sends electrical pulses along the conductors and calculates distance to anomalies based on signal reflection timing.

Answer

A Time-Domain Reflectometer (TDR), because it sends electrical pulses along the conductors and calculates distance to anomalies based on signal reflection timing.
The option specifying a Time-Domain Reflectometer (TDR) is correct because TDR instruments transmit high-frequency electrical pulses down copper conductors. When the pulse encounters an impedance change, break, or crushed section, part of the signal reflects back to the device. By measuring the elapsed time and reflection signature, the TDR calculates the precise distance to the fault along the cable run.

Step-by-Step Solution

1
Analyze physical layer troubleshooting requirements
Identified that simple end-to-end pinout continuity is confirmed, indicating the fault is an internal conductor anomaly along the length of the run.
Basic continuity wiremappers confirm pin mapping but cannot measure distance to impedance faults or internal physical damage.
2
Evaluate diagnostic tool capabilities for copper media
Determined that a Time-Domain Reflectometer (TDR) injects signal pulses and records reflections caused by impedance mismatches or breaks.
TDR technology converts signal reflection delay into precise linear distance along metallic conductors.
3
Select the correct instrument based on physical media and scenario
Selected the TDR instrument over toning tools, continuity testers, and optical meters.
TDR is specifically designed to locate hidden physical cable breaks and impedance anomalies in copper UTP runs.

Key Concept

Copper Cable Fault Diagnostics using Time-Domain Reflectometry (TDR)
Question 84Question →

A network engineer troubleshooting a loss of network redundancy on a core switch stack has confirmed that a mismatched VTP domain configuration was the root cause by successfully validating the hypothesis in a staging lab. Following the CompTIA troubleshooting methodology, the engineer is now advancing to the immediate NEXT phase before implementing any modifications on the production network. Which of the following actions should the engineer perform during this phase? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Outline a step-by-step implementation plan detailing the exact configuration commands needed to align the VTP domain settings.; Evaluate the risk of potential service disruption to downstream trunk links and identify necessary change control approvals.

Answer

The engineer must outline a step-by-step implementation plan detailing the configuration changes and evaluate the risk of potential service disruption while identifying change control approvals.
According to the CompTIA troubleshooting methodology, after testing a theory and confirming the root cause (Step 3), the technician must proceed to Step 4: 'Establish a plan of action to resolve the problem and identify potential effects'. Developing a clear step-by-step implementation plan and identifying potential risks or side effects on production traffic directly satisfy the requirements of Step 4.

Step-by-Step Solution

1
Identify the current phase completed in the CompTIA troubleshooting methodology.
The engineer confirmed the root cause in a lab, which completes Step 3: 'Test the theory to determine cause'.
Determining which phase was completed establishes where the technician is in the overall sequence.
2
Determine the immediate next sequential step in the methodology.
The next phase is Step 4: 'Establish a plan of action to resolve the problem and identify potential effects'.
CompTIA requires establishing a formal plan and assessing side effects prior to implementing any production changes.
3
Select the activities that correspond strictly to Step 4.
Formulating a step-by-step implementation plan and evaluating side effects / change control requirements belong to Step 4.
Implementation tasks, verification, and final documentation belong to subsequent steps in the methodology.

Key Concept

CompTIA 7-Step Troubleshooting Methodology Sequence
Question 85Question →

A network technician is troubleshooting a client workstation that cannot connect to a local server by hostname. To determine where the resolution process fails, arrange the name resolution mechanisms in the exact sequence the host operating system attempts them, from FIRST to LAST.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The host operating system resolves names sequentially by checking the local DNS resolver cache and HOSTS file first, sending a query to the primary DNS server second, querying the secondary DNS server third, and broadcasting an LLMNR or NetBIOS query on the local subnet last.
The correct order follows standard operating system host resolution behavior: inspecting local memory resources (DNS cache and HOSTS file) first, followed by configured unicast DNS servers (primary then secondary), and resorting to local subnet link-local resolution (LLMNR/NetBIOS) last.

Step-by-Step Solution

1
Check local memory and configuration files
The OS reads the local DNS cache and HOSTS file.
Local lookup is instant and prevents unnecessary network requests.
2
Contact the preferred unicast DNS server
A DNS request is sent over UDP/TCP port 53 to the primary DNS server.
Unicast DNS is the primary network name resolution service.
3
Contact the alternate unicast DNS server
The request is resent to the secondary DNS server after a timeout from the primary.
Secondary DNS servers provide redundant resolution capability.
4
Perform link-local multicast/broadcast resolution
The host broadcasts LLMNR or NetBIOS Name Service packets on the local subnet.
Link-local resolution serves as a final fallback for peer-to-peer name resolution on the local LAN segment.

Key Concept

Operating System Name Resolution Order
Question 86Question →

A network technician is troubleshooting poor wireless performance, excessive frame retransmissions, and intermittent connectivity dropouts across an office floor using three access points operating on the 2.4 GHz band. A site survey reveals that adjacent access points are currently assigned to Channel 1, Channel 3, and Channel 5. Which TWO actions should the technician take to resolve the radio frequency interference and stabilize the wireless network?

Select all that apply

Show answer & explanation

Answer: Reconfigure the access points to operate on non-overlapping channels 1, 6, and 11.; Adjust and reduce the transmission power levels on adjacent access points to limit cell coverage overlap.

Answer

The technician should reconfigure access point channel assignments to use non-overlapping channels (1, 6, and 11) and adjust transmission power levels to limit cell coverage overlap.
Reconfiguring the wireless access points to use channels 1, 6, and 11 eliminates adjacent-channel interference because these three channels have sufficient frequency separation. Decreasing transmission power resizes the coverage cells, minimizing co-channel interference and facilitating effective client roaming.

Step-by-Step Solution

1
Analyze current 2.4 GHz channel assignments.
Channels 1, 3, and 5 share overlapping frequencies, resulting in adjacent-channel interference.
Each 2.4 GHz channel is 20 MHz wide with center frequencies spaced only 5 MHz apart.
2
Reassign access point channels.
Using channels 1, 6, and 11 provides at least 25 MHz of separation between center frequencies.
Channels 1, 6, and 11 are the only standard non-overlapping 20 MHz channel combination in the 2.4 GHz band.
3
Tune access point transmission power.
Lowering transmit power reduces the coverage boundary of each AP cell.
Excessive cell overlap leads to co-channel interference and causes clients to remain connected to distant APs.

Key Concept

2.4 GHz Channel Overlap and RF Cell Tuning
Question 87Question →

A network technician receives reports that workstations on a local subnet are unable to access an internal intranet web server using its hostname `intranet.corp.local`, though connecting directly via IP address works properly. When executing `dig intranet.corp.local` from a workstation, the utility outputs `;; QUESTION SECTION: ;intranet.corp.local. IN A` followed by `;; AUTHORITY SECTION: corp.local. 3600 IN SOA ns1.corp.local. admin.corp.local. (...)` and zero answers in the `ANSWER SECTION`. Which of the following potential root causes and verification steps are valid for troubleshooting this issue? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: An A record for intranet.corp.local is missing or incorrectly named on the authoritative DNS server.; Using an authoritative lookup tool to query the primary name server directly will confirm whether the record exists on the zone file.

Answer

The valid root cause is that the requested host record is missing or misspelled in the authoritative zone file, and a valid troubleshooting step is to query the authoritative name server directly to confirm record presence.
Receiving an SOA record in the AUTHORITY section without records in the ANSWER section indicates that the DNS server is authoritative for the domain zone, but no A/AAAA entry exists for the queried hostname. Directly querying the primary DNS server specified in the SOA record allows an administrator to inspect the authoritative record status without cached interference.

Step-by-Step Solution

1
Analyze the provided `dig` output status and response sections.
The query succeeded without an error code like NXDOMAIN, but returned zero answer records while citing the zone SOA in the authority section.
This output pattern confirms the server is authoritative for `corp.local`, but no resource record exists for `intranet.corp.local`.
2
Evaluate potential host configuration and record causes.
Identified missing or misspelled A record in the zone configuration as the primary root cause.
When a domain zone exists but a specific record is missing, the server responds with NOERROR and an empty ANSWER section.
3
Select the proper verification methodology.
Directly querying the primary name server specified in the SOA record confirms if the zone file itself lacks the entry.
Targeting the authoritative server isolates zone misconfigurations from intermediate caching or forwarding anomalies.

Key Concept

DNS Lookup Output Interpretation & Record Verification
Question 88Question →

A network engineer is responding to reports of intermittent application session resets occurring across a hybrid cloud IPsec tunnel following a recent router firmware patch. Place the technician's troubleshooting procedures in the precise order required by the official CompTIA troubleshooting methodology, from the initial action to the final action.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential order of the troubleshooting process is: 1. Review logs, interview users, and duplicate the failure; 2. Formulate a hypothesis regarding DF bit enforcement and MTU mismatch; 3. Perform ping tests with the DF bit set to test the hypothesis; 4. Submit change management details, identify potential impacts, and apply MSS clamping; 5. Verify transaction stability under full system load and configure monitoring thresholds; 6. Log findings, parameters, and documentation in the ticketing system repository.
The correct sequence strictly adheres to the official CompTIA 6-step troubleshooting workflow: (1) Identify the problem by gathering symptoms and duplicating the issue; (2) Establish a theory of probable cause by analyzing header overhead and packet constraints; (3) Test the theory using DF bit ping sweeps; (4) Formulate a change management plan of action, evaluate side effects, and implement MSS clamping; (5) Verify full functionality under real workloads and apply preventive monitoring; (6) Document the root cause and configuration details in the enterprise repository.

Step-by-Step Solution

1
Identify the problem by interviewing users, reviewing error logs, and replicating the issue.
Establishes clear symptoms, baseline conditions, and scope of the failure.
CompTIA methodology strictly mandates gathering information and establishing symptoms before making assumptions or forming hypotheses.
2
Establish a theory of probable cause by evaluating physical, transport, and network layer parameters.
Develops a plausible hypothesis (MTU/DF bit mismatch across IPsec tunnel).
A theory must be established before conducting targeted diagnostic tests.
3
Test the theory using diagnostic utilities (ping with DF bit set).
Confirms or denies the root cause of the problem.
Testing validates the theory without prematurely implementing untested production modifications.
4
Establish a plan of action to resolve the issue, evaluate potential side effects, and implement the solution.
Applies the resolution (MSS clamping configuration) safely through change control procedures.
Remediation planning and impact analysis must precede implementation to prevent unintended outages.
5
Verify full system functionality and implement preventive measures.
Ensures the system operates correctly end-to-end and guards against future recurrence.
Confirmation of overall system health must occur before final sign-off and ticket closure.
6
Document findings, actions, and outcomes.
Updates organizational knowledge bases and incident history records.
Documentation provides reference material for future network incidents and completes the methodology.

Key Concept

CompTIA 6-Step Network Troubleshooting Methodology Sequential Flow
Question 89Question →

A network administrator is investigating reports that internal workstations are unable to connect to a web application at `payroll.internal.net`. To diagnose the issue, the administrator executes a hostname lookup using `nslookup` on a client machine, which returns the following output:

text
$ nslookup payroll.internal.net
Server: 10.1.1.5
Address: 10.1.1.5#53

Name: payroll.internal.net
Alias: app-server-04.internal.net

*** 10.1.1.5 can't find app-server-04.internal.net: Non-existent domain (NXDOMAIN)

Which of the following represents the primary root cause of this name resolution failure?

Show answer & explanation

Answer: The CNAME record for `payroll.internal.net` points to a canonical target (`app-server-04.internal.net`) that lacks a corresponding A or AAAA record in DNS.

Answer

The CNAME record for `payroll.internal.net` points to a canonical target (`app-server-04.internal.net`) that lacks a corresponding A or AAAA record in DNS.
A CNAME (Canonical Name) record acts as an alias pointing to another domain name rather than directly to an IP address. When a client requests `payroll.internal.net`, the DNS server resolves `payroll.internal.net` to `app-server-04.internal.net` and then attempts to resolve `app-server-04.internal.net` to an IP address. Because `app-server-04.internal.net` does not have a valid A/AAAA host record in the zone, the DNS server returns an NXDOMAIN error for the target, causing the entire resolution attempt to fail.

Step-by-Step Solution

1
Analyze the `nslookup` command output.
The lookup successfully resolved `payroll.internal.net` to its alias target `app-server-04.internal.net`.
This confirms that the CNAME entry for `payroll.internal.net` exists and is functional.
2
Examine the second stage of the DNS resolution chain.
The DNS server returned `Non-existent domain (NXDOMAIN)` when attempting to resolve `app-server-04.internal.net`.
Resolving a CNAME record requires a valid A (IPv4) or AAAA (IPv6) record for the destination canonical hostname. Without an A/AAAA record for `app-server-04.internal.net`, final IP address resolution cannot complete.
3
Identify the corrective action required to fix the issue.
Create an A record for `app-server-04.internal.net` mapping to the server's correct IP address.
Adding the missing host record will allow future CNAME chain resolution to complete successfully.

Key Concept

DNS CNAME Record Resolution and Chaining Dependencies
Estimated Time:2m 0s
Question 90Question →

Match each wireless network symptom described on the left with its primary physical or radio frequency (RF) root cause on the right.

Click a left item, then click its matching right item

Items

High frame retransmission rates and latency near metal warehouse racks despite strong RSSI measurements.
Intermittent 2.4 GHz Wi-Fi connection drops in an office area adjacent to a breakroom during lunch hours.
A sudden, drastic drop in signal strength (dBm) immediately after entering a room surrounded by reinforced concrete.
Severe throughput degradation on two nearby access points assigned to 2.4 GHz channels 2 and 3.

Matches

Show answer & explanation

Answer

High frame retransmissions near metal racks match RF reflection and multipath distortion. Intermittent drops near breakrooms match non-802.11 2.4 GHz interference. Signal drops behind reinforced concrete match RF attenuation. Performance drops on channels 2 and 3 match adjacent-channel interference.
Each symptom directly corresponds to a fundamental RF behavior: metal causes reflection and multipath delay spread; active microwave ovens create non-802.11 2.4 GHz interference; reinforced concrete causes high RF attenuation; and selecting channels 2 and 3 violates non-overlapping 2.4 GHz channel design (1, 6, 11), producing adjacent-channel interference.

Step-by-Step Solution

1
Analyze the metal warehouse rack scenario
Strong RSSI combined with high frame retransmissions indicates signal reflections bouncing off metal surfaces, causing multipath delay spread.
Metal is a known reflector of RF signals.
2
Analyze the breakroom Wi-Fi drops
Periodic disruption correlated with lunch hours points to microwave oven usage radiating noise in the 2.4 GHz band.
Microwaves operate in the 2.4 GHz ISM band and interfere with 802.11b/g/n signals.
3
Analyze the reinforced concrete scenario
Concrete absorbs RF energy, causing severe attenuation and lower dBm readings.
High-density physical barriers attenuate wireless signal strength.
4
Analyze the channel 2 and 3 configuration
Channels 2 and 3 overlap substantially with each other, generating destructive adjacent-channel interference.
Standard 2.4 GHz deployments require non-overlapping channels (1, 6, and 11) to avoid spectral overlap.

Key Concept

Identifying wireless RF degradation mechanisms and channel allocation rules.
Question 91Question →

A network technician is troubleshooting a workstation that lost connectivity to the local intranet. The technician established a hypothesis that a recently disabled network port was the cause and conducted tests that confirmed this theory. According to the CompTIA troubleshooting methodology, which of the following actions should the technician take NEXT?

Show answer & explanation

Answer: Establish a plan of action to resolve the problem and identify potential effects.

Answer

Establish a plan of action to resolve the problem and identify potential effects.
According to the CompTIA 7-step troubleshooting methodology, once a theory of probable cause has been tested and confirmed (Step 3), the technician must establish a plan of action to resolve the issue and identify any potential effects (Step 4) before implementing the fix.

Step-by-Step Solution

1
Determine the current phase in the CompTIA Troubleshooting Methodology.
The technician has completed Step 2 (Establish a theory) and Step 3 (Test the theory to determine cause).
The scenario states that testing confirmed the established theory.
2
Identify the immediate next step in the official 7-step sequence.
Step 4 is 'Establish a plan of action to resolve the problem and identify potential effects'.
After confirming the cause, the technician must plan the fix and consider any potential impacts before executing the resolution.

Key Concept

CompTIA Troubleshooting Methodology Order
Question 92Question →

A workstation on a corporate network cannot reach a web server located on a remote subnet. Arrange the following diagnostic steps in the correct logical sequence to systematically isolate whether the connectivity issue stems from local TCP/IP settings, the local default gateway, path routing, or router Access Control Lists (ACLs).

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with testing the local TCP/IP stack (127.0.0.1127.0.0.1), followed by pinging the default gateway, executing a traceroute to locate the failing hop, and finally inspecting the router table and ACL entries at the failure point.
Structured network troubleshooting progresses from inside to outside: verifying the local host TCP/IP stack first, testing the local default gateway second, running path tracing to pinpoint intermediate failure hops third, and examining router configuration state (routes and ACLs) at the point of failure last.

Step-by-Step Solution

1
Ping the loopback address (127.0.0.1127.0.0.1).
Confirms the host network driver and protocol stack are operational.
Eliminates local host software corruption before testing physical/network link reachability.
2
Ping the default gateway IP address.
Verifies local subnet connectivity and gateway IP configuration.
Determines whether the issue is restricted to the local broadcast domain or gateway reachability.
3
Run traceroute to the target destination address.
Identifies the exact gateway hop where path forwarding stops.
Isolates the network boundary between functional intermediate routers and the failing node.
4
Check routing tables and ACL rules on the failing hop router.
Reveals missing routes or filtering rules blocking destination traffic.
Provides the root cause configuration detail required to restore network traffic flow.

Key Concept

Standard Network Troubleshooting Flow for Gateway, Routing, and ACL Faults
Question 93Question →

A network engineer is diagnosing several distinct wireless performance and connectivity issues across a medical clinic. Match each observed diagnostic scenario on the left with its primary root cause on the right.

Click a left item, then click its matching right item

Items

A client device near a 2.4 GHz AP receives strong signal strength (−50 dBm-50 \text{ dBm}), but experiences an extremely low Signal-to-Noise Ratio (5 dB5 \text{ dB}) and severe packet retries near operating breakroom equipment.
Mobile tablet users experience brief dropouts and repeated re-authentication prompts when walking along a corridor between two access points operating on non-overlapping channels.
Clients connected to a 5 GHz wireless network on Channel 52 suddenly lose connectivity for up to one minute, after which the AP switches its broadcast to Channel 36.
A wireless laptop maintains a strong connection with high throughput in open hallway space, but experiences a drop of over 35 dBm35 \text{ dBm} immediately after moving into an adjacent lead-lined radiology room.

Matches

Show answer & explanation

Answer

1 matches non-802.11 RFI; 2 matches sub-optimal roaming/sticky client behavior; 3 matches DFS radar detection; 4 matches signal attenuation from building materials.
Each scenario maps to a fundamental RF behavior: non-Wi-Fi radiation increases the noise floor (RFI), client-driven AP switching delays cause roaming drops, regulatory radar compliance forces 5 GHz DFS channel shifts, and high-density lead shielding causes severe RF attenuation.

Step-by-Step Solution

1
Analyze Scenario 1 (High RSSI, low SNR near breakroom equipment)
Identified that non-802.11 devices like microwaves emit RF noise on 2.4 GHz, raising the noise floor and dropping SNR.
Low SNR with high RSSI points directly to environmental noise/RFI rather than distance or attenuation.
2
Analyze Scenario 2 (Dropouts during physical movement between APs)
Identified poor roaming transitions between AP cells.
When clients hang on to a weak AP (sticky client) or re-authenticate without fast roaming standards, voice/video connections drop.
3
Analyze Scenario 3 (Disconnect on 5 GHz Channel 52 followed by AP channel change)
Identified DFS radar detection behavior mandated for 5 GHz spectrum channels.
802.11 units sharing 5 GHz DFS channels must quiet radio transmissions and move to a non-DFS channel when radar is detected.
4
Analyze Scenario 4 (Severe signal drop behind lead-lined walls)
Identified physical absorption/attenuation of radio waves.
Dense materials such as lead, metal, or concrete absorb RF energy, dramatically reducing signal power.

Key Concept

Troubleshooting Wireless RF Issues: RFI, Roaming, DFS, and Attenuation
Question 94Question →

A user on a Windows workstation reports that navigating to `portal.corp.local` in a web browser leads to a 'Connection Refused' error. A network technician runs `nslookup portal.corp.local` and receives a successful authoritative response pointing to `192.168.10.45`. However, running `ipconfig /displaydns` on the client workstation reveals the following output:

text
Record Name . . . . . : portal.corp.local
Record Type . . . . . : 1
Time To Live . . . . : 86400
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 127.0.0.1

Which of the following is the root cause of the name resolution failure?

Show answer & explanation

Answer: A static entry in the client workstation's local HOSTS file is mapping the domain to the loopback address.

Answer

A static entry in the client workstation's local HOSTS file is mapping the domain to the loopback address.
Operating systems check local resolution mechanisms (such as the HOSTS file) prior to sending DNS requests across the network. Entries in the HOSTS file are cached locally with a TTL of 86400 seconds. Because `nslookup` bypasses local system resolution to directly query DNS servers, it received the valid IP address (`192.168.10.45`), whereas application traffic from the web browser utilized the local cache entry pointing to `127.0.0.1`.

Step-by-Step Solution

1
Analyze the result of the nslookup query
The DNS server resolves `portal.corp.local` to `192.168.10.45`.
Confirms that the host record on the DNS server is configured correctly.
2
Analyze the output of `ipconfig /displaydns`
The client resolver cache contains an A record mapping `portal.corp.local` to `127.0.0.1` with a TTL of 86400.
Identifies the exact IP address the workstation operating system uses for host resolution.
3
Evaluate operating system resolution order and source of entry
Entries defined in the local `HOSTS` file take precedence over DNS server queries and populate the resolver cache with a static 24-hour TTL (86400 seconds).
Explains why web browser connections fail while direct nslookup queries return the true server address.

Key Concept

Local HOSTS file precedence over DNS server queries and DNS cache behavior
Question 95Question →

A systems engineer is troubleshooting connectivity to a critical database server named `db1.internal.net`. Standard network utilities produce conflicting IP resolution results as shown below:

text
$ host db1.internal.net
db1.internal.net has address 192.168.1.50

$ dig @10.0.0.53 db1.internal.net +short
10.0.0.150

Which of the following is the most likely cause of this address discrepancy?

Show answer & explanation

Answer: A static entry in the local system HOSTS file is overriding standard DNS server resolution.

Answer

A static entry in the local system HOSTS file is overriding standard DNS server resolution.
In standard operating system TCP/IP stacks, local name resolution precedence checks local static files (such as `/etc/hosts` on Linux or `hosts` on Windows) before issuing queries to configured DNS servers. When standard lookup utilities yield a different result than an explicit, direct query to the authoritative DNS server, a static mapping in the local HOSTS file is overriding the network DNS response.

Step-by-Step Solution

1
Analyze the output of the default host command
The local system resolver returns IP address 192.168.1.50 when evaluating standard name requests.
The standard system resolver checks local cache and static configuration files before generating external network queries.
2
Analyze the output of the explicit dig command
Bypassing standard OS resolution and querying DNS server 10.0.0.53 directly returns IP address 10.0.0.150.
Explicit dig queries (@server) bypass OS resolution order and directly test the specified server's response.
3
Evaluate standard OS name resolution precedence order
Identify that local HOSTS file entries take precedence over DNS server queries.
Because the DNS server has the correct IP (10.0.0.150) but the system resolves to 192.168.1.50 locally, a local static mapping in `/etc/hosts` (or `C:\Windows\System32\drivers\etc\hosts`) is taking precedence.

Key Concept

Operating System Name Resolution Precedence (HOSTS file vs. DNS Server)
Question 96Question →

A network administrator receives complaints about intermittent Wi-Fi connectivity and poor throughput inside a newly renovated executive conference room surrounded by modern energy-efficient glass panels. An RF site survey indicates that 5 GHz signal strength drops sharply from -61 dBm just outside the room to -86 dBm inside the room. Which of the following is the most likely cause of this wireless signal degradation?

Show answer & explanation

Answer: Signal attenuation caused by metallic Low-E coatings on the glass panels

Answer

Signal attenuation caused by metallic Low-E coatings on the glass panels
Modern energy-efficient glass coated with Low-E (low-emissivity) metallic films severely absorbs and reflects radio frequency signals, causing significant RF signal attenuation when signals attempt to pass through the glass partition.

Step-by-Step Solution

1
Analyze the observed wireless symptom and measurements
The signal strength degrades significantly (a 25 dBm drop) specifically when moving across the glass barrier into the room.
Physical obstacles and building materials directly impact radio frequency propagation and receive signal metrics.
2
Evaluate the effect of energy-efficient glass on RF signals
Low-emissivity (Low-E) glass is treated with thin metallic oxide layers, which reflect and absorb RF signals similarly to solid metal barriers.
Metallic elements act as effective RF shields, leading to substantial signal attenuation.
3
Differentiate RF physical signal loss from network layer or configuration issues
Duplex mismatches, non-overlapping channel assignments, and APIPA IP address failures do not lower the physical RF signal level measured in dBm.
Only physical barriers, distance, or antenna issues alter measured received signal power.

Key Concept

RF Attenuation and Physical Obstacles in Wireless Networks
Estimated Time:1m 30s
Question 97Question →

An enterprise network engineer is investigating severe throughput degradation and excessive frame retransmissions on a newly installed 2.4 GHz wireless network servicing an open-plan office. A site survey reveals that three neighboring access points with overlapping coverage areas are configured as follows:

- Access Point North: Channel 1, 20 MHz channel width
- Access Point Center: Channel 3, 20 MHz channel width
- Access Point South: Channel 5, 20 MHz channel width

Which administrative action will most effectively eliminate the performance bottleneck caused by adjacent-channel interference?

Show answer & explanation

Answer: Reassign the access point channels to 1, 6, and 11 respectively.

Answer

Reassigning the access point operating channels to 1, 6, and 11 eliminates adjacent-channel interference by enforcing non-overlapping 20 MHz frequency spacing in the 2.4 GHz spectrum.
In 2.4 GHz Wi-Fi deployments, 20 MHz wide channels require 25 MHz of center-frequency separation to operate without overlapping. Channels 1, 6, and 11 are the standard non-overlapping channels. Reconfiguring adjacent access points from channels 1, 3, and 5 to channels 1, 6, and 11 removes adjacent-channel interference (ACI), preventing RF noise and high packet retransmission rates.

Step-by-Step Solution

1
Analyze the existing 2.4 GHz channel configuration.
Channels 1, 3, and 5 overlap directly with each other because standard 20 MHz 2.4 GHz channels require a 25 MHz separation (5 channel numbers apart) to avoid overlapping.
Channels 1, 3, and 5 cause partial spectrum overlap, leading to severe adjacent-channel interference (ACI) where radio receivers cannot effectively decode frames.
2
Identify standard non-overlapping channels for the 2.4 GHz Wi-Fi spectrum.
In the 2.4 GHz spectrum (802.11b/g/n), the three primary non-overlapping channels are 1, 6, and 11.
Using channels 1, 6, and 11 ensures complete frequency separation between neighboring access points.
3
Select the remediation action that enforces non-overlapping channel separation.
Reconfiguring the access points to channels 1, 6, and 11 eliminates ACI.
Eliminating ACI stops packet corruption at the physical layer, drastically reducing retransmission rates and restoring throughput.

Key Concept

2.4 GHz Non-Overlapping Channel Assignment & Adjacent-Channel Interference
Estimated Time:2m 0s
Question 98Question →

A network administrator is troubleshooting name resolution issues on a Linux workstation. The system successfully resolves typical small domain requests, but queries expecting large responses fail.

The administrator executes the following diagnostic commands from the workstation:

text dig TXT large-record.enterprise.internal ;; Truncated, retrying in TCP mode. ;; communications error to 10.20.4.53#53: timed out dig +notcp TXT large-record.enterprise.internal ;; ;; WARNING: recursion requested but not available ;; GOT ANSWER: ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: Messages truncated; TC bit is set.

Which of the following are the MOST likely causes of this name resolution failure? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: An intermediate firewall or network Access Control List (ACL) is dropping traffic on TCP port 53.; The requested DNS response payload exceeds the maximum UDP packet buffer size, forcing a fallback to TCP.

Answer

The primary causes are that the DNS response payload exceeds the UDP packet buffer limit (setting the TC bit) and an intermediate firewall or network ACL is blocking the required fallback connection over TCP port 53.
DNS relies on UDP port 53 for standard lightweight lookups. When a DNS response (such as a large TXT record set) exceeds the maximum allowed UDP payload size, the server returns a response with the Truncated (TC) header flag set. This signals the client to retry the request over TCP port 53. In this scenario, the UDP query succeeds and receives the TC flag, but the subsequent TCP connection times out because a firewall or network access control list is blocking TCP port 53.

Step-by-Step Solution

1
Analyze the output of the first `dig` command.
The message `Truncated, retrying in TCP mode.` indicates that the DNS server responded over UDP with the TC (Truncated) bit set because the response size exceeded the UDP payload capacity.
Standard DNS uses UDP port 53 for queries under 512 bytes (or EDNS limit). Larger responses require retrying via TCP.
2
Analyze the error message following the TCP fallback attempt.
The error `communications error to 10.20.4.53#53: timed out` indicates a layer 4 transport or access failure when attempting to establish a TCP connection on port 53.
Since UDP communication reached the server successfully, the host IP and general routing are functional; however, TCP port 53 traffic is being filtered by a security boundary.
3
Synthesize the root causes.
The combination of payload size exceeding UDP thresholds and blocked TCP port 53 traffic prevents the client from receiving the complete DNS record payload.
Both DNS protocol behavior (truncation) and network layer access rules (blocked TCP 53) directly account for the observed diagnostic output.

Key Concept

DNS Protocol Transport Modes (UDP vs TCP Port 53) and Truncation (TC Bit) Behavior
Question 99Question →

A network technician is troubleshooting severe packet loss and high Near-End Crosstalk (NEXT) error rates on a newly terminated Category 6 unshielded twisted-pair (UTP) cable run. A simple continuity wiremap tester indicates that all eight pins are correctly wired straight-through (pins 1 through 8 match on both ends). However, the link fails certification testing and suffers from extreme signal degradation under load. Which TWO of the following explain the likely cause of this issue or represent the correct troubleshooting steps? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The cable run contains split pairs, where pin continuity is maintained straight-through but wire pairs were matched incorrectly, breaking electromagnetic cancellation.; A cable certifier or Time-Domain Reflectometer (TDR) capable of RF frequency analysis must be used to pinpoint NEXT and impedance mismatches along the cable run.

Answer

The cable run suffers from split pairs (maintaining continuity while disrupting differential pair twisting), and a cable certifier/TDR analyzer must be deployed to locate and measure high-frequency Crosstalk (NEXT) and impedance anomalies.
Split pairs maintain pin-to-pin DC continuity on basic wiremap testers, but separate the intended twisted pairs across different circuits. This disrupts the differential cancellation of electromagnetic interference and causes severe Near-End Crosstalk (NEXT). Detecting split pairs and measuring NEXT requires a cable certifier or advanced Time-Domain Reflectometer (TDR).

Step-by-Step Solution

1
Analyze why a basic wiremap tester shows straight-through 1-to-1 pin alignment despite high Near-End Crosstalk (NEXT) errors.
Identify that split pairs fulfill DC continuity requirements on simple LED wiremap devices but split the twisted functional wire pairs, resulting in loss of noise cancellation.
Twisted pair cabling relies on balanced differential signaling over paired conductors to reject crosstalk.
2
Select the appropriate diagnostic tool for high-frequency signal and crosstalk analysis.
Choose a cable certifier or TDR with RF transmission testing capabilities.
Simple continuity testers and tone probes lack the electronics required to measure NEXT, return loss, or split pair phenomena.

Key Concept

Identifying split pairs and selecting advanced copper testing tools (cable certifiers/TDR) for crosstalk troubleshooting.
Question 100Question →

A technician is installing three wireless access points in a small office using the 2.4 GHz band. To prevent adjacent-channel interference between the access points, which combination of non-overlapping channels should the technician assign?

Show answer & explanation

Answer: Channels 1, 6, and 11

Answer

Channels 1, 6, and 11 should be assigned because they are the three standard non-overlapping channels in the 2.4 GHz spectrum.
Selecting channels 1, 6, and 11 ensures complete frequency separation among all three access points, eliminating adjacent-channel interference in the 2.4 GHz band.

Step-by-Step Solution

1
Identify the operating frequency band and channel width.
The network operates on the 2.4 GHz frequency band using 20 MHz wide channels.
2.4 GHz channel numbers are spaced 5 MHz apart, requiring 4 channel spacings (20 MHz) to prevent overlap.
2
Determine the non-overlapping channel set.
Channels 1, 6, and 11 have center frequencies of 2412 MHz, 2437 MHz, and 2462 MHz, keeping their spectra separate.
Assigning 1, 6, and 11 prevents adjacent-channel interference across three neighboring access points.

Key Concept

2.4 GHz Wireless Channel Planning and Non-Overlapping Channels
PreviousPage 5 / 25Next
Network Troubleshooting Practice Questions — CompTIA Network+ — Page 5 | Examkin