CompTIA N10-009 - CompTIA Network+ Certification Exam

Single Sign-On (SSO) enables a user to access multiple resources or applications with one set of credentials, improving usability and security. The document confirms:

“Single Sign-On (SSO) allows a user to authenticate once and gain access to multiple resources or applications without needing to log in again for each. It streamlines the login process and improves security by reducing the number of passwords that need to be managed.”

Troubleshooting Methodology:

Confirming the Root Cause: After testing and confirming the theory, the next logical step is to address the issue by implementing a solution.

Implementation of the Solution:

Resolve the Issue: Implement the identified solution to rectify the problem. This step involves making necessary changes to the network configuration, replacing faulty hardware, or applying software patches.

Documentation: Document the solution and the steps taken to resolve the issue to provide a reference for future troubleshooting.

Comparison with Other Steps:

Determine Resolution Steps: This is part of the implementation process where specific actions are outlined, but the actual next step after testing is to implement those steps.

Duplicate the Problem in a Lab: This step is typically done earlier in the troubleshooting process to understand the problem, not after confirming the root cause.

Present the Theory for Approval: In some scenarios, presenting the theory might be necessary for major changes, but generally, once the root cause is confirmed, the solution should be implemented.

Final Verification:

After implementing the solution, it is important to verify that the issue is resolved and that normal operations are restored. This may involve monitoring the network and testing to ensure no further issues arise.

Using Pre-Shared Key (PSK) authentication means that all users share the same Wi-Fi password, making it difficult to identify individual users when security incidents occur.

Migrating to WPA2-Enterprise (or WPA3-Enterprise) replaces PSK authentication with individual user credentials using 802.1X authentication and a RADIUS server. This allows the organization to:

Track and log specific user activity

Enforce per-user authentication policies

Improve network security

Breakdown of Options:

A. Restrict users to the 5GHz frequency – Improves performance but does not enhance user tracking or security.

B. Upgrade to a mesh network – A mesh network improves coverage, not security tracking.

C. Migrate from PSK to Enterprise – ✅ Correct answer. WPA2-Enterprise or WPA3-Enterprise uses individual user authentication, allowing per-user tracking.

D. Implement WPA2 encryption – WPA2 is already widely used; it does not resolve the tracking issue.

The issue is that more students have arrived on campus, meaning the available IP addresses are exhausted. To fix this, the administrator should increase the DHCP scope size to allow more devices to obtain IP addresses.

Breakdown of Options:

A. Enable IP helper – IP helper is used to forward DHCP requests across different subnets. However, the problem here is that the DHCP scope is full, not that requests are not reaching the server.

B. Change the subnet mask – The subnet mask determines the number of available hosts, but changing it without increasing the IP pool does not help.

C. Increase the scope size – Correct answer. Expanding the DHCP scope provides more IP addresses for assignment.

D. Add address exclusions – Exclusions reserve IP addresses, which would further reduce available addresses instead of solving the issue.

NetFlow (and similar flow technologies like IPFIX/sFlow in concept) is used to collect traffic-flow metadata such as source/destination IPs, ports, protocols, interfaces, and byte/packet counts over time. In Network+ (N10-009) operations and monitoring objectives, flow data is ideal for identifying top talkers and top destinations across the network on a given day because it provides summarized, queryable information at scale without capturing every packet payload. An administrator can review reports to determine which destination IPs/hosts consumed the most bandwidth, which applications were most active, and what time ranges saw spikes—perfect for historical analysis.

SNMP is great for polling device counters (interface utilization, errors, CPU) but it does not natively tell you the “top destination” by conversation/flow without additional flow awareness. Packet capture can reveal exact conversations and payloads, but it is heavy, localized, and not efficient for infrastructure-wide daily top-destination reporting. traceroute maps the path to a destination and helps isolate routing/path issues; it does not provide usage statistics. Therefore, NetFlow is the best fit.

===========

On Core-SW01, the ports are configured with LACP (mode active) for link aggregation. On Core-SW02, the ports are configured as independent trunks, not as part of an LACP group. Because of this mismatch, LACP cannot form the bundle, and the aggregated ports on SW01 will go into a suspended state.

A. CRC errors suggest cabling or signal integrity issues, not config mismatch.

B. Error disabled occurs when a violation (like BPDU guard or port security) disables the port, not LACP mismatch.

C. Administratively down indicates a shutdown command, not the case here.

References (CompTIA Network+ N10-009):

Domain: Network Troubleshooting — Port-channel/LACP configuration issues, interface states.

The correct solution is a Content Delivery Network (CDN). A CDN caches web content (like images, videos, scripts) on distributed servers close to end users. This reduces latency, improves load times, and decreases the load on origin servers. For a business requiring high-speed access to media-rich content, a CDN is the most effective option.

B. SAN (Storage Area Network) is used for storage in a data center, not for distributing web content.

C. Firewall secures traffic but doesn’t accelerate content delivery.

D. Switches forward packets within a LAN, not globally distribute content.

By leveraging CDNs, businesses can handle large traffic volumes efficiently while improving user experience.

References (CompTIA Network+ N10-009):

Domain: Network Infrastructure — CDNs, caching, performance optimization.

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.

An evil twin attack sets up a rogue AP with the same SSID as a legitimate wireless network, tricking users into connecting. Once connected, the attacker can intercept traffic or harvest credentials.

B. Describes ARP spoofing.

C. Describes MAC spoofing.

D. Describes on-path attacks, which may follow, but the evil twin method begins with SSID impersonation.

References (CompTIA Network+ N10-009):

Domain: Network Security — Wireless threats, rogue APs, evil twin.

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.

===========

•A. Isolate smart devices to their own network segment: Network segmentation using VLANs or separate SSIDs ensures that smart devices (like speakers) are not on the same network as guests, preventing unauthorized control.

•E. Change the default credentials: Many IoT devices (e.g., smart speakers) come with default usernames and passwords. If these are not changed, unauthorized users can easily take control.

•Why not the other options?

•B. Configure IPS: IPS (Intrusion Prevention System) detects threats but cannot block specific guest actions on an IoT device.

•C. Install a new AP: A new access point does not solve the unauthorized control issue.

•D. Set up a syslog server: Helps with logging, but does not prevent unauthorized access.

•F. Configure GRE: Generic Routing Encapsulation (GRE) is used for VPN tunneling, which is irrelevant in this case.

The failure of a ping to 127.0.0.1 (the loopback address) indicates a problem with the workstation’s TCP/IP stack or network interface card (NIC). Since 127.0.0.1 is a local address, the issue is not related to the network, router, or DNS. The first step in diagnosing this issue is to verify the NIC interface status to ensure the network adapter is functioning and properly configured.

Why not Verify the network is not congested? Network congestion affects external connectivity, not the loopback address.

Why not Verify the router is not dropping packets? Router issues are irrelevant since the loopback ping fails locally.

Why not Verify that DNS is resolving correctly? DNS resolution is not involved in pinging 127.0.0.1, which uses a direct IP address.

Recovery Point Objective (RPO) defines the maximum acceptable amount of data loss measured in time. If leadership states “no more than eight hours of data loss,” they are describing how far back the organization is willing to roll data after an outage or disaster—meaning backups, replication, snapshots, or journaling must ensure recoverable data is no older than eight hours. In Network+ terms, this is a core availability and resiliency planning concept: you choose an RPO based on business impact, then implement backup frequency/replication strategy to meet it. By contrast, Recovery Time Objective (RTO) is about how quickly services must be restored (downtime duration), not how much data can be lost. MTTR (Mean Time to Repair/Recover) is an operational reliability metric describing typical time to restore a system, and MTBF (Mean Time Between Failures) indicates expected time between failures—neither directly states acceptable data loss. Therefore, the metric matching “eight hours of data loss” is RPO.

Port 25 is associated with SMTP, which is traditionally used for Simple Mail Transfer Protocol traffic. In basic port-mapping questions for CompTIA Network+, SMTP on port 25 is commonly treated as the non-encrypted mail transport option. If the organization is migrating to encrypted mail protocols, closing port 25 can help deny non-encrypted SMTP access while allowing encrypted mail submission or web-based secure access to continue through other ports.

The CompTIA Network+ N10-009 objectives require candidates to recognize common protocols, port numbers, and their secure alternatives. Port 587 is commonly used for SMTP message submission with TLS support, so it should remain available when encrypted mail submission is required. Port 443 is HTTPS and may be used for secure webmail access. Port 22 is SSH, which is encrypted remote administration, not a mail protocol. Port 23 is Telnet, which is unencrypted, but it is not a mail protocol.

Because the question specifically asks about denying non-encrypted mail protocols, port 25 is the best answer among the listed options.