All practice questions

2237 questions

Question 1301Question

A network administrator receives reports that newly arriving wireless clients on a high-density office VLAN (192.168.32.0/23192.168.32.0/23) are unable to access network resources. Inspecting an affected workstation via `ipconfig /all` reveals the following output:

text
IPv4 Address. . . . . . . . . . . : 169.254.112.45
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . :

Wireless 802.1X authentication logs show that clients authenticate successfully, but DHCP lease requests time out. Further inspection of the centralized DHCP server shows that the scope for 192.168.32.0/23192.168.32.0/23 has 508508 active leases out of 508508 total allocated addresses, with a default lease duration of 88 days.

Which of the following actions is the most appropriate resolution to fix the IP address assignment failure?

Show answer & explanation

Answer: Reduce the DHCP scope lease duration and expand the available address pool for the wireless VLAN.

Answer

Reduce the DHCP scope lease duration and expand the available address pool for the wireless VLAN.
The client terminal output shows an APIPA address (169.254.112.45169.254.112.45), confirming that the client failed to receive a DHCP response. The DHCP server statistics confirm that all 508508 usable addresses in the 192.168.32.0/23192.168.32.0/23 pool are in use. Because the environment is high-density wireless and has an excessively long 88-day lease time, addresses are held long after devices leave the network. Reducing lease duration and increasing the pool capacity addresses the root cause of scope exhaustion.

Step-by-Step Solution

1
Analyze client IP configuration
The presence of an IPv4 address in the 169.254.0.0/16169.254.0.0/16 range (169.254.112.45169.254.112.45) with no default gateway indicates an Automatic Private IP Addressing (APIPA) self-assignment resulting from a failed DHCP request.
When a client fails to receive a response to its DHCPDISCOVER broadcast, the operating system self-assigns an APIPA address to maintain local link connectivity.
2
Evaluate DHCP server logs and scope state
The server logs show 508508 out of 508508 addresses in the 192.168.32.0/23192.168.32.0/23 scope are currently leased.
A /23/23 subnet provides 232232=5102=5082^{32-23} - 2 = 510 - 2 = 508 usable host addresses. Having 508508 active leases indicates total DHCP scope exhaustion.
3
Determine corrective action for high-density wireless environments
Long lease durations (88 days) in transient or high-density wireless environments prevent IP addresses from recycled back into the pool. Reducing the lease duration (e.g., to several hours) and expanding the IP range resolves exhaustion.
Shorter lease times reclaim IP addresses from disconnected transient devices, ensuring available capacity for incoming clients.

Key Concept

DHCP Scope Exhaustion and Lease Duration Tuning
Question 1302Question

A network administrator is investigating an issue where corporate users cannot authenticate to the 802.1X wireless network following a server maintenance window. The administrator suspects that an expired RADIUS server SSL certificate is preventing successful EAP-TLS handshakes. To test this theory, the administrator installs a valid test certificate on a staging RADIUS server and successfully authenticates a test client. According to the CompTIA troubleshooting methodology, what is the immediate NEXT step the administrator should perform?

Show answer & explanation

Answer: Establish a plan of action to deploy the renewed certificate in production and implement the solution.

Answer

Establish a plan of action to deploy the renewed certificate in production and implement the solution.
The technician has completed Step 3 of the CompTIA troubleshooting methodology by testing and confirming the theory on a staging environment. The immediate next phase (Step 4) requires establishing a plan of action to resolve the issue in the live environment and implementing that solution.

Step-by-Step Solution

1
Identify current phase in CompTIA troubleshooting methodology
The technician suspected an expired RADIUS certificate (Establish a theory - Step 2) and tested it on a staging server successfully (Test the theory - Step 3).
Confirming that authentications succeed with a valid test certificate validates the root cause theory.
2
Determine the next sequential phase
Following Step 3 (Test the theory to determine cause), the official CompTIA methodology mandates Step 4: Establish a plan of action to resolve the problem and implement the solution.
A formal rollout plan must be created and executed (including change approval if required) before verifying full system functionality.

Key Concept

CompTIA 6-Step Troubleshooting Methodology Sequence
Question 1303Question

A network administrator has verified that a recently modified firewall access control list (ACL) blocking TCP port 636 is the root cause of directory authentication failures for hybrid cloud VPN users. The administrator confirmed this theory after testing the ACL modification in a staging environment. According to the CompTIA troubleshooting methodology, which TWO of the following actions should the administrator perform NEXT during the upcoming phase? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Assess potential security and operational impacts before applying the revised access control list to the production firewall.; Apply the modified access control list on the production firewall to restore secure directory authentication services.

Answer

The administrator should evaluate potential security and operational impacts of the firewall change and implement the updated access control list on the production firewall.
Once a theory of probable cause has been confirmed through testing (Step 3), the network administrator must proceed to Step 4: Establish a plan of action to resolve the problem and implement the solution. This phase requires identifying potential side effects or impacts of the proposed change on production systems and subsequently deploying the fix.

Step-by-Step Solution

1
Identify the current phase completed in the CompTIA troubleshooting methodology.
The technician has already established and tested a theory of probable cause (Step 3: Test the theory to determine cause).
Confirming that TCP port 636 was blocked in staging completes the hypothesis testing step.
2
Determine the mandatory next phase according to the 6-step framework.
The immediate next phase is Step 4: Establish a plan of action to resolve the problem and implement the solution.
CompTIA methodology strictly dictates establishing a plan of action (including identifying potential effects) and then implementing the solution before moving to system verification.
3
Select the appropriate actions that align strictly with Step 4.
Evaluating potential impacts of the ACL change and deploying the fix to production fall directly within Step 4.
Impact assessment ensures change safety, while rule deployment executes the planned resolution.

Key Concept

CompTIA 6-Step Troubleshooting Methodology: Transitioning from Theory Testing (Step 3) to Plan of Action & Implementation (Step 4)
Estimated Time:2m 0s
Question 1304Question

A network administrator is preparing a formal Request for Change (RFC) to deploy updated security policies across several branch office routers. Before presenting the request to the Change Advisory Board (CAB) for formal review, which of the following elements must be included in the RFC documentation?

Show answer & explanation

Answer: A detailed rollback plan defining specific criteria and steps to restore the previous stable configuration if the deployment fails

Answer

A detailed rollback plan defining specific criteria and steps to restore the previous stable configuration if the deployment fails
In standardized IT change management, a Request for Change (RFC) submitted to the Change Advisory Board (CAB) must include a comprehensive rollback plan. This ensures that if the change causes unexpected network failure or performance degradation, administrators can rapidly revert the environment to its previous known-good baseline using pre-defined triggers and explicit CLI procedures.

Step-by-Step Solution

1
Identify the standard requirements for a formal Request for Change (RFC) submission within enterprise change management.
Recognize that an RFC must contain impact analyses, scheduled maintenance windows, risk assessments, and recovery procedures.
Ensures that all potential network disruptions are anticipated and mitigated before implementation.
2
Evaluate the necessity of a rollback plan during configuration updates.
Confirm that a rollback plan provides explicit parameters and step-by-step procedures to revert to a functional state if unexpected failures occur.
Minimizes network downtime and service degradation if the change produces unintended consequences.

Key Concept

Request for Change (RFC) Documentation and Rollback Procedures
Estimated Time:1m 30s
Question 1305Question

A network administrator is troubleshooting an intermittent 10GBASE-LR single-mode optical fiber link between two campus buildings. Switch port diagnostics indicate high optical signal attenuation and excessive return loss (back reflection) following a recent patch panel maintenance window. Optical transceivers on both endpoints report normal transmit power levels. Which of the following actions should the network administrator perform to accurately pinpoint the fault location and resolve the physical layer degradation? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Inspect all fiber end-faces with a optical fiber inspection scope and replace any mixed APC (green) and UPC (blue) connector patch cables with matching connector polish types.; Use an Optical Time-Domain Reflectometer (OTDR) to analyze reflection spikes and measure attenuation across splices, bends, and connector transitions along the fiber run.

Answer

The administrator must inspect ferrule end-faces using an optical inspection scope to ensure APC and UPC connector polishes are not mixed, and utilize an Optical Time-Domain Reflectometer (OTDR) to pinpoint physical attenuation and reflectometry anomalies along the single-mode fiber run.
High optical return loss and signal attenuation on a single-mode fiber link are key indicators of connector polish mismatches (e.g., mating green APC connectors with blue UPC connectors) or physical cable damage. Using an optical fiber inspection scope allows technicians to identify physical ferrule contamination or polish mismatch, while an Optical Time-Domain Reflectometer (OTDR) precise measures light loss and distance to reflective events across the fiber span.

Step-by-Step Solution

1
Evaluate the reported physical symptoms on the fiber link.
High attenuation (insertion loss) combined with excessive return loss (back reflection) on single-mode fiber points directly to physical interface mismatch, contaminated end-faces, microbends/macrobends, or damaged physical fiber.
Normal transceiver transmit power rules out active transceivers as the primary failure point, isolating the issue to the passive cabling medium and physical connector interfaces.
2
Select the proper optical diagnostic tool to localize faults across the fiber run.
An Optical Time-Domain Reflectometer (OTDR) measures backscattered light over distance to locate splices, severe bends, or physical breaks.
Copper testing tools (like standard electrical TDRs) cannot send or analyze light signals on fiber optic strands.
3
Verify physical connector polish compliance and end-face cleanliness.
Replacing mismatched APC (8-degree angle ferrule) and UPC (flat spherical ferrule) connectors eliminates air gap reflections and high decibel signal loss.
Mating an APC connector directly with a UPC connector damages ferrule tips and causes significant air gap reflection, yielding high return loss.

Key Concept

Fiber Optic Physical Layer Troubleshooting & Diagnostic Instrument Selection
Question 1306Question

A network administrator needs to grant third-party auditors access to an internal web-based financial dashboard. The security policy dictates that remote users must not be required to install dedicated client software or agent applications on their unmanaged personal endpoints, yet all session traffic must remain encrypted over the internet. Which remote access technology best meets these requirements?

Show answer & explanation

Answer: Clientless SSL/TLS VPN

Answer

Clientless SSL/TLS VPN is the correct selection because it allows users to establish an encrypted session through a standard web browser using HTTPS (TCP 443) without installing remote access software.
Clientless SSL/TLS VPNs operate through standard web browsers over HTTPS (TCP port 443). Because modern web browsers natively support TLS encryption, third-party users can securely access web-based applications without downloading or installing any dedicated VPN client software on unmanaged endpoints.

Step-by-Step Solution

1
Analyze the operational constraints presented in the scenario.
Identified two primary requirements: zero endpoint client software installation (unmanaged devices) and encrypted access restricted to a web-based application.
Remote access solutions differ by encapsulation layer and client requirements.
2
Evaluate protocol architectures against the endpoint software restriction.
Clientless SSL/TLS VPN leverages existing web browser capabilities (Application layer security), eliminating the need for administrative rights or client software installation on the endpoint.
IPsec, L2TP, and PPTP all operate at lower OSI layers (Network/Data Link) and mandate host client configurations or helper software.

Key Concept

Clientless SSL/TLS VPN Architecture
Question 1307Question

A network security administrator must configure an IPv4 Access Control List (ACL) on a router to enforce access policies for the internal host network (10.1.1.0/2410.1.1.0/24) communicating with a database server (172.16.10.5172.16.10.5). The policy requires that host 10.1.1.1510.1.1.15 is allowed HTTP access to the server, while all other hosts in 10.1.1.0/2410.1.1.0/24 are denied HTTP access. However, all hosts in 10.1.1.0/2410.1.1.0/24 must be allowed all other IP traffic to the server, and all remaining traffic from any other network must be dropped. Place the ACL statements in the correct top-to-bottom execution order to enforce this security policy without rule shadowing.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential order of ACL statements from top to bottom is: 1) permit tcp host 10.1.1.15 host 172.16.10.5 eq 80, 2) deny tcp 10.1.1.0 0.0.0.255 host 172.16.10.5 eq 80, 3) permit ip 10.1.1.0 0.0.0.255 host 172.16.10.5, and 4) deny ip any any.
Router Access Control Lists (ACLs) process incoming packets strictly top-to-bottom against each line item until a match is found. Once a match occurs, the action (permit or deny) is taken immediately and no further rules are evaluated. Therefore, more specific rules (such as host-specific permits or protocol-specific denies) must precede general rules (such as full subnet permits or catch-all denies). Placing host 10.1.1.15's HTTP permit first ensures it is processed before the 10.1.1.0/24 HTTP deny rule. Placing the 10.1.1.0/24 HTTP deny rule second ensures HTTP traffic from remaining subnet hosts is blocked before matching the third rule, which permits all other IP traffic from 10.1.1.0/24. Finally, the catch-all deny statement must be at the very bottom.

Step-by-Step Solution

1
Identify the most specific exception rule.
The rule permitting HTTP access specifically for host 10.1.1.15 must be evaluated first.
Sequential ACL evaluation stops at the first matching statement. Placing host-specific permits first prevents broader subnet deny statements from accidentally blocking the host (rule shadowing).
2
Identify specific protocol restrictions for the broader network.
The rule denying HTTP traffic from subnet 10.1.1.0/24 to host 172.16.10.5 must be placed second.
This blocks HTTP for all other hosts in 10.1.1.0/24 after host 10.1.1.15 has already matched the first rule and been permitted.
3
Identify broad network permission rules.
The rule permitting general IP traffic from subnet 10.1.1.0/24 to host 172.16.10.5 is placed third.
Placing this rule after the specific HTTP deny rule ensures HTTP traffic is denied while allowing all other IP protocols (such as ICMP or SSH) from the subnet.
4
Place default clean-up or implicit deny rules at the bottom.
The explicit deny ip any any statement is placed last.
Catch-all deny statements must always be positioned at the end of the ACL to catch any traffic not explicitly permitted by previous rules.

Key Concept

ACL Sequential Processing & Rule Shadowing Avoidance
Question 1308Question

A user's workstation is assigned the static IP address 10.0.4.5010.0.4.50 with a subnet mask of 255.255.255.0255.255.255.0. The workstation can successfully ping other local computers on the 10.0.4.0/2410.0.4.0/24 network, but it cannot reach any servers on external subnets or the internet. An administrator reviews the network configuration and notes that the default gateway is set to 10.0.5.110.0.5.1. Which of the following is the root cause of the outbound connectivity issue?

Show answer & explanation

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

Answer

The default gateway is configured on a different IP subnet than the host.
For a host to communicate with remote networks, its default gateway must reside on the exact same local IP subnet. Here, the host is on 10.0.4.0/2410.0.4.0/24, but the gateway is set to 10.0.5.110.0.5.1 (which is on 10.0.5.0/2410.0.5.0/24). Consequently, the host cannot deliver traffic to the gateway for routing to external subnets.

Step-by-Step Solution

1
Analyze the host IP address and subnet mask.
The host address is 10.0.4.5010.0.4.50 with subnet mask 255.255.255.0255.255.255.0 (/24), defining a usable local subnet of 10.0.4.110.0.4.1 through 10.0.4.25410.0.4.254.
Devices on a network can directly communicate only with other devices on their local IP subnet.
2
Compare the configured default gateway address to the local subnet.
The default gateway address 10.0.5.110.0.5.1 belongs to the 10.0.5.0/2410.0.5.0/24 subnet.
A host must send traffic destined for external networks to a gateway on its own local subnet. Because 10.0.5.110.0.5.1 is outside 10.0.4.0/2410.0.4.0/24, the host cannot resolve its MAC address locally to deliver outbound packets.

Key Concept

Default Gateway Subnet Matching
Question 1309Question

A network administrator is troubleshooting connectivity issues on a corporate wireless guest network spanning the 192.168.100.0/24192.168.100.0/24 subnet. Transient users report that their laptops periodically fail to connect to network resources and receive self-assigned IP addresses in the 169.254.0.0/16169.254.0.0/16 range during peak operating hours. Upon inspecting the central DHCP server status, the administrator observes the following command output snippet:

text
DHCP Scope: Guest_VLAN100
Subnet Prefix: 192.168.100.0/24
Range: 192.168.100.10 - 192.168.100.250
Total Scope Addresses: 241
Active Leases: 241 (100% utilized)
Pending Requests: 14 (Dropped - No available addresses)
Lease Duration: 8 days 00:00:00

Physical attendance logs confirm that no more than 60 guest users are ever present in the facility concurrently. Which of the following is the most likely root cause of this issue?

Show answer & explanation

Answer: The DHCP lease duration is configured too long for a network with high host turnover, leading to scope exhaustion.

Answer

The most likely root cause is that the DHCP lease duration is configured too long for a network with high host turnover, leading to scope exhaustion.
The correct answer identifies that an excessively long DHCP lease time (8 days) on a transient network (guest Wi-Fi) leads to scope exhaustion. Even though concurrent user count is low, new MAC addresses consume IP allocations that are retained long after devices leave the network.

Step-by-Step Solution

1
Analyze the client symptom
Clients receive 169.254.x.x169.254.x.x (APIPA) addresses, indicating a failure to receive a DHCP response during the DORA process.
When a host sends a DHCPDISCOVER and receives no DHCPOFFER, operating systems fall back to Automatic Private IP Addressing.
2
Examine the DHCP server log output
Active leases equal 241241 out of 241241 (100%100\% utilization), and 1414 pending requests are dropped due to no available addresses.
The server scope is completely exhausted, preventing new DHCPOFFER messages from being issued.
3
Correlate scope metrics with environment characteristics
The physical presence is only ~60 concurrent users, but the lease duration is set to 8 days.
Transient devices connect, lease an IP, and leave. Because the lease lasts 8 days, old MAC bindings remain occupied in state memory long after devices depart, accumulating 241 assigned leases over time.

Key Concept

DHCP Scope Exhaustion and Lease Time Optimization
Question 1310Question

During a post-incident audit following a scheduled core network maintenance event, auditors noted that engineers spent several hours attempting to resolve unexpected packet loss on a newly updated WAN interface rather than reverting to the previous baseline configuration. Although the maintenance window eventually expired without restoring stable service, the deployment team had not breached any formal protocols because no specific metrics were defined to dictate when troubleshooting should cease and restoration must begin. Which specific element of the Request for Change (RFC) documentation was missing or improperly constructed?

Show answer & explanation

Answer: Specific rollback triggers and criteria

Answer

Specific rollback triggers and criteria
A comprehensive Request for Change (RFC) must include detailed rollback triggers in addition to the step-by-step restoration procedure. Rollback triggers establish objective metrics (such as SLA threshold breaches, elapsed maintenance time, or unresolvable error rates) that mandate when implementation must be abandoned to safeguard business continuity.

Step-by-Step Solution

1
Analyze the incident details provided in the scenario
Identify that the deployment team continued troubleshooting unforeseen failures past reasonable thresholds because explicit quantitative or temporal boundaries for aborting the change were absent.
Engineers need objective criteria to make unbiased decisions during maintenance windows when changes fail.
2
Evaluate the components of a comprehensive Request for Change (RFC)
Determine that rollback plans must contain both the technical procedure for reversion and explicit rollback triggers (e.g., maximum allowable downtime, specific performance degradation limits, or clock-time cutoffs).
Without pre-defined rollback triggers, teams frequently over-commit to troubleshooting during active maintenance, leading to extended service outages.

Key Concept

Rollback Triggers and Reversion Criteria in Change Management
Question 1311Question

A network engineer is troubleshooting a client workstation that cannot connect to an internal web portal using its hostname `srv01.corp.internal`. The engineer executes two `nslookup` queries from the client's command prompt:

text
C:\> nslookup srv01.corp.internal
Server: UnKnown
Address: 192.168.1.1
*** UnKnown can't find srv01.corp.internal: Non-existent domain

C:\> nslookup srv01.corp.internal 10.0.0.53
Server: dc01.corp.internal
Address: 10.0.0.53

Name: srv01.corp.internal
Address: 10.0.0.150

Based on the output above, which of the following are the MOST likely root causes of the name resolution issue on the workstation? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The workstation is assigned a default DNS resolver IP address that lacks the internal domain zone information.; The local DHCP server scope is misconfigured to distribute a local gateway or public DNS server address instead of the internal DNS server.

Answer

The workstation is configured with a default DNS server (192.168.1.1, likely a home router or upstream gateway) that does not maintain or forward queries for the internal domain `.corp.internal`. Furthermore, the DHCP server scope distributing network configurations to local clients is misconfigured to pass out 192.168.1.1 rather than the authoritative internal DNS server (10.0.0.53).
The initial query to default DNS server 192.168.1.1 fails because that server does not hold authoritative records for the private zone `corp.internal`. However, explicitly specifying the internal DNS server (10.0.0.53) in the command parameter resolves the hostname successfully. This demonstrates that the internal DNS server is functioning and configured properly with the host A record, but client workstations are using an incorrect default DNS server assigned via DHCP.

Step-by-Step Solution

1
Analyze the default nslookup query output
The workstation automatically queries its configured default server 192.168.1.1, which fails with 'Non-existent domain' (NXDOMAIN).
This confirms that 192.168.1.1 cannot resolve hostnames within the `corp.internal` private namespace.
2
Analyze the explicit nslookup query output targeting 10.0.0.53
When explicitly directed to query server 10.0.0.53, name resolution succeeds immediately and returns IP address 10.0.0.150.
This proves that the internal DNS server is reachable, online, and contains a valid A record for the target host.
3
Deduce the underlying root causes
Identify that the client workstation has an incorrect preferred DNS resolver configured, which is typically distributed dynamically via DHCP scope settings.
Correcting the network adapter's primary DNS setting or updating the DHCP scope options to distribute 10.0.0.53 resolves the issue.

Key Concept

DNS Server Configuration & DHCP Resolver Scopes
Question 1312Question

An enterprise organization is mitigating two distinct security concerns regarding its web services: unauthorized tampering of REST API transactional data in transit, and frequent web server unresponsiveness caused by TCP SYN flood attacks. Which TWO of the following security mechanisms directly address the Integrity and Availability pillars of the CIA triad to mitigate these specific issues? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Implementation of HMAC (Hash-based Message Authentication Code) validation for API payload transmissions; Deployment of perimeter SYN proxy appliances with automated TCP rate-limiting capabilities

Answer

The correct mechanisms are implementing HMAC validation for API payloads (protecting Integrity against tampering in transit) and deploying SYN proxy appliances with rate-limiting (protecting Availability against SYN flood attacks).
HMAC verification protects payload Integrity by ensuring API transaction data is not modified during transit. Deploying a SYN proxy protects service Availability by absorbing spoofed TCP connection floods, keeping backend services operational.

Step-by-Step Solution

1
Analyze the security concern regarding API data tampering in transit.
Unauthorized modification of data during transmission is an Integrity violation.
HMAC uses a cryptographic hashing technique combined with a secret key to ensure data has not been altered between sender and receiver.
2
Analyze the security concern regarding TCP SYN flood attacks.
SYN floods attempt to exhaust server resources to make services unreachable, violating Availability.
Perimeter SYN proxies manage TCP handshakes on behalf of protected servers, preventing half-open connection state table exhaustion.
3
Evaluate distractors against the required security pillars.
Volume encryption ensures Confidentiality at rest, while RADIUS provides AAA administrative access control.
Neither storage encryption nor administrative AAA resolves transit payload tampering or active network denial-of-service incidents.

Key Concept

CIA Triad Principles (Integrity and Availability Controls)
Estimated Time:1m 30s
Question 1313Question

Match each physical layer cabling diagnostic tool to the primary troubleshooting task or measurement it is designed to perform.

Click a left item, then click its matching right item

Items

Tone Generator and Probe Kit
Time-Domain Reflectometer (TDR)
Optical Power Meter (OPM)
Cable Certifier

Matches

Show answer & explanation

Answer

Tone Generator and Probe Kit pairs with locating an unlabeled copper cable trace in a patch panel bundle. Time-Domain Reflectometer (TDR) pairs with determining the exact distance to an open or short circuit on a twisted-pair cable. Optical Power Meter (OPM) pairs with measuring optical signal loss and power levels on a fiber optic link. Cable Certifier pairs with verifying that a newly installed copper cable meets TIA/EIA Category 6A specification standards.
Each physical cabling tool serves a distinct role in network diagnostics: tone generators locate individual cable ends through audio signals, TDRs measure distance to physical copper faults using pulse reflections, Optical Power Meters calculate light attenuation on fiber runs, and Cable Certifiers validate that a cable installation meets official bandwidth performance standards.

Step-by-Step Solution

1
Identify the primary function of tracing cables
Connecting the Tone Generator and Probe Kit to the task of finding unlabeled cable ends via signal induction.
Toner probes are designed specifically for tracing and identifying individual conductors in mixed bundles.
2
Identify physical fault distance measurement tools for copper media
Mapping the Time-Domain Reflectometer (TDR) to locating the precise distance to physical breaks or short circuits.
TDR calculates distance to fault using electrical pulse reflections.
3
Determine the tool used for optical signal loss measurement
Associating the Optical Power Meter (OPM) with measuring light power across fiber optic strands.
OPMs measure light power loss in decibels (dB) on optical links.
4
Identify standard compliance testing tools
Linking the Cable Certifier to verifying full TIA/EIA Category 6A specification standards.
Cable certifiers perform comprehensive high-frequency electrical parameter testing against industry standard standards.

Key Concept

Selecting Appropriate Cabling Diagnostic Tools
Question 1314Question

An IT technician is troubleshooting name resolution issues on an administrator workstation. The technician issues an `nslookup` command for `app.finance.local` and receives a successful reply pointing to `192.168.10.50`. However, when attempting to ping `app.finance.local` from the same machine, the system attempts to send traffic to `10.0.0.99` and times out.

text
C:\Users\Admin> nslookup app.finance.local
Server: dns01.corp.internal
Address: 10.0.0.1

Name: app.finance.local
Address: 192.168.10.50

C:\Users\Admin> ping app.finance.local
Pinging app.finance.local [10.0.0.99] with 32 bytes of data:
Request timed out.

Which of the following is the most likely cause of the discrepancy in resolved IP addresses?

Show answer & explanation

Answer: A static entry for app.finance.local mapping to 10.0.0.99 is present in the local hosts file.

Answer

A static entry for app.finance.local mapping to 10.0.0.99 is present in the local hosts file.
The correct answer identifies that a static entry exists in the local hosts file. Standard operating system commands like `ping` utilize the OS name resolution pipeline, which evaluates the local `hosts` file and resolver cache before sending requests to remote DNS servers. The diagnostic tool `nslookup`, however, bypasses local system files and queries the DNS server directly. The discrepancy between `nslookup` (192.168.10.50) and `ping` (10.0.0.99) indicates that a local `hosts` file entry is overriding the DNS server's record for normal application traffic.

Step-by-Step Solution

1
Analyze the behavior of the nslookup utility
nslookup directly contacts the configured DNS server (10.0.0.1) over network sockets, completely bypassing the local operating system resolver library, DNS cache, and hosts file.
This confirms that the DNS server holds the correct record (192.168.10.50).
2
Analyze the behavior of standard OS utilities (e.g., ping)
ping relies on the OS Stub Resolver, which checks local mechanisms (such as the local hosts file and local DNS resolver cache) prior to initiating a network DNS query.
Because ping attempts to reach 10.0.0.99, a local override must exist on the client machine that takes precedence over network DNS responses.
3
Identify the root cause of the address discrepancy
A legacy or manual entry in the system's local hosts file (%SystemRoot%\System32\drivers\etc\hosts) maps app.finance.local to 10.0.0.99, overriding the valid DNS response for standard applications.
Removing or correcting the entry in the local hosts file will restore consistent name resolution.

Key Concept

Operating System Hostname Resolution Order vs. Direct DNS Diagnostics (nslookup vs. OS Resolver)
Question 1315Question

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

Click a left item, then click its matching right item

Items

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

Matches

Show answer & explanation

Answer

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

Step-by-Step Solution

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

Key Concept

Physical and Environmental RF Troubleshooting Mechanisms
Estimated Time:1m 30s
Question 1316Question

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

Drag items to arrange them in the correct order

Show answer & explanation

Answer

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

Step-by-Step Solution

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

Key Concept

CompTIA 6-Step Network Troubleshooting Methodology
Estimated Time:1m 30s
Question 1317Question

During an enterprise network audit, users report periodic voice distortion and video freezing during teleconference sessions over a WAN connection. Telemetry shows that overall link utilization is below 35% and total packet loss is 0%, but packet inter-arrival times fluctuate significantly between 4 ms and 130 ms. Which network performance metric is directly causing this quality degradation?

Show answer & explanation

Answer: Jitter

Answer

Jitter is the performance metric directly responsible for inter-arrival time fluctuations in real-time communication streams.
Jitter represents the variation in latency over time. Real-time media protocols rely on predictable packet arrival intervals. When inter-arrival times vary significantly, buffering mechanisms cannot smoothly process the stream, leading to audio artifacts and video frame stalls.

Step-by-Step Solution

1
Analyze the observed symptoms
Real-time communication applications (VoIP and video) suffer quality degradation despite sufficient available bandwidth and zero packet loss.
Real-time traffic is uniquely sensitive to delay variation rather than raw throughput constraints.
2
Evaluate the telemetry measurements
Fluctuations in inter-arrival times between 4 ms and 130 ms represent delay variance.
Variable packet arrival delay directly matches the definition of network jitter.
3
Identify the target metric
Jitter buffering or quality of service (QoS) queueing must be tuned to stabilize real-time packet delivery.
Addressing jitter resolves voice fragmentation and video playback freezes.

Key Concept

Jitter is the variance in latency (packet arrival delay) over time, critical to real-time protocols like RTP used in VoIP and video conferencing.
Estimated Time:1m 0s
Question 1318Question

A security engineer is updating an organization's wireless baseline documentation to prepare for a migration from legacy Wi-Fi security protocols to WPA3-Enterprise across all corporate facilities. Which of the following technical features and requirements specifically apply when implementing WPA3-Enterprise? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Mandatory implementation of Protected Management Frames (PMF) to safeguard unicast and multicast management actions against eavesdropping and spoofing; Availability of an optional 192-bit cryptographic security suite utilizing 256-bit Galois/Counter Mode Protocol (GCMP-256) for high-security environments

Answer

The transition to WPA3-Enterprise mandates Protected Management Frames (PMF) and introduces support for an optional 192-bit security mode using GCMP-256.
WPA3 requires Protected Management Frames (PMF) across all variants to defend against disassociation/deauthentication spoofing, and WPA3-Enterprise includes an optional 192-bit mode using GCMP-256 for enhanced data confidentiality.

Step-by-Step Solution

1
Analyze WPA3 baseline mandates.
PMF (IEEE 802.11w) is mandatory in WPA3 (both Personal and Enterprise modes), ensuring management frame integrity and protection against deauthentication spoofing.
WPA3 enforces PMF to mitigate wireless management frame attacks.
2
Evaluate WPA3-Enterprise specific cryptographic options.
WPA3-Enterprise supports an enhanced 192-bit security suite using GCMP-256 encryption for mission-critical environment baselines.
GCMP-256 and HMAC-SHA384 provide higher cryptographic assurance required for enterprise environments.
3
Distinguish authentication protocols between Personal and Enterprise modes.
SAE and PSK belong to personal/pre-shared key modes, whereas Enterprise mode utilizes 802.1X framework with EAP authentication types.
Confusing SAE (Personal) with 802.1X RADIUS (Enterprise) misidentifies the underlying authentication architecture.

Key Concept

WPA3-Enterprise Security Standards and Cryptographic Suites
Question 1319Question

A network engineering team is preparing to modify Access Control Lists (ACLs) across core datacenter routers to restrict outdated management protocols and enforce secure logging. Before executing the modifications during the scheduled maintenance window, which TWO of the following tasks must be completed as part of the standard change management workflow? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Document a detailed rollback plan specifying precise procedures and conditions for reverting the ACL modifications.; Submit the proposed changes for formal review and approval by the Change Advisory Board (CAB) prior to execution.

Answer

The engineering team must document a detailed rollback plan and obtain formal approval from the Change Advisory Board (CAB) prior to executing the change.
Standard change management protocols require non-emergency network modifications to undergo formal review by the Change Advisory Board (CAB) to assess potential business impact and scheduling. Additionally, every Request for Change (RFC) must include a fully articulated rollback plan to quickly restore original network operations should issues arise during execution.

Step-by-Step Solution

1
Identify key requirements of the formal Change Management process for network modifications.
Standard change management workflows mandate thorough risk evaluation, preliminary testing, explicit rollback procedures, and official authorization.
Ensures minimal disruption to production business operations and establishes clear accountability for infrastructure updates.
2
Evaluate the proposed operational steps against change management standards.
Documenting a rollback plan and securing CAB authorization represent essential risk-mitigation and approval controls.
CAB approval ensures cross-functional review of potential impacts, while a detailed rollback plan guarantees rapid recovery if implementation fails.

Key Concept

Standard Change Management Workflow and RFC Components
Question 1320Question

Match each Virtual Private Network (VPN) protocol or header component to its corresponding operational characteristics and transport specifications.

Click a left item, then click its matching right item

Items

WireGuard
SSTP (Secure Socket Tunneling Protocol)
IPsec AH (Authentication Header)
L2TP (Layer 2 Tunneling Protocol)

Matches

Show answer & explanation

Answer

WireGuard pairs with high-performance kernel-space UDP port 51820 execution; SSTP pairs with SSL/TLS encapsulation over TCP port 443; IPsec AH pairs with OSI Layer 3 IP protocol 51 authentication without encryption; L2TP pairs with OSI Layer 2 tunneling over UDP port 1701 requiring secondary encryption.
Each VPN technology fulfills a specific niche: WireGuard provides fast kernel-level VPN connectivity on UDP port 51820; SSTP leverages TLS over TCP port 443 to circumvent restrictive firewalls; IPsec AH secures packet headers at Layer 3 using IP protocol 51 without encrypting data; and L2TP establishes Layer 2 tunnels on UDP port 1701 that rely on external protocols like IPsec for payload encryption.

Step-by-Step Solution

1
Analyze WireGuard characteristics
WireGuard is recognized by its lightweight design, Linux kernel integration, modern ChaCha20-Poly1305 cipher suite, and default listening port on UDP 51820.
Differentiates modern state-of-the-art tunnel protocols from legacy PPP-based options.
2
Analyze SSTP transport features
SSTP uses TCP port 443 to tunnel PPP sessions inside TLS encryption.
Allows traffic to masquerade as standard HTTPS traffic to bypass firewall restrictions.
3
Differentiate IPsec Authentication Header (AH) from Encapsulating Security Payload (ESP)
AH uses IP protocol 51 for integrity and anti-replay protection without encrypting payload data, causing NAT verification failures due to header modification.
Identifies protocol-level security boundaries and NAT incompatibility issues.
4
Identify L2TP operational layer and security requirements
L2TP functions at Layer 2 to encapsulate PPP frames across IP networks over UDP port 1701, but requires IPsec for payload confidentiality.
Distinguishes pure tunneling mechanisms from integrated cryptographic VPN frameworks.

Key Concept

Distinguishing Virtual Private Network (VPN) and remote access protocols based on OSI layer operation, port numbers, encapsulation methods, and cryptographic capabilities.
PreviousPage 66 / 112Next
All practice questions — CompTIA Network+ | Examkin