Free Practice Questions for CompTIA N10-009 Exam

A Security Information and Event Management (SIEM) system collects, correlates, and analyzes logs from multiple sources in real-time, providing enhanced visibility across multivendor environments.

Breakdown of Options:

A. SNMP – SNMP is used for network device monitoring, but it lacks real-time correlation across multiple vendors.

B. SIEM – Correct answer. SIEM aggregates, analyzes, and correlates logs from multiple sources, providing real-time visibility.

C. Nmap – Nmap is a network scanning tool used for mapping hosts and detecting open ports but does not provide log correlation.

D. Syslog – Syslog collects logs but does not correlate or analyze them in real-time.

When the command switchport voice vlan 69 is used, it tags the voice traffic with VLAN 69, while the workstation traffic continues untagged on the access VLAN, which is typically considered thedata VLAN. This configuration enables both voice and data traffic over the same port while keeping them in separate VLANs for QoS and traffic management.

To enable communication between VLANs, the technician must configure inter-VLAN routing. On a Layer 3 switch, this is commonly done by creating an SVI (Switched Virtual Interface) for each VLAN. An SVI provides a virtual Layer 3 interface with an IP address that acts as the default gateway for hosts in that VLAN. Once SVIs exist and routing is enabled, the switch can route traffic between VLAN subnets internally, allowing clients in different VLANs to communicate (subject to any security controls). This aligns with Network+ (N10-009) infrastructure objectives covering VLANs, Layer 2/Layer 3 switching, and the requirement for routing to cross broadcast domains.

ACLs can permit or deny inter-VLAN traffic, but they do not create the routing function by themselves. VXLAN is an overlay tunneling technology used mainly in data centers to extend Layer 2 networks over Layer 3 fabrics, not the standard solution for basic VLAN-to-VLAN connectivity on a switch. VPC is not the required configuration element for inter-VLAN routing in this context. Therefore, configuring SVIs is the correct and most direct answer.

===========

Definition of RPO:

Recovery Point Objective (RPO) is a disaster recovery metric that describes the maximum acceptable amount of data loss measured in time. It indicates the point in time to which data must be recovered to resume normal operations after a disaster.

For example, if the RPO is set to 24 hours, then the business could tolerate losing up to 24 hours ' worth of data in the event of a disruption.

Why RPO is Important:

RPO is critical for determining backup frequency and helps businesses decide how often they need to back up their data. A lower RPO means more frequent backups and less potential data loss.

Comparison with Other Metrics:

MTTR (Mean Time to Repair): Refers to the average time required to repair a system or component and return it to normal operation.

RTO (Recovery Time Objective): The maximum acceptable length of time that a computer, system, network, or application can be down after a failure or disaster occurs.

MTBF (Mean Time Between Failures): The predicted elapsed time between inherent failures of a system during operation.

How RPO is Used in Disaster Recovery:

Organizations establish RPOs to ensure that they can recover data within a timeframe that is acceptable to business operations. This involves creating a backup plan that meets the RPO requirements.

Nmap (Network Mapper) is a powerful network scanning tool used to discover hosts and services on a computer network. It can be used to identify which ports are open on a remote server, which can help diagnose access issues to services like a remote file server.

Port Scanning: Nmap can perform comprehensive port scans to determine which ports are open and what services are running on those ports.

Network Discovery: It provides detailed information about the host’s operating system, service versions, and network configuration.

Security Audits: Besides troubleshooting, Nmap is also used for security auditing and identifying potential vulnerabilities.

Network References:

CompTIA Network+ N10-007 Official Certification Guide: Covers network scanning tools and their uses.

Nmap Documentation: Official documentation provides extensive details on how to use Nmap for port scanning and network diagnostics.

Network+ Certification All-in-One Exam Guide: Discusses various network utilities, including Nmap, and their applications in network troubleshooting.

The correct answer is Ad hoc because it allows wireless devices to communicate directly with one another without requiring a centralized access point or additional infrastructure. According to CompTIA Network+ (N10-009) objectives under wireless networking concepts, an ad hoc network (also known as an Independent Basic Service Set, or IBSS) enables peer-to-peer wireless communication.

This type of network is ideal for temporary or quick setups where only a small number of devices need to connect. In an ad hoc configuration, each device connects directly to others, making it simple and fast to deploy without requiring switches, routers, or wireless access points.

Spine and leaf (Option B) is a data center architecture designed for high scalability and redundancy, not small wireless setups. Point-to-point (Option C) refers to a direct connection between two devices only, which would not support five devices efficiently. Mesh (Option D) allows multiple nodes to interconnect and provide redundancy, but it is more complex and typically requires compatible infrastructure devices.

Therefore, for a quick setup with five wireless devices, an ad hoc network is the most appropriate choice.

The correct answer is B. NAT64 . This scenario says the internal network is using only IPv6 . In the real world, many internet services still rely on IPv4, so an IPv6-only client may need a translation mechanism to reach IPv4-based servers. That is exactly where NAT64 is used. It allows communication between IPv6-only clients and IPv4 resources by translating between the two protocols.

The other options do not solve that requirement. MPLS is used for traffic forwarding across provider networks and has nothing to do with IPv4/IPv6 protocol translation. GRE creates tunnels, but it does not automatically translate one IP version into another. Static routing can direct traffic, but it cannot make IPv6-only hosts speak to IPv4-only internet destinations.

From a Network+ perspective, this question is testing knowledge of IPv6 transition and interoperability mechanisms . If the network is entirely IPv6 internally, but still needs access to parts of the internet that may be IPv4, some translation service has to exist at the boundary. Among the choices given, NAT64 is the only technology that fits that role. That is why B is the best answer.

To verify ownership of a domain, providers commonly require adding a TXT record to DNS containing a specific validation token (a name/value pair). A TXT (text) record is designed to store arbitrary text data associated with a domain or hostname, which makes it ideal for domain verification workflows used by certificate authorities, email security (SPF/DKIM/DMARC-related entries), and third-party services that need proof of administrative control over DNS. This fits Network+ DNS objectives that cover common record types and their practical purposes in real deployments.

An A record maps a hostname to an IPv4 address and is used for name-to-address resolution, not ownership verification. A PTR record provides reverse DNS mapping (IP address to hostname) and is stored in reverse lookup zones, not typically used for validating web domain ownership. A CNAME record creates an alias from one hostname to another canonical hostname; while sometimes used in service integrations, the classic “record name + token value” ownership verification is most directly and universally satisfied by a TXT record. Therefore, TXT is the correct choice given the requirement and the provided record name and value.

Understanding TTL (Time to Live):

TTL is a value in a DNS record that tells how long that record should be cached by DNS servers and clients. A higher TTL value means that the record will be cached longer, reducing the load on the DNS server but delaying the propagation of changes.

Impact of TTL on DNS Changes:

When an MX record change is made, it may take time for the change to propagate across all DNS servers due to the TTL setting. If the TTL is high, old DNS information might still be cached, leading to email being directed to the old server.

Best Practice Before Making DNS Changes:

To ensure that changes to DNS records propagate quickly, it is recommended to reduce the TTL value to a lower value (such as 300 seconds or 5 minutes) well in advance of making the changes. This ensures that any cached records will expire quickly, and the new records will be used sooner.

Verification of DNS Changes:

After reducing the TTL and making the change to the MX record, it is important to verify the propagation using tools like dig or nslookup.

Comparison with Other Options:

Change the email client configuration to match the MX record: Email clients generally do not need to match the MX record directly; they usually connect to a specific mail server specified in their settings.

Perform a DNS zone transfer prior to the MX record change: DNS zone transfers are used to replicate DNS records between DNS servers, but they are not related to the propagation of individual record changes.

Update the NS record to reflect the IP address change: NS records specify the DNS servers for a domain and are not related to MX record changes.

Troubleshooting poor performance of a newly installed access point involves multiple steps. Checking for network bottlenecks and ensuring the device firmware is up to date are crucial first steps. The document confirms:“Network bottlenecks can severely limit the performance of even the fastest wireless access points, so it’s essential to verify that no other devices are causing a slowdown. In addition, keeping firmware updated ensures optimal performance and security.”

The correct answer is B. Installing a network tap in-line with the web server. A network tap (Test Access Point) is a hardware device placed directly in-line between network devices, allowing it to capture all traffic flowing across the link. Because it operates at the physical layer, a tap can capture 100% of packets, including malformed frames and Layer 1 errors, which are often missed by other methods.

This solution also minimizes impact on infrastructure, as taps are passive devices that do not introduce significant latency or processing overhead. They do not rely on switch configuration or consume switch resources, making them ideal for high-fidelity packet capture during troubleshooting.

Other options do not meet all requirements. Port mirroring (SPAN) can capture traffic but may drop packets under heavy load and typically does not capture Layer 1 errors. Installing a protocol analyzer on the server only captures traffic processed by the server’s NIC and may miss certain low-level issues. Running Nmap is an active scanning tool used for discovery and security auditing, not packet capture.

Therefore, a network tap is the best solution for complete, accurate, and low-impact packet capture.

Port mirroring, also known as SPAN (Switched Port Analyzer), is used to send a copy of network packets seen on one switch port (or an entire VLAN) to another port where the IDS is connected. This allows the IDS to passively inspect network traffic without interfering with the actual traffic flow. Port mirroring is an essential feature for implementing IDS in a network for traffic analysis and security monitoring.References: CompTIA Network+ study materials.

MAC flooding overwhelms a switch’s CAM (Content Addressable Memory) table by sending a flood of frames with spoofed MAC addresses. Once the CAM table overflows, the switch cannot learn legitimate MAC addresses and defaults to flooding all frames out all ports, effectively turning it into a hub. This allows an attacker to capture traffic not originally destined for their port.

A. ARP poisoning corrupts ARP tables to redirect traffic but does not overflow the CAM table.

B. Evil twin is a wireless rogue AP attack, unrelated to switch behavior.

D. DNS spoofing redirects domain queries, not Layer 2 switching.

References (CompTIA Network+ N10-009):

Domain: Network Security — Switch security, CAM table attacks, MAC flooding.