Free Practice Questions for CompTIA N10-009 Exam

Inconsistent arrival of RTP (Real-Time Protocol) packets indicates jitter or latency variation. A protocol analyzer (packet sniffer, e.g., Wireshark) can capture and analyze RTP streams, showing delay, jitter, and packet loss statistics.

A. Toner and probe locates cable runs, not packet analysis.

C. Cable tester checks wiring faults, not packet timing.

D. Spectrum reader is for identifying wireless interference, not analyzing RTP traffic.

References (CompTIA Network+ N10-009):

Domain: Network Troubleshooting — Protocol analyzers, VoIP troubleshooting, jitter analysis.

A honeypot is specifically designed to attract, isolate, and observe malicious activity so defenders can learn how an attacker is operating and determine attack techniques. In the context of Network+ (N10-009) security objectives, honeypots (and broader deception technologies) are defensive controls used to detect reconnaissance and exploitation attempts by presenting a decoy system or service that appears legitimate. Because a honeypot should not receive normal production traffic, any interaction is suspicious, making it valuable for identifying threat actors, collecting indicators of compromise, and analyzing the attacker’s tools, commands, and behavior patterns. This supports the goal of understanding the type of attack used (for example, credential stuffing, exploitation attempts, lateral movement probes) while keeping the attacker away from real assets.

MFA strengthens authentication but does not provide a controlled environment to observe attacker techniques. A screened subnet (DMZ) is for segmentation of public-facing services and reducing exposure of internal systems, but it is not primarily used to “bait” and analyze attackers. A captive portal enforces user acknowledgement/authentication for network access; it is not a deception/analysis system. Therefore, honeypot is the best match.

===========

A honeynet is a network of honeypots designed to attract and study attackers. Honeypots are decoy systems set up to lure cyber attackers and analyze their activities. A honeynet, being a collection of these systems, provides a broader view of attack methods and patterns, helping organizations improve their security measures. References: CompTIA Network+ Exam Objectives and official study guides.

A large number of collisions and input errors typically indicates a duplex mismatch, such as when one device is set to full duplex and the other to half duplex. This leads to communication issues and poor performance. The document explains:

“Collisions and input errors are clear signs of duplex mismatches… typically caused when one device operates in half duplex while the other is in full duplex, causing performance and connectivity issues.”

This is an example of Multi-Factor Authentication (MFA) because it requires:

Something you know (username/password)

Something you have (a phone-generated passcode)

Breakdown of Options:

A. SSO (Single Sign-On) – Allows one login for multiple services, but does not add a second authentication factor.

B. LDAP (Lightweight Directory Access Protocol) – Used for directory authentication, not MFA.

C. MFA (Multi-Factor Authentication) – ✅ Correct answer. Uses multiple authentication factors for better security.

D. SAML (Security Assertion Markup Language) – Used for federated identity management, not multi-factor authentication.

DNS poisoning (also commonly called DNS cache poisoning) is characterized by inserting fraudulent DNS data into a resolver’s cache so that subsequent queries return incorrect IP mappings. Option D describes this precisely: false DNS records are injected into a DNS server’s cache, causing users to be redirected to attacker-controlled destinations even when they request a legitimate hostname. This aligns with Network+ security objectives covering common network attacks targeting name resolution and trust relationships. Editing authoritative DNS records on a DNS server (A) implies direct compromise or unauthorized administrative change, which is a different scenario than cache poisoning. Setting up a malicious DNS server in place of a legitimate server (B) is closer to DNS hijacking or rogue DNS configuration rather than cache poisoning. Intercepting client requests and returning false responses (C) describes man-in-the-middle style spoofing on the wire; while related, the defining “poisoning” trait is the persistence created by corrupting the cache so the bad answer continues to be served. For defensive relevance in Network+ scope, cache poisoning highlights the importance of DNS security controls such as source port randomization, transaction ID entropy, and DNSSEC validation where applicable.

The CIA triad (Confidentiality, Integrity, Availability) is a foundational security model used in Network+ (N10-009) to evaluate risk and guide prioritization of mitigations. By categorizing assets and threats based on how they could impact confidentiality (data exposure), integrity (unauthorized alteration), or availability (service disruption), administrators can better understand which attacks from external actors matter most to the business and which controls to apply first. For example, a public-facing portal might prioritize availability protections (DDoS mitigation, redundancy), while sensitive customer records demand strong confidentiality controls (encryption, access control), and financial systems require integrity controls (logging, validation, change control). This model helps translate “threats” into business impact, which is central to deciding what to mitigate.

Compliance benchmarks support meeting regulatory/industry requirements, but they don’t inherently provide a conceptual lens for analyzing external attacker impact across all systems. SAML is a federation/authentication standard, not a risk model. A honeypot can provide insight into attacker behavior, but it doesn’t broadly structure risk prioritization the way CIA does. Therefore, CIA triad is the best answer.

===========

Introduction to Administrative Distance

Administrative distance (AD) is a value used by routers to rank routes from different routing protocols. AD represents the trustworthiness of the source of the route. Lower AD values are more preferred. If a router has multiple routes to a destination from different sources, it will choose the route with the lowest AD.

Static Routes and Backup Routes

When a dynamic routing protocol is not used, static routes can be employed. Static routes are manually configured routes. To ensure a backup route, multiple static routes to the same destination can be configured with different AD values.

Configuring Static Routes with Administrative Distance

The primary route is configured with a lower AD value, making it the preferred route. The backup route is configured with a higher AD value. In the event of the primary route failure, the router will then use the backup route.

Example Configuration:

plaintext

Copy code

ip route 192.168.1.0 255.255.255.0 10.0.0.1 1

ip route 192.168.1.0 255.255.255.0 10.0.0.2 10

In the above example, 192.168.1.0/24 is the destination network.

10.0.0.1 is the next-hop IP address for the primary route with an AD of 1.

10.0.0.2 is the next-hop IP address for the backup route with an AD of 10.

Verification:

After configuration, use the show ip route command to verify that the primary route is in use and the backup route is listed as a candidate for use if the primary route fails.

A central repository describes a single location where critical network infrastructure configurations are stored and managed. This can include switch configurations, router configurations, firewall rules, wireless controller settings, diagrams, templates, backup files, and standard operating procedures. A central repository helps administrators maintain consistency, improve recovery time, simplify audits, and reduce the risk of losing important configuration data.

The CompTIA Network+ N10-009 objectives include network documentation, configuration management, change management, and operational best practices. Storing configurations in a central repository supports backup and recovery because administrators can quickly retrieve known-good configurations if a device fails or a change causes an outage. It also helps teams collaborate by giving authorized personnel access to the same current documentation and configuration files.

Version control is related but refers specifically to tracking changes, revisions, and rollback history over time. Conflict mitigation involves reducing conflicts when multiple people work on the same files or configurations. Branching is a version-control feature that allows separate lines of development or change testing. Since the question focuses on housing all configurations in one location, the best answer is central repository.

Top of Form

Bottom of Form

Plugging each switch into a different UPS provides the most uptime during a power outage. A UPS, or uninterruptible power supply, provides temporary battery power when utility power fails. Using separate UPS units also improves redundancy because a failure of one UPS does not necessarily affect both switches. This design helps maintain network availability and supports fault tolerance during electrical outages.

The CompTIA Network+ N10-009 objectives include network availability, redundancy, power management, UPS usage, and environmental considerations. Network switches are critical infrastructure devices, and loss of switch power can disconnect users, servers, wireless access points, VoIP phones, and other dependent systems. A UPS gives administrators time to maintain operations during short outages or shut systems down gracefully during longer outages.

Plugging both switches into the same PDU creates a single point of failure. Plugging each switch into a different circuit improves electrical redundancy, but it does not provide backup power if both circuits lose utility power. Plugging each switch into a different PDU can help with power distribution, but a PDU alone does not provide battery backup unless connected to a UPS. Therefore, different UPS units provide the best uptime.

To monitor the contents of data (i.e., inspect the actual packets/frames and their payloads) moving between networks, the administrator should use port mirroring (also called SPAN on some platforms). Port mirroring copies traffic from one or more switch ports (or VLANs) to a designated monitoring port where a packet analyzer/IDS sensor can capture and inspect the traffic in detail. This aligns with Network+ (N10-009) security and monitoring concepts that distinguish between packet-level visibility and higher-level summaries or logs. If the requirement is explicitly to monitor “contents,” you need a method that provides full packet capture capability, not just metadata.

Flow data (e.g., NetFlow) provides summarized metadata—who talked to whom, how much, ports, and timestamps—but not full payload contents. Syslog entries are device/application-generated logs and only show events a device chooses to report; they don’t provide full data content visibility. SNMP traps are alerts about status changes (interfaces, thresholds, etc.) and similarly do not include traffic contents. Therefore, port mirroring is the correct monitoring method for inspecting data contents in transit.

===========

Importance of Proper Termination:

Cat 8 cabling requires precise termination practices to ensure signal integrity and reduce interference. One common requirement is to wrap the end connections in copper tape to maintain shielding and reduce electromagnetic interference (EMI).

Interference Troubleshooting:

Interference in high-frequency cables like Cat 8 can be caused by improper shielding or grounding. Checking the end connections for proper wrapping in copper tape is a crucial step.

Why Other Options are Less Likely:

Passthrough modular crimping plugs: Not specifically related to interference issues and are typically used for ease of cable assembly.

Connecting RX/TX wires to different pins: Would likely result in no connection or incorrect data transmission rather than interference.

Running a speed test on a device that can only achieve 100Mbps speeds: This would not diagnose interference and would not provide relevant information for Cat 8 cabling rated for higher speeds.

Corrective Actions:

Verify that all end connections are properly wrapped with copper tape before termination.

Ensure that the shielding is continuous and properly grounded throughout the installation.

Retest the cabling for interference after making corrections.

Cross talk can often be caused by improper termination of cables. The first step in troubleshooting should be to inspect the connectors for any wires that might be touching or exposed. Ensuring that all wires are correctly seated and that no conductors are exposed can help reduce or eliminate cross talk. This step should be taken before attempting to re-terminate the connections or check for other sources of interference.References: CompTIA Network+ study materials.