N10-009 Exam Dumps - CompTIA Network+ Certification 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.

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 CompTIA troubleshooting methodology includes steps like identifying the problem, establishing a theory of probable cause, testing the theory, creating a plan of action, implementing the solution, verifying functionality, and documenting findings. Establishing a theory involves analyzing the problem and considering possible causes, often by systematically checking each level of the OSI model (Physical, Data Link, Network, etc.) to pinpoint the root cause.

Why not Implement the solution? This step involves applying the fix, not analyzing the OSI model.

Why not Create a plan of action? This step focuses on planning the solution, not diagnosing the cause.

Why not Verify functionality? This step confirms the solution worked, not analyzing the OSI model.

The right answer is C. BNC . A BNC connector is associated with coaxial cabling , which has been used for certain networking, video, and radio frequency applications. In networking history, coax with BNC connectors was common in older Ethernet implementations such as 10BASE2.

The other choices point to different media types. SC is a fiber optic connector. MPO is also a fiber connector, usually for high-density fiber connections. RJ11 is commonly used for telephone wiring rather than coaxial network cabling. Since the question specifically asks about transmission through a coaxial cable , BNC is the only match.

This is one of those basic media and connector recognition questions that CompTIA likes to include. The goal is to connect the connector type to the cabling standard it belongs with. When you see coax, the classic connector to remember is BNC . When you see fiber, think of connectors such as SC, LC, ST, or MPO. When you see telephone pairs, RJ11 is the common answer.

So the clean way to solve this one is by matching cable type to connector type. Coaxial cable goes with BNC .

After implementing a solution and putting preventive measures in place, the next step is to verify that the system is functioning correctly. This ensures that the issue has been fully resolved.

=================

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.”

Comprehensive and Detailed Explanation (aligned to N10-009):

For a log collector server, the primary needed service is Syslog, which typically uses UDP port 514. Other ports may be open for management (e.g., 22 for SSH) or SNMP traps (162) if integrated. However, port 80 (HTTP) should not be open unless required, as it increases attack surface and does not directly serve the log collection purpose. Disabling it hardens the server.

A. 22 (SSH) is needed for secure management.

C. 162 (SNMP trap) may be required for monitoring/log correlation.

D. 514 (Syslog) is essential for log collection.

References (CompTIA Network+ N10-009):

Domain: Network Security — Hardening servers, disabling unnecessary services and ports.

VXLAN (Virtual Extensible LAN) encapsulates Ethernet frames inside UDP packets, increasing packet size. This can lead to fragmentation and performance degradation unless Jumbo Frames are enabled.

Breakdown of Options:

A. 802.1Q tagging – VLAN tagging enables segmentation but does not address fragmentation issues.

B. Spanning tree – STP prevents loops but does not improve performance for VXLAN traffic.

C. Link aggregation – LACP combines links for higher bandwidth but does not prevent fragmentation.

D. Jumbo frames – Correct answer. Enabling Jumbo Frames allows larger packet sizes, reducing fragmentation and improving VXLAN performance.