CompTIA N10-009 - CompTIA Network+ Certification Exam

The correct solution is to configure the connecting ports as trunk ports. When connecting switches, the uplink ports must be configured to carry traffic for multiple VLANs (trunking), not just a single access VLAN. Without trunking, VLAN tags may be dropped, and traffic from hosts will not reach the rest of the network or internet.

B. STP cables is a misnomer — STP refers to Spanning Tree Protocol or Shielded Twisted Pair cables, neither of which solves this logical configuration issue.

C. PoE budget is irrelevant because switches and hosts in this context don’t require PoE.

D. Link aggregation (LACP, EtherChannel) is for increasing bandwidth/redundancy across multiple links, not required with a single cable.

By enabling trunking on the uplink ports, the switches can pass VLAN-tagged traffic, ensuring hosts connected to the new switch have access to the same resources as those on the existing switch.

References (CompTIA Network+ N10-009):

Domain: Network Troubleshooting — VLAN trunking, inter-switch connectivity.

The correct answer is ACL (Access Control List). According to the CompTIA Network+ N10-009 objectives, ACLs are a fundamental and cost-effective method for controlling traffic flow at routers and firewalls. An ACL allows administrators to permit or deny traffic based on source IP address, destination IP address, protocol, or port number.

In this scenario, the suspicious traffic is identified as originating from a specific unknown foreign IP address. The most direct and economical mitigation strategy is to configure an ACL rule that denies traffic from that specific IP address (or subnet) at the network perimeter. This approach leverages existing network infrastructure without requiring additional hardware or licensing costs.

An IDS (Intrusion Detection System) monitors and alerts on malicious activity but does not actively block traffic unless paired with IPS functionality, and it may involve additional cost and complexity. NAT is used for address translation and does not provide traffic filtering based on threat intelligence. DoS prevention solutions are typically more advanced, specialized, and costly, often intended for large-scale distributed denial-of-service attacks rather than blocking traffic from a single suspicious IP.

The Network+ objectives emphasize implementing layered security controls, starting with simple and effective measures. In this case, applying an ACL at the firewall or router is the most cost-efficient and immediate method to mitigate the identified threat.

To monitor server availability, SNMP traps are the best choice. SNMP (Simple Network Management Protocol) allows devices to send alerts (traps) when certain conditions are met, such as server downtime or high resource usage.

Breakdown of Options:

A. Packet capture – Capturing packets provides insights into network traffic but does not actively monitor server availability.

B. Data usage reports – These analyze network traffic consumption but do not indicate whether a server is available or not.

C. SNMP traps – Correct answer. SNMP traps notify administrators of server issues in real time.

D. Configuration monitoring – This tracks configuration changes rather than availability.

The three-tier hierarchical model in network design consists of three layers: access, distribution, and core. The access layer is where devices like PCs and printers connect to the network. The distribution layer aggregates the data received from the access layer switches before it is transmitted to the core layer, which is responsible for high-speed data transfer and routing. This approach improves scalability and performance in larger networks. References: CompTIA Network+ Exam Objectives and official study guides.

•Cable termination issues (e.g., improper crimping, loose connectors) can cause connectivity failures.

•Power budget (A) applies to PoE devices, not general cabling issues.

•Device requirements (B) relate to software/hardware compatibility, not wiring faults.

•Port status (C) would help if the issue was switch-related, but since moving devices didn’t help, it’s likely a cabling issue.

📖 Reference: CompTIA Network+ N10-009 Official Documentation – Cabling & Physical Layer Troubleshooting.

(Note: Ips will be change on each simulation task, so we have given example answer for the understanding)

To troubleshoot all the network components and review the cable test results, you can use the following steps:

Click on each device and cable to open its information window.

Review the information and identify any problems or errors that may affect the network connectivity or performance.

Diagnose the appropriate component(s) by identifying any components with a problem and recommend a solution to correct each problem.

Fill in the remediation form using the drop-down menus provided.

Here is an example of how to fill in the remediation form for PC1:

The component with a problem is PC1.

The problem is Incorrect IP address.

The solution is Change the IP address to 192.168.1.10.

You can use the same steps to fill in the remediation form for other components.

To enter commands in each device, you can use the following steps:

Click on the device to open its terminal window.

Enter the command ipconfig /all to display the IP configuration of the device, including its IP address, subnet mask, default gateway, and DNS servers.

Enter the command ping < IP address >  to test the connectivity and reachability to another device on the network by sending and receiving echo packets. Replace < IP address > with the IP address of the destination device, such as 192.168.1.1 for Core Switch 1.

Enter the command tracert < IP address >  to trace the route and measure the latency of packets from the device to another device on the network by sending and receiving packets with increasing TTL values. Replace < IP address > with the IP address of the destination device, such as 192.168.1.1 for Core Switch 1.

Here is an example of how to enter commands in PC1:

Click on PC1 to open its terminal window.

Enter the command ipconfig /all to display the IP configuration of PC1. You should see that PC1 has an incorrect IP address of 192.168.2.10, which belongs to VLAN 2 instead of VLAN 1.

Enter the command ping 192.168.1.1 to test the connectivity to Core Switch 1. You should see that PC1 is unable to ping Core Switch 1 because they are on different subnets.

Enter the command tracert 192.168.1.1 to trace the route to Core Switch 1. You should see that PC1 is unable to reach Core Switch 1 because there is no route between them.

You can use the same steps to enter commands in other devices, such as PC3, PC4, PC5, and Server 1.

LDAP (Lightweight Directory Access Protocol) uses port 389 for standard connections and port 636 for LDAP over SSL (LDAPS), which secures directory service communication.

Breakdown of Options:

A. 22 – SSH port, not used for directory services.

B. 389 – Used for LDAP, but not encrypted.

C. 445 – Used for SMB file sharing, not LDAP.

D. 636 – Correct answer. LDAPS (LDAP over SSL/TLS) secures directory authentication.

The correct solution is NTP (Network Time Protocol). Accurate timestamps across servers, firewalls, and network devices are critical for correlating logs during incident response. NTP synchronizes device clocks to a trusted time source, ensuring consistency across the network.

A. Syslog centralizes logs but does not synchronize time.

B. SMTP is email transfer, unrelated to time.

D. SNMP monitors devices but does not correct time discrepancies.

By implementing NTP, analysts can ensure that logs from different devices are time-aligned, which is essential for reconstructing attack timelines and detecting anomalies.

References (CompTIA Network+ N10-009):

Domain: Network Operations — Time synchronization, NTP, log correlation.

Bottlenecking occurs when a device in the network (such as an IPS) cannot process traffic efficiently, resulting in a dramatic drop in throughput. The significant difference between the firewall ' s speed (48.8 Mbps down) and the end-user devices’ speeds (4.8 - 5.2 Mbps down) indicates a bottleneck caused by the IPS.

•Why not the other options?

•Packet loss (A) – Would typically cause connection timeouts, not just slow speeds.

•Channel overlap (C) – Affects only wireless networks, but the wired desktop is also experiencing slow speeds.

•Network congestion (D) – Would show fluctuations in both upload and download speeds, but upload speeds remain unaffected.

Out-of-band (OOB) management refers to using a dedicated management network that is physically separate from the regular data network. This management network uses a different set of IP addresses to ensure that management traffic is isolated from user data traffic, providing a secure way to manage network devices even if the main network is down or compromised.References: CompTIA Network+ study materials. ​

Spanning Tree Protocol (STP) uses bridge priority values to determine the root bridge in a switched network topology. Correctly configuring bridge priority helps in maintaining a loop-free and efficient network. The document explains:

“Spanning Tree Protocol (STP) uses bridge priority values to determine which switch will be the root bridge, ensuring loop prevention and efficient path selection within the network.”

An API (Application Programming Interface) is the best choice when a development team needs to integrate a device’s reporting data directly into custom software. In Network+ (N10-009) objectives, network operations commonly include device management, monitoring, and automation, and APIs are a key method for programmatic access to operational data (often via REST/HTTPS with structured formats like JSON). This enables the internal support application to pull dashboards, health metrics, events, configuration details, and reporting outputs in a controlled, developer-friendly way.

SNMPv2c is primarily used for network monitoring and polling counters/alerts, but it is less secure (community strings) and is not as flexible for modern application integration as an API. A MIB is not a data-access “feature” by itself; it’s the schema/definitions SNMP uses to describe managed objects. A SIEM is a separate security analytics platform that collects and correlates logs/events—useful for security operations, but not the direct interface a custom support tool would typically call to retrieve device reporting data.

Link aggregation (also known as port trunking or EtherChannel) combines multiple network connections in parallel to increase throughput and provide redundancy. When two switches are connected with multiple links without any additional configuration, a Layer 2 loop may occur. Link aggregation prevents these loops by treating the multiple connections as a single logical link, using a protocol such as LACP (Link Aggregation Control Protocol).

From Andrew Ramdayal’s guide:

“Link aggregation allows you to combine multiple network connections to increase the bandwidth and provide redundancy. It helps prevent Layer 2 loops when connecting switches with multiple links by making them operate as a single logical interface.”

Definition of a Rogue DHCP Server:

A rogue DHCP server is an unauthorized DHCP server on a network, which can assign IP addresses to devices without proper control, leading to IP address conflicts.

Impact of a Rogue DHCP Server:

IP Address Conflicts: Multiple devices may receive the same IP address from different DHCP servers, causing network connectivity issues.

Network Disruption: Devices may be assigned incorrect network configuration settings, disrupting network services and connectivity.

Comparison with Other Attacks:

DNS poisoning: Alters DNS records to redirect traffic to malicious sites, but does not cause IP address conflicts.

Social engineering: Involves manipulating individuals to gain unauthorized access or information, not directly related to IP address conflicts.

Denial-of-service (DoS): Floods a network or service with excessive traffic to disrupt operations, but does not cause duplicate IP addresses.

Prevention and Detection:

Implement network access control measures to prevent unauthorized devices from acting as DHCP servers.

Use DHCP snooping on switches to allow DHCP responses only from authorized DHCP servers.

An access point (AP) provides users with an extended footprint that allows connections from multiple devices within a designated Wireless Local Area Network (WLAN).

Router: Typically used to connect different networks, not specifically for extending wireless coverage.

Switch: Used to connect devices within a wired network, not for providing wireless access.

Access Point (AP): Extends wireless network coverage, allowing multiple wireless devices to connect to the network.

Firewall: Primarily used for network security, controlling incoming and outgoing traffic based on security rules, not for providing wireless connectivity.

Network References:

CompTIA Network+ N10-007 Official Certification Guide: Explains the roles and functions of network appliances, including access points.

Cisco Networking Academy: Provides training on deploying and managing wireless networks with access points.

Network+ Certification All-in-One Exam Guide: Covers network devices and their roles in creating and managing networks.