Explanation:

An organization has four departments, each needing access to different resources that do not overlap, and a technician needs to configure and assign an Access Control List (ACL) to implement this segregation. The best solution is to use VLANs (Virtual Local Area Networks).

A. VLAN:

How it works: VLANs segment a network into separate broadcast domains at the data link layer (Layer 2), allowing each department to be assigned to its own VLAN. An ACL can then be applied to a router or Layer 3 switch to control traffic between VLANs, ensuring each department accesses only its designated resources.

Why it fits: VLANs provide logical separation of departments, and ACLs can be configured to permit or deny traffic based on IP addresses, ports, or protocols, aligning with the requirement for non-overlapping resource access. For example, VLAN 10 for Department A, VLAN 20 for Department B, etc., with ACLs restricting inter-VLAN traffic to specific resources.

Implementation: The technician would create VLANs on the switch, assign ports to each VLAN, configure inter-VLAN routing on a router or Layer 3 switch, and apply ACLs to enforce access policies.

Why Not the Other Options?

B. DHCP (Dynamic Host Configuration Protocol):
DHCP assigns IP addresses to devices automatically but does not provide network segmentation or access control. It could be used within VLANs to assign IP ranges, but it doesn’t support ACL implementation or resource isolation on its own.

C. VPN (Virtual Private Network):
A VPN creates a secure tunnel for remote access or site-to-site connectivity but is not designed for internal department segregation or ACL enforcement within a local network. It’s irrelevant to the scenario of four departments in the same office.

D. STP (Spanning Tree Protocol):
STP prevents network loops in switched environments by managing redundant paths but does not segment networks or support ACLs for resource access control. It’s a Layer 2 protocol for loop prevention, not a solution for this requirement.

Why VLAN?
VLANs enable the technician to logically separate the four departments into distinct network segments, even if they share the same physical infrastructure. ACLs, applied on a router or Layer 3 switch handling inter-VLAN routing, can then enforce granular access policies (e.g., allowing Department A to access Resource X but not Resource Y). This combination meets the need for non-overlapping resource access efficiently.

Implementation Steps:
Configure VLANs on the switch (e.g., VLAN 10, 20, 30, 40 for each department). Assign switch ports to the respective VLANs based on department devices. Set up inter-VLAN routing on a router or Layer 3 switch. Create and apply ACLs to control traffic between VLANs (e.g., access-list 101 permit ip 192.168.10.0 0.0.0.255 192.168.100.0 0.0.0.255). Test connectivity to verify resource isolation.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:

Section 2.3 – "Given a scenario, configure and deploy common network devices." This includes configuring VLANs and ACLs for network segmentation.

IEEE 802.1Q:

Defines VLAN tagging and segmentation.

Cisco Networking Documentation:

Details the use of VLANs with ACLs for access control between departments.

Explanation:

Users at a satellite office are experiencing issues with video conferencing, which is a real-time application sensitive to latency, jitter, and packet loss. The technician should focus first on Quality of Service (QoS) to rectify these issues.

A. Quality of Service:

How it works: QoS is a network configuration that prioritizes certain types of traffic (e.g., voice and video) over others (e.g., file transfers) by assigning bandwidth, reducing latency, and minimizing jitter. For video conferencing, QoS can ensure that UDP traffic (commonly used for real-time applications) is given higher priority.

Why it fits: Video conferencing issues like choppy video, audio delays, or dropped calls are often caused by network congestion or lack of prioritization. Since the problem is specific to a satellite office, QoS can be adjusted locally on the router or switch to prioritize video traffic, addressing the root cause first. This is a proactive step to optimize performance before investigating other factors.

Example: The technician might configure QoS to reserve bandwidth for ports 3478-3481 (used by Zoom) or mark video traffic with DSCP values (e.g., EF for Expedited Forwarding).

Why Not the Other Options?

B. Network signal:
For wireless networks, a weak signal (e.g., low RSSI) can cause connectivity issues, but the question doesn’t specify a wireless setup, and the issue is with video conferencing across the network (likely wired or a mix). Signal strength is secondary unless a site survey reveals poor coverage, which should be checked after QoS if needed.

C. Time to Live (TTL):
TTL is a field in the IP header that limits the lifespan of a packet to prevent routing loops. It’s unrelated to video conferencing performance; adjusting TTL wouldn’t address latency or jitter issues.

D. Load balancing:
Load balancing distributes traffic across multiple links or servers to optimize resource use. While it could help if multiple internet connections exist, it’s a broader network optimization technique and not the first focus for real-time application issues like video conferencing, which require prioritization over load distribution.

Why QoS First?
Video conferencing relies on consistent, low-latency delivery of data, and QoS directly addresses this by managing network resources. In a satellite office, where bandwidth might be limited or shared with other traffic, QoS ensures video packets are prioritized. The technician should start by checking and configuring QoS settings on the local router or switch (e.g., using Cisco’s MQC or similar) before exploring signal or load issues.

Troubleshooting Steps:
Check current QoS policies on the network device (e.g., router or switch). Prioritize video conferencing traffic (e.g., UDP ports 3478-3481 for Zoom, 5060-5061 for SIP). Test video conferencing performance after applying QoS. If issues persist, investigate network signal or load balancing as secondary factors.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 2.4 – "Explain common configuration concepts." This includes configuring QoS for real-time applications like video conferencing.

RFC 4594 (Configuration Guidelines for DiffServ Service Classes):
Recommends QoS for voice and video traffic.

Cisco QoS Design Guides:
Highlight QoS as the primary solution for video conferencing issues.

Explanation:

A VoIP phone is plugged into a port but cannot receive calls, indicating a configuration issue related to how the phone interacts with the network, likely involving VLAN assignment. The most appropriate action to address this issue is to tag the traffic to voice VLAN.

C. Tag the traffic to voice VLAN:

How it works: VoIP phones typically require a dedicated VLAN (voice VLAN) to separate voice traffic from data traffic for quality of service (QoS) and security. Tagging the traffic involves configuring the switch port to use 802.1Q tagging, where the VoIP phone’s traffic is assigned to a specific voice VLAN (e.g., VLAN 10) using a VLAN ID. The phone sends tagged frames, and the switch prioritizes this traffic accordingly.

Why it fits: If the port is not configured to tag traffic to the voice VLAN, the VoIP phone cannot communicate with the call manager or other VoIP infrastructure, preventing call reception. Configuring the port with a command like switchport voice vlan 10 (on Cisco devices) ensures the phone’s traffic is correctly tagged and routed to the voice VLAN, resolving the issue.

Context: The phone likely expects to operate on a voice VLAN, and without this configuration, it may default to the native VLAN or fail to register with the VoIP system.

Why Not the Other Options?

A. Trunk all VLANs on the port:
Configuring the port as a trunk with all VLANs allows multiple VLANs to pass through, which is suitable for connecting switches or routers but not ideal for a VoIP phone. This could lead to security risks or improper traffic handling, as the phone needs a specific voice VLAN, not all VLANs.

B. Configure the native VLAN:
The native VLAN is the untagged VLAN on a trunk port, typically used for data traffic. While configuring it might help data devices, it doesn’t address the VoIP phone’s need for a tagged voice VLAN, which is essential for call functionality.

D. Disable VLANs:
Disabling VLANs on the port would eliminate network segmentation, causing all traffic (including VoIP) to share the same broadcast domain. This would worsen the issue, as VoIP requires a dedicated VLAN for proper operation and QoS.

Why Tag the Traffic to Voice VLAN?
VoIP phones rely on a voice VLAN to ensure low-latency, high-priority traffic delivery, often using protocols like SIP or H.323. The switch port must be configured to tag the phone’s traffic with the voice VLAN ID (e.g., via Cisco’s switchport voice vlan command or similar on other vendors). Without this, the phone cannot register with the call manager or receive calls, as the traffic isn’t properly segregated or prioritized.

Implementation Steps:
Identify the voice VLAN ID used by the network (e.g., VLAN 10). Configure the switch port with a command like switchport mode access and switchport voice vlan 10 (Cisco syntax). Ensure the phone is set to tag its traffic with the correct VLAN ID (check phone settings if configurable). Verify connectivity by checking if the phone registers with the call manager and can receive calls. Adjust QoS settings (e.g., trust CoS/ DSCP) if needed for voice traffic prioritization.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 2.3 – "Given a scenario, configure and deploy common network devices." This includes configuring VLANs for VoIP.

IEEE 802.1Q:
Defines VLAN tagging for network segmentation, including voice VLANs.

Cisco VoIP Deployment Guides:
Recommend tagging traffic to a voice VLAN for VoIP phone functionality.

Explanation:

The question asks for the protocol port used to securely transfer a file, implying a need for encryption and authentication to protect the file during transfer. The best option is port 22.

A. 22:

Purpose:Port 22 is the default port for SSH (Secure Shell), which provides a secure channel over an unsecured network. SSH is commonly used with SFTP (SSH File Transfer Protocol) or SCP (Secure Copy Protocol) to securely transfer files.

Why it fits: SFTP and SCP use port 22 to encrypt file transfers, ensuring confidentiality, integrity, and authentication. This meets the requirement for secure file transfer, as the data is protected against eavesdropping and tampering. For example, a network administrator might use sftp user@remote_host to transfer a file securely.

Security: SSH uses strong encryption (e.g., AES) and supports user authentication (e.g., passwords or keys), making it a standard choice for secure file transfers.

Why Not the Other Options?

B. 69:
Port 69 is the default port for TFTP (Trivial File Transfer Protocol), a lightweight protocol for file transfers. However, TFTP is unencrypted and lacks authentication, making it insecure for transferring sensitive files.

C. 80:
Port 80 is the default port for HTTP (HyperText Transfer Protocol), used for unencrypted web traffic. While HTTPS (port 443) provides secure web transfers, port 80 alone does not, and it’s not designed specifically for file transfers (though files can be downloaded via HTTP).

D. 3389:
Port 3389 is the default port for RDP (Remote Desktop Protocol), used for remote desktop access. While files can be transferred during a remote session, RDP is not a file transfer protocol, and its security depends on additional encryption settings, making it less suitable than SFTP/SCP on port 22.

Why Port 22?
Port 22 is the standard for secure file transfer protocols (SFTP/SCP) built on SSH, offering end-to-end encryption and user authentication. This aligns with the need to securely transfer a file, especially in a network environment where data protection is critical. The administrator should ensure the SSH server is properly configured with strong ciphers and access controls.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 1.5 – "Compare and contrast common network protocols and their functions." This includes understanding secure file transfer protocols like SFTP.

RFC 4251 (SSH Protocol Architecture):
Defines SSH and its use for secure data transfer, including files.

IANA Service Name and Transport Protocol Port Number Registry:
Lists port 22 as the default for SSH.

Explanation:

Users are unable to connect to the terminal server with hostname TS19, which points to IP address 10.0.100.19, via RDP. The technician pings 10.0.100.19 and receives an "unreachable" error, indicating a connectivity issue at the IP level. The most likely cause is the IP address was not reserved.

C. The IP address was not reserved:
How it works: In a DHCP environment, if the terminal server’s IP address (10.0.100.19) is not reserved for its MAC address, another device could have been assigned that IP after the server’s lease expired or was released. This results in an IP conflict or the server losing its expected address, making it unreachable.

Why it fits: The ping failure suggests the IP 10.0.100.19 is either assigned to a different device or not active on the intended server. Since the hostname TS19 resolves to this IP (via DNS), a change in IP assignment due to lack of reservation is a common cause. The technician can verify this by checking the DHCP server’s lease table or ARP cache. Example: If the server rebooted and requested a new IP, DHCP might have reassigned 10.0.100.19 to another device, leaving the server unreachable at that address.

Why Not the Other Options?

A. The users are on the wrong subnet:
If users were on the wrong subnet (e.g., 10.0.200.0/24 instead of 10.0.100.0/24), they might not reach 10.0.100.19 due to routing issues, but the ping from the technician (presumably on the correct subnet) would still succeed if the server were online. The "unreachable" error indicates the IP itself is not responding, not a subnet mismatch.

B. The DHCP server renewed the lease:
A lease renewal typically maintains the same IP if reserved or available. This option implies the server retained 10.0.100.19, which contradicts the ping failure unless the renewal failed or assigned a different IP. Lack of reservation (option C) is a more direct cause of IP reassignment.

D. The hostname was changed:
If the hostname TS19 were changed, DNS resolution might fail, but the technician pinged the IP (10.0.100.19) directly and got an "unreachable" error. This suggests the IP is the issue, not the hostname, as the IP should still respond if the server is online.

Why IP Address Not Reserved?
In a DHCP network, without a reservation, the terminal server’s IP can be reassigned after its lease expires, especially in a dynamic environment. The "unreachable" ping result indicates 10.0.100.19 is either inactive or claimed by another device, likely due to the absence of a DHCP reservation. The technician should check the DHCP server and reserve 10.0.100.19 for the server’s MAC address. Troubleshooting Steps: Check the DHCP server’s lease table to see if 10.0.100.19 is assigned to another device. Verify the terminal server’s current IP address (e.g., via console or ARP). Reserve 10.0.100.19 for the server’s MAC address in DHCP. Update DNS if the server’s IP changed. Test connectivity with ping and RDP after reconfiguration.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 3.2 – "Given a scenario, troubleshoot common network connectivity issues." This includes diagnosing DHCP-related IP conflicts

RFC 2131 (Dynamic Host Configuration Protocol):
Describes DHCP lease management and the importance of reservations.

Microsoft DHCP Documentation:
Highlights IP reservations to prevent address conflicts.

Explanation:

A network administrator recently updated configurations on a Layer 3 switch, and users report being unable to reach a specific file server afterward. Since the issue is specific to accessing one server and occurred post-configuration change, the most likely cause is incorrect ACLs (Access Control Lists).

A. Incorrect ACLs:

How it works: A Layer 3 switch can use ACLs to filter traffic based on IP addresses, ports, or protocols. If the administrator added or modified an ACL during the update, it might inadvertently block traffic to the file server’s IP address or the ports it uses (e.g., SMB on 445 or NFS on 2049).

Why it fits: The issue is isolated to a specific file server, suggesting a targeted configuration change (e.g., an ACL denying access to 192.168.10.20) rather than a network-wide problem. The timing of the update points to a misconfiguration in the ACL, which is a common mistake when applying new rules on a Layer 3 switch.

Example: An ACL like access-list 101 deny ip any 192.168.10.20 could block all traffic to the server, even if intended to restrict specific users.

Why Not the Other Options?

B. Switching loop:
A switching loop, caused by misconfigured STP (Spanning Tree Protocol) or redundant links, would typically affect the entire network with broadcast storms or connectivity drops, not just access to a specific server. The localized nature of the issue makes this unlikely.

C. Duplicate IP addresses:
Duplicate IP addresses would cause intermittent connectivity issues (e.g., ARP conflicts) across the network or for devices sharing the IP, but the problem is specific to the file server. This would also likely be detected by other devices, not just post-update.

D. Wrong default route:
A wrong default route on the Layer 3 switch would prevent access to external networks or all destinations outside the local subnet, not just a specific file server. Since users can likely reach other resources, this is not the cause.

Why Incorrect ACLs?
Layer 3 switches handle routing and can apply ACLs to control inter-VLAN or routed traffic. A recent configuration update might have introduced an ACL that denies access to the file server’s subnet, port, or specific traffic type. The administrator should review the switch’s ACL configuration (e.g., show access-lists on Cisco devices) to identify and correct the rule.

Troubleshooting Steps:
Check the Layer 3 switch configuration for recently added or modified ACLs (e.g., show running-config | include access-list). Verify the ACL applied to the VLAN or interface associated with the file server’s subnet. Test connectivity with a ping or traceroute to the file server’s IP. Temporarily remove or adjust the ACL to test if access is restored. Document and apply the corrected ACL.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 3.2 – "Given a scenario, troubleshoot common network connectivity issues." This includes diagnosing ACL-related problems

. RFC 3704 (Access Control Lists):
Describes ACL functionality in network devices.

Cisco Layer 3 Switching Guides:
Detail how ACLs can block traffic if misconfigured.

Explanation:

The small business is deploying new phones with full HD videoconferencing features, and the Chief Information Officer (CIO) is concerned that the network might not handle the traffic if it reaches a certain threshold. The network engineer needs to configure a solution to ease these concerns, focusing on managing bandwidth and traffic. The best option is a VLAN with 100Mbps speed limits.

A. A VLAN with 100Mbps speed limits:
How it works: Creating a dedicated VLAN for VoIP and videoconferencing traffic allows the engineer to apply bandwidth limits (e.g., 100Mbps per VLAN or port) using Quality of Service (QoS) or rate-limiting policies. This caps the traffic to prevent it from overwhelming the network, ensuring other services (e.g., data) are not impacted.

Why it fits: HD videoconferencing requires significant bandwidth (e.g., 1-4 Mbps per call), and with multiple phones, the cumulative traffic could exceed network capacity. A 100Mbps limit per VLAN provides a controlled threshold, addressing the CIO’s concern about traffic overload. The engineer can monitor usage and adjust limits as needed.

Example: Configure a voice VLAN (e.g., VLAN 10) with a rate limit of 100Mbps using a command like srr-queue bandwidth limit 100 on Cisco switches.

Why Not the Other Options?

B. An IP helper to direct VoIP traffic:
An IP helper (DHCP relay agent) forwards DHCP requests to a server on another subnet, which is useful for IP address assignment but does not manage traffic thresholds or ease congestion concerns. It’s unrelated to bandwidth control.

C. A smaller subnet mask:
A smaller subnet mask (e.g., /24 to /25) reduces the number of IP addresses in a subnet but does not address traffic volume or videoconferencing bandwidth needs. It’s a network design choice, not a traffic management solution.

D. Full duplex on all user ports:
Full duplex allows simultaneous two-way communication on a port, improving efficiency by eliminating collisions. While beneficial for performance, it doesn’t limit or manage traffic thresholds, so it won’t directly address the CIO’s concern about network overload.

Why VLAN with 100Mbps Speed Limits?
HD videoconferencing generates high-bandwidth traffic, and without control, it could saturate the network, causing delays or dropped calls. A dedicated VLAN with a 100Mbps speed limit ensures that VoIP and video traffic is isolated and capped, preventing it from exceeding the network’s capacity. The engineer can pair this with QoS to prioritize voice/video traffic within the limit, providing a balanced solution to the CIO’s concerns.

Implementation Steps:
Create a new VLAN (e.g., VLAN 10) for VoIP/videoconferencing. Assign phone ports to the VLAN and configure a 100Mbps rate limit. Implement QoS to prioritize voice/video traffic (e.g., DSCP EF for Expedited Forwarding). Test videoconferencing with multiple phones to ensure performance within the limit. Monitor traffic and adjust the limit if needed.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 2.4 – "Explain common configuration concepts." This includes configuring VLANs and QoS for traffic management

. RFC 4594 (Configuration Guidelines for DiffServ Service Classes):
Recommends bandwidth limits and QoS for real-time traffic like videoconferencing

. Cisco VoIP Design Guides:
Suggest VLANs with rate limits to manage VoIP traffic thresholds.

Explanation:

A network administrator installs new cabling to connect new computers and access points, but after deployment, some devices are not connecting properly. Moving the devices to a different port does not resolve the issue, indicating the problem is likely related to the physical cabling rather than the port itself. The next step the administrator should verify is cable termination.

D. Cable termination:

How it works: Cable termination refers to the proper connection of twisted-pair cables (e.g., Cat 5e, Cat 6) to RJ45 connectors or patch panels, following the T568A or T568B wiring standard. Improper termination (e.g., incorrect pin assignments, loose connections, or damaged wires) can prevent a device from establishing a link, causing connectivity issues.

Why it fits: Since moving devices to different ports didn’t help, the issue is likely with the cabling rather than the switch ports. New cabling installations are prone to termination errors, especially if done manually or without proper testing. Verifying termination ensures the cables are correctly wired and connected, which is critical for Ethernet communication.

Example: A miswired pair (e.g., TX and RX reversed) or a loose connector could explain the connectivity failure.

Why Not the Other Options?

A. Power budget:
Power budget is relevant for Power over Ethernet (PoE) scenarios, where the switch supplies power to devices like access points. However, connectivity issues persisting across ports suggest a data link problem rather than a power issue, unless all ports lack PoE capability (which would be inconsistent with the scenario).

B. Device requirements:
Verifying device requirements (e.g., speed, duplex settings) is important but would typically be checked before deployment. Since the issue arose post-installation and persists across ports, it’s more likely a cabling issue than a mismatch in device settings.

C. Port status:
The administrator already moved devices to different ports, implying the port status (e.g., up/down) was checked or assumed functional. If the new ports also fail, the problem lies beyond the port itself, pointing to the cabling.

Why Cable Termination?
New cabling installations often involve manual termination, which can introduce errors like incorrect wiring, damaged conductors, or poor crimping. These issues can prevent the establishment of a link layer connection (e.g., no link lights), leading to the observed connectivity problems. The administrator should use a cable tester to verify continuity, pinouts, and pair integrity.

Troubleshooting Steps:
Inspect the cable terminations at both ends (e.g., RJ45 connectors) for proper wiring (T568B standard). Use a cable tester to check for opens, shorts, or crossed pairs. Re-terminate or replace faulty cables if issues are found. Test connectivity after correction. Document the findings.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 3.2 – "Given a scenario, troubleshoot common network connectivity issues." This includes diagnosing cabling problems.

TIA/EIA-568-B:
Defines cabling standards, including proper termination for Ethernet.

Fluke Networks Cable Testing Guides:
Recommend verifying termination to resolve connectivity issues.

Explanation:

In an environment with one router, the network engineer needs to enable communication between VLANs without purchasing additional hardware. The best solution is subinterfaces.

A. Subinterfaces:

How it works: Subinterfaces are logical interfaces created on a router’s physical interface, each assigned to a different VLAN using 802.1Q tagging. The router performs inter-VLAN routing by routing traffic between these subinterfaces, allowing communication between VLANs.

Why it fits: Since the environment has only one router and no additional hardware can be purchased, subinterfaces leverage the existing router to handle inter-VLAN routing. For example, on a Cisco router, the engineer could configure interface fa0/0.10 for VLAN 10 and interface fa0/0.20 for VLAN 20, with each subinterface having its own IP address and VLAN tag.

Context: This is a cost-effective solution using the router’s existing capabilities, commonly known as "router-on-a-stick" configuration when connected to a switch trunk port.

Why Not the Other Options?

B. VXLAN (Virtual Extensible LAN)
VXLAN is a tunneling protocol that extends VLANs across Layer 3 networks using overlay networks, typically requiring VXLAN-capable hardware or software (e.g., on switches or virtualized environments). It involves additional configuration and likely hardware support beyond a single router, making it unsuitable without upgrades.

C. Layer 3 switch:
A Layer 3 switch performs inter-VLAN routing natively, which is ideal but requires purchasing new hardware, as the scenario specifies no additional hardware can be acquired. The existing router must be used.

D. VIR:
This appears to be a typo or misinterpretation (possibly intended as "VIR" for Virtual Router or similar). No standard networking protocol or feature matches "VIR" in this context. Assuming it’s a mistake, it’s not a viable option.

Why Subinterfaces?
Subinterfaces allow a single router to route between VLANs by creating virtual interfaces for each VLAN, eliminating the need for additional devices like a Layer 3 switch. The router connects to a switch via a trunk link, and the subinterfaces handle the routing. This is a practical solution given the constraint of using existing hardware.

Implementation Steps:
Configure the router’s physical interface as a trunk (e.g., interface fa0/0, no shutdown, encapsulation dot1Q). Create subinterfaces for each VLAN (e.g., interface fa0/0.10, encapsulation dot1Q 10, ip address 192.168.10.1 255.255.255.0). Ensure the switch port connected to the router is configured as a trunk allowing all relevant VLANs. Verify inter-VLAN routing with a ping between VLANs. Adjust ACLs if access control is needed.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 2.3 – "Given a scenario, configure and deploy common network devices." This includes configuring subinterfaces for inter-VLAN routing.

IEEE 802.1Q:
Defines VLAN tagging used with subinterfaces.

Cisco Router-on-a-Stick Configuration Guides:
Detail subinterface setup for inter-VLAN routing with a single router.

Explanation:

A university is implementing a new campus wireless network to support a large number of devices and high bandwidth demands from students. The network administrator needs a wireless technology that can handle dense environments and deliver robust performance. The best option is Wi-Fi 6E.

B. Wi-Fi 6E:

How it works: Wi-Fi 6E is an extension of Wi-Fi 6 (802.11ax) that operates in the 6GHz band in addition to the 2.4GHz and 5GHz bands. It supports higher throughput (up to 9.6 Gbps), increased capacity with more non-overlapping channels (e.g., 120MHz or 160MHz wide), and improved efficiency with technologies like OFDMA and MU-MIMO.

Why it fits: A university campus with many students and devices (laptops, phones, tablets) requires high device density support and bandwidth for activities like streaming, online learning, and large file transfers. Wi-Fi 6E’s use of the 6GHz band reduces congestion from the crowded 2.4GHz and 5GHz bands, offering better performance and lower latency. It’s ideal for a large-scale deployment with high demand.

Example: With hundreds of students in a lecture hall, Wi-Fi 6E can handle simultaneous connections efficiently, ensuring stable connectivity.

Why Not the Other Options?

A. Bluetooth:
Bluetooth is a short-range wireless technology (up to 10-100 meters) designed for personal area networks (e.g., connecting headphones or keyboards). It lacks the range, capacity, and bandwidth to support a campus-wide network with many devices, making it unsuitable.

C. 5G:
5G is a cellular technology offering high speeds and low latency, suitable for mobile devices over wide areas. However, it requires carrier infrastructure (e.g., base stations) and user subscriptions, which may not be feasible for an on-campus network controlled by the university. It’s complementary but not a primary campus wireless solution.

D. LTE:
LTE (Long-Term Evolution) is a 4G cellular technology with moderate speeds (up to 300 Mbps) and wide coverage. Like 5G, it relies on carrier networks and isn’t designed for campus-wide Wi-Fi deployment, where the university needs to manage its own infrastructure.

Why Wi-Fi 6E?
Wi-Fi 6E is tailored for dense, high-demand environments like universities, where thousands of devices need simultaneous access. The 6GHz band provides additional spectrum (up to 1,200MHz), reducing interference and supporting more devices with higher throughput. As of August 20, 2025, Wi-Fi 6E is a leading standard for enterprise and educational networks, aligning with the administrator’s need for scalability and performance.

Implementation Considerations:
Deploy Wi-Fi 6E-compatible access points across campus. Use a centralized wireless controller for management and channel optimization. Ensure client devices support 6GHz (e.g., recent laptops, phones). Configure QoS to prioritize bandwidth-intensive applications.

Reference:

CompTIA Network+ (N10-009) Exam Objectives:
Section 2.2 – "Given a scenario, configure and deploy common network devices." This includes selecting appropriate wireless technologies.

IEEE 802.11ax (Wi-Fi 6/6E):
Defines the standard for high-efficiency wireless, including 6GHz support.

Cisco Wireless Deployment Guides:
Recommend Wi-Fi 6E for high-density environments like campuses.