All practice questions

2237 questions

Question 1521Question

A network technician is diagnosing host reachability issues and executes a query using the `dig` command-line utility on a Linux workstation to verify name resolution for `app.corp.local`:

text
$ dig app.corp.local

; <<>> DiG 9.18.1-1-Debian <<>> app.corp.local
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41205
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

;; AUTHORITY SECTION:
corp.local. 3600 IN SOA ns1.corp.local. admin.corp.local. 2026072601 7200 3600 1209600 3600

;; Query time: 12 msec
;; SERVER: 192.168.10.5#53(192.168.10.5)

Which of the following describes the root cause of the name resolution failure based on the command output?

Show answer & explanation

Answer: The domain zone exists, but no IPv4 host (A) record is configured for the requested hostname.

Answer

The target domain zone exists on the authoritative server, but no IPv4 host (A) record is defined for the requested hostname.
In `dig` utility output, a header status of `NOERROR` paired with `ANSWER: 0` and an authoritative `SOA` record returned in the `AUTHORITY` section indicates a NODATA condition. This occurs when the DNS server is reachable and holds the domain zone, but no resource record matching the requested name and record type exists.

Step-by-Step Solution

1
Examine the dig command header and flags
The header status displays NOERROR with query time 12 msec from server 192.168.10.5.
This confirms that network connectivity exists and the DNS server responded successfully to the query.
2
Inspect the ANSWER and AUTHORITY sections
ANSWER is 0, while the AUTHORITY section returns the zone Start of Authority (SOA) record.
This condition represents a DNS NODATA response, confirming that the zone `corp.local` is present on the server, but the specified hostname `app.corp.local` has no corresponding A record entry.

Key Concept

DNS NODATA Response and Dig Output Interpretation
Estimated Time:1m 30s
Question 1522Question

A network engineer is analyzing several Layer 2 switching and trunking issues across an enterprise network. Match each observed switch diagnostic indicator or log message on the left to its underlying root cause on the right.

Click a left item, then click its matching right item

Items

Console log repeatedly displays %CDP-4-NATIVE_VLAN_MISMATCH while untagged management frames spill into inappropriate VLANs across the inter-switch link.
Interface statistics report a high count of late collisions, duplex mismatch symptoms, and frame check sequence (FCS) errors on a link set to full-duplex.
A non-root switch port unexpectedly transitions to an STP Blocking state after receiving BPDUs with a bridge priority of 4096 from an unauthorized access switch.
Tagged traffic for VLAN 50 is dropped across an 802.1Q trunk interface, while untagged native traffic and other tagged VLANs transit normally.

Matches

Show answer & explanation

Answer

Each diagnostic indicator corresponds directly to a specific Layer 2 misconfiguration: Native VLAN mismatch CDP logs indicate differing native VLAN configurations across the trunk; late collisions indicate an autonegotiation mismatch resulting in half-duplex operation on one peer; unexpected STP blocking indicates a superior BPDU causing root bridge re-election; and specific tagged VLAN traffic dropping indicates pruning via the trunk allowed VLAN list.
The correct pairings accurately associate specific diagnostic output to their root causes: %CDP-4-NATIVE_VLAN_MISMATCH directly indicates conflicting native VLAN configurations on trunk endpoints; late collision counters indicate a duplex mismatch where one end operates half-duplex; unexpected STP blocking states result from receiving superior BPDUs with a lower bridge priority; and isolated VLAN traffic dropping across a trunk indicates an incomplete trunk allowed VLAN list.

Step-by-Step Solution

1
Analyze the CDP log message regarding native VLAN mismatch.
Identify that 802.1Q trunking sends native VLAN traffic untagged. If native VLAN IDs differ on opposite sides, CDP logs an explicit mismatch error.
Matching native VLAN configurations are required on both ends of an 802.1Q trunk for proper untagged frame processing.
2
Examine interface collision counters and error types.
Recognize that late collisions (collisions occurring after transmitting the first 512 bits / 64 bytes of a frame) are a definitive diagnostic indicator of a duplex mismatch, typically caused when one port is hardcoded to full-duplex and the connected port falls back to half-duplex autonegotiation.
Full-duplex interfaces do not test for carrier sense or collisions, transmitting while the half-duplex side is mid-frame.
3
Evaluate Spanning Tree Protocol (STP) state changes.
Determine that receiving a BPDU with a priority value of 4096 (lower than the default 32768) represents a superior BPDU, forcing STP topology re-convergence and altering port blocking states.
STP elects the switch with the lowest Bridge ID (Priority + MAC address) as the root bridge.
4
Correlate selective VLAN dropping on trunk links.
Confirm that when specific VLAN traffic is dropped while other VLANs succeed, the affected VLAN ID has been omitted from the allowed list configured on the trunk port.
Trunk interfaces only forward traffic for VLANs explicitly permitted in their allowed VLAN list.

Key Concept

Layer 2 VLAN, Trunking, and STP Troubleshooting Indicators
Question 1523Question

Following a rack migration inside a data center, a 10GBASE-SR OM4 multimode fiber patch run connecting two distribution switches experiences high rates of frame check sequence (FCS) errors and intermittent link flapping. An optical power meter confirms that overall received optical signal power is within acceptable decibel-milliwatt (dBm) thresholds, and inspecting connector end-faces shows no contamination. Which diagnostic tool should the network engineer use to locate the exact position and measure the magnitude of localized optical reflections or physical macrobends along the concealed cable run?

Show answer & explanation

Answer: Optical Time-Domain Reflectometer (OTDR)

Answer

An Optical Time-Domain Reflectometer (OTDR) is the required tool because it analyzes Rayleigh backscattering and Fresnel reflections to pinpoint exact distance measurements and attenuation loss for physical fiber faults.
An Optical Time-Domain Reflectometer (OTDR) injects light pulses into an optical fiber and analyzes the backscattered and reflected light returning along the strand. By measuring the timing and intensity of these reflections, an OTDR creates a trace graph that precisely locates high-loss events (such as macrobends, bad connectors, or tight cable ties) in terms of exact distance from the tester.

Step-by-Step Solution

1
Analyze the reported link symptoms and media type.
The issue involves a multimode optical fiber link experiencing FCS errors and intermittent link flapping despite acceptable total optical power levels.
This indicates localized physical impairments (such as a tight bend radius or faulty splice point) that cause signal distortion/reflection rather than complete signal loss.
2
Evaluate the capabilities of potential optical diagnostic tools.
An OPM only provides aggregate end-to-end power measurements, whereas an OTDR characterizes events along the entire length of the fiber strand.
OTDR injection of optical pulses allows precise distance mapping to specific reflective or non-reflective loss events.
3
Select the correct physical layer troubleshooting tool.
The Optical Time-Domain Reflectometer (OTDR) is chosen.
It is specifically designed for optical fiber reflection event localization, unlike copper TDRs or simple tone probes.

Key Concept

Fiber Optic Fault Localization with OTDR
Estimated Time:2m 0s
Question 1524Question

A network engineer is responding to an enterprise network outage affecting internal application access after an infrastructure update. Arrange the following administrative troubleshooting actions in the correct sequence according to the official CompTIA troubleshooting methodology, starting from the earliest phase to the final phase.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence follows CompTIA's official 6-step troubleshooting methodology: 1. Identify the problem (gather symptoms and duplicate the issue), 2. Establish a theory of probable cause (question the obvious/OSI layer analysis), 3. Test the theory to determine the cause (simulate in a lab), 4. Establish a plan of action to resolve the problem and implement the solution (develop change plan and deploy rollback/fix), 5. Verify full system functionality and implement preventive measures (confirm user access and configure alerts), and 6. Document findings, actions, and outcomes (log entry in ticket system).
CompTIA Network+ strictly requires adhering to the six sequential steps of troubleshooting: 1. Identify the problem (gathering symptoms), 2. Establish a theory of probable cause (evaluating hypotheses), 3. Test the theory (confirming root cause in lab/test environment), 4. Establish a plan of action and implement the solution (change control execution), 5. Verify full system functionality and implement preventive measures (end-to-end testing and monitoring), and 6. Document findings, actions, and outcomes (ticketing log update).

Step-by-Step Solution

1
Perform initial user interviews, duplicate failure symptoms, and check recent change logs.
Defines problem scope and boundaries (CompTIA Step 1: Identify the problem).
Troubleshooting must begin with clear problem identification before formulating theories.
2
Analyze symptoms and question obvious physical/logical factors to build a working hypothesis.
Establishes probable cause theory focused on switch ACL misconfiguration (CompTIA Step 2: Establish a theory of probable cause).
Formulating a targeted hypothesis prevents unguided and disruptive changes.
3
Test the hypothesis in a lab or staging setup without impacting production traffic.
Confirms the exact cause of the failure (CompTIA Step 3: Test the theory to determine cause).
Testing validates the theory before executing modifications on live network infrastructure.
4
Draft a resolution procedure with change control approval and execute the configuration fix.
Implements the solution safely (CompTIA Step 4: Establish a plan of action to resolve the problem and implement the solution).
Structured implementation minimizes risks of unintended secondary outages.
5
Test system reachability across affected user segments and install proactive monitoring.
Ensures full system operation and prevents future occurrences (CompTIA Step 5: Verify full system functionality and, if applicable, implement preventive measures).
Verification ensures the issue is resolved completely and won't reoccur immediately.
6
Update incident tickets and knowledge base articles with configuration details and root cause.
Completes the lifecycle documentation (CompTIA Step 6: Document findings, actions, and outcomes).
Documentation provides historical context and reference for future troubleshooting.

Key Concept

CompTIA Troubleshooting Methodology
Question 1525Question

A network administrator must configure a top-to-bottom sequence of rules in an extended IPv4 Access Control List (ACL) applied inbound on a router interface serving the internal user VLAN (192.168.10.0/24192.168.10.0/24). The ACL must enforce the following security policies for traffic destined to the DMZ web server (10.0.0.50/3210.0.0.50/32):

1. Host 192.168.10.5192.168.10.5 must be explicitly allowed HTTPS access (TCP/443TCP/443).
2. Host 192.168.10.5192.168.10.5 must be explicitly denied HTTP access (TCP/80TCP/80).
3. All other hosts on the 192.168.10.0/24192.168.10.0/24 subnet must be allowed HTTP access (TCP/80TCP/80).
4. All other traffic targeting the DMZ subnet (10.0.0.0/2410.0.0.0/24) must be blocked.

Arrange the Access Control List (ACL) statements in the correct top-to-bottom evaluation sequence to ensure all rules execute as intended without rule shadowing.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence from top to bottom is: 1) access-list 101 permit tcp host 192.168.10.5 host 10.0.0.50 eq 443, 2) access-list 101 deny tcp host 192.168.10.5 host 10.0.0.50 eq 80, 3) access-list 101 permit tcp 192.168.10.0 0.0.0.255 host 10.0.0.50 eq 80, and 4) access-list 101 deny ip any 10.0.0.0 0.0.0.255.
ACLs execute in sequential order from top to bottom and stop processing as soon as a packet matches a rule. Therefore, specific host rules must be placed above general subnet rules. Placing the host HTTPS permit rule and host HTTP deny rule first ensures host 192.168.10.5 is handled correctly. Placing the subnet HTTP permit rule next allows the rest of the 192.168.10.0/24 network to access HTTP. Finally, placing the broad DMZ deny rule at the bottom prevents any other unintended IP traffic from reaching the 10.0.0.0/24 subnet.

Step-by-Step Solution

1
Identify specific host exceptions requiring permissions or blocks.
Host 192.168.10.5 has specific requirements: permit TCP 443 and deny TCP 80.
ACLs process sequentially from top to bottom on a first-match basis, so specific host entries must appear before broader subnet entries.
2
Place host-specific rules above subnet-level rules to avoid shadowing.
Place 'permit tcp host 192.168.10.5 host 10.0.0.50 eq 443' and 'deny tcp host 192.168.10.5 host 10.0.0.50 eq 80' above the subnet permit rule.
If the subnet rule 'permit tcp 192.168.10.0 0.0.0.255...' were placed above the host 192.168.10.5 deny rule, the router would match host 192.168.10.5 to the subnet rule first and permit HTTP traffic, shadowing the host deny rule.
3
Place general permit rules for the subnet below specific host rules.
Place 'permit tcp 192.168.10.0 0.0.0.255 host 10.0.0.50 eq 80' after host-specific rules.
This grants HTTP access to all hosts in 192.168.10.0/24 except host 192.168.10.5, which has already matched the earlier deny rule.
4
Place broad restrictive subnet rules at the end of the ACL sequence.
Place 'deny ip any 10.0.0.0 0.0.0.255' as the final entry in this rule sequence.
This rule blocks all other IP traffic to the DMZ network while permitting the desired specific web traffic processed by earlier rules.

Key Concept

ACL Sequential Evaluation and Shadowing Prevention
Question 1526Question

A network administrator provisions a new VLAN (VLAN 80, subnet 10.80.4.0/2210.80.4.0/22) on a core multilayer switch. The central enterprise DHCP server resides on VLAN 10 at IP address 10.10.0.1010.10.0.10. Workstations connected to VLAN 80 fail to receive IP configuration parameters dynamically, resulting in clients auto-configuring 169.254.x.x169.254.x.x IPv4 addresses. A packet capture on the VLAN 80 switchport confirms that workstations are successfully broadcasting `DHCPDISCOVER` packets, but no `DHCPOFFER` packets return. Which of the following interface configuration omissions on the VLAN 80 Layer 3 gateway interface is the root cause of this connectivity issue?

Show answer & explanation

Answer: The Layer 3 gateway interface for VLAN 80 is missing an `ip helper-address 10.10.0.10` directive to relay broadcast DHCP requests to the remote DHCP server.

Answer

The Layer 3 gateway interface for VLAN 80 is missing an `ip helper-address 10.10.0.10` directive to relay broadcast DHCP requests to the remote DHCP server.
The correct answer correctly identifies that routers break broadcast domains. When client hosts and the DHCP server reside on different VLANs/subnets, the client gateway interface (VLAN 80) must be configured with an IP helper address (`ip helper-address 10.10.0.10`). This encapsulates client `DHCPDISCOVER` broadcasts into unicast packets routed directly to the DHCP server on VLAN 10.

Step-by-Step Solution

1
Analyze client symptoms and diagnostic packet capture output.
Workstations self-assign APIPA addresses (169.254.x.x169.254.x.x) and send broadcast `DHCPDISCOVER` frames, but receive zero `DHCPOFFER` responses.
This confirms Layer 2 local connectivity is operational, but Layer 3 DHCP traffic is failing to reach the cross-subnet DHCP server.
2
Evaluate router/switch Layer 3 boundary behavior for broadcast traffic.
Routers block MAC/IP broadcast packets (255.255.255.255255.255.255.255) by default.
Because the DHCP server resides on VLAN 10 (10.10.0.1010.10.0.10) and clients are on VLAN 80 (10.80.4.0/2210.80.4.0/22), the router interface must act as a DHCP Relay Agent.
3
Identify the mandatory configuration required to relay DHCP traffic.
Configuring `ip helper-address 10.10.0.10` under the VLAN 80 SVI/subinterface enables the gateway to forward broadcast `DHCPDISCOVER` messages as unicast packets directly to the DHCP server.
Without this directive, the DHCP requests never reach VLAN 10.

Key Concept

DHCP Relay / IP Helper Address Configuration in Multi-VLAN Environments
Question 1527Question

A network engineer is troubleshooting high packet loss and throughput degradation on an 8 km 10GBASE-LR single-mode fiber link connecting two core switches. The switch SFP+ modules report optical receive power levels comfortably within receiver sensitivity thresholds (4 dBm-4\text{ dBm} received vs. a receiver sensitivity range of 14 dBm-14\text{ dBm} to +0.5 dBm+0.5\text{ dBm}). Interface counters show zero FCS or CRC frame errors. An Optical Time-Domain Reflectometer (OTDR) test reveals a high-amplitude reflective Fresnel spike with an Optical Return Loss (ORL) of 22 dB-22\text{ dB} at 3.2 km3.2\text{ km}, while overall fiber end-to-end attenuation remains normal at 0.4 dB/km0.4\text{ dB/km}. Concurrently, packet captures exhibit repeated TCP Out-of-Order and Fast Retransmission packets. Which of the following physical layer anomalies is the primary cause of the degradation?

Show answer & explanation

Answer: A contaminated or damaged optical connector at 3.2 km causing high back-reflection that destabilizes the transmitter laser diode.

Answer

A contaminated or damaged optical connector at 3.2 km causing high back-reflection that destabilizes the transmitter laser diode is the primary cause of the network degradation.
The correct answer identifies that a contaminated or damaged connector end-face creates an air gap causing Fresnel reflection. In high-speed single-mode fiber systems (10 Gbps10\text{ Gbps} and above), back-reflection toward the optical transmitter destabilizes the laser source through optical feedback, leading to physical bit stream corruptions, frame loss, and TCP retransmissions despite adequate optical receive power.

Step-by-Step Solution

1
Analyze the physical layer OTDR measurement data.
The OTDR indicates normal linear optical attenuation (0.4 dB/km0.4\text{ dB/km}) and sufficient receiver power (4 dBm-4\text{ dBm}), eliminating complete fiber breaks or high macrobend signal absorption as the root cause. However, it highlights a large reflective event (Fresnel spike with ORL of 22 dB-22\text{ dB}) at 3.2 km3.2\text{ km}.
High reflectance events in single-mode fiber (SMF) typically indicate air gaps, dirty end-faces, or mismatched polish types (e.g., UPC plugged into APC) at connection points.
2
Correlate physical reflection (ORL) with transmitter stability and packet capture symptoms.
High Optical Return Loss (ORL) causes optical power to reflect straight back into the transmitting laser cavity (optical feedback). This destabilizes the laser diode's operational wavelength and output phase (laser jitter/mode hopping), introducing bit-level errors.
When bit-level signal degradation occurs dynamically due to laser instabilities, receiver clock recovery fails, causing lost frames and triggering TCP Fast Retransmissions without necessarily registering structured Layer 2 CRC errors.
3
Evaluate alternative explanations.
Macrobends cause non-reflective power loss (low receiver power), 10GbE fiber does not support half-duplex negotiation, and TCP MSS misconfigurations are pure Layer 4 issues incapable of generating OTDR reflective spikes.
Only optical back-reflection at a dirty or damaged connector matches both the OTDR reflective spike and the packet capture loss symptoms while maintaining normal receiver power levels.

Key Concept

Optical Time-Domain Reflectometry (OTDR) Fresnel Reflection and Optical Return Loss (ORL) Troubleshooting
Question 1528Question

A network systems engineer is troubleshooting an issue where a newly provisioned Linux database server cannot communicate with remote clients or download updates from an off-site repository at 172.16.50.10172.16.50.10. The server interface configuration and routing table display the following CLI output:

$ ip addr show dev eth0
inet 192.168.45.200/27 brd 192.168.45.223 scope global eth0

$ ip route show
default via 192.168.45.225 dev eth0
192.168.45.192/27 dev eth0 proto kernel scope link src 192.168.45.200

$ ping -c 2 172.16.50.10
connect: Network is unreachable

Based on the diagnostic output, which of the following identifies the root cause of the connectivity failure?

Show answer & explanation

Answer: The configured default gateway address resides outside the host's IPv4 subnet boundaries.

Answer

The configured default gateway address resides outside the host's IPv4 subnet boundaries.
The CIDR prefix /27 establishes subnets in increments of 32 host addresses. For the network starting at 192.168.45.192/27192.168.45.192/27, the usable host addresses span from 192.168.45.193192.168.45.193 to 192.168.45.222192.168.45.222, and the broadcast address is 192.168.45.223192.168.45.223. The default gateway address of 192.168.45.225192.168.45.225 belongs to the next network segment (192.168.45.224/27192.168.45.224/27). Because the default gateway is not on the same local subnet as the server interface, the operating system cannot ARP for the gateway or route packets out of the interface, generating the 'Network is unreachable' error.

Step-by-Step Solution

1
Calculate the subnet boundaries from the CIDR prefix
For prefix /27, the block size is 23227=322^{32-27} = 32. The network address is 192.168.45.192192.168.45.192, giving a host address range of 192.168.45.193192.168.45.193 through 192.168.45.222192.168.45.222, with broadcast 192.168.45.223192.168.45.223.
Determining the valid usable IP address range is necessary to check if the host and gateway reside on the same Layer 3 segment.
2
Analyze the configured host IP and default gateway IP
Host IP 192.168.45.200192.168.45.200 falls within 192.168.45.192/27192.168.45.192/27. The default gateway 192.168.45.225192.168.45.225 falls in the adjacent subnet 192.168.45.224/27192.168.45.224/27.
A host can only directly communicate via Layer 2 ARP with a default gateway that shares its local IP subnet.
3
Evaluate the kernel error message
The OS kernel rejects sending off-subnet packets because the target default gateway cannot be resolved on the directly attached link, raising 'Network is unreachable'.
Confirms the failure originates at local Layer 3 configuration rather than network ACLs or switch VLANs.

Key Concept

Default Gateway Subnet Alignment
Estimated Time:2m 0s
Question 1529Question

A network administrator is troubleshooting an enterprise wireless network in a multi-story office building. Employees carrying laptops along hallways report brief disconnections and video call freezes when moving between adjacent Access Points (APs). A site survey indicates that AP transmit power is set to maximum on all units (23 dBm23\text{ dBm}), whereas client devices transmit at around 12 dBm12\text{ dBm}. Furthermore, seamless roaming protocols are currently unconfigured. Which of the following statements correctly identify a root cause or a proper remediation step for this issue? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The APs' high transmit power causes sticky client behavior, because clients detect a strong downlink signal from distant APs and fail to roam to closer APs; reducing AP transmit power will resolve this.; Enabling 802.11r (Fast BSS Transition) on the wireless controller will reduce re-authentication latency during inter-AP roaming.

Answer

The connection drops during roaming are caused by power asymmetry (sticky clients) and the lack of fast-roaming standards. The issue is resolved by reducing AP transmit power to match client capabilities and enabling 802.11r Fast BSS Transition.
Excessive AP transmit power creates coverage asymmetry where client devices perceive a strong signal from a distant AP and refuse to roam to a closer AP (sticky client). Lowering AP power aligns downlink and uplink boundaries. Additionally, enabling 802.11r (Fast BSS Transition) allows handshakes to complete prior to AP transitions, preventing re-authentication delays.

Step-by-Step Solution

1
Analyze RF signal power asymmetry
Determined that AP transmit power (23 dBm) significantly exceeds client transmit capability (12 dBm), leading to sticky client behavior.
Reducing AP transmit power balances the cell boundaries so clients initiate roaming when their uplink degraded.
2
Evaluate wireless roaming authentication handoffs
Identified that full re-authentication pauses real-time applications when moving between access points.
Enabling 802.11r allows key caching across APs to eliminate authentication overhead during handoffs.

Key Concept

Wireless Roaming Optimization and Power Matching
Question 1530Question

Users at a corporate branch office report frequent audio distortion and frame freezing during real-time video conferencing calls. The network administrator verifies that total interface bandwidth utilization remains low, but suspects variable packet arrival delay is causing the degradation. The administrator must establish performance polling of router MIB counters for this metric while ensuring management traffic is both cryptographically authenticated and fully encrypted. Which monitoring configuration should the administrator implement?

Show answer & explanation

Answer: SNMPv3 configured with the authPriv security level

Answer

The network administrator should implement SNMPv3 configured with the authPriv security level.
The correct answer specifies SNMPv3 with the authPriv security level. SNMPv3 is the only SNMP version that natively supports advanced security features. The authPriv (Authentication and Privacy) security level uses hashing algorithms like SHA for authenticating management users and symmetric encryption algorithms like AES to encrypt MIB query payloads, protecting performance monitoring data against sniffing.

Step-by-Step Solution

1
Identify the required network metric and management requirements
The scenario identifies variable packet arrival delay (jitter) requiring MIB polling, alongside mandatory authentication and encryption for management traffic.
Tracking device performance counters requires SNMP querying, while organizational security policy mandates protecting telemetry in transit.
2
Evaluate SNMP security levels for compliance
SNMPv3 supports three security levels: noAuthNoPriv (no auth, no encryption), authNoPriv (authentication, no encryption), and authPriv (authentication and encryption).
Only authPriv satisfies the mandate for both identity verification and payload confidentiality.

Key Concept

SNMP Version 3 Security Levels and Network Telemetry
Estimated Time:1m 15s
Question 1531Question

A network technician is troubleshooting connectivity for workstations in a newly configured department. The workstations are connected to access ports on Switch-A assigned to VLAN 20. However, none of the hosts can acquire an IP address from the DHCP server located across an 802.1Q trunk link connected to the core switch. The technician issues the following CLI command on Switch-A interface GigabitEthernet0/1:

text
Switch-A# show interfaces trunk

Port Mode Encapsulation Status Native vlan
Gi0/1 on 802.1q trunking 1

Port Vlans allowed on trunk
Gi0/1 1-10,30-100

Port Vlans in spanning tree forwarding state and not pruned
Gi0/1 1,10,30,40

Based on the terminal output and symptoms, which configuration issue on interface GigabitEthernet0/1 is preventing communication for hosts on VLAN 20?

Show answer & explanation

Answer: VLAN 20 is absent from the trunk interface allowed VLAN list.

Answer

VLAN 20 is absent from the trunk interface allowed VLAN list.
The correct answer identifies that VLAN 20 is missing from the 802.1Q trunk allowed list. The command output indicates that interface GigabitEthernet0/1 only permits VLAN ranges 1-10 and 30-100. Consequently, frames originating from access ports in VLAN 20 are pruned at the trunk boundary and cannot reach external network services like DHCP.

Step-by-Step Solution

1
Examine the 'Vlans allowed on trunk' field in the interface trunk output.
The range specified is '1-10,30-100'.
By default, an 802.1Q trunk allows VLANs 1-4094, but explicit filtering using the switchport trunk allowed vlan command restricts allowed traffic.
2
Compare the department VLAN ID with the allowed VLAN list.
VLAN 20 falls outside the allowed ranges (1-10 and 30-100).
When a VLAN ID is omitted from the allowed list, the switch interface discards incoming frames tagged with that VLAN ID and will not forward outgoing frames for that VLAN.
3
Determine the required resolution to restore traffic flow.
Execute 'switchport trunk allowed vlan add 20' on interface GigabitEthernet0/1.
Adding VLAN 20 permits tagged frames for VLAN 20 to transit the trunk link to reach the upstream DHCP server and gateway.

Key Concept

802.1Q Trunk Allowed VLAN Filtering
Question 1532Question

A network engineer must select the appropriate diagnostic tool for various troubleshooting tasks across an enterprise network infrastructure. Match each troubleshooting requirement on the left with the most suitable hardware tester or packet analysis tool on the right.

Click a left item, then click its matching right item

Items

Locating the exact distance to a conductor short circuit on a 70-meter copper UTP cable run
Measuring Near-End Crosstalk (NEXT) and attenuation to verify TIA/EIA Category 6A compliance
Verifying current draw, voltage drop, and negotiated wattage under active load for an IEEE 802.3bt device
Inspecting raw 802.1X EAPOL handshake frames and 802.1Q VLAN header tags in real time

Matches

Show answer & explanation

Answer

Each troubleshooting requirement maps to its specific diagnostic tool based on physical layer signal measurements or data link/network layer packet decodes: fault distance locating maps to the Time-Domain Reflectometer (TDR); NEXT and attenuation compliance verification maps to the Cable Certifier; active power delivery validation maps to the Inline PoE Tester; and real-time frame/header inspection maps to the Packet Analyzer.
The matches correctly pair each diagnostic challenge with its purpose-built tool: distance-to-fault measurements require a Time-Domain Reflectometer (TDR); TIA/EIA standard compliance certification for crosstalk and attenuation requires a Cable Certifier; real-time voltage/amperage load testing for high-power standards like IEEE 802.3bt requires an Inline PoE Tester; and granular frame decoding for 802.1X or 802.1Q protocols requires a Packet Analyzer.

Step-by-Step Solution

1
Analyze physical cabling fault measurement needs
Locating physical conductor distance to a fault requires measuring signal reflection delay over time.
A Time-Domain Reflectometer (TDR) is engineered specifically to calculate fault distance on copper cables by analyzing reflected electrical pulses.
2
Evaluate standards verification and high-frequency noise parameters
Measuring NEXT and attenuation against TIA/EIA specifications requires high-frequency signal analysis beyond basic pinout continuity.
Cable certifiers execute comprehensive frequency sweeps across all wire pairs to validate compliance with standards such as Category 6A.
3
Examine active power delivery and load conditions for switch drops
Testing IEEE 802.3bt power delivery demands measuring voltage drops and current draw under simulated or active load.
An inline PoE tester measures live power negotiation, voltage level, and amperage draw to verify sufficient power budget and delivery.
4
Identify the level of protocol frame inspection required
Decoding 802.1X EAPOL handshakes and 802.1Q tags requires protocol packet capture and decoding at Layers 2 and 3.
A packet analyzer captures network frames and decodes individual field headers for troubleshooting authentication and VLAN tagging issues.

Key Concept

Selecting network diagnostic tools based on physical signal characteristics, power standards, and OSI layer frame analysis.
Estimated Time:2m 0s
Question 1533Question

A network security engineer is updating an organization's wireless security baseline to transition branch offices to WPA3-Enterprise. The baseline mandates individual user credential validation integrated with central directory services and protection against wireless management frame spoofing attacks. Which of the following technical requirements must be included in the WPA3-Enterprise specification? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Implementation of IEEE 802.1X port-based authentication integrated with a central RADIUS server; Mandatory deployment of Protected Management Frames (PMF) across all connected access points and clients

Answer

The mandatory requirements for WPA3-Enterprise deployment are the implementation of IEEE 802.1X authentication integrated with a RADIUS server and the mandatory deployment of Protected Management Frames (PMF).
WPA3-Enterprise specifies IEEE 802.1X authentication using a RADIUS infrastructure for individual user identity validation. Additionally, the WPA3 standard makes Protected Management Frames (PMF) strictly mandatory to prevent malicious management frame injection and deauthentication attacks.

Step-by-Step Solution

1
Identify the authentication mechanism required for WPA3-Enterprise.
WPA3-Enterprise uses 802.1X port-based network access control with EAP protocols communicating to a backend RADIUS server.
Enterprise mode avoids shared keys by using centralized, individual credentials.
2
Identify the management protection requirement mandated in the WPA3 standard.
Protected Management Frames (PMF / IEEE 802.11w) are mandatory in WPA3.
PMF prevents deauthentication and disassociation spoofing attacks on wireless networks.

Key Concept

WPA3-Enterprise Requirements & Protected Management Frames
Estimated Time:1m 30s
Question 1534Question

A network security engineer is configuring secure management plane controls on a newly installed distribution switch before introducing it to the enterprise network. In what sequence should the engineer execute the baseline hardening steps to properly establish and secure SSH administrative access?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with setting the domain name and generating RSA keys, followed by enforcing SSH protocol transport on VTY lines, constructing an administrative access control list, and finally applying the access control list to the VTY lines.
Establishing secure administrative access requires generating cryptographic host keys as a prerequisite, restricting VTY protocols to SSH to prevent cleartext exposure, defining administrative IP filtering rules via an access control list, and lastly binding that list to the VTY interfaces.

Step-by-Step Solution

1
Initialize cryptographic host keys.
Domain name is configured and the RSA host key pair is created.
SSH protocol daemons require an RSA key pair for host identification and session encryption.
2
Enforce secure transport protocols.
VTY interfaces are set to accept only SSH connections.
Disabling insecure protocols like Telnet prevents cleartext credential interception over the network.
3
Construct management access filtering rules.
An access control list is created specifying permitted management source subnets.
Defines network layer boundaries specifying which administrative hosts are authorized to connect.
4
Bind filter rules to virtual terminal interfaces.
Access control list actively filters inbound connection attempts on VTY lines.
Enforces the defined IP address filtering policy on remote access sessions.

Key Concept

Secure Management Plane Baseline Hardening
Question 1535Question

A network engineer is configuring a resilient remote access and out-of-band (OOB) management solution for network hardware installed at an unstaffed edge data center. The implementation must ensure administrators maintain management access to device consoles and can power-cycle unresponsive equipment during a complete failure of the primary WAN link. Which TWO of the following components should be deployed to meet these operational requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: An out-of-band terminal server connected to device serial console ports and equipped with an independent cellular modem; Smart switched Power Distribution Units (PDUs) reachable via the dedicated out-of-band management network

Answer

The correct deployments are an out-of-band terminal server connected to serial console ports with an independent cellular modem, and smart switched Power Distribution Units (PDUs) connected to the out-of-band management network.
Out-of-band (OOB) management relies on physically isolated alternate communication paths. Connecting hardware serial console ports to a terminal server backed by an independent cellular modem preserves command-line access during primary network transport cuts. Additionally, switched PDUs allow administrators to execute remote power-cycling of frozen equipment over the OOB pathway when soft reboots cannot execute.

Step-by-Step Solution

1
Identify the primary functional requirement for remote console access during a WAN link cut.
Out-of-band console access requires an independent channel such as a cellular modem paired with a terminal server connected to RS-232 serial console ports.
In-band management paths become completely inaccessible whenever the primary WAN circuit fails.
2
Identify the mechanism needed to reboot frozen network devices remotely.
Switched Power Distribution Units (PDUs) allow remote socket power cycling.
When a network operating system crashes or freezes completely, soft reboots via software commands cannot process, necessitating a physical hard power cycle via an OOB-managed PDU.

Key Concept

Out-of-Band (OOB) Management Infrastructure
Question 1536Question

A security technician is investigating a multi-stage incident on an enterprise network segment. Packet logs reveal that an unauthorized internal host transmitted forged Gratuitous ARP messages to map the IP address of the default gateway to its own physical address. Simultaneously, internal users reported that entering legitimate domain names into their web browsers redirected them to a suspicious external IP address hosted on an unauthorized server. Which of the following attack types were executed during this incident? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: ARP Poisoning; DNS Poisoning

Answer

The attack types executed in this scenario are ARP Poisoning and DNS Poisoning.
ARP Poisoning occurs when forged ARP messages alter the MAC-to-IP mapping on local hosts, misdirecting traffic intended for the gateway. DNS Poisoning alters domain name resolution data so that queries for legitimate web services return malicious IP addresses.

Step-by-Step Solution

1
Analyze the first incident symptom
Identified forged Gratuitous ARP packets remapping the default gateway's IP to an attacker's MAC address.
This behavior directly defines ARP poisoning (or ARP spoofing), enabling man-in-the-middle positioning on Layer 2.
2
Analyze the second incident symptom
Identified domain name queries resolving to an unauthorized destination IP address.
Altering or spoofing name resolution responses to redirect users to unauthorized web servers defines DNS cache poisoning/spoofing.

Key Concept

Identifying Man-in-the-Middle and redirection attack vectors based on network signatures
Question 1537Question

A network technician needs to perform a localized hardware diagnostic test on a workstation's network interface card (NIC) to verify that its physical transmission and reception circuitry are functioning correctly without connecting the host to an active network switch. Which tool should the technician plug directly into the Ethernet port to conduct this test?

Show answer & explanation

Answer: Loopback plug

Answer

Loopback plug
A loopback plug connects the output (transmit) pins directly to the input (receive) pins on a network interface port. This enables self-testing of the adapter's physical hardware signaling and port integrity without requiring external network connectivity.

Step-by-Step Solution

1
Identify the diagnostic requirement
The test requires verifying physical transmission (Tx) and reception (Rx) functions of a local Ethernet port in isolation.
Determining hardware operational status requires a closed electrical signal path directly at the physical interface.
2
Evaluate hardware tester capabilities
Connecting a loopback plug routes the Tx pins back into the Rx pins of the same RJ-45 port.
This configuration allows diagnostic software or link indicator LEDs to confirm that physical port circuitry can send and receive electrical signals properly.

Key Concept

Utilizing Hardware Loopback Plugs for Interface Testing
Question 1538Question

A network administrator is addressing an incident where remote users connected via SSL VPN cannot access internal intranet sites following a gateway software update. The administrator conducted diagnostic packet captures on the gateway and confirmed that the internal security policy was dropping traffic from the SSL VPN IP pool due to an unmapped subnet mask. Which of the following actions should the administrator take NEXT according to the CompTIA troubleshooting methodology?

Show answer & explanation

Answer: Establish a plan of action to modify the gateway security policy and identify potential side effects.

Answer

The administrator should establish a plan of action to modify the gateway security policy and identify potential side effects.
In the CompTIA troubleshooting methodology, once a theory of probable cause has been tested and verified (Step 3), the network administrator must establish a plan of action to resolve the issue and identify potential effects (Step 4) before implementing changes.

Step-by-Step Solution

1
Analyze the current state in the troubleshooting sequence
The administrator performed packet captures and confirmed the root cause (unmapped subnet mask in security policy dropping SSL VPN traffic), which completes Step 3 (Test the theory to determine cause).
Identifying the current step determines which step must follow logically according to the CompTIA methodology.
2
Determine the immediate next step in the CompTIA 7-step methodology
The step directly following 'Test the theory to determine cause' is 'Establish a plan of action to resolve the problem and identify potential effects'.
CompTIA methodology strictly mandates planning and risk identification prior to applying configuration changes to network devices.

Key Concept

CompTIA Troubleshooting Methodology Step Sequence
Estimated Time:1m 15s
Question 1539Question

A network administrator is performing a baseline security hardening audit on core enterprise switches. The security report reveals that idle administrative sessions on virtual terminal (VTY) lines remain active indefinitely when left unattended, and remote management traffic lacks centralized command authorization and traffic encryption. Which set of configuration controls should the administrator implement to best address these findings?

Show answer & explanation

Answer: Configure an exec-timeout on VTY lines, enforce SSH version 2, and integrate TACACS+ for centralized AAA authentication and command authorization.

Answer

The administrator should configure an exec-timeout on VTY lines, enforce SSH version 2, and integrate TACACS+ for centralized AAA authentication and command authorization.
Hardening the management plane of network devices requires restricting session lifespans, encrypting management traffic in transit, and centralizing access control. Configuring an exec-timeout ensures that idle VTY sessions automatically close, preventing unauthorized local access to abandoned terminals. Utilizing SSH version 2 replaces insecure cleartext protocols such as Telnet. Incorporating TACACS+ provides centralized authentication, authorization, and accounting, ensuring every administrative command is explicitly authorized and audited.

Step-by-Step Solution

1
Identify session timeout requirements for virtual terminal lines.
Configuring an exec-timeout forces inactive management connections to terminate automatically after a specified period of inactivity.
This mitigates risks associated with unattended terminal sessions.
2
Select a secure, encrypted management protocol.
Enforcing SSH v2 disables insecure legacy protocols like Telnet and encrypts all session content including credentials.
Cleartext transmission of administrative credentials over the network must be prevented.
3
Implement centralized AAA for command accounting and authorization.
Integrating TACACS+ allows granular control over which commands individual administrators can execute, alongside centralized auditing.
TACACS+ decouples authentication, authorization, and accounting, encrypting the full payload of access control packets.

Key Concept

Management Plane Hardening and Secure Remote Access
Question 1540Question

A network security administrator is investigating an incident where external application servers fail to establish TCP sessions with an authentication daemon running on a Linux system. The administrator executes `ss -tulpn` on the target host and receives the following terminal output snippet:

Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
tcp LISTEN 0 128 127.0.0.1:8443 0.0.0.0:* users:(("auth_svc",pid=8812,fd=4))

Based on this command output, which of the following statements correctly identifies the root cause of the connectivity failure for remote clients?

Show answer & explanation

Answer: The authentication daemon is bound exclusively to the IPv4 loopback interface, preventing remote network adapters from accepting incoming connections on port 8443.

Answer

The authentication daemon is bound exclusively to the IPv4 loopback interface, preventing remote network adapters from accepting incoming connections on port 8443.
The `ss -tulpn` output shows that the process `auth_svc` is listening on `127.0.0.1:8443`. In IP networking, binding to `127.0.0.1` restricts socket traffic to internal inter-process communication on the local loopback interface. Remote hosts trying to reach port 8443 over external physical network interfaces will be unable to establish a TCP connection because the operating system will not route external packets to the loopback adapter.

Step-by-Step Solution

1
Analyze the CLI command and options executed.
The administrator ran `ss -tulpn`, which displays socket statistics for TCP (`-t`), UDP (`-u`), listening sockets (`-l`), numeric ports (`-n`), and associated processes (`-p`).
Understanding the CLI switches confirms that the output represents active listening sockets on the local system.
2
Inspect the socket binding IP address in the Local Address:Port column.
The socket displays `127.0.0.1:8443` in the LISTEN state.
The IP address `127.0.0.1` represents the IPv4 loopback interface.
3
Evaluate the network impact of binding to 127.0.0.1.
Sockets bound strictly to loopback (`127.0.0.1` or `::1`) accept traffic originated locally within the same operating system kernel and automatically drop packets arriving from external subnets.
To accept external connections, the service must bind to `0.0.0.0` (all IPv4 interfaces), `::` (all IPv6 interfaces), or the host's specific network interface IP address.

Key Concept

Socket Interface Binding and Listening States in CLI Utilities
Estimated Time:2m 0s
PreviousPage 77 / 112Next
All practice questions — CompTIA Network+ | Examkin