All practice questions

2237 questions

Question 1401Question

A workstation on an enterprise network is unable to access internal network shares or the Internet. A network technician runs `ipconfig` on the command prompt and receives the following output:

IPv4 Address. . . . . . . . . . . . : 169.254.184.91
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

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

Show answer & explanation

Answer: The workstation failed to reach a DHCP server and self-assigned an Automatic Private IP Addressing (APIPA) address.

Answer

The workstation failed to reach a DHCP server and self-assigned an Automatic Private IP Addressing (APIPA) address.
An IPv4 address in the range 169.254.0.1 through 169.254.255.254 indicates that the operating system assigned an Automatic Private IP Addressing (APIPA) address after failing to contact a DHCP server.

Step-by-Step Solution

1
Examine the IP address assigned to the host from the command output.
The host IP is 169.254.184.91 with a subnet mask of 255.255.0.0.
IP addresses in the 169.254.0.0/16 block are reserved for Automatic Private IP Addressing (APIPA).
2
Determine why an APIPA address is assigned to a DHCP client.
APIPA is activated when a DHCP client sends a broadcast request but fails to receive a DHCPOFFER response.
The client self-assigns an address to enable local link communication while indicating a failure to contact the DHCP server.

Key Concept

Automatic Private IP Addressing (APIPA) Identification
Estimated Time:45s
Question 1402Question

A network technician connects two switches, Switch-A and Switch-B, via an 802.1Q trunk link. Users on VLAN 10 connected to Switch-A cannot communicate with users on VLAN 10 attached to Switch-B. Console output on Switch-A displays `%CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on interface GigabitEthernet0/1 (10), with Switch-B GigabitEthernet0/1 (1)`. Which TWO of the following statements correctly explain the network behavior and the required resolution?

Select all that apply

Show answer & explanation

Answer: Untagged frames sent by Switch-A on native VLAN 10 are received by Switch-B and assigned to VLAN 1.; Configuring the native VLAN to match on both ends of the trunk interface will resolve the connectivity issue.

Answer

The two correct statements are that untagged frames sent by Switch-A on native VLAN 10 are received by Switch-B and assigned to VLAN 1, and configuring the native VLAN to match on both ends of the trunk interface will resolve the connectivity issue.
Under the IEEE 802.1Q standard, traffic on the native VLAN travels untagged across trunk links. When Switch-A uses VLAN 10 as native and Switch-B uses VLAN 1, untagged frames sent from Switch-A's VLAN 10 arrive at Switch-B and are incorrectly processed as VLAN 1 frames. Reconfiguring both switch interfaces to share the same native VLAN restores proper frame segregation and trunk connectivity.

Step-by-Step Solution

1
Analyze the syslog console error message
Identify that Switch-A is using VLAN 10 as its native VLAN on link GigabitEthernet0/1, whereas Switch-B is using VLAN 1.
Cisco Discovery Protocol (CDP) flags discrepancies when native VLAN configurations differ across a trunk.
2
Determine 802.1Q frame encapsulation behavior
Recognize that untagged frames leaving Switch-A on native VLAN 10 enter Switch-B untagged and are placed into Switch-B's configured native VLAN 1.
802.1Q trunking standard specifies that native VLAN traffic is forwarded without an IEEE 802.1Q header tag.
3
Identify the troubleshooting remediation steps
Configure identical native VLAN numbers on both switch interfaces forming the trunk.
Trunk interfaces must have matching native VLAN settings to maintain consistent Layer 2 domain boundaries.

Key Concept

802.1Q Trunk Native VLAN Mismatch Identification and Resolution
Question 1403Question

A network technician is troubleshooting a laptop that was moved from an executive office to a newly created conference room VLAN. The laptop cannot access internal resources, and executing `ipconfig /all` displays an IPv4 address of 169.254.88.15169.254.88.15 with a subnet mask of 255.255.0.0255.255.0.0. Which of the following statements correctly identify the cause of this issue and the appropriate next diagnostic step? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The host automatically self-assigned an Automatic Private IP Addressing (APIPA) address because it did not receive a lease response from a DHCP server.; The technician should verify if a DHCP relay agent (IP helper address) is configured on the router interface for the new conference room VLAN.

Answer

The workstation assigned itself an APIPA address because it failed to obtain a DHCP lease, and the network technician should check whether a DHCP relay agent (IP helper address) is configured on the router interface serving the new VLAN.
Addresses in the 169.254.0.0/16169.254.0.0/16 range are self-assigned APIPA addresses generated by client host operating systems when DHCP discovery fails. When a host is relocated to a new VLAN separated from the central DHCP server, DHCP broadcast requests fail unless a DHCP relay agent (IP helper address) is configured on the default gateway router interface to forward the packets.

Step-by-Step Solution

1
Examine the output of the command showing 169.254.88.15169.254.88.15.
Identify that addresses starting with 169.254.x.x169.254.x.x represent APIPA addresses.
APIPA is activated by the client operating system when DHCP broadcast requests yield no lease response.
2
Analyze the network scenario involving a newly provisioned VLAN.
Recognize that DHCP broadcasts cannot cross subnets without relay intervention.
Routers block broadcast traffic by default; a DHCP relay agent (IP helper address) must be enabled on the local router interface to forward requests to a central DHCP server.

Key Concept

Diagnosing APIPA address assignment and resolving cross-VLAN DHCP request failures using DHCP relay agents.
Question 1404Question

A network engineer is troubleshooting performance degradation on an enterprise Storage Area Network (SAN) uplink. After analyzing link metrics and performing diagnostic tests, the engineer successfully confirms their hypothesis that excessive frame errors are caused by an over-subscribed switch interface. Which of the following is the NEXT step the engineer should take according to the CompTIA troubleshooting methodology?

Show answer & explanation

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

Answer

Establish a plan of action to resolve the problem and identify potential effects.
According to the CompTIA troubleshooting methodology, once a theory of probable cause is tested and confirmed, the network professional must establish a plan of action to resolve the problem while identifying potential side effects before implementing changes.

Step-by-Step Solution

1
Identify the completed phase described in the scenario.
The engineer has completed gathering information (Step 1), forming a theory (Step 2), and testing the theory to confirm the root cause (Step 3).
Determining the completed step is necessary to select the immediate next step in the CompTIA sequence.
2
Determine the next sequential step in the CompTIA troubleshooting methodology.
Following Step 3 (Test the theory to determine cause), the immediate next step is Step 4: Establish a plan of action to resolve the problem and identify potential effects.
Network alterations require a clear plan of action to minimize disruption and avoid unintended consequences before executing changes.

Key Concept

CompTIA Troubleshooting Methodology Sequence
Estimated Time:1m 0s
Question 1405Question

A network technician replaces a damaged modular plug on a Category 6 UTP cable. A basic continuity test shows that all eight conductors line up end-to-end, but the network link suffers from severe Near-End Crosstalk (NEXT) and high packet loss. Which physical cabling mistake is the most likely cause of this issue?

Show answer & explanation

Answer: The conductor pairs were untwisted excessively before being inserted into the RJ-45 connector.

Answer

The conductor pairs were untwisted excessively before being inserted into the RJ-45 connector.
In twisted-pair Ethernet cabling, the tight twisting of conductor pairs provides cancellation against electromagnetic interference and crosstalk. When terminating a Category 6 cable, untwisting the pairs more than 0.5 inches (13 mm) destroys this shielding effect at the connector base, causing signals from one pair to bleed into adjacent pairs (Near-End Crosstalk). A basic continuity tester will still show a pass because electrical connectivity is maintained.

Step-by-Step Solution

1
Analyze the reported physical symptoms.
Electrical continuity passes across all pins, eliminating open breaks or short circuits as the primary fault.
Basic wiremap tests verify end-to-end pin conductivity.
2
Identify the root physical cause of Near-End Crosstalk (NEXT).
Excessive untwisting of wire pairs removes the natural electromagnetic cancellation provided by the twists.
Maintaining pair twisting up to the point of termination (within 0.5 inches / 13 mm for Cat 6) is mandatory to prevent NEXT.

Key Concept

Excessive untwisting of copper conductor pairs during RJ-45 connector termination causes Near-End Crosstalk (NEXT).
Question 1406Question

Match each network performance monitoring metric or telemetry mechanism on the left with its corresponding operational impact or functional behavior on the right.

Click a left item, then click its matching right item

Items

Jitter (Inter-packet Delay Variance)
Latency (Round-Trip Time)
Interface Packet Drops
Flow-Based Telemetry

Matches

Show answer & explanation

Answer

Jitter maps to irregular packet arrival intervals in voice traffic; Latency maps to total round-trip duration affecting interactive sessions; Interface Packet Drops map to buffer queue discards during bandwidth saturation; Flow-Based Telemetry maps to exporting aggregated traffic metadata records.
Each metric or mechanism matches its core diagnostic behavior: Jitter represents inter-packet delay variance (VoIP artifacts); Latency measures round-trip time (interactive delay); Interface Packet Drops represent queue buffer overflows during congestion; Flow-Based Telemetry collects session metadata records (IPFIX/NetFlow).

Step-by-Step Solution

1
Analyze Jitter characteristics
Identify that delay variance directly impacts real-time streaming and voice applications, matching right_1.
VoIP buffers require consistent inter-packet timing to reconstitute smooth audio streams.
2
Analyze Latency characteristics
Identify that overall delay from source to destination and back affects round-trip metrics and interactive responsiveness, matching right_2.
Round-Trip Time directly determines how quickly a client receives acknowledgment or output from a server.
3
Analyze Interface Packet Drops
Identify that drops on an interface signal queue buffer overruns caused by congestion, matching right_3.
When interface transmit/receive buffers fill completely, additional incoming frames are dropped.
4
Analyze Flow-Based Telemetry
Identify that IPFIX and NetFlow generate flow records summarizing 5-tuple session metrics without packet payloads, matching right_4.
Flow protocols stream statistical records of network traffic rather than full packet captures.

Key Concept

Network Performance Metrics and Telemetry Mechanisms
Question 1407Question

A network technician is troubleshooting an issue where a workstation fails to connect to an internal web application after a recent server migration. The technician executes two command-line utilities on the client workstation and receives the following output:

C:\> nslookup portal.company.local
Server: dns01.company.local
Address: 10.10.5.2

Name: portal.company.local
Address: 10.10.20.100

C:\> ping portal.company.local
Pinging portal.company.local [10.10.5.50] with 32 bytes of data:
Request timed out.

Based on the diagnostic output, which of the following is the most likely cause of this discrepancy?

Show answer & explanation

Answer: A stale cached entry or static entry in the client workstation's local resolution files is overriding DNS server queries.

Answer

A stale cached entry or static entry in the client workstation's local resolution files is overriding DNS server queries.
The nslookup utility bypasses local system resolution mechanisms (such as the client DNS cache and local HOSTS file) and queries the designated DNS server directly, returning the updated IP address (10.10.20.100). In contrast, standard applications and utilities like ping rely on the operating system's DNS client service, which checks local cache and static HOSTS file entries first. The discrepancy indicates that the local workstation is resolving the host via a stale cached entry or static file entry.

Step-by-Step Solution

1
Analyze the nslookup output.
The nslookup command queries the primary DNS server directly and obtains the current IP address 10.10.20.100 for portal.company.local.
nslookup bypasses the OS client resolver cache and local HOSTS file by default.
2
Analyze the ping output.
The ping command attempts to send packets to 10.10.5.50, which is an outdated IP address.
Standard OS applications use the local resolver mechanism, which checks the HOSTS file and local DNS cache before querying external DNS servers.
3
Synthesize the cause of the discrepancy.
The workstation is using stale cached DNS data or a hardcoded entry in the HOSTS file for hostname resolution.
Clearing the cache using ipconfig /flushdns or removing the static entry from the HOSTS file will align local resolution with the authoritative DNS server.

Key Concept

DNS Name Resolution Order and Client Resolver Cache vs. Direct Server Queries
Estimated Time:1m 30s
Question 1408Question

A client workstation on VLAN 10 (192.168.10.45/24192.168.10.45/24) cannot reach a database server located on VLAN 30 (10.0.30.100/2410.0.30.100/24) across an enterprise Layer 3 switch with Access Control Lists (ACLs). Following the CompTIA network troubleshooting methodology, place the diagnostic and remediation actions 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 logical order begins with checking local host configuration, testing local default gateway reachability, performing a traceroute to identify the blocking network hop, inspecting the switch routing table and ACLs at that hop, and finally applying the configuration fix and verifying service connectivity.
The correct sequence follows the CompTIA troubleshooting methodology by starting at the local host (verifying host IP settings), testing the local link to the default gateway, executing path analysis to pinpoint the failure point (traceroute), inspecting infrastructure configuration files (routes and ACLs), and concluding with remediation and verification.

Step-by-Step Solution

1
Check host IP configuration
Confirms the host has valid IP settings and points to the correct gateway IP.
Always eliminate basic host-level misconfigurations before investigating network infrastructure.
2
Test local default gateway reachability using ICMP ping
Verifies Layer 2 link integrity and local router interface accessibility.
If the local gateway does not respond, remote routing cannot be evaluated.
3
Perform path tracing with traceroute
Identifies the exact intermediate router hop where communication fails.
Traceroute narrows down the problem domain to a specific gateway or filtering device.
4
Examine device routing tables and active ACL statements
Reveals root cause such as a missing route entry or an explicit/implicit ACL block.
Diagnoses the precise administrative or policy configuration issue on the failing node.
5
Remediate configuration and perform end-to-end test
Restores traffic flow and confirms application access is functional.
Finalizes the troubleshooting methodology cycle by validating system functionality.

Key Concept

Sequential isolation of routing, gateway, and ACL issues using CompTIA troubleshooting methodology
Estimated Time:2m 0s
Question 1409Question

A network administrator is securing a newly deployed edge router at a remote facility. The organization requires central monitoring of system health over public networks while enforcing payload encryption and cryptographic user authentication. Additionally, legacy unencrypted protocols must be removed. Which configuration strategy best satisfies these hardening requirements for network monitoring?

Show answer & explanation

Answer: Configure SNMPv3 with authPriv mode using strong passphrase hashing and AES payload encryption.

Answer

Configure SNMPv3 with authPriv mode using strong passphrase hashing and AES payload encryption.
Configuring SNMPv3 with the authPriv security level ensures both user authentication (using SHA or MD5) and payload encryption (using AES or DES). This guarantees that network monitoring statistics and system management traffic cannot be eavesdropped on or modified in transit across untrusted network links.

Step-by-Step Solution

1
Identify security requirements for management monitoring
Requirements specify central health monitoring over untrusted networks with authentication and payload encryption.
Cleartext protocols expose administrative credentials and telemetry to eavesdropping.
2
Evaluate protocol features for SNMP versions
SNMPv1 and SNMPv2c use cleartext community strings (no encryption). SNMPv3 supports noAuthNoPriv, authNoPriv, and authPriv.
Only SNMPv3 authPriv provides both message integrity/authentication and data privacy (encryption).
3
Select the hardening control matching all criteria
SNMPv3 in authPriv mode meets both cryptographic authentication and AES payload encryption mandates.
This establishes robust management plane hardening for monitoring over public or shared network infrastructure.

Key Concept

SNMP Security Modes and Management Plane Hardening
Estimated Time:1m 0s
Question 1410Question

A user's workstation is assigned the static IP address 192.168.10.45192.168.10.45 with a subnet mask of 255.255.255.0255.255.255.0 (/24). The user can successfully communicate with other devices on the local subnet, but cannot access any remote subnets or external websites. Running diagnostic checks shows that the workstation's default gateway is configured as 192.168.20.1192.168.20.1. Which of the following is the root cause of the gateway connectivity failure?

Show answer & explanation

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

Answer

The configured default gateway address resides on a different IP subnet than the workstation.
For a host to communicate with remote networks, its default gateway IP address must be an IP address located on the same local subnet. Because 192.168.10.45/24192.168.10.45/24 and 192.168.20.1/24192.168.20.1/24 are on separate subnets, local ARP requests for the gateway fail and traffic destined outside the subnet cannot be routed.

Step-by-Step Solution

1
Determine the host's subnet boundary.
For IP 192.168.10.45192.168.10.45 with mask 255.255.255.0255.255.255.0 (/24), the network segment is 192.168.10.0/24192.168.10.0/24, covering usable host IPs from 192.168.10.1192.168.10.1 to 192.168.10.254192.168.10.254.
Host IP configuration dictates which addresses are considered local vs remote.
2
Evaluate the configured default gateway address.
The gateway address 192.168.20.1192.168.20.1 belongs to the 192.168.20.0/24192.168.20.0/24 network segment.
A host must be on the same Layer 3 subnet as its default gateway to send frames directly to the gateway's MAC address.
3
Identify the underlying connectivity problem.
The host cannot communicate with the gateway because it expects its default gateway to be reachable within its local broadcast domain.
A misconfigured gateway IP on a foreign subnet prevents all off-subnet forwarding.

Key Concept

Default Gateway Subnet Alignment
Question 1411Question

A network engineer provisions a new subinterface `GigabitEthernet0/0.40` on a branch router to serve an isolated IoT subnet (172.16.40.0/24172.16.40.0/24). Devices connected to VLAN 40 are unable to reach external resources and auto-assign link-local IPv4 addresses in the 169.254.x.x169.254.x.x range. A terminal capture on the router shows the following configuration:

text
interface GigabitEthernet0/0.10
description Corporate_Users
encapsulation dot1Q 10
ip address 172.16.10.1 255.255.255.0
ip helper-address 10.10.10.50
!
interface GigabitEthernet0/0.40
description IoT_Devices
encapsulation dot1Q 40
ip address 172.16.40.1 255.255.255.0

Existing client workstations on `GigabitEthernet0/0.10` receive leases dynamically from the central DHCP server at 10.10.10.5010.10.10.50 without issue. Which configuration change on the branch router will resolve the IP addressing failure for VLAN 40?

Show answer & explanation

Answer: Add the command `ip helper-address 10.10.10.50` under the `GigabitEthernet0/0.40` subinterface interface configuration mode.

Answer

Add the command `ip helper-address 10.10.10.50` under the `GigabitEthernet0/0.40` subinterface interface configuration mode.
DHCP broadcasts (UDP ports 67 and 68) are confined to their local Layer 2 broadcast domain and do not pass through Layer 3 boundaries. Subinterface `GigabitEthernet0/0.40` acts as the default gateway for VLAN 40. Without the `ip helper-address` command on this specific subinterface, the router drops the client DHCPDISCOVER broadcast frames. Adding `ip helper-address 10.10.10.50` configures the router to act as a DHCP relay agent for VLAN 40, converting incoming client broadcasts into unicast UDP packets sent directly to the central DHCP server at 10.10.10.5010.10.10.50.

Step-by-Step Solution

1
Analyze client symptoms and subinterface configuration.
IoT devices on VLAN 40 receive 169.254.x.x addresses, indicating APIPA assignment caused by a failure to complete the DHCP DORA process.
DHCP client broadcast requests (DHCPDISCOVER) are stopped by default at Layer 3 router interfaces unless a relay agent is configured.
2
Compare working subinterface `GigabitEthernet0/0.10` with non-working subinterface `GigabitEthernet0/0.40`.
`GigabitEthernet0/0.10` has `ip helper-address 10.10.10.50` configured, while `GigabitEthernet0/0.40` is missing any relay statement.
DHCP relay agent directives must be explicitly applied to each routed logical interface/subinterface that receives client broadcasts.
3
Identify the required remediation step.
Applying `ip helper-address 10.10.10.50` to subinterface `GigabitEthernet0/0.40` allows the router to convert client UDP broadcasts into unicast packets routed to the centralized server.
This establishes the necessary Layer 3 relay mechanism for VLAN 40.

Key Concept

DHCP Relay Agent and IP Helper Placement on VLAN Subinterfaces
Estimated Time:2m 0s
Question 1412Question

A network administrator has confirmed through diagnostic testing that an outdated firmware version on a core distribution switch caused intermittent BGP route flapping. Having confirmed this theory, the administrator is now preparing to execute the 'Establish a plan of action to resolve the problem and identify potential effects' step in the CompTIA troubleshooting methodology. Which of the following specific tasks should be conducted as part of this step? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Identify potential side effects and downstream consequences of upgrading the switch firmware during production hours.; Develop a detailed rollback procedure to restore previous operations if the firmware installation fails.

Answer

The correct actions are identifying potential side effects/downstream impacts of the switch firmware upgrade and developing a detailed rollback procedure to restore previous operations if the installation fails.
Establishing a plan of action (Step 4) specifically involves designing a clear, step-by-step remediation path, assessing potential side effects on network infrastructure, and preparing rollback/contingency plans prior to making changes.

Step-by-Step Solution

1
Analyze the target phase of the CompTIA Troubleshooting Methodology
The current scenario is at Step 4: Establish a plan of action to resolve the problem and identify potential effects.
The technician has already identified the problem (Step 1), established a theory (Step 2), and tested the theory to confirm the cause (Step 3).
2
Evaluate candidate troubleshooting tasks against Step 4 requirements
Establishing a plan of action requires building a structured remediation plan, analyzing potential side effects, and creating a backup/rollback plan before implementation.
Anticipating unintended consequences and establishing contingency rollback plans ensures operational continuity during implementation.
3
Filter out tasks belonging to other methodology phases
User interviews (Step 1), full system verification/prevention (Step 5), and ticketing documentation (Step 6) are placed in different phases of the 6-step framework.
CompTIA methodology strictly sequences tasks to prevent unnecessary risk or premature action.

Key Concept

CompTIA 6-Step Troubleshooting Methodology (Step 4: Establish Plan of Action)
Question 1413Question

A network technician is provisioning an isolated Wi-Fi network for temporary contractors at a branch office. The organization requires protection against offline dictionary attacks and passive eavesdropping, but explicitly wants to avoid the operational complexity of deploying an 802.1X RADIUS server or digital certificates. Which wireless security standard and authentication mechanism best meets these specifications?

Show answer & explanation

Answer: WPA3-Personal utilizing Simultaneous Authentication of Equals (SAE)

Answer

WPA3-Personal utilizing Simultaneous Authentication of Equals (SAE)
WPA3-Personal implements Simultaneous Authentication of Equals (SAE) in place of the static pre-shared key four-way handshake used in WPA2. SAE leverages a Dragonfly key exchange that mitigates offline dictionary attacks even when simple passphrases are used and delivers forward secrecy for session traffic without requiring 802.1X RADIUS servers.

Step-by-Step Solution

1
Analyze the technical requirements and constraints presented in the scenario.
The requirements specify mitigating offline dictionary attacks without implementing an 802.1X RADIUS infrastructure or client certificate management.
Identifying constraints eliminates both legacy vulnerable standards and complex enterprise authentication modes.
2
Evaluate wireless authentication protocols against the requirement set.
WPA3-Personal replaces the legacy WPA2 pre-shared key handshake with Simultaneous Authentication of Equals (SAE).
SAE incorporates the Dragonfly key exchange algorithm, which resists dictionary attacks and guarantees forward secrecy while retaining passphrase convenience.

Key Concept

WPA3-Personal SAE vs. WPA3-Enterprise RADIUS authentication mechanisms
Estimated Time:1m 15s
Question 1414Question

A network administrator is configuring an extended IPv4 Access Control List (ACL) on a gateway router to secure a DMZ web server at IP address 10.80.1.20/2410.80.1.20/24. The security policy requires allowing inbound web traffic (HTTPS) from any external source, and allowing remote administration (SSH) strictly from the internal network management subnet (172.16.50.0/24172.16.50.0/24). All other inbound traffic must be blocked. Which TWO of the following extended ACL statements must be included to satisfy these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: permit tcp any host 10.80.1.20 eq 443; permit tcp 172.16.50.0 0.0.0.255 host 10.80.1.20 eq 22

Answer

The correct ACL entries are 'permit tcp any host 10.80.1.20 eq 443' and 'permit tcp 172.16.50.0 0.0.0.255 host 10.80.1.20 eq 22'.
The security policy requires allowing HTTPS (TCP port 443) from any source to the DMZ server IP (10.80.1.2010.80.1.20), which is fulfilled by 'permit tcp any host 10.80.1.20 eq 443'. Additionally, allowing SSH (TCP port 22) strictly from the management subnet (172.16.50.0/24172.16.50.0/24) requires matching the source subnet with wildcard mask 0.0.0.255 directed to the server on destination port 22, fulfilled by 'permit tcp 172.16.50.0 0.0.0.255 host 10.80.1.20 eq 22'.

Step-by-Step Solution

1
Identify transport protocols and destination ports for the required services.
HTTPS uses TCP port 443, and SSH uses TCP port 22.
Extended IPv4 ACLs inspect Layer 4 protocol headers to filter traffic by port number.
2
Construct the rule for public HTTPS traffic.
'permit tcp any host 10.80.1.20 eq 443'
The source is 'any', the destination host is 10.80.1.2010.80.1.20, and the destination port is 443.
3
Construct the rule for restricted SSH administration traffic.
'permit tcp 172.16.50.0 0.0.0.255 host 10.80.1.20 eq 22'
The source network 172.16.50.0/24172.16.50.0/24 requires wildcard mask 0.0.0.255, targeting destination host 10.80.1.2010.80.1.20 on port 22.

Key Concept

Extended Access Control List (ACL) Syntax and Layer 4 Port Filtering
Question 1415Question

A network administrator is troubleshooting an issue where internal workstations on subnet 10.10.10.0/2410.10.10.0/24 cannot access a web server at 10.10.50.25/2410.10.50.25/24 using HTTPS. Upon inspecting the inbound Access Control List (ACL) on the destination interface, the administrator views the following configuration:

text
access-list 105 permit tcp 10.10.10.0 0.0.0.255 host 10.10.50.25 eq 80
access-list 105 deny ip any host 10.10.50.25
access-list 105 permit tcp 10.10.10.0 0.0.0.255 host 10.10.50.25 eq 443

Which of the following describes the root cause of the connection failure?

Show answer & explanation

Answer: The rule permitting HTTPS traffic on port 443 is shadowed by a preceding explicit deny statement.

Answer

The rule permitting HTTPS traffic on port 443 is shadowed by a preceding explicit deny statement.
Router access control lists evaluate rules in top-down order until the first matching rule is found. In this configuration, line 20 explicitly blocks all IP traffic from any source to host 10.10.50.2510.10.50.25. Because line 20 is evaluated before line 30, any incoming HTTPS packet on port 443 matches line 20 and is dropped immediately, rendering line 30 ineffective (shadowed). To resolve this, the permit rule for port 443 must be placed before the broad deny rule.

Step-by-Step Solution

1
Analyze the sequential evaluation order of the ACL entries.
Network ACLs process packets sequentially from top to bottom and stop evaluating as soon as a matching rule is encountered.
Top-down processing determines which rule action applies to matched traffic.
2
Trace HTTPS packet matching through the rule list.
An HTTPS packet targeted at port 443 fails to match line 10 (port 80), but matches line 20 (deny ip any host 10.10.50.25).
Line 20 covers all IP protocols and source addresses destined for the server host.
3
Identify why line 30 is ineffective.
Line 30 is shadowed because matching traffic has already been dropped by line 20.
Rules placed after a broader matching deny statement will never be evaluated.

Key Concept

ACL Rule Shadowing and Sequential Processing
Question 1416Question

A network administrator is troubleshooting an issue where database servers deployed on a new broadcast domain (VLAN 104, 10.104.0.0/2210.104.0.0/22) fail to acquire dynamic IPv4 addresses and assign themselves 169.254.x.x169.254.x.x addresses instead. A packet capture on the local router subinterface `GigabitEthernet0/0.104` shows incoming broadcast DHCP DISCOVER frames from clients, but no DHCP OFFER packets return. The central DHCP server is located on VLAN 10 (10.10.10.210.10.10.2). The configuration of the local subinterface is as follows:

interface GigabitEthernet0/0.104
encapsulation dot1Q 104
ip address 10.104.0.1 255.255.252.0

Which of the following actions should the network administrator perform to resolve this issue and enable dynamic address assignment for clients in VLAN 104? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure the command `ip helper-address 10.10.10.2` under the `GigabitEthernet0/0.104` subinterface.; Ensure intermediate firewalls and router Access Control Lists (ACLs) permit UDP ports 67 and 68 traffic between the router relay interface and the central DHCP server.

Answer

The administrator must configure the DHCP relay agent using `ip helper-address 10.10.10.2` on the client-facing router subinterface `GigabitEthernet0/0.104` and ensure that router ACLs/firewalls allow UDP ports 67 and 68 traffic between the relay agent and the central DHCP server.
When clients are located on a separate subnet or VLAN from the central DHCP server, routers block the initial client DHCP DISCOVER broadcast packets by default. To fix this, the router subinterface serving as the client gateway (`GigabitEthernet0/0.104`) must be configured with `ip helper-address 10.10.10.2` to convert local broadcasts into unicast packets directed to the DHCP server. Additionally, because DHCP relay relies on UDP ports 67 and 68, any network ACLs or firewalls along the traffic path between the router interface and the DHCP server must explicitly permit UDP 67/68 traffic.

Step-by-Step Solution

1
Analyze client symptoms and packet capture output
Clients acquiring 169.254.x.x (APIPA) addresses indicates complete DHCP lease acquisition failure. DHCP DISCOVER broadcast packets reach the default gateway subinterface but cannot traverse Layer 3 boundaries without a relay agent.
DHCP DISCOVER messages are Layer 2/3 broadcasts (255.255.255.255) that routers drop by default.
2
Identify the missing router subinterface configuration
Configuring `ip helper-address 10.10.10.2` on `GigabitEthernet0/0.104` intercepts client broadcast requests and unicasts them to the DHCP server at 10.10.10.2.
Cross-subnet DHCP deployment requires explicit relay agent configuration on the client's gateway interface.
3
Verify network transport security and ACL rules between relay agent and server
Ensuring UDP ports 67 (DHCP server) and 68 (DHCP client) are allowed on intermediate ACLs guarantees unhindered transmission of DHCP DISCOVER/REQUEST unicast relays and server DHCP OFFER/ACK replies.
Firewalls or implicit deny statements in router ACLs blocking UDP 67/68 prevent communication between the relay agent and the DHCP server.

Key Concept

DHCP Relay (IP Helper) and Traffic Permitting across Layer 3 Boundaries
Question 1417Question

A network administrator attempts to force Switch-B to become the primary Spanning Tree Protocol (STP) root bridge for VLAN 10 during an upcoming maintenance window. The administrator executes the CLI command `spanning-tree vlan 10 priority 61440` on Switch-B. After taking the existing core switch offline, host traffic experiences unexpected latency, and diagnostic logs reveal that Switch-C—which has a default configuration—was elected root bridge instead of Switch-B. Switch-C has an STP priority of 32768 for VLAN 10. Which of the following explains why Switch-C became the root bridge instead of Switch-B?

Show answer & explanation

Answer: Spanning Tree Protocol elects the root bridge based on the lowest priority numerical value, making Switch-C's default priority of 32768 preferred over Switch-B's priority of 61440.

Answer

Spanning Tree Protocol elects the root bridge based on the lowest numerical priority value. Setting Switch-B's priority to 61440 made it less preferred than Switch-C's default priority of 32768.
In Spanning Tree Protocol (IEEE 802.1D / 802.1w), the root bridge election selects the switch with the lowest Bridge ID, which is composed of the priority value and MAC address. Because the administrator set Switch-B's priority to 61440, Switch-C (with the default priority of 32768) possessed a lower priority value and was successfully elected root bridge.

Step-by-Step Solution

1
Analyze the Bridge ID structure used in STP root bridge selection.
The Bridge ID consists of a configurable Priority value plus the switch MAC address.
STP uses Bridge IDs to determine which switch in the Layer 2 domain serves as the root.
2
Compare the priority values configured on Switch-B and Switch-C.
Switch-B has a priority of 61440, while Switch-C has the default priority of 32768.
The administrator incorrectly assumed a higher numerical value increases election priority.
3
Apply STP election criteria (lowest Bridge ID wins).
Switch-C wins the root bridge election because 32768 is numerically lower than 61440.
Lower priority numbers represent higher precedence in Spanning Tree Protocol.

Key Concept

STP Root Bridge Priority Selection
Question 1418Question

A network administrator is troubleshooting a client workstation that receives a name resolution error when attempting to reach an internal portal at `hrportal.contoso.com`. In what sequence should the administrator execute the following steps to systematically isolate the issue according to standard operating system name resolution precedence?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows operating system resolution precedence: first inspect the local static HOSTS file, second flush the OS DNS resolver cache, third perform a direct `nslookup` against the DNS server, and fourth verify Layer 3 IP reachability using `ping`.
Troubleshooting follows OS resolution precedence: checking local HOSTS entries first, clearing the local resolver cache second, querying the DNS server directly via `nslookup` third, and testing IP connectivity via `ping` fourth once an IP is obtained.

Step-by-Step Solution

1
Examine the local HOSTS file.
Determines whether a local static text mapping is overriding network DNS resolution.
The OS evaluates the local HOSTS file prior to checking local DNS cache or issuing network queries.
2
Flush the client DNS cache using `ipconfig /flushdns`.
Purges cached negative responses or outdated A/AAAA records.
If no static HOSTS entry exists, the OS checks the local cache next.
3
Perform a direct DNS lookup using `nslookup hrportal.contoso.com`.
Verifies if the configured local DNS server has a valid, reachable record.
Bypasses local client caching mechanisms to isolate DNS server availability and record accuracy.
4
Test IP connectivity using `ping` to the resolved IP address.
Confirms whether network routing, firewalls, and server ports allow communication.
IP-level testing is only meaningful once name resolution yields an IP address.

Key Concept

OS Name Resolution Order and Systematic DNS Troubleshooting Sequence
Question 1419Question

A network administrator is troubleshooting an issue where a client workstation cannot reach an internal database server located at 172.28.15.100172.28.15.100. The administrator collects the host settings and router interface details:

Host Settings:
- IP Address: 10.50.10.4510.50.10.45
- Subnet Mask: 255.255.255.192255.255.255.192 (/26/26)
- Default Gateway: 10.50.10.6510.50.10.65

Router Interface (GigabitEthernet0/0) & Inbound ACL:
- Interface IP: 10.50.10.1/2610.50.10.1/26
- Applied Inbound Access Control List:
- `line 10: permit tcp 10.50.10.0 0.0.0.63 host 172.28.15.100 eq 3306`
- `line 20: deny ip any any`

Which TWO of the following issues are directly preventing or obstructing successful communication and verification between the workstation and the database server?

Select all that apply

Show answer & explanation

Answer: The host's configured default gateway (10.50.10.6510.50.10.65) falls outside the usable IP range (10.50.10.110.50.10.110.50.10.6210.50.10.62) of the configured /26/26 subnet.; The inbound ACL on GigabitEthernet0/0 permits only TCP port 3306, causing standard diagnostic ICMP ping tests to be blocked by the explicit deny rule.

Answer

The host's default gateway is misconfigured outside its /26/26 subnet boundary, and the router ACL drops ICMP diagnostic traffic due to permitting only TCP port 3306.
The host cannot reach external networks because its gateway IP (10.50.10.6510.50.10.65) is outside its local /26/26 subnet (10.50.10.0/2610.50.10.0/26, usable IPs 10.50.10.110.50.10.110.50.10.6210.50.10.62). Additionally, network troubleshooting via ICMP ping fails because the inbound ACL only permits TCP port 3306 traffic, causing ICMP to hit the explicit deny rule on line 20.

Step-by-Step Solution

1
Analyze the subnet boundaries for the host IP configuration.
A subnet mask of 255.255.255.192255.255.255.192 (/26/26) yields 256192=64256 - 192 = 64 addresses per subnet. Subnet range: 10.50.10.010.50.10.0 to 10.50.10.6310.50.10.63. Usable range: 10.50.10.110.50.10.1 to 10.50.10.6210.50.10.62.
The configured default gateway 10.50.10.6510.50.10.65 resides on subnet 10.50.10.64/2610.50.10.64/26, making it unreachable to the host on 10.50.10.45/2610.50.10.45/26.
2
Evaluate the Access Control List (ACL) entries on interface GigabitEthernet0/0.
Line 10 permits only `tcp` traffic on port 3306. ICMP traffic hits line 20 (`deny ip any any`).
Network administrators commonly use `ping` (ICMP) for initial diagnostic tests. Since ICMP is not explicitly permitted before line 20, ICMP diagnostic traffic will fail even if Layer 3 routing is established.

Key Concept

Subnet Boundary & Default Gateway Verification, ACL Rule Filtering
Question 1420Question

A network technician is investigating intermittent connectivity and framing errors on a trunk link between two distribution switches. The technician has established a theory that a native VLAN mismatch is causing untagged traffic to drop and has confirmed this cause by inspecting packet captures on both switch interfaces. According to the CompTIA troubleshooting methodology, which of the following actions should the technician take NEXT?

Show answer & explanation

Answer: Establish a plan of action to align the native VLAN configurations across the trunk link and identify potential side effects.

Answer

Establish a plan of action to align the native VLAN configurations across the trunk link and identify potential side effects.
The technician has completed Step 3 of the CompTIA troubleshooting methodology by testing the theory and confirming that a native VLAN mismatch is the root cause. The next step (Step 4) requires establishing a plan of action to resolve the issue while identifying potential side effects before implementing the solution.

Step-by-Step Solution

1
Determine the current stage of the troubleshooting process from the scenario stem.
The technician has established a theory and tested it via packet captures to confirm the root cause, satisfying Step 3 (Test the theory to determine cause).
Identifying the completed step is necessary to accurately select the next logical phase.
2
Map the next phase in the official CompTIA 6-step troubleshooting methodology.
Step 1: Identify problem → Step 2: Establish theory → Step 3: Test theory → Step 4: Establish plan of action & identify potential effects → Step 5: Verify full system functionality & preventive measures → Step 6: Document findings.
CompTIA standards require strictly following sequential methodology.
3
Select the correct action corresponding to Step 4.
Formulating a plan of action to change the native VLAN settings while considering potential network disruptions represents Step 4.
A plan of action ensures that changes are systematically planned and risks are identified before implementation.

Key Concept

CompTIA Troubleshooting Methodology Sequence
PreviousPage 71 / 112Next
All practice questions — CompTIA Network+ | Examkin