All practice questions

2237 questions

Question 1201Question

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

Show answer & explanation

Answer: Establish a theory of probable cause.

Answer

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

Step-by-Step Solution

1
Identify the current phase completed in the scenario.
The technician gathered information, reviewed system logs, and duplicated the issue, which completes Step 1 (Identify the problem).
Recognizing the completed step allows determination of the next sequential phase in the standard process.
2
Determine the next sequential phase in the CompTIA troubleshooting methodology.
Step 2 is to establish a theory of probable cause (questioning the obvious).
The CompTIA methodology follows a strict sequence: Identify problem -> Establish theory -> Test theory -> Plan of action/Implement -> Verify functionality -> Document.

Key Concept

CompTIA Troubleshooting Methodology Order
Question 1202Question

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

Drag items to arrange them in the correct order

Show answer & explanation

Answer

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

Step-by-Step Solution

1
Identify the problem
Information is gathered from logs and user reports to define the scope of the SD-WAN failover issue.
Troubleshooting must begin with gathering facts and defining symptoms before making assumptions.
2
Establish a theory of probable cause
A hypothesis regarding asymmetric routing and stateful firewall drops is formulated.
Developing a logical cause based on gathered symptoms focuses diagnostic testing.
3
Test the theory to determine the cause
Staging lab tests and packet captures confirm that asymmetric routing is the true root cause.
The theory must be confirmed empirically before modifying live network configurations.
4
Establish a plan of action to resolve the problem and implement the solution
A change management plan for BGP routing adjustments is created, assessed for potential impact, and executed.
System changes require impact identification and structured execution to prevent unintended downtime.
5
Verify full system functionality and implement preventive measures
End-to-end microservice connectivity is confirmed during failover, and proactive alerts are configured.
Ensures the fix completely resolved the issue without secondary failures and guards against recurrence.
6
Document findings, actions, outcomes, and lessons learned
Root cause and resolution steps are recorded in the service desk knowledge base.
Complete documentation provides historical references and aids future incident resolution.

Key Concept

CompTIA 6-Step Network Troubleshooting Methodology
Question 1203Question

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

1
Analyze the completed methodology steps in the scenario.
Identified that Step 1 (Identify the problem), Step 2 (Establish a theory of probable cause), and Step 3 (Test the theory to determine cause) have all been completed.
Testing the theory in a staging environment and confirming that the ICMP inspection rule resolved 15001500-byte frame drops signifies the completion of Step 3.
2
Determine the next sequential phase of the CompTIA 6-step troubleshooting methodology.
The immediate next step is Step 4: Establish a plan of action to resolve the problem and implement the solution.
Before making changes to production infrastructure, a structured plan of action considering potential side effects and rollback steps must be established.
3
Evaluate the response options against Step 4 requirements.
Drafting the deployment plan, performing risk analysis, and defining a rollback procedure aligns directly with Step 4.
Direct implementation without a plan skips necessary risk management, whereas verification and documentation occur later in the troubleshooting process.

Key Concept

CompTIA Troubleshooting Methodology Step Sequence
Question 1204Question

Following a compliance audit, a network engineer must establish centralized performance polling for hardware metrics including CPU utilization, memory usage, and interface throughput across core enterprise routers. The organization's security policy strictly mandates that all monitoring telemetry communications must enforce cryptographic user authentication and encrypt all payload data in transit to prevent eavesdropping. Which protocol and security level combination should the engineer implement to satisfy these requirements?

Show answer & explanation

Answer: SNMPv3 configured with the authPriv security level

Answer

SNMPv3 configured with the authPriv security level
SNMPv3 with authPriv (Authentication and Privacy) provides both cryptographic authentication and full payload encryption. This ensures that SNMP polling requests for core metrics are authenticated and that telemetry data in transit cannot be read by unauthorized packet sniffers.

Step-by-Step Solution

1
Identify the performance monitoring mechanism required.
System metric polling (CPU, memory, bandwidth) requires a structured management protocol like SNMP rather than an event logging protocol like Syslog.
SNMP provides structured OID polling capabilities suited for device health telemetry.
2
Evaluate the security requirements specified in the scenario.
The requirements demand both cryptographic user authentication and payload encryption of traffic in transit.
Security mandates require protection against unauthorized polling access and eavesdropping.
3
Select the SNMP version and security level that satisfies both requirements.
SNMPv3 with authPriv (Authentication and Privacy) provides HMAC authentication and AES/DES payload encryption.
authNoPriv lacks encryption, noAuthNoPriv lacks both, and SNMPv2c sends plain-text community strings without security.

Key Concept

SNMPv3 Security Levels and Telemetry Security
Estimated Time:1m 15s
Question 1205Question

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

1
Analyze the physical environment and symptoms
Decorative mirrors (which contain metallic backings) were added, and symptoms show strong RSSI but poor SNR and high frame retransmissions.
Metal surfaces act as RF reflectors, causing radio waves to bounce off obstacles and take multiple propagation paths to the receiver.
2
Evaluate the RF behavior
Reflected waves arrive at the receiver at slightly different times and phases, causing destructive phase cancellation.
This phenomenon, known as multipath interference or multipath distortion, corrupts incoming frames while maintaining high overall RF energy (RSSI).
3
Select the correct diagnosis
Multipath distortion caused by reflection from the metallic mirror backings is identified as the root cause.
Other options describe Layer 3 IP assignment issues, wired physical link errors, or incorrect channel configuration concepts.

Key Concept

RF Reflection and Multipath Distortion
Estimated Time:1m 15s
Question 1206Question

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

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct logical sequence starts with inspecting `/etc/resolv.conf`, followed by directly querying the configured DNS server using `dig`, checking `/etc/hosts` for conflicting static entries, and finally flushing the local resolver cache.
Methodological troubleshooting progresses from checking local system configuration (`/etc/resolv.conf`), to testing DNS server transport responsiveness via direct utility queries (`dig`), checking local resolution overrides (`/etc/hosts`), and lastly purging stale system cache (`resolvectl flush-caches`).

Step-by-Step Solution

1
Inspect local resolver configuration files.
Verifies that the workstation is configured with valid DNS server IP addresses.
According to the CompTIA troubleshooting methodology, you must verify the basic client configuration settings before initiating complex network queries.
2
Query the configured DNS server explicitly using `dig @<dns_ip>`.
Tests whether DNS queries reach the resolver over port 53 and receive valid responses.
Direct lookup bypasses local OS resolution mechanisms to isolate whether the root cause lies within network transport or DNS server performance.
3
Examine the local static host table (`/etc/hosts`).
Identifies any hardcoded IP-to-hostname mappings that override DNS lookups.
Operating systems process `/etc/hosts` prior to querying external DNS servers. A legacy entry will prevent proper DNS name resolution.
4
Flush the local OS DNS resolver cache.
Removes cached NXDOMAIN or outdated responses.
Flushing clears lingering stale records so that subsequent application requests pull fresh, authoritative records from the DNS infrastructure.

Key Concept

OS Name Resolution Troubleshooting Sequence
Question 1207Question

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

Show answer & explanation

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

Answer

The administrator should establish a plan of action to resolve the problem and identify potential effects prior to implementing the fix on production equipment.
According to the CompTIA troubleshooting methodology, the steps occur in the following order: (1) Identify the problem, (2) Establish a theory of probable cause, (3) Test the theory to determine cause, (4) Establish a plan of action to resolve the problem and identify potential effects / implement solution, (5) Verify full system functionality and implement preventive measures, and (6) Document findings, actions, and outcomes. Because the administrator has just tested and confirmed the theory (Step 3), the immediate next step is Step 4: establishing a plan of action and identifying potential operational effects before implementation.

Step-by-Step Solution

1
Analyze current phase in CompTIA methodology
The technician has gathered symptoms (Step 1), formed a hypothesis (Step 2), and tested/confirmed the hypothesis in a lab (Step 3).
Determining the completed step is essential to identifying the required next step in the 6-step methodology.
2
Identify the next sequential step in the methodology
Step 4 is 'Establish a plan of action to resolve the problem and identify potential effects' followed by implementing the solution.
CompTIA requires planning changes and assessing potential risks/effects before applying changes to production networks.

Key Concept

CompTIA 6-Step Troubleshooting Methodology Sequence
Estimated Time:1m 30s
Question 1208Question

A network administrator is setting up a performance monitoring and telemetry strategy across an enterprise network that supports real-time voice communications and core infrastructure devices. The design requires secure polling of switch hardware metrics alongside precise measurement of packet delay variability for voice streams. Which of the following configuration options and metric analysis practices should the administrator implement? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Implement SNMPv3 configured with the authPriv security level to ensure both cryptographic authentication and payload encryption during switch metric polling.; Monitor jitter metrics using IPFIX or NetFlow flow records transported via UDP to assess packet arrival time variation across real-time voice streams.

Answer

The correct selections are implementing SNMPv3 with the authPriv security level for encrypted hardware polling, and monitoring jitter metrics using IPFIX or NetFlow flow records over UDP to evaluate delay variation in voice streams.
Configuring SNMPv3 with authPriv satisfies enterprise security standards by authenticating the session and encrypting metric payloads. Additionally, tracking jitter metrics via IPFIX/NetFlow transported over UDP enables network engineers to diagnose delay variation affecting latency-sensitive traffic such as VoIP.

Step-by-Step Solution

1
Identify the security requirements for infrastructure telemetry.
SNMPv3 authPriv is required because it adds cryptographic authentication and privacy (data encryption), whereas legacy versions (SNMPv1/v2c) transmit data in plain text.
Enterprise monitoring baselines demand protection against eavesdropping and unauthorized command injection.
2
Select the appropriate performance metric and transport method for real-time voice quality analysis.
Jitter measures the variability in packet arrival intervals, directly affecting voice quality. Flow-based telemetry (IPFIX/NetFlow) exported over UDP provides timely flow metrics without protocol buffering overhead.
Voice quality degradation is primarily driven by delay variation (jitter) and packet loss rather than simple bandwidth saturation.

Key Concept

SNMPv3 Security Levels and Flow-based Jitter Telemetry
Question 1209Question

Match each Virtual Private Network (VPN) or remote access technology on the left with its core security or operational characteristic on the right.

Click a left item, then click its matching right item

Items

Clientless SSL/TLS VPN
IPsec Encapsulating Security Payload (ESP)
IPsec Authentication Header (AH)
Generic Routing Encapsulation (GRE)

Matches

Show answer & explanation

Answer

Clientless SSL/TLS VPN matches browser-based access using TCP 443 without client software; IPsec ESP matches payload encryption and integrity via IP protocol 50; IPsec AH matches complete IP packet integrity via IP protocol 51 incompatible with NAT; GRE matches unencrypted encapsulation of multicast and routing traffic.
Each VPN and remote access technology aligns directly with its primary operating mode: Clientless SSL/TLS VPN enables client-free web access on TCP 443; IPsec ESP encrypts payloads using IP protocol 50; IPsec AH authenticates entire IP headers via IP protocol 51 (which breaks under NAT modification); and GRE provides unencrypted multiprotocol tunneling.

Step-by-Step Solution

1
Analyze client-side software requirements for remote access portals.
Clientless SSL/TLS VPN establishes remote access within standard web browser sessions over TCP 443, eliminating endpoint software deployment.
Web portals leverage built-in browser cryptography for lightweight remote connectivity.
2
Differentiate between IPsec ESP and AH header capabilities and NAT interactions.
ESP provides payload encryption using IP protocol 50, while AH authenticates outer IP headers using IP protocol 51, causing ICV failures when NAT alters packet headers.
AH includes mutable IP header fields in its hash verification, making it incompatible with address translation unless Nat-Traversal encapsulates it differently.
3
Evaluate multiprotocol routing encapsulation protocols.
GRE encapsulates non-IP and multicast traffic like OSPF/EIGRP updates across IP networks, but provides zero native encryption.
GRE delivers protocol versatility for site-to-site transport, relying on IPsec when confidentiality is required.

Key Concept

Virtual Private Networks and Remote Access Security protocols, IPsec modes, and tunneling mechanisms.
Question 1210Question

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

Show answer & explanation

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

Answer

Configuring 40 MHz40\text{ MHz} channel bonding on the 2.4 GHz2.4\text{ GHz} band consumes 8 standard channels, creating unavoidable adjacent-channel interference across the limited 2.4 GHz2.4\text{ GHz} spectrum.
In the 2.4 GHz2.4\text{ GHz} Wi-Fi band, channels are spaced 5 MHz5\text{ MHz} apart, and a standard 20 MHz20\text{ MHz} channel requires 20 MHz20\text{ MHz} of separation to avoid overlapping adjacent channels (yielding non-overlapping channels 1, 6, and 11). Configuring a 40 MHz40\text{ MHz} channel width spans 8 adjacent channels simultaneously, overlapping with almost all available channels in the 2.4 GHz2.4\text{ GHz} spectrum and causing high frame corruption and retransmission rates due to adjacent-channel interference.

Step-by-Step Solution

1
Analyze the physical radio frequency parameters reported in the scenario.
The deployment uses 40 MHz40\text{ MHz} channel widths on the 2.4 GHz2.4\text{ GHz} band centered around Channel 3.
Understanding the channel layout of the 2.4 GHz2.4\text{ GHz} band is necessary to evaluate RF interference.
2
Calculate the spectral footprint of a 40 MHz40\text{ MHz} channel in the 2.4 GHz2.4\text{ GHz} band.
The 2.4 GHz2.4\text{ GHz} spectrum (Channels 1–11 in North America) has only 60 MHz60\text{ MHz} of total usable bandwidth for non-overlapping channels (20 MHz20\text{ MHz} per channel for Channels 1, 6, and 11). A single 40 MHz40\text{ MHz} channel occupies 8 overlapping 5 MHz5\text{ MHz} channels (e.g., Channels 1 through 8).
Enabling 40 MHz40\text{ MHz} channels on 2.4 GHz2.4\text{ GHz} prevents the deployment of non-overlapping channels and causes severe adjacent-channel interference (ACI) with any nearby 20 MHz20\text{ MHz} or 40 MHz40\text{ MHz} APs.
3
Identify the recommended best practice for 2.4 GHz2.4\text{ GHz} channel width configuration.
Wi-Fi best practices dictate restricting 2.4 GHz2.4\text{ GHz} radios strictly to 20 MHz20\text{ MHz} channel widths using non-overlapping channels 1, 6, and 11.
Restricting channel width to 20 MHz20\text{ MHz} eliminates adjacent-channel overlap and allows CSMA/CA to properly manage co-channel medium sharing.

Key Concept

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

A network security administrator must configure an IPv4 Access Control List (ACL) on a router to enforce network security policies for the internal subnet 172.16.10.0/24172.16.10.0/24. Place the following ACL rules in the correct top-to-bottom sequence so that host-specific restrictions are properly enforced without being shadowed by broader subnet rules.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct top-to-bottom sequence is: 1) deny tcp host 172.16.10.5 host 192.168.1.50 eq 443, 2) permit tcp 172.16.10.0 0.0.0.255 host 192.168.1.50 eq 443, 3) permit icmp 172.16.10.0 0.0.0.255 192.168.1.0 0.0.0.255 echo, 4) deny ip any any.
Access Control Lists operate sequentially using first-match logic. Specific rules (such as blocking host 172.16.10.5) must be placed at the top of the list. Placing a general subnet permit rule above a specific host deny rule causes rule shadowing, where traffic matches the subnet permit first and the host block is never evaluated. Finally, general protocol permissions follow, and the catch-all deny rule resides at the very end.

Step-by-Step Solution

1
Identify specific host exceptions requiring explicit denial.
Position host-specific deny rule (deny tcp host 172.16.10.5 host 192.168.1.50 eq 443) at the very top of the list.
ACLs perform top-down evaluation and stop checking rules on the first match. Placed lower, a broader permit statement would grant access unintentionally (rule shadowing).
2
Place general application traffic permits for the wider subnet.
Position the subnet permit rule (permit tcp 172.16.10.0 0.0.0.255 host 192.168.1.50 eq 443) immediately below the specific host deny.
This allows all authorized hosts in the 172.16.10.0/24 subnet to reach the HTTPS server while still enforcing the preceding host block.
3
Add auxiliary protocol permit rules.
Position ICMP Echo permit rules (permit icmp 172.16.10.0 0.0.0.255 192.168.1.0 0.0.0.255 echo) below key application permissions.
This enables diagnostic traffic across subnets without overriding specific application access controls.
4
Ensure global catch-all drop functionality.
Place explicit or implicit default deny (deny ip any any) at the bottom.
All unallowed traffic must be systematically dropped at the end of the ACL processing chain.

Key Concept

ACL First-Match Processing and Rule Shadowing
Estimated Time:1m 30s
Question 1212Question

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

1
Analyze the reported symptoms and RF metrics
The client experiences high retransmissions and erratic SNR despite strong received signal strength indicator (RSSI of 55 dBm-55\text{ dBm}).
High RSSI combined with low/fluctuating SNR in an environment full of metallic obstacles indicates severe RF signal distortion rather than low signal amplitude.
2
Identify the underlying RF phenomenon
Reflections off metal racks create multiple propagation paths, causing out-of-phase wave recombination at the client receiver (multipath fading / delay spread).
When reflected signals arrive slightly delayed and out of phase with the direct line-of-sight signal, destructive interference occurs, cancelling out the carrier wave.
3
Select the appropriate antenna design and deployment change
Replacing omnidirectional ceiling antennas with focused directional patch antennas aligned down aisles concentrates the signal path and reduces reflective scatter.
Directional antennas constrain RF energy to intended corridors, minimizing bounce off surrounding metallic structures.

Key Concept

Multipath Fading and Directional Antenna Remediation in Industrial RF Environments
Question 1213Question

An enterprise network administrator needs to set up performance monitoring to periodically poll CPU usage and interface bandwidth metrics across remote routers. Institutional security compliance mandates that all network telemetry must enforce both user authentication and data encryption in transit. Which monitoring protocol and security level should the administrator configure?

Show answer & explanation

Answer: SNMPv3 configured with the authPriv security level

Answer

SNMPv3 configured with the authPriv security level
Simple Network Management Protocol version 3 (SNMPv3) with the authPriv (Authentication and Privacy) security level provides cryptographic user authentication using hashes like SHA and data payload encryption using algorithms like AES. This meets both performance monitoring and strict encryption compliance standards.

Step-by-Step Solution

1
Identify the primary performance monitoring requirement
The requirement calls for periodic polling of device performance metrics (CPU and interface bandwidth) across network hardware.
Simple Network Management Protocol (SNMP) is the standard protocol for polling device performance parameters and metrics.
2
Evaluate protocol security requirements
The compliance policy explicitly specifies both user authentication and data encryption in transit.
SNMPv1 and SNMPv2c send community strings in plaintext without encryption. Only SNMPv3 includes robust cryptographic security models.
3
Select the correct SNMPv3 security level
The authPriv security level provides authentication (auth) and privacy/encryption (priv).
authNoPriv provides authentication without encryption, whereas noAuthNoPriv provides neither cryptographic authentication nor encryption.

Key Concept

SNMP Security Levels and Telemetry Monitoring
Question 1214Question

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

Show answer & explanation

Answer: Attenuation

Answer

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

Step-by-Step Solution

1
Analyze the physical environment described in the scenario.
The signal loss occurs specifically when moving behind a solid physical obstacle (a thick reinforced concrete wall).
Dense building materials absorb radio frequency energy as signals pass through them.
2
Identify the RF phenomenon corresponding to signal loss through obstacles.
Attenuation describes the reduction in signal power/strength over distance or through obstructing media.
Concrete and rebar significantly decrease the amplitude of Wi-Fi signals.

Key Concept

RF Attenuation and Physical Obstructions
Estimated Time:45s
Question 1215Question

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

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential order is: 1) Identify the problem, 2) Establish a theory of probable cause, 3) Test the theory to determine cause, 4) Establish a plan of action and implement the solution, and 5) Verify full system functionality and implement preventive measures.
The official CompTIA 6-step troubleshooting methodology follows a strict sequence: 1. Identify the problem, 2. Establish a theory of probable cause, 3. Test the theory to determine cause, 4. Establish a plan of action to resolve the problem and implement the solution, 5. Verify full system functionality and implement preventive measures, and 6. Document findings, actions, and outcomes.

Step-by-Step Solution

1
Begin with problem identification
Information, symptom reports, and recent changes are gathered.
You must understand what is failing before forming hypotheses.
2
Formulate a probable cause theory
A prioritized hypothesis of the failure point is established.
Hypothesizing narrows down the operational scope before testing.
3
Test the theory
The root cause is verified (or disproved, triggering a new theory).
Changes should not be implemented without confirming the cause.
4
Plan and execute the solution
A plan of action is established and the fix is deployed.
Structured execution minimizes unwanted side effects during remediation.
5
Verify functionality and prevent recurrence
System operation is validated and preventive controls are applied.
Verification ensures the problem is fully resolved and won't immediately reoccur.

Key Concept

CompTIA Troubleshooting Methodology Order
Question 1216Question

A network security administrator needs to select a security control that specifically protects log files against unauthorized modification while stored at rest on a syslog server. Which of the following technical controls directly fulfills this Integrity requirement?

Show answer & explanation

Answer: Calculating and periodically verifying SHA-256 cryptographic hashes of the stored log files

Answer

Calculating and periodically verifying SHA-256 cryptographic hashes of the stored log files directly ensures data integrity at rest by providing a mechanism to detect any unauthorized modification of stored data.
The correct option involves generating and verifying SHA-256 cryptographic hashes. Cryptographic hashing provides one-way mathematical verification that file contents remain unaltered, directly supporting the Integrity pillar of the CIA triad for stored log files.

Step-by-Step Solution

1
Identify the primary security requirement specified in the scenario
The requirement focuses on maintaining Integrity for stored data (preventing/detecting unauthorized modification of log files at rest).
The CIA triad categorizes protection against unauthorized alteration as Integrity.
2
Evaluate technical mechanisms designed to guarantee data integrity at rest
Cryptographic hashing algorithms like SHA-256 produce deterministic digests. Comparing current hashes against baseline hashes detects file modifications immediately.
Hashing is a one-way function specifically designed to detect data tampering.
3
Differentiate integrity controls at rest from transit protection or access control mechanisms
Transport protocols protect data in motion, RADIUS provides AAA access services, and VLANs provide network segmentation.
None of those alternative controls compute or verify file checksums for stored static files.

Key Concept

Integrity Control via Cryptographic Hashing
Question 1217Question

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

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows client-side resolution order followed by targeted network diagnostics: 1. Verify adapter IP and DNS server assignments (`ipconfig /all`). 2. Inspect the local `hosts` file. 3. Check the local DNS resolver cache (`ipconfig /displaydns`). 4. Flush the local DNS cache (`ipconfig /flushdns`). 5. Issue a direct interactive network lookup via `nslookup` specifying the server IP address.
Operating systems process host name resolution in a strict sequence: local hostname check, static HOSTS file evaluation, local DNS cache lookup, and finally outbound DNS queries to configured servers. Logical troubleshooting isolates client configuration first (ipconfig /all), local file overrides second (HOSTS file), local memory cache third (displaydns), cache remediation fourth (flushdns), and direct server probing last (nslookup).

Step-by-Step Solution

1
Verify basic IP and DNS server settings on the local adapter.
Confirms the host is using valid network configuration settings and designated DNS server IPs.
Before inspecting resolution cache or files, basic IP connectivity parameters must be confirmed.
2
Inspect the local HOSTS file.
Identifies any static overrides taking priority over network DNS.
Standard client operating systems parse local HOSTS file entries prior to evaluating local DNS memory caches or sending wire requests.
3
Query the local DNS cache using `ipconfig /displaydns`.
Exposes existing cached records and negative cache entries.
The client resolver cache is evaluated next in the name resolution order prior to generating a network frame.
4
Purge the local DNS resolver cache using `ipconfig /flushdns`.
Removes cached entries and resets local memory.
Clearing the local cache prevents old TTLs or negative cache records from obstructing new name resolution attempts.
5
Query the remote DNS server directly using `nslookup`.
Tests network transport on port 53 and verifies server authoritative zone data.
Direct lookup bypasses local client mechanisms to isolate whether the root cause resides on the network or upstream DNS server.

Key Concept

Standard Operating System Name Resolution Hierarchy and Systematic DNS Troubleshooting Workflow
Question 1218Question

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

Click a left item, then click its matching right item

Items

A 5 GHz access point operating on channel 52 periodically stops transmitting on the 5 GHz band for up to 10 minutes, forcing clients to drop to 2.4 GHz, despite no co-channel APs being present.
A 2.4 GHz wireless client records a high RSSI of -58 dBm, yet suffers severe throughput drop and >50% frame retransmissions near active legacy industrial equipment operating on 2.45 GHz.
A newly deployed access point configured on 2.4 GHz channel 3 causes excessive Frame Check Sequence (FCS) errors and packet corruption for clients on adjacent APs set to channel 1.
A wireless client stationed in a modern glass and steel atrium displays strong signal strength (-52 dBm RSSI) but experiences frequent corrupt frames due to out-of-phase signal reflections.

Matches

Show answer & explanation

Answer

1. Dynamic Frequency Selection (DFS) radar detection matches the periodic 5 GHz channel 52 radio shutoffs. 2. Non-802.11 RFI matches the high RSSI but low SNR/high retransmission scenario near industrial equipment. 3. Adjacent-Channel Interference (ACI) matches channel 3 overlapping channel 1. 4. Multipath propagation delay spread matches high RSSI with signal reflection corruption in the steel/glass atrium.
Each scenario maps directly to its characteristic RF phenomenon: DFS radar quiet periods cause periodic channel 52 outages; non-802.11 RF energy elevates noise floor and degrades SNR despite high RSSI; non-standard 2.4 GHz channel allocations (channel 3) generate ACI against channel 1; and reflective architectural elements create multipath delay spread leading to inter-symbol interference.

Step-by-Step Solution

1
Analyze the 5 GHz periodic outage scenario
Identify DFS requirement on UNII-2/UNII-2 Extended channels (channels 52-144)
Federal regulations require APs to clear the channel upon detecting radar signals, taking the 5 GHz radio offline during the CAC scan period.
2
Evaluate high RSSI combined with high retransmission rates near non-Wi-Fi equipment
Identify Non-802.11 RFI as the noise floor inflator
RSSI measures total energy (signal + noise). Non-Wi-Fi RF sources increase noise, reducing SNR without providing decodable Wi-Fi frames.
3
Assess the 2.4 GHz channel 3 deployment impact on channel 1
Identify Adjacent-Channel Interference (ACI)
Channels 2 through 5 overlap partially with channel 1. Partially overlapping channels cause uncoordinated transmission collisions and frame corruption.
4
Examine the reflective atrium environment with high RSSI but corrupt frames
Identify Multipath delay spread / Inter-symbol interference
Multiple reflected waves arriving at slightly different times cause phase cancellation and symbol distortion even when total received energy is strong.

Key Concept

Advanced Wireless RF Troubleshooting and Interference Mechanisms
Estimated Time:3m 0s
Question 1219Question

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

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

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

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

1
Analyze the nslookup command output
The target DNS server at 10.0.0.10 answered the query directly with 'Non-existent domain' (NXDOMAIN).
An explicit NXDOMAIN response indicates that network connectivity and DNS service availability are functional.
2
Determine the cause of the NXDOMAIN response
The DNS zone database on the server does not contain a valid mapping for portal.local.
Standard hostname resolution requires a host (A or AAAA) record entry in the DNS server database.

Key Concept

Interpreting DNS Lookup Output and NXDOMAIN Error Response
Question 1220Question

A network technician is configuring a workstation with the IP address 192.168.1.45 and a subnet mask of 255.255.255.0. The technician manually sets the workstation's default gateway address to 192.168.2.1. The workstation can communicate with other hosts on the 192.168.1.0/24 subnet but cannot reach any internet destinations. Which of the following is the most likely cause of this issue?

Show answer & explanation

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

Answer

The default gateway address is configured on a different IP subnet than the workstation.
For a workstation to send traffic to external networks, its default gateway must be on the same local IP subnet. With an IP of 192.168.1.45/24, the gateway must be an address within 192.168.1.0/24 (such as 192.168.1.1). Configuring 192.168.2.1 makes the gateway unreachable at Layer 2.

Step-by-Step Solution

1
Determine the host subnet boundaries.
An IP of 192.168.1.45 with mask 255.255.255.0 (/24) belongs to the 192.168.1.0/24 subnet with usable host IPs from 192.168.1.1 through 192.168.1.254.
Host IP configuration determines which addresses are considered local (on-link).
2
Compare the default gateway IP to the host subnet.
The IP address 192.168.2.1 belongs to the 192.168.2.0/24 subnet.
To route off-subnet traffic, the host must be able to send Ethernet frames directly to the gateway's IP address on the local segment.
3
Identify the connectivity impact.
Because 192.168.2.1 is off-link, the workstation cannot send ARP requests directly to resolve the gateway's MAC address, preventing remote communication.
Default gateways must be local host neighbors on the same IP subnet.

Key Concept

Default Gateway Subnet Alignment
Estimated Time:45s
PreviousPage 61 / 112Next
All practice questions — CompTIA Network+ | Examkin