All practice questions

2237 questions

Question 1481Question

A network technician needs to trace an unlabeled copper UTP cable run from a wall jack in a user's office to its corresponding port on a patch panel in the telecommunications closet. Which of the following diagnostic tools is best suited for this task?

Show answer & explanation

Answer: Tone generator and probe kit

Answer

The tone generator and probe kit is the correct tool for tracing an unlabeled cable run from an office wall jack to a patch panel port.
A tone generator and probe kit (commonly referred to as a toner probe) is specifically designed to trace copper cabling. The generator attaches to one end of the cable run to emit an electrical signal, and the technician uses the inductive probe near the patch panel to hear where the signal is strongest, pinpointing the correct termination.

Step-by-Step Solution

1
Identify the diagnostic objective
The task requires locating the specific physical termination of an intact copper cable run across two rooms.
The technician needs to identify which patch panel port corresponds to a specific wall outlet without disconnecting unrelated cables.
2
Select the appropriate diagnostic hardware tool
Choose a tone generator and probe kit.
The tone generator injects a high-frequency audio signal into the cable at the wall jack, and the inductive probe generates an audible tone when placed near the target wire at the patch panel.

Key Concept

Cable Tracing and Identification Tools
Question 1482Question

A network technician is troubleshooting a switch-to-switch trunk link that is dropping traffic. Reviewing the switch console logs reveals a native VLAN mismatch error, while interface statistics report high numbers of late collisions. Which TWO configuration actions should the technician take to resolve these issues? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Reconfigure both ends of the trunk link to use the same native VLAN ID.; Configure matching duplex settings (or enable auto-negotiation on both ends) for the trunk interfaces.

Answer

The technician should configure identical native VLAN IDs on both switch trunk ports and ensure matching duplex settings across the link.
To resolve native VLAN mismatch errors, both ends of the 802.1Q trunk must be configured with the exact same native VLAN ID so untagged frames are correctly directed. To resolve late collisions, both switch ports must agree on duplex settings (either both forced to full-duplex or both using auto-negotiation), eliminating collision detection conflicts.

Step-by-Step Solution

1
Identify the causes of the reported trunk errors from the symptoms.
The log message indicates an 802.1Q native VLAN mismatch, while late collisions point to a duplex mismatch.
Late collisions occur when one side operates in full-duplex while the other operates in half-duplex, while native VLAN mismatch occurs when trunk endpoints use different untagged VLAN IDs.
2
Select the correct remediation for native VLAN mismatch.
Aligning the native VLAN ID on both switch trunk interfaces resolves frame leakage and drops.
802.1Q trunking requires both ends of a trunk to agree on which VLAN carries untagged traffic.
3
Select the correct remediation for duplex mismatch.
Configuring matching duplex settings (or auto-negotiation on both sides) restores clean frame transmission.
Matching duplex settings ensures both ports transmit and listen according to the same collision rules.

Key Concept

Troubleshooting 802.1Q native VLAN mismatches and interface duplex mismatches on switch trunks.
Question 1483Question

A network administrator is troubleshooting host reachability issues on an enterprise dual-stack network. Workstations cannot connect to an internal server using its hostname `app.internal.example.com`, though direct IPv6 ping tests succeed. The administrator executes the following troubleshooting command from a client system:

C:\> nslookup app.internal.example.com
Server: dns01.internal.example.com
Address: 10.0.0.53

*** dns01.internal.example.com can't find app.internal.example.com: Non-existent domain

Next, the administrator runs `nslookup -type=AAAA app.internal.example.com`, which successfully returns the IPv6 address `2001:db8:85a3::8a2e:370:7334`.

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

Show answer & explanation

Answer: The DNS server lacks an IPv4 address (A) record for the target host, and the default query requested an A record.

Answer

The DNS server lacks an IPv4 address (A) record for the target host, and the default query requested an A record.
The initial nslookup command without specified parameters queries for IPv4 address (A) records by default. Because the DNS server only contains an IPv6 address (AAAA) record for app.internal.example.com, the initial lookup fails with a 'Non-existent domain' or record missing error. Explicitly setting -type=AAAA successfully retrieves the IPv6 mapping.

Step-by-Step Solution

1
Analyze the default nslookup output.
The tool queries the primary DNS server (10.0.0.53) for app.internal.example.com without explicit parameters, defaulting to an IPv4 host (A) record request.
Standard DNS resolution tools query for A records unless specified otherwise.
2
Compare the default command with the explicit -type=AAAA query.
The explicit query returns the IPv6 address 2001:db8:85a3::8a2e:370:7334.
This confirms that a valid AAAA record exists in DNS, but no A record has been created for IPv4.
3
Determine the root cause.
The failure occurs because the DNS zone lacks an A record while the client default lookup relies on A record resolution.
Creating an A record (or ensuring dual-stack applications query AAAA records) resolves the name resolution issue.

Key Concept

DNS Record Types and Default Command-Line Query Behavior
Question 1484Question

A network technician needs to isolate administrative access for core switches situated in an unstaffed facility. The security policy dictates that remote administrative management traffic must be completely separated from user data traffic so that compromised production host networks cannot reach the switch management interfaces. Which of the following strategies best fulfills this security requirement?

Show answer & explanation

Answer: Configure switch management interfaces within a dedicated Virtual Routing and Forwarding (VRF) instance and restrict management protocols to that isolated network.

Answer

Configure switch management interfaces within a dedicated Virtual Routing and Forwarding (VRF) instance and restrict management protocols to that isolated network.
Out-of-band (OOB) management using a dedicated management VRF or physical management interface ensures management traffic remains completely segregated from production data paths. This prevents hosts on production subnets from reaching or probing management interfaces.

Step-by-Step Solution

1
Analyze the security requirement
Identified the core requirement: total isolation of management traffic (out-of-band) from user data traffic.
Preventing production host networks from reaching administrative interfaces mitigates unauthorized management plane access.
2
Evaluate network device hardening best practices
Implementing Out-of-Band (OOB) management via a dedicated physical management port or isolated VRF provides complete separation between administrative plane traffic and data plane traffic.
Traffic in a dedicated management VRF cannot be routed or accessed from the global production routing table.

Key Concept

Out-of-band management plane isolation
Estimated Time:1m 30s
Question 1485Question

A server located at a remote branch office experiences a severe kernel panic, causing its host operating system to crash completely and lose network connectivity. An engineer needs to remotely inspect the server's POST output, modify BIOS/UEFI settings, and reinstall the operating system without traveling to the site. Which solution provides the hardware-level console and display access required to perform these tasks?

Show answer & explanation

Answer: An IP-KVM switch attached to the server's video output and USB ports

Answer

An IP-KVM switch attached to the server's video output and USB ports provides out-of-band, hardware-level access to the BIOS/UEFI and POST sequence independent of the operating system.
An IP-KVM (Keyboard, Video, Mouse over IP) device connects directly to the motherboard or graphics output and USB ports of the physical server. It operates independently of the target server's operating system and internal network stack, providing remote administrators with unconstrained access to the pre-boot environment, BIOS/UEFI configurations, and low-level recovery consoles.

Step-by-Step Solution

1
Analyze the management access requirements
The target system has suffered an operating system crash, meaning in-band network services and OS-dependent daemons are offline.
Remote BIOS/UEFI access and POST inspection require an out-of-band mechanism operating at the hardware layer below the operating system.
2
Evaluate candidate remote management technologies
IP-KVM captures raw display output directly from the graphics card and redirects USB keyboard/mouse control over an independent network link.
Because IP-KVM hardware functions independently of host software, it allows full low-level administration even during OS kernel panics.

Key Concept

IP-KVM Hardware Out-of-Band Management
Estimated Time:1m 15s
Question 1486Question

Match each remote management tool or protocol to the operational scenario where it serves as the primary solution.

Click a left item, then click its matching right item

Items

Serial Console Server
In-Band SSH
Switched PDU
IP-KVM

Matches

Show answer & explanation

Answer

Serial Console Server connects to RS-232 ports for access during WAN outages; In-Band SSH provides encrypted CLI management over an operational IP network; Switched PDU enables remote hard reboots of unresponsive power supplies; IP-KVM delivers hardware-level keyboard/video/mouse control for pre-OS/BIOS configuration.
Out-of-band management techniques (Serial Console Servers, IP-KVMs, and Switched PDUs) bypass primary network interfaces and host OS states to provide low-level access or power control, whereas in-band protocols (SSH) manage operational systems over standard IP network connections.

Step-by-Step Solution

1
Differentiate between in-band and out-of-band management methods
In-band methods (SSH) rely on standard data network connectivity; out-of-band methods (Console server, Switched PDU, IP-KVM) function independently of host OS or primary IP network availability.
Choosing the correct tool requires analyzing whether the host network stack or operating system is functional.
2
Map physical control requirements to out-of-band management capabilities
Power cycling requires power outlet switching (Switched PDU); GUI/BIOS interaction requires video signal redirection (IP-KVM); direct router serial access requires asynchronous console aggregation (Serial Console Server).
Each out-of-band hardware component interfaces with a different physical plane of the target device.

Key Concept

Distinguishing between in-band protocols and specialized out-of-band management hardware mechanisms based on target system state and failure mode.
Estimated Time:1m 30s
Question 1487Question

A network security analyst is updating incident classification guidelines for enterprise threat vectors. Match each network attack type on the left with its corresponding attack vector characteristics on the right.

Click a left item, then click its matching right item

Items

Switch Spoofing
Bluesnarfing
DNS Tunneling
IP Address Spoofing

Matches

Show answer & explanation

Answer

Switch Spoofing matches DTP frame forgery for trunk negotiation; Bluesnarfing matches unauthorized Bluetooth data extraction; DNS Tunneling matches encoding non-DNS payloads in port 53 queries; IP Address Spoofing matches modifying source IP headers to bypass access controls.
Each attack type matches its exact vector description: Switch Spoofing exploits DTP negotiation to force trunking; Bluesnarfing extracts confidential data over Bluetooth; DNS Tunneling encapsulates covert data within standard port 53 queries; and IP Address Spoofing alters source IP header fields to bypass filters.

Step-by-Step Solution

1
Analyze Switch Spoofing mechanisms
Identify that switch spoofing exploits automatic switch port negotiation using DTP frames to create unauthorized VLAN trunks.
Understanding layer 2 dynamic trunk negotiation identifies the DTP forgery vector.
2
Differentiate Bluetooth attack categories
Distinguish Bluesnarfing (data theft/extraction) from Bluejacking (sending unsolicited messages).
Bluesnarfing specifically targets the exfiltration of personal data like contacts and text messages.
3
Examine covert tunnel characteristics
Recognize that DNS Tunneling utilizes port 53 lookup packets to encapsulate non-DNS protocol data for data exfiltration.
Firewalls often allow outbound DNS unconditionally, making it a primary covert channel vector.
4
Evaluate packet header alteration attacks
Associate IP Address Spoofing with forged source IP addresses in packet headers.
Spoofing IP addresses allows attackers to evade simple address-based filtering or misattribute traffic.

Key Concept

Common Network Attack Types and Vectors
Question 1488Question

A network engineer is configuring an extended Access Control List (ACL) on a stateless router interface. Client workstations on the internal subnet (10.200.15.0/2410.200.15.0/24) can successfully transmit outgoing HTTPS requests (TCPTCP port 443443) to external web servers, but return web traffic is blocked by the inbound ACL. Which of the following configuration adjustments will allow internal clients to receive return HTTPS traffic from external servers while maintaining stateless security controls? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Add an inbound ACL rule permitting TCP traffic originating from source port 443 directed to the internal subnet 10.200.15.0/2410.200.15.0/24 on destination ephemeral ports (10241024-6553565535).; Include the established keyword on the inbound TCP permit rule for port 443 to match packets with the ACK or RST flags set.

Answer

To allow return HTTPS traffic through a stateless router ACL, the configuration must explicitly permit inbound TCP traffic originating from source port 443 destined for internal ephemeral client ports (10241024-6553565535), and utilize the established keyword to restrict permitted packets to established TCP sessions (packets with ACK/RST flags set).
Because stateless firewalls and ACLs do not automatically dynamically track TCP connection states, return traffic from external servers is dropped by default. To permit return HTTPS packets, an explicit inbound ACL rule must be created that matches TCP source port 443 heading to client ephemeral destination ports. Adding the established keyword guarantees that only return packets belonging to established sessions (ACK/RST flags set) are allowed, preventing unsolicited inbound SYN packets.

Step-by-Step Solution

1
Analyze the stateless filtering limitation
Stateless ACLs evaluate each packet individually without maintaining a session table, meaning return packets for outbound requests are blocked unless an explicit inbound rule exists.
Outbound client traffic uses random high-numbered ephemeral ports as source ports and port 443 as the destination port; return traffic reverses these roles.
2
Formulate the inbound transport layer rule
Define an inbound rule matching TCP traffic from remote source port 443 to destination subnet 10.200.15.0/2410.200.15.0/24 on destination ephemeral ports (10241024-6553565535).
This explicitly opens the return path for HTTPS web server replies to client browsers.
3
Apply connection flag safety controls
Append the `established` keyword to the inbound TCP permit rule.
This restricts the rule to match packets with ACK or RST control bits set, preventing external actors from initiating new inbound TCP SYN connections on those ports.

Key Concept

Stateless ACL Return Traffic Handling and Established TCP Filtering
Estimated Time:1m 30s
Question 1489Question

A network technician needs to inspect a newly terminated Category 6 UTP patch cable to confirm proper T568B pinout alignment and verify that there are no open or shorted conductor pairs. Which TWO of the following diagnostic tools are designed to verify conductor continuity and pinout arrangement on copper twisted-pair cables?

Select all that apply

Show answer & explanation

Answer: Wiremapper; Cable certifier

Answer

Wiremapper and Cable certifier
Both a wiremapper and a cable certifier test individual copper conductors in a twisted-pair Ethernet cable for pin alignment, shorts, opens, and reversed pairs.

Step-by-Step Solution

1
Identify the cabling test requirement.
The requirement is to verify pinout mapping (T568B) and check for electrical continuity issues (opens/shorts) on Category 6 UTP copper cable.
Pinout arrangement and conductor continuity are Layer 1 electrical properties of twisted-pair copper media.
2
Evaluate diagnostic tools designed for copper pinout and continuity verification.
Wiremappers test pin-to-pin electrical connections across twisted pairs. Cable certifiers also execute wiremap tests as part of their comprehensive standard verification.
Both tools connect to both ends of a copper cable run to analyze pinout configuration.
3
Rule out non-applicable tools.
Optical power meters test fiber optics rather than copper conductors, while tone probes trace cable paths without analyzing individual pin connections.
Selecting media-appropriate diagnostic equipment prevents incorrect diagnosis of cabling faults.

Key Concept

Diagnostic tool selection for copper cabling continuity and pinout verification
Question 1490Question

A network administrator installs a new set of IP phones on a dedicated voice VLAN (VLAN 40). The enterprise DHCP server resides on VLAN 10. The phones fail to obtain IP addresses and automatically configure APIPA addresses instead. Which TWO of the following resolution actions or diagnostic steps should the technician perform to troubleshoot and resolve this issue? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Configure an IP helper address (DHCP relay agent) pointing to the DHCP server IP on the VLAN 40 router interface.; Verify that intermediate firewalls and access control lists (ACLs) permit UDP ports 67 and 68 traffic between VLAN 40 and VLAN 10.

Answer

The technician should configure an IP helper address (DHCP relay agent) on the VLAN 40 gateway interface and verify that intermediate ACLs permit traffic on UDP ports 67 and 68.
DHCP client requests rely on Layer 2 broadcasts that default gateway routers do not forward. Configuring an IP helper address (DHCP relay) on the interface facing the client subnet enables the router to encapsulate DISCOVER broadcasts into unicast packets directed to the central DHCP server. Additionally, verifying that security controls permit traffic on UDP ports 67 and 68 ensures that relayed DHCP traffic passes through intermediate interfaces without being dropped.

Step-by-Step Solution

1
Identify the cause of cross-subnet DHCP request drops
Recognize that client DHCP DISCOVER messages are Layer 2 broadcasts that routers drop by default.
Devices on remote VLANs require a DHCP relay agent (IP helper) on their default gateway to forward broadcast requests as unicast traffic to a central DHCP server.
2
Verify transport protocol accessibility between subnets
Check that firewalls or router ACLs permit traffic on UDP ports 67 and 68.
Even with a relay agent active, restrictive security rules blocking UDP ports 67/68 will prevent relayed unicast DHCP messages from reaching the server or returning to the client.

Key Concept

Troubleshooting Cross-Subnet DHCP Relay and Port Accessibility
Question 1491Question

A network engineer is troubleshooting a newly deployed 10GBASE-LR single-mode optical fiber link between two distribution switches spaced 2 kilometers apart. An optical power meter registers an excessive loss of 14 dB14\text{ dB} across the link, significantly exceeding the maximum insertion loss budget of 2.5 dB2.5\text{ dB}, despite both transceiver end-face connectors passing visual inspection with a fiber microscope. Which diagnostic tool should the engineer utilize to measure reflections and pinpoint the precise location and cause of the attenuation fault along the fiber run?

Show answer & explanation

Answer: Optical Time-Domain Reflectometer (OTDR)

Answer

The Optical Time-Domain Reflectometer (OTDR) is the correct tool because it analyzes Rayleigh backscattering and Fresnel reflections over distance to pinpoint specific attenuation faults.
The Optical Time-Domain Reflectometer (OTDR) is designed specifically to trace optical fiber cables by sending light pulses down the fiber and analyzing backscattered light. It produces a graph displaying loss against distance, allowing engineers to identify the exact distance to high-attenuation events such as macrobends, splices, or physical breaks.

Step-by-Step Solution

1
Evaluate the symptom and requirements
The optical fiber link experiences excessive signal loss (14 dB14\text{ dB}) somewhere along a 2 km span, but connectors are clean.
End-to-end power testing confirmed an issue exists, but does not provide distance or location details.
2
Assess diagnostic tool capabilities for fiber optics
An OTDR transmits pulsed light signals down the fiber strand and records the amplitude and timing of reflected light signals.
This signature trace identifies event locations (e.g., sharp bends, bad splices, or physical stress) relative to distance from the transmitter.
3
Select the correct physical layer diagnostic tool
Select the Optical Time-Domain Reflectometer (OTDR).
It is the only instrument capable of pinpointing fault distances along an extended optical cable pathway.

Key Concept

Pinpointing Fiber Optic Cable Faults with OTDR
Estimated Time:2m 0s
Question 1492Question

Match each command-line network utility on the left with its primary diagnostic function on the right.

Click a left item, then click its matching right item

Items

ping
tracert
nslookup
netstat

Matches

Show answer & explanation

Answer

ping matches reachability verification; tracert matches hop-by-hop path tracing; nslookup matches DNS query testing; netstat matches active connections and listening ports inspection.
Each utility targets a distinct diagnostic domain: ping tests basic ICMP reachability; tracert maps route paths and hop latencies; nslookup queries DNS infrastructure; and netstat inspects active protocol connections and listening ports on the local machine.

Step-by-Step Solution

1
Identify the basic reachability tool
ping sends ICMP requests to check if a remote host is reachable.
ping is the primary tool for testing Layer 3 ICMP echo response.
2
Identify the route tracing tool
tracert identifies intermediate router hops and latency along a path.
tracert increments TTL values to discover each router along the path to a destination.
3
Identify the name resolution diagnostic tool
nslookup queries DNS servers directly.
nslookup evaluates DNS record lookups and name resolution issues.
4
Identify the protocol and session statistics tool
netstat lists active connections and open ports on the local endpoint.
netstat provides socket-level information for active TCP/UDP sessions.

Key Concept

Command-Line Network Troubleshooting Utilities
Estimated Time:45s
Question 1493Question

A network engineer is troubleshooting reachability issues for a newly provisioned monitoring server located in an enterprise branch office. The server is assigned the static IP address 10.64.36.19510.64.36.195 with a subnet mask of 255.255.255.192255.255.255.192 (/26/26). The default gateway configured on the server interface is 10.64.36.12910.64.36.129. The server can successfully ping its own IP address, but all attempts to reach the default gateway or remote networks fail with a destination host unreachable error. Which of the following identifies the root cause of this connectivity failure?

Show answer & explanation

Answer: The host IP address and the default gateway reside on different IP subnets due to an incorrect subnet mask configuration.

Answer

The host IP address and the default gateway reside on different IP subnets due to an incorrect subnet mask configuration.
Under a 255.255.255.192 (/26) subnet mask, subnets increment by 64 in the fourth octet. The subnet containing host address 10.64.36.195 spans 10.64.36.192 to 10.64.36.255 (usable host range 10.64.36.193–10.64.36.254). The configured default gateway IP 10.64.36.129 falls into the previous subnet block spanning 10.64.36.128 to 10.64.36.191 (usable host range 10.64.36.129–10.64.36.190). Because a device's default gateway must reside on the same IP subnet as the host itself, local gateway reachability fails.

Step-by-Step Solution

1
Analyze the subnet boundaries for the given host configuration.
A subnet mask of 255.255.255.192255.255.255.192 corresponds to a /26/26 prefix, dividing an octet into blocks of 6464 addresses (256192=64256 - 192 = 64).
Determining block size is essential to find the network ID and usable range.
2
Determine the subnet block containing host IP 10.64.36.19510.64.36.195.
The block boundaries in the 4th octet are 0,64,128,1920, 64, 128, 192. Therefore, 10.64.36.19510.64.36.195 belongs to the subnet 10.64.36.192/2610.64.36.192/26. The usable host range for this subnet is 10.64.36.19310.64.36.193 to 10.64.36.25410.64.36.254, with broadcast address 10.64.36.25510.64.36.255.
Validates the network placement of the host.
3
Determine the subnet block containing gateway IP 10.64.36.12910.64.36.129.
The gateway address 10.64.36.12910.64.36.129 falls into the preceding block 10.64.36.128/2610.64.36.128/26 (usable range 10.64.36.12910.64.36.129 to 10.64.36.19010.64.36.190).
Validates the network placement of the default gateway.
4
Evaluate local subnet reachability.
Because the host and default gateway reside on different subnets under the /26/26 mask, the host cannot directly communicate with its default gateway without a routing boundary, causing unreachability to outside networks.
A host default gateway must reside on the same local Layer 3 broadcast domain as the host interface.

Key Concept

Default Gateway Subnet Boundary and Subnet Mask Alignment
Estimated Time:2m 0s
Question 1494Question

A systems engineer is troubleshooting an issue where corporate users cannot authenticate to an enterprise wireless network. The engineer established a theory that an expired SSL/TLS certificate on the RADIUS server was causing EAP-TLS handshake failures and confirmed this theory by analyzing RADIUS authentication failure logs. Which of the following actions should the engineer perform NEXT in accordance with the CompTIA troubleshooting methodology? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Develop a plan of action to renew and install the updated SSL/TLS certificate while identifying potential service impact.; Implement the planned solution by applying the new RADIUS server certificate during an authorized maintenance window.

Answer

The engineer should establish a plan of action to renew the certificate while identifying potential effects, and implement the solution during an approved maintenance window.
Once a theory of probable cause has been confirmed (Step 3), the CompTIA troubleshooting methodology requires moving to Step 4: 'Establish a plan of action to resolve the problem and identify potential effects' and 'Implement the solution or escalate as necessary'. Developing the certificate renewal plan while evaluating service impact and deploying the updated certificate during a maintenance window correctly fulfill this phase.

Step-by-Step Solution

1
Identify the completed phase of the CompTIA troubleshooting methodology from the scenario context.
The engineer completed Step 3 (Test the theory to determine the cause) by verifying the RADIUS authentication logs.
Identifying the current step establishes the baseline required to determine the next immediate action.
2
Determine the next sequential phase mandated by the CompTIA methodology.
Step 4 requires establishing a plan of action to resolve the issue and identifying potential effects, followed by implementing the solution.
CompTIA standards dictate that theory verification must be followed by action planning, impact assessment, and implementation before verification.
3
Select the options matching the Step 4 requirements.
Developing the renewal plan with impact assessment and applying the certificate update are the correct Step 4 actions.
System functionality testing (Step 5) and documenting findings (Step 6) occur later in the troubleshooting lifecycle.

Key Concept

CompTIA Troubleshooting Methodology Step Sequence
Estimated Time:1m 30s
Question 1495Question

Match each wireless network troubleshooting scenario or signal anomaly to its primary underlying cause.

Click a left item, then click its matching right item

Items

A client experiences high packet retries near operating microwave ovens while signal strength (RSSI) remains high.
A 2.4 GHz wireless deployment using 40 MHz channel bonding suffers from severe throughput degradation in an office.
Wireless signal strength drops significantly when users enter a newly renovated room bounded by Low-E glass partitions.
A laptop remains connected to an AP located far down the hallway with poor performance instead of roaming to a nearby AP in the room.

Matches

Show answer & explanation

Answer

Each wireless symptom corresponds to a distinct physical layer or configuration problem: non-Wi-Fi appliances generate non-802.11 noise; 40 MHz bonding on 2.4 GHz depletes non-overlapping channels; metallic Low-E glass causes RF attenuation; and excessive AP transmit power results in sticky client behavior.
Matching each symptom to its core physical or structural cause allows proper diagnostic isolation: microwave emissions elevate background noise without lowering signal levels; 40 MHz bonding on 2.4 GHz violates non-overlapping channel design; metallic glass causes physical attenuation; and over-amplified AP beacon power prevents client disassociation.

Step-by-Step Solution

1
Analyze the impact of non-Wi-Fi electronic emissions on the 2.4 GHz spectrum.
Identify that devices like microwave ovens emit non-802.11 RF noise.
Unregulated electromagnetic radiation elevates the noise floor, decreasing the Signal-to-Noise Ratio (SNR) despite high RSSI.
2
Evaluate channel width boundaries within the 2.4 GHz band.
Recognize that 40 MHz channel bonding overlaps the limited non-overlapping channels (1, 6, 11).
Bonding channels in a constrained frequency spectrum forces neighboring radios onto overlapping frequencies.
3
Assess physical signal loss caused by specialized architectural materials.
Determine that metallic coatings on Low-E glass induce RF attenuation.
Conductive metallic particles reflect and absorb RF signals as they pass through structural barriers.
4
Examine wireless client roaming behavior and cell coverage boundaries.
Associate excessive AP transmit power with sticky client persistence.
Clients evaluate downlink beacon strength to decide when to roam; high AP power prevents disassociation even when uplink frames fail.

Key Concept

Troubleshooting wireless signal degradation by identifying root causes such as non-802.11 noise, channel overlap, physical material attenuation, and roaming cell misconfigurations.
Question 1496Question

A network technician suspects that a workstation's local DNS resolver is returning cached, out-of-date IP addresses for an internal server. The technician needs to test name resolution by sending a DNS query directly to a specific authoritative name server rather than relying on the local resolver configuration. Which command-line utility should the technician use to perform this direct query?

Show answer & explanation

Answer: nslookup

Answer

The correct utility is nslookup, which allows targeted DNS server queries and record inspection.
The nslookup command (along with dig) is designed specifically to test and troubleshoot DNS infrastructure. It allows technicians to query specific name servers by IP address or hostname, view specific record types (A, AAAA, MX, CNAME), and bypass local DNS client cache settings.

Step-by-Step Solution

1
Identify the diagnostic requirement
The requirement is to send a direct DNS query to a specific target DNS server to test domain name resolution without using local cached results.
Testing specific DNS server responses requires a command-line tool dedicated to name resolution lookup.
2
Evaluate candidate CLI network utilities
The nslookup command (or dig on Linux/macOS) accepts a specified DNS server IP address as an argument (e.g., nslookup hostname server_ip) to perform explicit targeted queries.
Other utilities rely on operating system default socket calls or serve completely different diagnostic purposes like layer 3 pinging or protocol stat tracking.

Key Concept

Direct DNS Querying using CLI Utilities
Estimated Time:45s
Question 1497Question

A network engineer is troubleshooting why internal workstations cannot access a newly deployed secure internal portal at `vault.corp.local`. The engineer executes `dig vault.corp.local` on a client workstation and captures the following terminal output:

;; QUESTION SECTION:
;vault.corp.local. IN A

;; ANSWER SECTION:
vault.corp.local. 300 IN CNAME sec-srv01.corp.local.

;; ADDITIONAL SECTION:
sec-srv01.corp.local. 300 IN A 10.200.5.25

Next, the engineer remotely accesses the destination server (`10.200.5.25`) and runs `netstat -tuln`, which displays:

Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 10.200.5.25:8443 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN

When end users attempt to navigate to `https://vault.corp.local` using standard browser defaults, the request immediately fails with a "Connection Refused" error. Based on the command outputs provided, which root cause explains why clients are unable to connect?

Show answer & explanation

Answer: The web application daemon is listening on TCP port 8443 rather than standard HTTPS port 443, causing default client web requests to be rejected by the host.

Answer

The web application daemon is listening on non-standard TCP port 8443 rather than standard HTTPS port 443, causing default client web requests to be rejected by the host.
The `dig` output demonstrates successful name resolution, resolving `vault.corp.local` via alias to IP address `10.200.5.25`. However, the `netstat -tuln` output shows the web daemon listening on custom TCP port 8443 (`10.200.5.25:8443`) rather than the standard HTTPS port 443. When users attempt to connect via standard HTTPS (`https://vault.corp.local`), their browser sends traffic to port 443. Because no service is bound to TCP port 443 on the target host, the server's OS rejects the connection attempt.

Step-by-Step Solution

1
Analyze the `dig` command output snippet to evaluate DNS resolution.
The `dig` query for `vault.corp.local` returns a CNAME pointing to `sec-srv01.corp.local.`, and the ADDITIONAL section successfully resolves `sec-srv01.corp.local.` to IP address `10.200.5.25`.
DNS resolution is functioning correctly; the client successfully resolves the target domain name to IPv4 address `10.200.5.25`.
2
Analyze the `netstat -tuln` command output snippet from target host `10.200.5.25`.
The output indicates an active TCP listening socket on `10.200.5.25:8443` (`tcp 0 0 10.200.5.25:8443 ... LISTEN`). Port 443 is not listed.
Web browsers attempting an HTTPS connection to `https://vault.corp.local` automatically target TCP port 443 by default unless an explicit port is appended to the URL.
3
Synthesize the DNS resolution result and socket binding state to determine why connections are refused.
Because no process is listening on TCP port 443 on host `10.200.5.25`, TCP SYN packets sent to port 443 trigger a TCP RST (Reset) packet from the operating system, resulting in a 'Connection Refused' error in the client browser.
Connecting requires matching both IP address resolution and target port listening states.

Key Concept

Correlating DNS query output with host netstat socket bindings during protocol troubleshooting
Question 1498Question

An infrastructure engineer is analyzing network logs to determine why an application server located at 10.50.20.1510.50.20.15 cannot transmit syslog data to a remote log collector at 172.18.4.50172.18.4.50. The collector receives log streams using UDP port 514514. The engineer inspects the active router interface access control list (ACL):

text
Extended IP access list ENTERPRISE_OUT
10 permit tcp 10.50.20.0 0.0.0.63 host 172.18.4.50 eq 514
20 permit ip 10.50.20.0 0.0.0.63 10.50.0.0 0.0.255.255
30 deny ip any any

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

Show answer & explanation

Answer: The access control list specifies TCP port 514 instead of UDP, causing syslog traffic to miss Rule 10 and fall through to the deny rule.

Answer

The access control list specifies TCP port 514 instead of UDP, causing syslog traffic to miss Rule 10 and fall through to the deny rule.
Standard syslog logging services utilize UDP port 514. In the configured access control list, Rule 10 explicitly permits TCP traffic on port 514. Because transport layer protocol matching is strict, UDP syslog packets miss Rule 10 as well as Rule 20 (which targets a different subnet block), falling through to Rule 30 where they are denied.

Step-by-Step Solution

1
Identify the transport protocol and port used by the service
Syslog standard protocol operates over UDP port 514.
Correct ACL matching depends on matching both transport protocol (UDP vs TCP) and port number.
2
Evaluate ACL rules top-down against the traffic specifications
UDP traffic from 10.50.20.15 to 172.18.4.50 on port 514 is evaluated against Rule 10 (permit tcp...), which fails due to protocol mismatch. Rule 20 permits traffic to 10.50.0.0/16, which does not match 172.18.4.50.
ACLs process sequentially until the first matching statement.
3
Determine the ultimate fate of unmatched packets
The traffic reaches Rule 30 (deny ip any any) and is dropped.
Unmatched traffic falls through to explicit or implicit deny rules.

Key Concept

ACL Transport Protocol Mismatch & Sequential Processing
Question 1499Question

A network engineer is investigating an inter-switch trunk link issue between Switch-A and Switch-B. Console logs on Switch-A continuously report "%CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on GigabitEthernet0/1 (50), with Switch-B GigabitEthernet0/1 (10)". Furthermore, hosts assigned to VLAN 50 on Switch-A are unable to reach services on VLAN 50 connected to Switch-B, and frame traffic is leaking into VLAN 10. Which TWO configuration actions must be performed to restore proper Layer 2 trunking and isolation? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Reconfigure GigabitEthernet0/1 on Switch-B so its native VLAN setting matches VLAN 50 on Switch-A.; Ensure VLAN 50 is explicitly included in the allowed VLAN list on GigabitEthernet0/1 on both switches.

Answer

To resolve the inter-switch trunking and isolation failures, the administrator must align the native VLAN setting on Switch-B to VLAN 50 to match Switch-A, and ensure VLAN 50 is added to the allowed VLAN list on both trunk ports.
The correct actions are aligning the native VLAN ID across both ends of the 802.1Q trunk link and ensuring that VLAN 50 is included in the allowed VLAN list on both switchports. A native VLAN mismatch causes untagged frames sent from Switch-A on VLAN 50 to be received on Switch-B and placed into VLAN 10, resulting in security leakage and cross-VLAN communication failures. Additionally, VLAN 50 must be permitted on the trunk allowed list for traffic to successfully traverse between switches.

Step-by-Step Solution

1
Identify the root cause of native VLAN traffic leakage
Console logs confirm Switch-A considers VLAN 50 native while Switch-B considers VLAN 10 native, causing untagged frames on VLAN 50 to be received into VLAN 10.
802.1Q trunks transmit native VLAN frames without an 802.1Q tag header. Mismatched native VLAN definitions cause frames to be placed into the wrong VLAN on the opposing switch.
2
Align native VLAN configuration on Switch-B
Changing Switch-B's native VLAN on interface GigabitEthernet0/1 to VLAN 50 resolves the CDP native VLAN mismatch log and stops traffic leakage.
Both trunk endpoints must agree on which VLAN ID handles untagged frames.
3
Verify allowed VLAN list on the trunk interfaces
Adding VLAN 50 to the trunk allowed list permits 802.1Q tagged frames for VLAN 50 to traverse the link.
If a VLAN is pruned or excluded from the switchport trunk allowed list, frames matching that VLAN ID are dropped at the egress interface.

Key Concept

802.1Q Trunking Native VLAN and Allowed List Troubleshooting
Question 1500Question

A network administrator is reviewing the management plane configuration of core campus switches during a security hardening initiative. The organization requires encrypted remote management and secure system monitoring. Which TWO configuration actions should the administrator implement to meet these hardening requirements?

Select all that apply

Show answer & explanation

Answer: Migrate system monitoring from SNMPv2c to SNMPv3 using authPriv security mode; Disable Telnet and enforce SSHv2 for all VTY remote access lines

Answer

The administrator should migrate system monitoring to SNMPv3 with authPriv security mode and disable Telnet in favor of SSHv2 on VTY access lines.
Device hardening guidelines require encrypting all administrative sessions and telemetry data. Enforcing SSHv2 secures remote command-line sessions, while deploying SNMPv3 using authPriv ensures both user authentication and payload encryption.

Step-by-Step Solution

1
Identify unencrypted management protocols running on network devices.
Telnet and older SNMP versions (SNMPv1/v2c) transmit credentials or monitoring data in clear text.
Hardening standards mandate replacing unencrypted protocols on the management plane.
2
Select secure protocol alternatives with cryptographic protection.
SSHv2 provides encrypted remote command-line access, and SNMPv3 authPriv supplies both authentication (HMAC) and privacy (encryption).
These protocols enforce confidentiality and integrity for device management.

Key Concept

Management Plane Hardening via Encrypted Protocols
PreviousPage 75 / 112Next
All practice questions — CompTIA Network+ | Examkin