Bottlenecking occurs when a device in the network (such as an IPS) cannot process traffic efficiently, resulting in a dramatic drop in throughput. The significant difference between the firewall's speed (48.8 Mbps down) and the end-user devices' speeds (4.8 - 5.2 Mbps down) indicates a bottleneck caused by the IPS.
*Why not the other options?
*Packet loss (A) - Would typically cause connection timeouts, not just slow speeds.
*Channel overlap (C) - Affects only wireless networks, but the wired desktop is also experiencing slow speeds.
*Network congestion (D) - Would show fluctuations in both upload and download speeds, but upload speeds remain unaffected.

Band Steering: This technology enables wireless devices to connect to the most optimal frequency band (2.4 GHz or 5 GHz) by encouraging capable devices to switch to the less congested 5 GHz band. This improves overall network performance and prevents overcrowding on the 2.4 GHz band.
Wireless LAN controller (B): This manages multiple access points in a network but does not handle frequency optimization.
Directional antenna (C): This focuses the signal in a specific direction but does not affect frequency selection.
Autonomous access point (D): This operates independently but lacks advanced features like band steering.

* Understanding Spanning Tree Protocol (STP):
* STP is used to prevent network loops in Ethernet networks by creating a spanning tree that selectively blocks some redundant paths.
* Default Priority Value:
* Bridge Priority: STP uses bridge priority to determine which switch becomes the root bridge. The default bridge priority value for most switches is 32768.
* Priority Range: The bridge priority can be set in increments of 4096, ranging from 0 to 61440.
* Configuration and Verification:
* When deploying a new switch, the network administrator can verify the bridge priority using commands such as show spanning-tree to ensure it is set to the default value of 32768.
* Comparison with Other Values:
* 4096 and 8192: Lower than the default priority, indicating these would be manually configured for higher preference.
* 36684: A non-standard value, likely a result of specific configuration changes.
References:
* CompTIA Network+ study materials on Spanning Tree Protocol and network configuration.

*nslookup allows querying DNS records to verify if the new server is correctly resolving domain names.
*ping (A) tests basic connectivity, not DNS configuration.
*tracert (B) shows network path latency but doesn't test DNS.
*tcpdump (C) captures packets but isn't ideal for DNS verification.
#Reference: CompTIA Network+ N10-009 Official Documentation - DNS Testing Tools.