Network Troubleshooting

486 questions

All types486 Multiple choice248 Multiple select111 Matching61 Ordering66

A network technician is investigating a report that a client computer cannot access internal corporate resources using hostnames. Place the following troubleshooting steps in the correct logical sequence to systematically isolate and resolve the name resolution issue, from basic stack verification to cache remediation.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct logical sequence for troubleshooting DNS name resolution issues is: 1) Ping loopback address (127.0.0.1), 2) Run ipconfig /all to check DNS server configurations, 3) Ping primary DNS server IP, 4) Execute nslookup targeting hostname, 5) Run ipconfig /flushdns.

The standard network troubleshooting methodology progresses from local hardware/stack verification up to higher-level service queries and cache remediation. Verifying the loopback adapter establishes local TCP/IP operational status. Checking network configuration via `ipconfig /all` identifies target DNS server IP addresses. Pinging the DNS server tests Layer 3 reachability. Using `nslookup` isolates Application layer (DNS port 53) functionality. Finally, clearing the client resolver cache with `ipconfig /flushdns` resolves stale mapping issues on the workstation.

Step-by-Step Solution

Verify local TCP/IP stack operation.

Pinging

127.0.0.1

confirms local protocol stack integrity.

Eliminates local OS networking software corruption before evaluating network settings.

Inspect client network parameters.

`ipconfig /all` displays client IP settings and primary/secondary DNS server IP addresses.

Determines whether the client is configured with correct DNS server IP addresses.

Verify network path to the DNS server.

Pinging the DNS server IP verifies ICMP connectivity and default gateway routing.

Ensures physical link and routing to the DNS server are operational.

Test DNS application protocol.

`nslookup` directly queries the DNS server over port 53 to check if records are properly retrieved.

Isolates application-layer DNS server functionality from local OS caching behavior.

Remediate local resolution cache.

`ipconfig /flushdns` purges stale or incorrect records stored in the client cache.

Clears bad cached entries after confirming the authoritative DNS server holds correct records.

Key Concept

Systematic OSI Bottom-Up / Layered Network Troubleshooting for Name Resolution

Estimated Time:1m 30s

Question 62Question →

A network administrator is troubleshooting persistent wireless connectivity dropouts and high frame retransmission rates in a newly renovated office building. Diagnostic scans reveal that $5\text{ GHz}$ access points are operating on $80\text{ MHz}$ channel widths spanning Dynamic Frequency Selection (DFS) channels, while office partition walls contain foil-backed insulation and heavy metal mesh. Client devices experience sudden $25\text{ dBm}$ signal drops when stepping behind partitions, alongside temporary disconnections whenever access point logs record radar detection events. Which of the following root causes are contributing to these wireless performance issues? (Select TWO.)

Select all that apply

Severe signal attenuation and absorption caused by metallic building materials within office partitions

Service interruptions caused by mandatory channel changes when access points detect radar on DFS frequencies

Co-channel interference resulting from assigning overlapping 2.4 GHz channels 1, 2, and 3 across adjacent access points

Unassigned IP address states caused by clients falling back to APIPA self-assignment during roaming transitions

Show answer & explanation

Answer: Severe signal attenuation and absorption caused by metallic building materials within office partitions; Service interruptions caused by mandatory channel changes when access points detect radar on DFS frequencies

Answer

The primary root causes are severe RF signal attenuation caused by metallic wall materials and mandatory channel switches triggered by DFS radar detection events.

High-density metallic obstacles (foil insulation and metal mesh) heavily absorb and reflect high-frequency

5\text{ GHz}

signals, causing sharp drop-offs in signal strength. Simultaneously,

5\text{ GHz}

access points configured on Dynamic Frequency Selection (DFS) channels are legally mandated to clear the channel immediately upon detecting radar signals, causing temporary disconnections while the AP shifts to an alternate channel.

Step-by-Step Solution

Analyze physical obstacle impact on RF propagation

Identify that metal mesh and foil-backed insulation act as electromagnetic shields, causing dramatic signal attenuation (

25\text{ dBm}

drops) and coverage dead zones.

Dense metallic materials reflect and absorb RF energy at high frequencies such as

5\text{ GHz}

much more severely than standard drywall.

Analyze spectrum usage and log events

Correlate access point radar detection logs with client disconnections on DFS channels.

Regulatory requirements force 802.11 devices operating on DFS spectrum to immediately mute transmissions and switch channels upon detecting radar, causing temporary client dropouts.

Rule out non-applicable frequency and protocol misconfigurations

Confirm 2.4 GHz channel overlap and DHCP APIPA fallbacks do not match the

5\text{ GHz}

scenario and diagnostic logs.

The system operates on

5\text{ GHz}

DFS channels with established Layer 2/3 connections prior to physical attenuation or channel vacation.

Key Concept

Wireless Signal Attenuation & Dynamic Frequency Selection (DFS) Radar Clearing

Estimated Time:2m 0s

Question 63Question →

A network administrator is troubleshooting an issue where remote access VPN users cannot resolve names for specific corporate subdomains. Standard DNS queries for small records complete successfully, but queries that return large payload responses fail. The technician executes the following command on an affected client workstation:

$ nslookup -vc large-record.corp.internal 10.100.1.2
Server: dns1.corp.internal
Address: 10.100.1.2

DNS request timed out.
timeout was 2 seconds.
*** Request to dns1.corp.internal timed out

Which of the following is the most likely root cause of this failure?

An intermediate firewall along the VPN path is blocking TCP port 53 traffic required for truncated DNS responses.

The client workstation is configured to use UDP port 530 instead of standard UDP port 53 for name resolution.

The primary DNS zone is missing a PTR record for the internal server 10.100.1.2.

The local DNS resolver cache on the client has been corrupted by a stale CNAME record.

Show answer & explanation

Answer: An intermediate firewall along the VPN path is blocking TCP port 53 traffic required for truncated DNS responses.

Answer

An intermediate firewall along the VPN path is blocking TCP port 53 traffic required for truncated DNS responses.

DNS primarily operates over UDP port 53 for standard short queries. However, when a response payload exceeds the maximum UDP packet size, or when using command flags like `-vc` in `nslookup` (which forces Virtual Circuit / TCP mode), DNS relies on TCP port 53. If an intermediate firewall permits UDP port 53 but blocks TCP port 53, normal small queries succeed while large responses or forced TCP queries time out.

Step-by-Step Solution

Analyze the nslookup command syntax and flags.

The `-vc` flag explicitly forces nslookup to establish a Virtual Circuit connection using TCP instead of UDP.

Understanding tool flags isolates whether the failure is specific to TCP transport.

Evaluate the command output error message.

The output indicates `DNS request timed out`, meaning the client sent a TCP segment to 10.100.1.2:53 but received no response (SYN dropped or blocked).

Connection timeouts on specific protocol transports typically point to network filtering or firewall rules.

Correlate TCP behavior with large DNS responses.

DNS queries that exceed the UDP payload size limit set the Truncation (TC) flag, prompting clients to retry over TCP port 53.

If TCP port 53 is blocked by a network firewall, any large DNS response or forced TCP query (-vc) will fail with a timeout.

Key Concept

DNS Transport Protocols (UDP vs TCP Port 53)

Estimated Time:2m 0s

Question 64Question →

A desktop technician is troubleshooting a client system that cannot connect to an internal web application hosted at `payroll.internal`. The application server was recently migrated to a new IP address ( $10.0.5.90$ ), and the authoritative DNS zone was updated accordingly. However, when attempting to open the application on the client workstation, network traffic is still sent to the decommissioned IP address ( $10.0.5.12$ ). The technician executes `ipconfig /displaydns` on the client system and receives the following command output snippet:

Record Name . . . . . : payroll.internal
Record Type . . . . . : 1
Time To Live . . . . . : 86400
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 10.0.5.12

Which of the following identifies the root cause of this failure and the correct remediation action to take on the client workstation?

The client workstation is retaining a stale mapping in its local DNS resolver cache due to a high Time To Live value; running `ipconfig /flushdns` will clear the outdated entry.

The client resolver is failing because Record Type 1 is invalid for IPv4 hostname resolution; the server administrator must change the zone entry to an AAAA record.

The client system is unable to update its local cache because TCP port 53 is blocked by the host firewall; an inbound firewall exception must be created.

The `ipconfig /displaydns` command output indicates a server-side lookup failure; restarting the DNS Server service on the domain controller is required to refresh the subnet.

Show answer & explanation

Answer: The client workstation is retaining a stale mapping in its local DNS resolver cache due to a high Time To Live value; running `ipconfig /flushdns` will clear the outdated entry.

Answer

The client workstation holds an outdated mapping in its local DNS cache owing to a high Time To Live setting; executing `ipconfig /flushdns` on the client resolves the issue.

The correct answer correctly identifies that `ipconfig /displaydns` displays entries currently held in the client system's local resolver cache. Because the TTL (Time To Live) was configured for 86,400 seconds (24 hours), the client operating system reuses the cached IP address (

10.0.5.12

) instead of querying the DNS server for the newly updated record (

10.0.5.90

). Running `ipconfig /flushdns` clears this local cache and forces a new DNS lookup.

Step-by-Step Solution

Analyze the command output from `ipconfig /displaydns`.

The local DNS cache contains an A record (Record Type 1) mapping `payroll.internal` to

10.0.5.12

with

86,400

seconds remaining on its TTL.

When a host queries a domain name, the operating system checks its local resolver cache before querying external DNS servers. A cached entry prevents new network requests from hitting the server.

Compare the cached entry to the actual updated infrastructure state.

The server was updated on the DNS server to

10.0.5.90

, but the client is still using the cached

10.0.5.12

address.

Because the TTL was set high (

86,400

seconds or 24 hours), the client will not automatically query DNS until the cache entry expires.

Determine the appropriate command to invalidate the local cache.

Executing `ipconfig /flushdns` purges all entries in the Windows DNS resolver cache.

Flushing the cache forces the next application lookup to send a fresh request to the network's DNS server, obtaining the new IP address.

Key Concept

Local DNS Resolver Cache and TTL Behavior

Estimated Time:1m 30s

Question 65Question →

A network technician is resolving high packet retransmission rates caused by adjacent-channel interference on a 2.4 GHz wireless deployment. The current access points were incorrectly configured using overlapping frequencies. Which TWO of the following channels should the technician assign to ensure non-overlapping 2.4 GHz operation? (Select TWO.)

Select all that apply

Channel 1

Channel 6

Channel 2

Channel 4

Show answer & explanation

Answer: Channel 1; Channel 6

Answer

Channel 1 and Channel 6 are standard non-overlapping channels in the 2.4 GHz spectrum.

In 2.4 GHz Wi-Fi deployments, 20 MHz channels require a 25 MHz center-frequency separation to operate without interference. Channel 1 and Channel 6 (along with Channel 11) fulfill this requirement and provide clean, non-overlapping coverage.

Step-by-Step Solution

Identify the 2.4 GHz channel width and total available spectrum

Standard 802.11 2.4 GHz channels use a 20 MHz channel width with 5 MHz spacing between center frequencies.

Channels must be spaced at least 25 MHz apart between center frequencies to prevent spectral overlap.

Select the standard non-overlapping channel set

Channels 1, 6, and 11 do not share overlapping frequency ranges.

Choosing Channel 1 and Channel 6 eliminates adjacent-channel interference between neighboring access points.

Key Concept

2.4 GHz Non-Overlapping Channels

Estimated Time:45s

Question 66Question →

A network architect is diagnosing severe performance degradation, high frame retransmission rates, and intermittent disconnections in a newly renovated logistics warehouse. An RF spectrum analyzer and site survey reveal two primary findings: (1) several 2.4 GHz access points (APs) are statically assigned to channels 1, 3, 7, and 11, and (2) high-power directional antennas mounted near metal support beams are creating significant delay spread at ground level. Which of the following statements accurately identify an underlying RF issue or a correct remediation step for this scenario? (Select TWO.)

Select all that apply

The APs operating on channels 3 and 7 induce adjacent-channel interference (ACI), which should be mitigated by reconfiguring all 2.4 GHz radios to use only non-overlapping channels 1, 6, and 11.

The signal reflections off metallic beams cause multipath distortion, which can be mitigated by adjusting AP placement, selecting appropriate antenna patterns, or enabling antenna diversity.

Channel bonding adjacent 2.4 GHz channels 1 and 3 will eliminate frame retransmissions by doubling the channel bandwidth to

40\text{ MHz}

The observed packet loss and latency are indicative of a native VLAN mismatch on the trunk links connecting the APs to the switch infrastructure.

Show answer & explanation

Answer: The APs operating on channels 3 and 7 induce adjacent-channel interference (ACI), which should be mitigated by reconfiguring all 2.4 GHz radios to use only non-overlapping channels 1, 6, and 11.; The signal reflections off metallic beams cause multipath distortion, which can be mitigated by adjusting AP placement, selecting appropriate antenna patterns, or enabling antenna diversity.

Answer

The correct statements identify that assigning channels 3 and 7 causes adjacent-channel interference (which requires reassigning radios to non-overlapping channels 1, 6, and 11) and that reflection off metal beams causes multipath distortion (which requires adjusting placement, antenna patterns, or utilizing antenna diversity).

The option addressing channel configuration is correct because using channels 3 and 7 in 2.4 GHz Wi-Fi introduces adjacent-channel interference; using only non-overlapping channels 1, 6, and 11 resolves this. The option addressing metal reflection is correct because metal structures create multipath signals and delay spread, which are mitigated by adjusting AP antenna positioning, diversity, or radiation patterns.

Step-by-Step Solution

Analyze the 2.4 GHz channel assignment findings.

Channels 1, 3, 7, and 11 overlap in frequency space. Channels 3 and 7 overlap partially with channels 1, 6, and 11, creating destructive adjacent-channel interference (ACI).

In the 2.4 GHz ISM band, each 20 MHz channel spaced 5 MHz apart overlaps with adjacent channels unless restricted to channels 1, 6, and 11 in North America/standard deployments.

Analyze the RF propagation issue near metallic beams.

Metallic surfaces reflect RF signals, causing multiple out-of-phase copies of the signal to reach the receiver at varying time intervals (delay spread), leading to multipath distortion.

High delay spread degrades signal quality (SNR) and causes symbols to overlap, resulting in corrupt frames and retransmissions.

Evaluate mitigation techniques for both findings.

Reassigning APs to non-overlapping channels 1, 6, and 11 resolves ACI. Adjusting AP placement, utilizing MIMO/antenna diversity, or optimizing directional coverage resolves multipath distortion.

These physical-layer RF remedies directly resolve the root causes revealed by the spectrum analyzer and site survey.

Key Concept

Wireless RF Interference and Multipath Propagation Troubleshooting

Estimated Time:2m 0s

Question 67Question →

A network technician is troubleshooting a client workstation that cannot connect to an internal server named `appserver.corp.local`. When the technician checks the local client cache using `ipconfig /displaydns`, the following output is returned:

text Record Name . . . . . : appserver.corp.local Record Type . . . . . : 1 Time To Live . . . . : 480 Data Length . . . . . : 4 Section . . . . . . . : Answer A (Host) Record . . . : 10.0.1.50

The system administrator notes that `appserver.corp.local` was recently migrated to IP address `10.0.1.150`. Which TWO of the following solutions will address the stale resolution issue on this workstation? (Select TWO.)

Select all that apply

Run the `ipconfig /flushdns` command on the workstation to purge the local DNS resolver cache.

Reconfigure outbound port rules on the workstation to block TCP port 53 traffic.

Allow the record's Time to Live (TTL) timer to expire naturally before making subsequent connection requests.

Change the DNS record type on the client from an A record to a CNAME record.

Show answer & explanation

Answer: Run the `ipconfig /flushdns` command on the workstation to purge the local DNS resolver cache.; Allow the record's Time to Live (TTL) timer to expire naturally before making subsequent connection requests.

Answer

Running `ipconfig /flushdns` to immediately clear the local DNS resolver cache and allowing the Time to Live (TTL) period to expire naturally are the two valid methods to resolve the stale record issue.

When a host IP address changes on the server side, workstations that have recently resolved the old IP address store that mapping in their local DNS resolver cache until the TTL expires. Running `ipconfig /flushdns` forcibly purges the cache immediately so the next request queries the server for the new IP address (`10.0.1.150`). Alternatively, waiting for the remaining TTL timer to count down to zero will cause the client to purge the entry naturally.

Step-by-Step Solution

Analyze the `ipconfig /displaydns` output

The output reveals a cached A record mapping `appserver.corp.local` to an outdated IP address (`10.0.1.50`) with 480 seconds remaining on its TTL.

The client system relies on locally cached entries before querying upstream DNS servers.

Identify immediate cache remediation

Executing `ipconfig /flushdns` clears all cached host entries from memory immediately.

Clearing the cache forces the OS DNS resolver to send a new query to the DNS server, receiving the updated IP (`10.0.1.150`).

Identify passive cache remediation

Waiting out the 480-second TTL countdown automatically invalidates the stale record.

Once TTL reaches zero, the workstation discards the cached entry and queries the server for a fresh record.

Key Concept

DNS Client Cache and TTL Management

Question 68Question →

A network technician receives a service request reporting that a workstation in the accounting department cannot connect to the internal intranet server. The technician speaks with the affected user, reviews system logs, and successfully reproduces the connectivity failure. According to the CompTIA troubleshooting methodology, which of the following steps should the technician perform NEXT?

Establish a theory of probable cause.

Formulate a plan of action to resolve the connectivity issue.

Verify full system functionality by testing connection to the intranet server.

Document the findings, actions, and outcomes in the ticketing system.

Show answer & explanation

Answer: Establish a theory of probable cause.

Answer

Establish a theory of probable cause.

The technician has completed Step 1 (Identify the problem) by interviewing the user, analyzing logs, and duplicating the symptom. According to the CompTIA framework, the immediate next step is Step 2: Establish a theory of probable cause.

Step-by-Step Solution

Identify the current phase completed in the scenario.

The technician gathered information, reviewed system logs, and duplicated the issue, which completes Step 1 (Identify the problem).

Recognizing the completed step allows determination of the next sequential phase in the standard process.

Determine the next sequential phase in the CompTIA troubleshooting methodology.

Step 2 is to establish a theory of probable cause (questioning the obvious).

The CompTIA methodology follows a strict sequence: Identify problem -> Establish theory -> Test theory -> Plan of action/Implement -> Verify functionality -> Document.

Key Concept

CompTIA Troubleshooting Methodology Order

Question 69Question →

A network infrastructure team is addressing a critical issue where enterprise users experience session disconnections to cloud-hosted microservices whenever an SD-WAN edge appliance fails over to its secondary link. Place the following administrative actions in the correct sequence according to the official CompTIA troubleshooting methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence strictly adheres to the 6-step CompTIA methodology: 1. Identify the problem (gather telemetry and user feedback) -> 2. Establish a theory of probable cause (hypothesize asymmetric routing) -> 3. Test the theory to determine cause (replicate failover and analyze packet traces) -> 4. Establish a plan of action and implement the solution (design and execute BGP local preference changes) -> 5. Verify full system functionality and implement preventive measures (test user traffic and configure automated alerts) -> 6. Document findings, actions, and outcomes (update the IT service desk knowledge repository).

The standard CompTIA Network+ troubleshooting methodology follows a strict 6-step sequence: (1) Identify the problem through telemetry and user inquiry, (2) Establish a theory of probable cause, (3) Test the theory to confirm the cause, (4) Formulate a plan of action and implement the resolution, (5) Verify full system functionality and apply preventive measures, and (6) Document findings, outcomes, and lessons learned.

Step-by-Step Solution

Identify the problem

Information is gathered from logs and user reports to define the scope of the SD-WAN failover issue.

Troubleshooting must begin with gathering facts and defining symptoms before making assumptions.

Establish a theory of probable cause

A hypothesis regarding asymmetric routing and stateful firewall drops is formulated.

Developing a logical cause based on gathered symptoms focuses diagnostic testing.

Test the theory to determine the cause

Staging lab tests and packet captures confirm that asymmetric routing is the true root cause.

The theory must be confirmed empirically before modifying live network configurations.

Establish a plan of action to resolve the problem and implement the solution

A change management plan for BGP routing adjustments is created, assessed for potential impact, and executed.

System changes require impact identification and structured execution to prevent unintended downtime.

Verify full system functionality and implement preventive measures

End-to-end microservice connectivity is confirmed during failover, and proactive alerts are configured.

Ensures the fix completely resolved the issue without secondary failures and guards against recurrence.

Document findings, actions, outcomes, and lessons learned

Root cause and resolution steps are recorded in the service desk knowledge base.

Complete documentation provides historical references and aids future incident resolution.

Key Concept

CompTIA 6-Step Network Troubleshooting Methodology

Question 70Question →

A network architect is troubleshooting an issue where large database backups across a hybrid cloud IPsec tunnel intermittently drop during peak hours. The architect gathered system logs, verified that small control packets traverse the tunnel cleanly, and hypothesized that Path MTU Discovery (PMTUD) blackholing was occurring because ICMP Type 3 Code 4 (Fragmentation Needed) packets were being dropped by a perimeter security policy. In a staging environment, the architect configured an explicit ICMP inspection rule and successfully validated that $1500$ -byte test frames were correctly fragmented and transmitted without session drops, thereby confirming the root cause. According to the CompTIA Troubleshooting Methodology, which of the following actions should the architect take NEXT?

Establish a plan of action to deploy the ICMP policy change to production, including risk analysis and a rollback procedure.

Apply the modified ICMP firewall rules directly to the production gateway and test for packet drops during the next scheduled backup cycle.

Perform a full system verification by monitoring database synchronization metrics and backup job completion status across all remote cloud nodes.

Document the ICMP packet size mismatch findings, root cause analysis, and staging test results in the incident management database.

Show answer & explanation

Answer: Establish a plan of action to deploy the ICMP policy change to production, including risk analysis and a rollback procedure.

Answer

Establish a plan of action to deploy the ICMP policy change to production, including risk analysis and a rollback procedure.

The scenario describes a technician who has already identified the issue (Step 1), established a theory regarding ICMP blocking (Step 2), and successfully tested the theory in a staging environment to confirm the root cause (Step 3). According to the official CompTIA Troubleshooting Methodology, the next required step is Step 4: 'Establish a plan of action to resolve the problem and implement the solution.' This step includes assessing potential impacts, creating rollback strategies, and securing proper change management approval prior to deploying changes in production.

Step-by-Step Solution

Analyze the completed methodology steps in the scenario.

Identified that Step 1 (Identify the problem), Step 2 (Establish a theory of probable cause), and Step 3 (Test the theory to determine cause) have all been completed.

Testing the theory in a staging environment and confirming that the ICMP inspection rule resolved

1500

-byte frame drops signifies the completion of Step 3.

Determine the next sequential phase of the CompTIA 6-step troubleshooting methodology.

The immediate next step is Step 4: Establish a plan of action to resolve the problem and implement the solution.

Before making changes to production infrastructure, a structured plan of action considering potential side effects and rollback steps must be established.

Evaluate the response options against Step 4 requirements.

Drafting the deployment plan, performing risk analysis, and defining a rollback procedure aligns directly with Step 4.

Direct implementation without a plan skips necessary risk management, whereas verification and documentation occur later in the troubleshooting process.

Key Concept

CompTIA Troubleshooting Methodology Step Sequence

Question 71Question →

A network technician is investigating reports of intermittent connectivity and reduced throughput in a newly renovated conference room where decorative mirror panels were installed along the walls. Signal readings show a strong Received Signal Strength Indicator (RSSI) of $-55\text{ dBm}$ , but the Signal-to-Noise Ratio (SNR) is low and packet captures reveal a high frequency of corrupted 802.11 frames requiring retransmission. Which of the following wireless phenomena is most likely causing this signal degradation?

Multipath distortion resulting from RF signal reflection off metallic mirror backings

Adjacent-channel interference caused by assigning non-overlapping channels across access points

An automated failover to an APIPA address caused by DHCP scope exhaustion on the wireless VLAN

A Ethernet duplex mismatch occurring between the access point and its connected switch port

Show answer & explanation

Answer: Multipath distortion resulting from RF signal reflection off metallic mirror backings

Answer

Multipath distortion resulting from RF signal reflection off metallic mirror backings

The correct answer identifies multipath distortion caused by signal reflection off the metallic backing of the decorative mirrors. When radio waves bounce off reflective surfaces, multiple signals arrive at the receiving client out of phase, leading to signal cancellation, lower Signal-to-Noise Ratio (SNR), and high frame corruption despite high measured signal power (RSSI).

Step-by-Step Solution

Analyze the physical environment and symptoms

Decorative mirrors (which contain metallic backings) were added, and symptoms show strong RSSI but poor SNR and high frame retransmissions.

Metal surfaces act as RF reflectors, causing radio waves to bounce off obstacles and take multiple propagation paths to the receiver.

Evaluate the RF behavior

Reflected waves arrive at the receiver at slightly different times and phases, causing destructive phase cancellation.

This phenomenon, known as multipath interference or multipath distortion, corrupts incoming frames while maintaining high overall RF energy (RSSI).

Select the correct diagnosis

Multipath distortion caused by reflection from the metallic mirror backings is identified as the root cause.

Other options describe Layer 3 IP assignment issues, wired physical link errors, or incorrect channel configuration concepts.

Key Concept

RF Reflection and Multipath Distortion

Estimated Time:1m 15s

Question 72Question →

A network security analyst is troubleshooting an issue where a Linux workstation fails to resolve internal hostnames after a recent network migration, though IP-based routing functions normally. What is the correct logical sequence of diagnostic steps to systematically isolate and resolve this name resolution failure?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct logical sequence starts with inspecting `/etc/resolv.conf`, followed by directly querying the configured DNS server using `dig`, checking `/etc/hosts` for conflicting static entries, and finally flushing the local resolver cache.

Methodological troubleshooting progresses from checking local system configuration (`/etc/resolv.conf`), to testing DNS server transport responsiveness via direct utility queries (`dig`), checking local resolution overrides (`/etc/hosts`), and lastly purging stale system cache (`resolvectl flush-caches`).

Step-by-Step Solution

Inspect local resolver configuration files.

Verifies that the workstation is configured with valid DNS server IP addresses.

According to the CompTIA troubleshooting methodology, you must verify the basic client configuration settings before initiating complex network queries.

Query the configured DNS server explicitly using `dig @<dns_ip>`.

Tests whether DNS queries reach the resolver over port 53 and receive valid responses.

Direct lookup bypasses local OS resolution mechanisms to isolate whether the root cause lies within network transport or DNS server performance.

Examine the local static host table (`/etc/hosts`).

Identifies any hardcoded IP-to-hostname mappings that override DNS lookups.

Operating systems process `/etc/hosts` prior to querying external DNS servers. A legacy entry will prevent proper DNS name resolution.

Flush the local OS DNS resolver cache.

Removes cached NXDOMAIN or outdated responses.

Flushing clears lingering stale records so that subsequent application requests pull fresh, authoritative records from the DNS infrastructure.

Key Concept

OS Name Resolution Troubleshooting Sequence

Question 73Question →

A network administrator is investigating authentication failures on an enterprise SOHO branch network following a RADIUS server migration. The administrator gathered user symptoms, reviewed radius log files, established a hypothesis regarding a mismatched shared secret on the wireless access points, and successfully confirmed this cause by conducting a test authentication using the updated secret in a controlled lab segment. According to the CompTIA troubleshooting methodology, which step should the administrator take NEXT?

Develop a plan of action to update the shared secrets on production access points while identifying potential operational impacts.

Perform test authentications across all client devices to confirm that full wireless functionality is completely restored.

Log the root cause, change details, and resolution summary into the organization's centralized ticketing system.

Conduct user interviews and check recent network infrastructure change logs to gather additional problem symptoms.

Show answer & explanation

Answer: Develop a plan of action to update the shared secrets on production access points while identifying potential operational impacts.

Answer

The administrator should establish a plan of action to resolve the problem and identify potential effects prior to implementing the fix on production equipment.

According to the CompTIA troubleshooting methodology, the steps occur in the following order: (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 / implement solution, (5) Verify full system functionality and implement preventive measures, and (6) Document findings, actions, and outcomes. Because the administrator has just tested and confirmed the theory (Step 3), the immediate next step is Step 4: establishing a plan of action and identifying potential operational effects before implementation.

Step-by-Step Solution

Analyze current phase in CompTIA methodology

The technician has gathered symptoms (Step 1), formed a hypothesis (Step 2), and tested/confirmed the hypothesis in a lab (Step 3).

Determining the completed step is essential to identifying the required next step in the 6-step methodology.

Identify the next sequential step in the methodology

Step 4 is 'Establish a plan of action to resolve the problem and identify potential effects' followed by implementing the solution.

CompTIA requires planning changes and assessing potential risks/effects before applying changes to production networks.

Key Concept

CompTIA 6-Step Troubleshooting Methodology Sequence

Estimated Time:1m 30s

Question 74Question →

An IT technician is troubleshooting persistent performance degradation and high packet retransmission rates affecting legacy handheld inventory scanners in a logistics warehouse. The scanners operate exclusively on the $2.4\text{ GHz}$ band. A wireless spectrum analysis reveals severe co-channel and adjacent-channel interference across the facility, with channel utilization exceeding $85\%$ . Inspection of the wireless controller configuration shows that the $2.4\text{ GHz}$ radios on three neighboring Access Points (APs) are configured to use $40\text{ MHz}$ channel bonding set to primary Channel 3. Which of the following is the primary root cause of the wireless connectivity issues?

Configuring

40\text{ MHz}

channel bonding on the

2.4\text{ GHz}

band consumes 8 out of the 11 available channels, causing unavoidable adjacent-channel interference with almost all standard channel assignments.

The access points are triggering Dynamic Frequency Selection (DFS) radar events on Channel 3, forcing the

2.4\text{ GHz}

radios to drop connected client sessions.

The handheld inventory scanners are experiencing authentication dropouts because WPA3-Enterprise RADIUS authentication is incompatible with the

2.4\text{ GHz}

frequency spectrum.

The access points are failing to assign APIPA addresses to the inventory scanners due to a mismatch between the primary channel bandwidth and the DHCP scope range.

Show answer & explanation

Answer: Configuring $40\text{ MHz}$ channel bonding on the $2.4\text{ GHz}$ band consumes 8 out of the 11 available channels, causing unavoidable adjacent-channel interference with almost all standard channel assignments.

Answer

Configuring

40\text{ MHz}

channel bonding on the

2.4\text{ GHz}

band consumes 8 standard channels, creating unavoidable adjacent-channel interference across the limited

2.4\text{ GHz}

spectrum.

In the

2.4\text{ GHz}

Wi-Fi band, channels are spaced

5\text{ MHz}

apart, and a standard

20\text{ MHz}

channel requires

20\text{ MHz}

of separation to avoid overlapping adjacent channels (yielding non-overlapping channels 1, 6, and 11). Configuring a

40\text{ MHz}

channel width spans 8 adjacent channels simultaneously, overlapping with almost all available channels in the

2.4\text{ GHz}

spectrum and causing high frame corruption and retransmission rates due to adjacent-channel interference.

Step-by-Step Solution

Analyze the physical radio frequency parameters reported in the scenario.

The deployment uses

40\text{ MHz}

channel widths on the

2.4\text{ GHz}

band centered around Channel 3.

Understanding the channel layout of the

2.4\text{ GHz}

band is necessary to evaluate RF interference.

Calculate the spectral footprint of a

40\text{ MHz}

channel in the

2.4\text{ GHz}

band.

The

2.4\text{ GHz}

spectrum (Channels 1–11 in North America) has only

60\text{ MHz}

of total usable bandwidth for non-overlapping channels (

20\text{ MHz}

per channel for Channels 1, 6, and 11). A single

40\text{ MHz}

channel occupies 8 overlapping

5\text{ MHz}

channels (e.g., Channels 1 through 8).

Enabling

40\text{ MHz}

channels on

2.4\text{ GHz}

prevents the deployment of non-overlapping channels and causes severe adjacent-channel interference (ACI) with any nearby

20\text{ MHz}

40\text{ MHz}

APs.

Identify the recommended best practice for

2.4\text{ GHz}

channel width configuration.

Wi-Fi best practices dictate restricting

2.4\text{ GHz}

radios strictly to

20\text{ MHz}

channel widths using non-overlapping channels 1, 6, and 11.

Restricting channel width to

20\text{ MHz}

eliminates adjacent-channel overlap and allows CSMA/CA to properly manage co-channel medium sharing.

Key Concept

2.4 GHz Channel Width and Adjacent-Channel Interference (ACI)

Question 75Question →

A network administrator is diagnosing severe, localized wireless connection drops and high frame retransmission rates for mobile barcode scanners in a high-bay warehouse. Access points (APs) with omnidirectional antennas are mounted along the ceiling, operating at maximum transmit power ( $+20\text{ dBm}$ ). RF site measurements reveal strong signal strength (RSSI of $-55\text{ dBm}$ ), but the Signal-to-Noise Ratio (SNR) fluctuates wildly as scanners move between tall metallic storage racks, leading to phase cancellation when radio signals reflect off the metal surfaces and reach the receiver out of phase. Which RF phenomenon is primary responsible for this signal degradation, and what is the most effective remediation?

Multipath fading (delay spread); replace ceiling omnidirectional antennas with directional patch antennas directed down the aisles.

Adjacent-channel interference; reassign the 2.4 GHz AP radios to operate on contiguous channels 1, 2, 3, and 4 to maximize channel availability.

Free-space path loss (FSPL); increase the AP radio transmit power to

+30\text{ dBm}

to overcome environmental attenuation.

RF absorption; migrate all warehouse access points from the 5 GHz band to the 2.4 GHz band to leverage longer wavelength penetration.

Show answer & explanation

Answer: Multipath fading (delay spread); replace ceiling omnidirectional antennas with directional patch antennas directed down the aisles.

Answer

The primary cause of the issue is multipath fading (delay spread) resulting from RF reflections off metallic storage racks. The correct remediation is deploying directional patch antennas pointed down the warehouse aisles.

Multipath fading occurs when RF waves bounce off metal surfaces (like warehouse shelving), creating multiple signal paths that reach the receiver at slightly different times. When these signals recombine out of phase, destructive interference causes signal nulls and severe packet loss even though raw RSSI remains high. Replacing omnidirectional antennas with directional patch antennas directs signal beams straight down the storage aisles, reducing side-lobe reflections off metal racks.

Step-by-Step Solution

Analyze the reported symptoms and RF metrics

The client experiences high retransmissions and erratic SNR despite strong received signal strength indicator (RSSI of

-55\text{ dBm}

High RSSI combined with low/fluctuating SNR in an environment full of metallic obstacles indicates severe RF signal distortion rather than low signal amplitude.

Identify the underlying RF phenomenon

Reflections off metal racks create multiple propagation paths, causing out-of-phase wave recombination at the client receiver (multipath fading / delay spread).

When reflected signals arrive slightly delayed and out of phase with the direct line-of-sight signal, destructive interference occurs, cancelling out the carrier wave.

Select the appropriate antenna design and deployment change

Replacing omnidirectional ceiling antennas with focused directional patch antennas aligned down aisles concentrates the signal path and reduces reflective scatter.

Directional antennas constrain RF energy to intended corridors, minimizing bounce off surrounding metallic structures.

Key Concept

Multipath Fading and Directional Antenna Remediation in Industrial RF Environments

Question 76Question →

A technician is troubleshooting a wireless connectivity issue in a medical clinic. Staff members report that mobile tablets experience severe signal degradation and frequent disconnections whenever they are moved behind a thick reinforced concrete wall separating the exam rooms from the central wireless access point. Which radio frequency (RF) phenomenon is primarily causing this reduction in signal strength?

Attenuation

Channel overlap

APIPA auto-configuration

Default gateway mismatch

Show answer & explanation

Answer: Attenuation

Answer

Attenuation is the primary cause of signal degradation when radio waves travel through dense physical barriers like reinforced concrete.

Attenuation refers to the gradual loss of RF signal intensity as electromagnetic waves propagate through space and physical obstacles. Dense materials like concrete, brick, and metal absorb and reflect radio signals, drastically weakening signal strength on the far side of the barrier.

Step-by-Step Solution

Analyze the physical environment described in the scenario.

The signal loss occurs specifically when moving behind a solid physical obstacle (a thick reinforced concrete wall).

Dense building materials absorb radio frequency energy as signals pass through them.

Identify the RF phenomenon corresponding to signal loss through obstacles.

Attenuation describes the reduction in signal power/strength over distance or through obstructing media.

Concrete and rebar significantly decrease the amplitude of Wi-Fi signals.

Key Concept

RF Attenuation and Physical Obstructions

Estimated Time:45s

Question 77Question →

A network technician needs to troubleshoot a reported network outage by following standard industry methodology. Place the given CompTIA troubleshooting methodology steps in the correct sequential order from first step to last step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential order is: 1) Identify the problem, 2) Establish a theory of probable cause, 3) Test the theory to determine cause, 4) Establish a plan of action and implement the solution, and 5) Verify full system functionality and implement preventive measures.

The official CompTIA 6-step 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 implement the solution, 5. Verify full system functionality and implement preventive measures, and 6. Document findings, actions, and outcomes.

Step-by-Step Solution

Begin with problem identification

Information, symptom reports, and recent changes are gathered.

You must understand what is failing before forming hypotheses.

Formulate a probable cause theory

A prioritized hypothesis of the failure point is established.

Hypothesizing narrows down the operational scope before testing.

Test the theory

The root cause is verified (or disproved, triggering a new theory).

Changes should not be implemented without confirming the cause.

Plan and execute the solution

A plan of action is established and the fix is deployed.

Structured execution minimizes unwanted side effects during remediation.

Verify functionality and prevent recurrence

System operation is validated and preventive controls are applied.

Verification ensures the problem is fully resolved and won't immediately reoccur.

Key Concept

CompTIA Troubleshooting Methodology Order

Question 78Question →

A network systems engineer is troubleshooting a workstation that is repeatedly failing to access an internal web application hosted at `app.enterprise.internal`. Other hosts on the same subnet can resolve the service correctly. Arrange the following diagnostic and remediation steps in the correct order according to standard operating system name resolution behavior and systematic troubleshooting methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows client-side resolution order followed by targeted network diagnostics: 1. Verify adapter IP and DNS server assignments (`ipconfig /all`). 2. Inspect the local `hosts` file. 3. Check the local DNS resolver cache (`ipconfig /displaydns`). 4. Flush the local DNS cache (`ipconfig /flushdns`). 5. Issue a direct interactive network lookup via `nslookup` specifying the server IP address.

Operating systems process host name resolution in a strict sequence: local hostname check, static HOSTS file evaluation, local DNS cache lookup, and finally outbound DNS queries to configured servers. Logical troubleshooting isolates client configuration first (ipconfig /all), local file overrides second (HOSTS file), local memory cache third (displaydns), cache remediation fourth (flushdns), and direct server probing last (nslookup).

Step-by-Step Solution

Verify basic IP and DNS server settings on the local adapter.

Confirms the host is using valid network configuration settings and designated DNS server IPs.

Before inspecting resolution cache or files, basic IP connectivity parameters must be confirmed.

Inspect the local HOSTS file.

Identifies any static overrides taking priority over network DNS.

Standard client operating systems parse local HOSTS file entries prior to evaluating local DNS memory caches or sending wire requests.

Query the local DNS cache using `ipconfig /displaydns`.

Exposes existing cached records and negative cache entries.

The client resolver cache is evaluated next in the name resolution order prior to generating a network frame.

Purge the local DNS resolver cache using `ipconfig /flushdns`.

Removes cached entries and resets local memory.

Clearing the local cache prevents old TTLs or negative cache records from obstructing new name resolution attempts.

Query the remote DNS server directly using `nslookup`.

Tests network transport on port 53 and verifies server authoritative zone data.

Direct lookup bypasses local client mechanisms to isolate whether the root cause resides on the network or upstream DNS server.

Key Concept

Standard Operating System Name Resolution Hierarchy and Systematic DNS Troubleshooting Workflow

Question 79Question →

A network engineer is analyzing several persistent Wi-Fi connectivity and performance issues across a enterprise campus. Match each observed diagnostic scenario and measurement to its primary underlying RF anomaly or configuration root cause.

Click a left item, then click its matching right item

Show answer & explanation

Answer

1. Dynamic Frequency Selection (DFS) radar detection matches the periodic 5 GHz channel 52 radio shutoffs. 2. Non-802.11 RFI matches the high RSSI but low SNR/high retransmission scenario near industrial equipment. 3. Adjacent-Channel Interference (ACI) matches channel 3 overlapping channel 1. 4. Multipath propagation delay spread matches high RSSI with signal reflection corruption in the steel/glass atrium.

Each scenario maps directly to its characteristic RF phenomenon: DFS radar quiet periods cause periodic channel 52 outages; non-802.11 RF energy elevates noise floor and degrades SNR despite high RSSI; non-standard 2.4 GHz channel allocations (channel 3) generate ACI against channel 1; and reflective architectural elements create multipath delay spread leading to inter-symbol interference.

Step-by-Step Solution

Analyze the 5 GHz periodic outage scenario

Identify DFS requirement on UNII-2/UNII-2 Extended channels (channels 52-144)

Federal regulations require APs to clear the channel upon detecting radar signals, taking the 5 GHz radio offline during the CAC scan period.

Evaluate high RSSI combined with high retransmission rates near non-Wi-Fi equipment

Identify Non-802.11 RFI as the noise floor inflator

RSSI measures total energy (signal + noise). Non-Wi-Fi RF sources increase noise, reducing SNR without providing decodable Wi-Fi frames.

Assess the 2.4 GHz channel 3 deployment impact on channel 1

Identify Adjacent-Channel Interference (ACI)

Channels 2 through 5 overlap partially with channel 1. Partially overlapping channels cause uncoordinated transmission collisions and frame corruption.

Examine the reflective atrium environment with high RSSI but corrupt frames

Identify Multipath delay spread / Inter-symbol interference

Multiple reflected waves arriving at slightly different times cause phase cancellation and symbol distortion even when total received energy is strong.

Key Concept

Advanced Wireless RF Troubleshooting and Interference Mechanisms

Estimated Time:3m 0s

Question 80Question →

A administrator executes a command-line test on a workstation to verify name resolution for an internal web server named `portal.local`. The command output is shown below:

C:\> nslookup portal.local
Server: dns1.contoso.com
Address: 10.0.0.10

*** dns1.contoso.com can't find portal.local: Non-existent domain

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

The DNS server is missing an active host (A) record for portal.local.

The workstation resolver cache is corrupted and returning stale data.

An outbound firewall is blocking TCP port 53 traffic to the server.

The hostname requires a Mail Exchanger (MX) record for standard name resolution.

Show answer & explanation

Answer: The DNS server is missing an active host (A) record for portal.local.

Answer

The DNS server is missing an active host (A) record for portal.local.

The output explicitly shows a successful query transaction with the DNS server at 10.0.0.10, which replied with 'Non-existent domain' (NXDOMAIN). This confirms that network communication with the DNS server is working, but the server has no host (A) record registered for portal.local.

Step-by-Step Solution

Analyze the nslookup command output

The target DNS server at 10.0.0.10 answered the query directly with 'Non-existent domain' (NXDOMAIN).

An explicit NXDOMAIN response indicates that network connectivity and DNS service availability are functional.

Determine the cause of the NXDOMAIN response

The DNS zone database on the server does not contain a valid mapping for portal.local.

Standard hostname resolution requires a host (A or AAAA) record entry in the DNS server database.

Key Concept

Interpreting DNS Lookup Output and NXDOMAIN Error Response

PreviousPage 4 / 25Next

Network Troubleshooting

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept