CompTIA Updated N10-009 Exam Questions and Answers by solomon

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.

===========

To determine where slowness is occurring—especially if an upstream router is suspected—the best tools are ping and tracert/traceroute. Network+ (N10-009) troubleshooting objectives emphasize using these to test connectivity, latency, and the path packets take through the network. Ping measures reachability and round-trip time; rising latency or packet loss can indicate congestion or a failing link/device. Tracert identifies each hop along the route and reports per-hop response times, helping pinpoint whether delays begin at a specific hop (for example, the default gateway, the upstream router, or a provider edge). This allows the engineer to localize the problem area and decide whether the issue is internal, at the upstream router, or beyond.

nslookup and dig are DNS tools; they diagnose name resolution, not general network slowness location. Nmap focuses on scanning ports/hosts, and a “speed tester” measures throughput but does not locate the failing hop. tcpdump and protocol analyzer can reveal retransmissions, windowing, or application behavior, but they are not the fastest first-choice tools for locating an upstream routing/performance bottleneck across hops. Hence, tracert and ping are the correct pair.

The best answer is C. Insufficient bandwidth. The pattern in the question matters more than anything else. The company moved to a hosted VoIP and video solution, which means voice and video traffic now depend heavily on the site’s internet connection. The problems begin mid-morning and continue into the afternoon, which strongly suggests the link becomes congested during the busiest usage period of the day.

That also explains why users see dropped calls, broken video, and slow internet access all at the same time. Real-time applications like VoIP and video are very sensitive to delay, jitter, and packet loss. When bandwidth is limited or saturated, those services are usually the first to show noticeable symptoms.

The fact that remote users do not report the same issue is another major clue. If the application platform itself were failing, remote users would likely be affected too. Since the issue seems limited to the main site, the bottleneck is most likely the local office’s WAN or internet connection rather than the hosted service.

The other options are weaker. Roaming misconfiguration is more of a wireless mobility issue, signal degradation is too vague for this traffic pattern, and a miswired cable would not usually appear only during peak business hours. This points to insufficient bandwidth.