Ditch the Fluff: CompTIA Network+ (N10-009) Practice That Actually Works

A hybrid cloud deployment model is the best choice for the CTO ' s requirements. It allows the organization to run key services from the on-site data center while leveraging the cloud for enterprise services. This approach provides flexibility, scalability, and cost savings, while also minimizing disruptions to users by keeping critical services local. The hybrid model integrates both private and public cloud environments, offering the benefits of both.References: CompTIA Network+ study materials and cloud computing principles.

For a secure 802.1X design that includes BYOD access to a trusted wireless network, the engineer should implement NAC (Network Access Control). In the Network+ (N10-009) objectives, 802.1X provides authentication (commonly via EAP to a RADIUS server), but NAC expands this by enforcing policy-based access decisions—such as device posture checks, user/device identity validation, and dynamic assignment to the appropriate VLAN/role. With BYOD, the organization often needs to confirm whether devices meet requirements (OS version, encryption, security software) and then grant the correct level of access (full, limited, or quarantine/remediation). NAC is the architecture that ties these controls together in a scalable way for wireless networks.

An ACL can restrict traffic after a device connects, but it doesn’t perform authentication/posture assessment. MAC filtering is weak because MAC addresses can be spoofed and it does not provide strong identity assurance. Port security is mainly a wired switch control (limiting MAC addresses per port) and is not the right control set for secure BYOD wireless access. NAC best matches the requirement of secure, policy-driven 802.1X BYOD access.

===========

A /23 subnet provides 512 total addresses, of which 510 are usable (subtracting 2 for network and broadcast addresses). This would satisfy the need for 255 additional addresses.

Shoulder surfing is a social engineering attack where attackers observe someone’s private information by looking over their shoulder or using tools like cameras to capture input.

From Andrew Ramdayal’s guide:

“Shoulder surfing is the act of watching someone enter confidential information, such as PINs or passwords, often using direct line-of-sight or surveillance equipment.”

An evil twin is a rogue Wi-Fi access point that mimics a legitimate network. Attackers use it to intercept and manipulate traffic, making it an on-path (formerly MITM) attack opportunity.

Breakdown of Options:

A. Phishing – Tries to steal credentials through fake emails/websites but does not intercept network traffic.

B. Dumpster diving – Involves physical security breaches, not network interception.

C. Evil twin – ✅ Correct answer. A rogue Wi-Fi AP impersonates a real network, allowing traffic interception.

D. Tailgating – Involves physical access security, not network interception.

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.

Port 443 is used by HTTPS (Hypertext Transfer Protocol Secure), a secure version of HTTP that uses SSL/TLS to encrypt the communication between a client and server. This ensures confidentiality and integrity of data in transit. The document states:

“Port 443 is the default port for HTTPS, which secures HTTP traffic using SSL/TLS, providing encryption and secure identification of web servers.”

The laptop is most likely using the 2.4GHz frequency band. According to the CompTIA Network+ N10-009 objectives, the 2.4GHz band is particularly susceptible to electromagnetic interference (EMI) from common household and office devices, including microwave ovens, cordless phones, Bluetooth devices, and baby monitors. Microwave ovens operate at approximately 2.45GHz, which overlaps directly with the 2.4GHz Wi-Fi spectrum. When the microwave is powered on, it emits interference that can significantly degrade or completely disrupt nearby wireless communications operating in this band.

The 5GHz and 6GHz bands operate at much higher frequencies and do not overlap with microwave emissions, making them far less prone to this type of interference. While higher-frequency bands have shorter range and lower wall penetration, they provide cleaner channels and improved performance in dense environments. The 900MHz band is not used by standard Wi-Fi networks defined in the Network+ objectives and is more commonly associated with legacy cordless phones and certain IoT or proprietary wireless technologies.

Network+ troubleshooting guidance emphasizes identifying environmental interference sources when diagnosing intermittent wireless connectivity. A common mitigation strategy is to migrate affected devices to the 5GHz or 6GHz bands or reposition access points away from interference sources like break room appliances.

A full-tunnel VPN forces a remote user’s traffic—including access to public internet resources—to traverse the corporate VPN tunnel and egress from the organization’s network. This is commonly required to ensure consistent enforcement of corporate security controls such as web filtering, IDS/IPS inspection, DLP policies, logging, and access control. In Network+ terms, full-tunnel VPNing routes the user’s default gateway through the VPN, meaning both internal traffic (to corporate subnets) and external traffic (to internet destinations) is sent through the encrypted tunnel.

By contrast, a split-tunnel VPN (not listed) would send only corporate-bound traffic through the VPN while allowing internet traffic to go directly out the user’s local ISP—reducing corporate bandwidth usage but also reducing centralized inspection and control. Clientless VPN usually refers to browser-based access to specific internal applications without a full network tunnel for all traffic. Site-to-site VPN connects entire networks to each other (e.g., branch office to HQ) rather than an individual remote user. SSE (Security Service Edge) is a cloud security framework/service model, not the classic VPN configuration described in the question. Hence, full-tunnel is the correct answer.

SNMPv3 is the version of the Simple Network Management Protocol that introduces security enhancements, including message integrity, authentication, and encryption. Unlike previous versions (v1 and v2c), SNMPv3 supports encrypted communication, ensuring that data is not transmitted in plaintext. This provides confidentiality and protects against eavesdropping and unauthorized access.References: CompTIA Network+ study materials.

The best answer is SNMP (Simple Network Management Protocol). SNMP enables monitoring of network devices (routers, switches, firewalls, servers) and provides performance data such as CPU usage, bandwidth utilization, and interface status. In this scenario, if SNMP monitoring had been in place, administrators would have received alerts that the router was overutilized before customers noticed outages.

A. Packet capture (e.g., Wireshark) is useful for deep troubleshooting but is reactive, not proactive, and not scalable for continuous monitoring.

C. Syslog collects log messages but generally does not provide proactive resource utilization metrics. It is complementary but not the best fit for this problem.

D. SIEM aggregates logs and security events for analysis, but the primary requirement here is performance and availability monitoring.

By implementing SNMP monitoring (and potentially integrating it with a network monitoring tool such as Nagios, PRTG, or SolarWinds), the organization can track utilization trends, set thresholds, and automatically generate alerts, thereby preventing downtime from going unnoticed.

References (CompTIA Network+ N10-009):

Domain: Network Operations — SNMP monitoring, proactive network performance management.

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

In a spine–leaf architecture, endpoints (including servers, firewalls, and WAN/edge routers) connect to leaf switches. Leaf switches then uplink to spine switches; spine switches do not have endpoints connected directly to them. Therefore, a WAN router (an external/edge device) should connect to the leaf layer—often specifically to a “border leaf” that handles external connectivity.

Why not B. Core or D. Spine? In spine–leaf, “core” isn’t a formal layer, and spines are designed only to interconnect leafs, not to terminate endpoints.

Why not A. Access? “Access” is a term from the traditional three-tier model (access–distribution–core). In modern spine–leaf language, the analogous layer for endpoint attachment is the leaf.

References (CompTIA Network+ N10-009):

Domain: Network Infrastructure — Data center and campus architectures (spine–leaf vs. three-tier), roles of leaf/spine, WAN/edge connectivity points.

===========

The correct answer is 802.1X, which is an identity-based Network Access Control (NAC) framework emphasized in the CompTIA Network+ N10-009 objectives under network security and access control. 802.1X uses a policy-driven authentication process to determine whether a user or device is allowed network access based on verified credentials, such as usernames, passwords, or digital certificates.

802.1X operates using three main components: the supplicant (the client requesting access), the authenticator (the network device such as a switch or wireless access point), and the authentication server (typically a RADIUS server). Once the user’s identity is authenticated, predefined policies determine the level of access granted—full access, limited access, or denial. This makes 802.1X a cornerstone of zero trust and enterprise-grade NAC implementations.

A standard ACL controls traffic based on IP addresses and ports, not user identity. MAC filtering allows or denies access based on device MAC addresses, which can be easily spoofed and does not verify user identity. SSO (Single Sign-On) simplifies authentication across multiple systems but does not control network-layer access.

Network+ highlights 802.1X as a secure, scalable solution for enforcing identity-based network access policies in both wired and wireless environments.