Free Practice Questions for CompTIA N10-009 Exam

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.

In a split-tunnel VPN, only corporate traffic is sent through the VPN tunnel, while public internet traffic goes directly through the user’s local ISP. This reduces bandwidth use on the corporate VPN concentrator and improves performance for non-work traffic.

B. Separate tunnels for encrypted traffic describes multi-tunnel VPNs, not split tunneling.

C. All traffic routed through on-site servers is a full-tunnel VPN, not split-tunnel.

D. ACLs balancing traffic relates to routing or load balancing, not VPN split tunneling.

References (CompTIA Network+ N10-009):

Domain: Networking Concepts — VPN types, split vs. full tunnel, remote access.

Understanding MTBF:

Mean Time Between Failures (MTBF): A reliability metric that estimates the average time between successive failures of a device or system.

Calculation and Importance:

Calculation: MTBF is calculated as the total operational time divided by the number of failures during that period.

Usage: Used by manufacturers and engineers to predict the lifespan and reliability of a device, helping in maintenance planning and lifecycle management.

Comparison with Other Metrics:

RTO (Recovery Time Objective): The maximum acceptable time to restore a system after a failure.

RPO (Recovery Point Objective): The maximum acceptable amount of data loss measured in time.

MTTR (Mean Time to Repair): The average time required to repair a device or system and return it to operational status.

Application:

MTBF is crucial for planning maintenance schedules, spare parts inventory, and improving the overall reliability of systems.

The correct solution is a Data Center Interconnect (DCI). DCIs extend Layer 2 networks across geographically dispersed data centers, enabling seamless replication of services such as SAN storage, backup synchronization, or VM migrations. This ensures workloads and data can move between sites while maintaining the same VLANs and addressing.

A. Security Service Edge (SSE) provides cloud-delivered security functions like secure web gateways and CASB, not Layer 2 extension.

C. Infrastructure as code (IaC) automates deployment and management of network infrastructure but is unrelated to extending Layer 2 domains.

D. Zero Trust architecture is a security framework ensuring strict access control but doesn’t address network connectivity between sites.

In scenarios where backups need replication between sites, Layer 2 extension is often required so systems can communicate as if they are in the same broadcast domain. DCI is specifically designed to provide this functionality reliably and securely.

References (CompTIA Network+ N10-009):

Domain: Network Infrastructure — WAN technologies, data center interconnect, backup replication.

Devices in both buildings should be able to access the Internet.

Security insists that all Internet traffic be inspected before entering the network.

Desktops should not see traffic destined for other devices.

Here is the corrected layout with explanation:

Building A:

Switch: Correctly placed to connect all desktops.

Firewall: Correctly placed to inspect all incoming and outgoing traffic.

Building B:

Switch: Not needed. Instead, place a Wireless Access Point (WAP) to provide wireless connectivity for laptops and mobile devices.

Between Buildings:

Wireless Range Extender: Correctly placed to provide connectivity between the buildings wirelessly.

Connection to the Internet:

Router: Correctly placed to connect to the Internet and route traffic between the buildings and the Internet.

Firewall: The firewall should be placed between the router and the internal network to inspect all traffic before it enters the network.

Corrected Setup:

Top-left (Building A): Switch

Bottom-left (Building A): Firewall (inspect traffic before it enters the network)

Top-middle (Internet connection): Router

Bottom-middle (between buildings): Wireless Range Extender

Top-right (Building B): Wireless Access Point (WAP)

In this corrected setup, the WAP in Building B will connect wirelessly to the Wireless Range Extender, which is connected to the Router. The Router is connected to the Firewall to ensure all traffic is inspected before it enters the network.

Configuration for Wireless Range Extender:

SSID: CORP

Security Settings: WPA2 or WPA2 - Enterprise

Key or Passphrase: [Enter a strong passphrase]

Mode: [Set based on your network plan]

Channel: [Set based on your network plan]

Speed: Auto

Duplex: Auto

With these settings, both buildings will have secure access to the Internet, and all traffic will be inspected by the firewall before entering the network. Desktops and other devices will not see traffic intended for others, maintaining the required security and privacy.

To configure the wireless range extender for security, follow these steps:

SSID (Service Set Identifier):

Ensure the SSID is set to " CORP " as shown in the exhibit.

Security Settings:

WPA2 or WPA2 - Enterprise: Choose one of these options for stronger security. WPA2-Enterprise provides more robust security with centralized authentication, which is ideal for a corporate environment.

Key or Passphrase:

If you select WPA2, enter a strong passphrase in the " Key or Passphrase " field.

If you select WPA2 - Enterprise, you will need to configure additional settings for authentication servers, such as RADIUS, which is not shown in the exhibit.

Wireless Mode and Channel:

Set the appropriate mode and channel based on your network design and the environment to avoid interference. These settings are not specified in the exhibit, so set them according to your network plan.

Wired Speed and Duplex:

Set the speed to " Auto " unless you have specific requirements for 100 or 1000 Mbps.

Set the duplex to " Auto " unless you need to specify half or full duplex based on your network equipment.

Save Configuration:

After making the necessary changes, click the " Save " button to apply the settings.

Here is how the configuration should look after adjustments:

SSID: CORP

Security Settings: WPA2 or WPA2 - Enterprise

Key or Passphrase: [Enter a strong passphrase]

Mode: [Set based on your network plan]

Channel: [Set based on your network plan]

Speed: Auto

Duplex: Auto

Once these settings are configured, your wireless range extender will provide secure connectivity for devices in both buildings.

Firewall setting to to ensure complete compliance with the requirements and best security practices, consider the following adjustments and additions:

DNS Rule: This rule allows DNS traffic from the internal network to any destination, which is fine.

HTTPS Outbound: This rule allows HTTPS traffic from the internal network (assuming 192.169.0.1/24 is a typo and should be 192.168.0.1/24) to any destination, which is also good for secure web browsing.

Management: This rule allows SSH access to the firewall for management purposes, which is necessary for administrative tasks.

HTTPS Inbound: This rule denies inbound HTTPS traffic to the internal network, which is good unless you have a web server that needs to be accessible from the internet.

HTTP Inbound: This rule denies inbound HTTP traffic to the internal network, which is correct for security purposes.

Suggested Additional Settings:

Permit General Outbound Traffic: Allow general outbound traffic for web access, email, etc.

Block All Other Traffic: Ensure that all other traffic is blocked to prevent unauthorized access.

Firewall Configuration Adjustments:

Correct the Network Typo:

Ensure that the subnet 192.169.0.1/24 is corrected to 192.168.0.1/24.

Permit General Outbound Traffic:

Rule Name: General Outbound

Source: 192.168.0.1/24

Destination: ANY

Service: ANY

Action: PERMIT

Deny All Other Traffic:

Rule Name: Block All

Source: ANY

Destination: ANY

Service: ANY

Action: DENY

Here is how your updated firewall settings should look:

Rule Name

Source

Destination

Service

Action

DNS Rule

192.168.0.1/24

ANY

DNS

PERMIT

HTTPS Outbound

192.168.0.1/24

ANY

HTTPS

PERMIT

Management

ANY

192.168.0.1/24

SSH

PERMIT

HTTPS Inbound

ANY

192.168.0.1/24

HTTPS

DENY

HTTP Inbound

ANY

192.168.0.1/24

HTTP

DENY

General Outbound

192.168.0.1/24

ANY

ANY

PERMIT

Block All

ANY

ANY

ANY

DENY

These settings ensure that:

Internal devices can access DNS and HTTPS services externally.

Management access via SSH is permitted.

Inbound HTTP and HTTPS traffic is denied unless otherwise specified.

General outbound traffic is allowed.

All other traffic is blocked by default, ensuring a secure environment.

Make sure to save the settings after making these adjustments.

802.1X provides port-based Network Access Control (NAC). Ports remain in a blocked state until a device authenticates (usually with RADIUS). This is ideal for public or semi-public areas where ports should not be “always on.”

A. Port security restricts by MAC addresses but does not authenticate users.

C. MAC filtering is easily spoofed and weaker than 802.1X.

D. ACLs filter traffic but do not enforce port-based authentication.

References (CompTIA Network+ N10-009):

Domain: Network Security — NAC, 802.1X authentication, port-based security.

X.509 certificates are most commonly associated with Public Key Infrastructure (PKI). These certificates are used for a variety of security functions, including digital signatures, encryption, and authentication.

PKI: X.509 certificates are a fundamental component of PKI, used to manage encryption keys and authenticate users and devices.

Digital Certificates: They are used to establish secure communications over networks, such as SSL/TLS for websites and secure email communication.

Authentication and Encryption: X.509 certificates provide the means to securely exchange keys and verify identities in various applications, ensuring data integrity and confidentiality.

Network References:

CompTIA Network+ N10-007 Official Certification Guide: Covers PKI and the role of X.509 certificates in network security.

Cisco Networking Academy: Provides training on PKI, certificates, and secure communications.

Network+ Certification All-in-One Exam Guide: Explains PKI, X.509 certificates, and their applications in securing network communications.

Understanding ACLs:

Access Control Lists (ACLs): A set of rules used to control network traffic and restrict access to network resources by filtering packets based on IP addresses, protocols, or ports.

Implementing Security Zones:

Defining Zones: ACLs can be used to create security zones by applying specific rules to different departments, ensuring that only authorized traffic is allowed between these zones.

Control Traffic: ACLs control inbound and outbound traffic at network boundaries, enforcing security policies and preventing unauthorized access.

Comparison with Other Options:

Port Security: Limits the number of devices that can connect to a switch port, preventing MAC address flooding attacks, but not used for defining security zones.

Content Filtering: Blocks or allows access to specific content based on predefined policies, typically used for web filtering rather than network segmentation.

NAC (Network Access Control): Controls access to the network based on the security posture of devices but does not define security zones.

Implementation Steps:

Define ACL rules based on the requirements of each department.

Apply these rules to the appropriate network interfaces or firewall policies to segment the network into security zones.

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.

Site-to-Site VPN: A site-to-site VPN is used to securely connect two networks, such as a company ' s headquarters and a branch location, over the internet. This type of VPN creates a secure tunnel for data transmission, ensuring confidentiality and integrity.

Split-tunnel VPN (A): Allows some traffic to bypass the VPN tunnel, which may not secure all communications.

Clientless VPN (B): Used for individual users to access the network without VPN client software.

Full-tunnel VPN (C): Typically used for individual user traffic rather than connecting two networks.

The longest prefix match is a routing concept used to find the most specific route to a destination IP address. The routing table performs this calculation to determine the exit interface for a packet, ensuring the most accurate delivery. The document explains:

“Routers use the longest prefix match when searching the routing table to determine the best path for an IP packet. This ensures that the most specific (and thus optimal) route is chosen, based on the destination IP address.”

The 802.11n standard supports MIMO (Multiple Input Multiple Output), which allows multiple antennas to increase data throughput and improve reliability. Additionally, it uses non-overlapping channels in the 5 GHz band (and optionally the 2.4 GHz band), making it a good choice for high-speed, interference-resistant wireless connections. (Reference: CompTIA Network+ Study Guide, Chapter on Wireless Technologies)

The correct answer is Autonomous system path because BGP (Border Gateway Protocol) prevents routing loops by using the AS_PATH attribute. According to CompTIA Network+ (N10-009) objectives under routing protocols, BGP is a path vector protocol used to exchange routing information between autonomous systems (AS) on the internet.

When a BGP router advertises a route, it includes its autonomous system number (ASN) in the AS_PATH attribute. As the route passes through additional autonomous systems, each AS appends its own ASN to the path. If a BGP router receives a route advertisement that already contains its own ASN in the AS_PATH list, it recognizes this as a loop and rejects the route. This mechanism effectively prevents routing loops across large-scale networks such as the internet.

Option B (Peer autonomous system) refers to neighboring BGP routers but does not describe the loop prevention mechanism. Option C (Autonomous system length) relates to path selection metrics, as shorter AS_PATH lengths are generally preferred, but this is not the loop avoidance function itself. Option D (Public autonomous system) is not a loop prevention mechanism.

Therefore, BGP uses the AS_PATH attribute for loop avoidance.

A SIEM (Security Information and Event Management) platform is built to collect, correlate, and alert on security-relevant events across many sources, which is exactly what’s needed to identify patterns such as brute force attempts, port scanning, and DDoS indicators. In Network+ (N10-009) security operations concepts, correlation is key: a SIEM can ingest logs from firewalls, IDS/IPS, servers, authentication systems, endpoint agents, and network devices, then apply rules/analytics to detect suspicious behavior that might not be obvious from a single log source. It can also generate real-time alerts, dashboards, and incident timelines—helping the engineer respond quickly and prioritize threats.

Packet capture provides deep visibility into traffic but is not inherently designed for enterprise-wide correlation and alerting without significant additional tooling and expertise. SNMPv3 is used for secure device monitoring (status, counters, performance) rather than detecting coordinated attack patterns. A syslog collector centralizes logs but generally does not provide the same level of correlation, enrichment, and automated alerting capabilities as a SIEM. Therefore, SIEM is the best answer.

===========