300-110 Designing Cisco Enterprise Wireless Networks Questions and Answers

The requirement for users to retain their VLAN assignment and IP address when roaming between buildings managed by different WLCs is a Layer 3 roaming scenario. In Cisco ' s wireless architecture, IP address preservation across controller boundaries is achieved through inter-controller mobility — specifically the foreign-anchor mobility tunnel mechanism. When a client roams from Building A (WLC-A) to Building B (WLC-B), WLC-B becomes the foreign controller and WLC-A becomes the anchor controller. WLC-B tunnels the client ' s traffic back to WLC-A, allowing the client to retain its original IP address even while physically associated to an AP managed by WLC-B. This requires creating a mobility group between WLC-A and WLC-B with both controllers configured with the same mobility group name — the group name is the trust identifier that permits the mobility tunnel and anchor-foreign relationship to form. An SSO cluster (Option B) creates redundancy between two WLCs operating as one logical entity, not inter-building roaming between independent controllers. 802.11r (Option C) accelerates re-association but does not preserve IP addresses across different Layer 3 subnets. AP groups (Option D) control SSID and VLAN assignments but do not enable inter-controller IP preservation. Reference: WLSD Study Guide — Inter-Controller Mobility, Layer 3 Roaming, IP Address Preservation.

The hidden node problem is a classic RF design flaw that emerges when APs transmit at excessive power levels relative to the attenuation characteristics of the environment. In a brick-walled building, AP signals penetrate walls with significant attenuation. When an AP transmits at maximum power, its signal propagates far beyond the intended cell boundary and reaches client devices that may be physically near other APs but unable to detect the original transmitting AP due to wall attenuation between them. These clients can hear the distant AP ' s signal but cannot hear each other — making them hidden from one another. This leads to simultaneous transmissions, frame collisions at the AP receiver, and dramatic throughput degradation. The 802.11 CSMA/CA mechanism depends on all stations being able to sense the medium before transmitting; hidden nodes defeat this mechanism entirely. The WLSD curriculum consistently identifies excessive AP transmit power in high-attenuation environments as a primary cause of hidden node conditions. The solution is to reduce AP transmit power so that cell sizes remain appropriate for the physical environment. Reference: WLSD Study Guide — RF Design Fundamentals, Hidden Node Problem, Transmit Power and Cell Size Optimization.

In a high-availability configuration with multiple WLCs in a mobility group, when APs that only have a primary controller configured become orphaned (their primary WLC fails), they will by default join the controller with the lowest percentage of associated APs per license capacity. This load-based selection mechanism ensures a balanced distribution of APs across the remaining controllers in the mobility group. The WLC with the lowest percentage of AP capacity utilized is chosen because it has the most headroom to accept additional APs without becoming overloaded. This prevents a single backup controller from becoming overwhelmed while others remain underutilized. The selection is not based on absolute number of APs (Option D), available free licenses in absolute terms (Option A), or CPU utilization (Option C) — it specifically uses the percentage of license capacity occupied, which normalizes across controllers with different total AP capacities. Reference: WLSD Study Guide — N+1 Redundancy Default Behavior, AP Orphan Failover Logic, WLC Load-Based AP Assignment.

In Ekahau Site Survey ' s multi-floor predictive modeling workflow, alignment points are the critical mechanism that allows the software to understand the precise vertical spatial relationship between floors in a multi-story building. Once floor plans are imported with their scale correctly defined, alignment points must be placed on each floor at the same real-world physical location — such as a stairwell corner, elevator shaft, or structural column — so that Ekahau can accurately calculate vertical signal propagation and inter-floor RF bleed. Without alignment points, the software has no spatial reference to determine which area on Floor 2 is directly above a given point on Floor 1, making floor-to-floor signal bleed calculations geometrically impossible. Drawing coverage areas (Option A) is a post-AP-placement activity. Starting the auto planner (Option B) would attempt to place APs without the required spatial reference. Choosing AP models (Option D) is a subsequent step. Alignment points are a fundamental requirement for any predictive survey involving multi-floor buildings. Reference: WLSD Study Guide — Ekahau Predictive Survey Methodology, Multi-Floor Building Configuration, Signal Propagation Modeling.

In Ekahau Site Survey, when planning a warehouse deployment using patch (directional) antennas, the antenna downtilt setting is the critical adjustment made when placing simulated APs on the floor plan map. Patch antennas have a defined radiation pattern with a main lobe that must be aimed precisely at the intended coverage zone. In a warehouse environment, APs with patch antennas are typically wall-mounted and aimed down aisles. The downtilt angle determines the vertical component of the antenna ' s aim — adjusting the downtilt in Ekahau tilts the simulated antenna ' s main radiation lobe downward toward the warehouse floor and the working zone of RF scanner devices, rather than projecting RF energy horizontally at an ineffective angle. Ekahau allows engineers to specify the horizontal and vertical orientation of the antenna in three dimensions, and the downtilt value directly controls how the software models the antenna ' s coverage pattern in the vertical plane. AP channel (Option A) is set during channel planning, not during AP placement. Wi-Fi technology (Option B) determines the modulation and protocol standard but is set as an AP property. AP transmission power (Option D) controls cell radius but is set separately from antenna orientation. Reference: WLSD Study Guide — Ekahau Predictive Survey, Directional Antenna Configuration, Warehouse RF Design and Antenna Orientation.

The command ' debug mobility handoff enable ' is used to validate the mobility control packets between Wireless LAN Controllers (WLCs). This command enables debugging of the handoff process, which is critical for ensuring seamless client roaming between controllers. When WLCs are separated by firewalls, it is essential to confirm that mobility control packets can traverse these firewalls without being dropped or rejected. The ' debug mobility handoff enable ' command allows network administrators to monitor the handoff process in real time and identify whether mobility PDUs are being exchanged successfully. If mobility control packets are being blocked by the firewall, this debug output will show failures in the handoff sequence. This command directly validates bidirectional mobility traffic flow, making it the correct troubleshooting tool for the scenario described. Options A and D are not valid Cisco WLC commands. Option C enables configuration-level mobility debugging but does not specifically validate handoff packet flow. Reference: WLSD Study Guide — Mobility Troubleshooting, Debug Commands, Inter-Controller Roaming Validation.

In an anchored WLAN deployment, client traffic is encapsulated within CAPWAP mobility tunnels between the foreign WLC (where the AP joins) and the anchor WLC (in the DMZ or designated network segment). This tunneling adds encapsulation overhead — CAPWAP/mobility tunnel headers consume a portion of the available MTU on the transport path. When video streaming clients generate large TCP segments, these segments may exceed the effective MTU of the mobility tunnel path, causing IP fragmentation at the WLC or along the path to the anchor. Fragmentation significantly degrades throughput and increases CPU overhead for high-volume video traffic. The correct solution is TCP MSS Clamping — reducing the Maximum Segment Size value advertised in TCP SYN packets so that TCP endpoints negotiate a segment size remaining below the fragmentation threshold. The Cisco 9800 WLC supports TCP MSS adjustment, which intercepts TCP handshake packets and rewrites the MSS option to a value accounting for CAPWAP tunnel overhead. Setting matching MTUs (Option A) does not prevent fragmentation if the effective tunnel MTU is lower than the client segment size. Increasing the MTU (Option B) is often constrained by physical infrastructure. Setting the DF bit (Option D) would cause packets to be dropped rather than fragmented. Reference: WLSD Study Guide — Anchored WLAN Design, CAPWAP Mobility Tunnel MTU, TCP MSS Clamping.

During a client roaming event in a Cisco SD-Access fabric deployment, the Wireless LAN Controller (WLC) is responsible for communicating the new Layer 2 Endpoint ID (EID) mapping of a wireless supplicant to the fabric domain. In the SD-Access architecture, the WLC acts as a mobility orchestrator and serves as the interface between the wireless domain and the wired fabric. When a client roams from one AP to another, the WLC detects the roaming event and updates the fabric control plane with the new EID-to-RLOC (Routing Locator) mapping by notifying the fabric control plane node (CP). This ensures that the fabric knows the client ' s new location and can route traffic correctly without interruption. The Border Node (BN) handles traffic between the fabric and external networks. CP1 and CP2 are control plane nodes that maintain the mapping database but receive EID update notifications from the WLC — they do not initiate the EID mapping communication themselves. Reference: WLSD Study Guide — SD-Access Wireless Architecture, Client Roaming in Fabric Deployments, EID Mapping and Control Plane Notifications.

When using Metageek Chanalyzer in conjunction with a Cisco CleanAir-capable AP for Layer 1 spectrum analysis, the AP must be configured in SE-Connect mode (Spectrum Expert Connect). SE-Connect mode enables the AP ' s CleanAir radio to operate as a dedicated spectrum analyzer, feeding raw spectrum data to the connected Chanalyzer software for visualization and analysis. In this mode, the AP does not serve any Wi-Fi clients and instead focuses all radio resources on spectrum scanning. Metageek Chanalyzer uses the SE-Connect mode specifically to receive the CleanAir ASIC ' s spectrum analysis data. Local mode (Option A) serves clients normally, only providing periodic CleanAir reports. Sniffer mode (Option B) captures 802.11 frames for protocol analysis and does not provide raw spectrum data to Chanalyzer. Monitor mode (Option C) performs WIDS scanning and RRM measurements but does not support the direct Chanalyzer integration. SE-Connect is the specific mode that enables external spectrum analysis software to use the CleanAir ASIC ' s spectrum data in real time. Reference: WLSD Study Guide — Cisco CleanAir Technology, AP Operating Modes, SE-Connect Mode for Spectrum Analysis.

Layer 1 interference analysis is foundational to the Cisco site survey methodology. When a spectrum analyzer reveals periodic noise floor spikes across multiple channels with no clear line-of-sight obstruction, the root cause is almost certainly a non-802.11 device — candidates include cordless phones, video cameras, microwave equipment, or radar systems triggering DFS events. The correct engineering response is systematic documentation: capture the time of occurrence, the specific frequency or frequency range, and the geographic location of the interference signature. This triangulation data enables correlation with physical devices present in the facility. Simply increasing transmit power (Option A) raises the noise floor for neighboring cells and worsens co-channel interference. Using WLC monitoring tools (Option B) is insufficient because the WLC cannot detect non-802.11 energy at Layer 1. Adjusting the channel plan (Option C) without fully characterizing the interferer is premature. Only Option D follows the correct Cisco survey methodology for Layer 1 analysis, leading to actionable AP placement adjustments. Reference: WLSD Study Guide — Wireless Site Survey Methodology, Layer 1 Spectrum Analysis, Interference Identification and Mitigation.

When configuring high availability on a Cisco access point, the AP can be configured with a maximum of three controllers: a primary controller, a secondary controller, and a tertiary controller. This three-tier hierarchy defines the failover order — the AP first attempts to join its primary controller, then the secondary if the primary is unavailable, and finally the tertiary if both the primary and secondary are unreachable. After exhausting all three configured options, the AP enters a discovery process to find any available controller. This three-controller configuration (primary, secondary, tertiary) allows network engineers to implement N+1 redundancy where critical APs can be directed to specific backup controllers in a deliberate sequence. Limiting the configuration to only 2 controllers (as stated in Option B which would be incorrect) would reduce redundancy options for environments with geographically distributed controllers requiring specific failover paths. Reference: WLSD Study Guide — AP High Availability Configuration, Primary/Secondary/Tertiary Controller Assignment, AP Failover Design.

The requirement for users to retain their session state and IP address when roaming between buildings managed by different WLCs is a Layer 3 roaming scenario. In Cisco ' s wireless architecture, IP address preservation across controller boundaries is achieved through inter-controller mobility — specifically the foreign-anchor mobility tunnel mechanism. When a client roams from Building A (WLC-A) to Building B (WLC-B), WLC-B becomes the foreign controller and WLC-A becomes the anchor controller. WLC-B tunnels the client ' s traffic back to WLC-A, allowing the client to retain its original IP address even while physically associated to an AP managed by WLC-B. This requires a mobility tunnel between WLC-A and WLC-B with both controllers configured in the same mobility group name — the group name is the trust identifier that permits the mobility tunnel and anchor-foreign relationship to form. Without the same group name, the controllers will not form a trusted mobility peer relationship. AP groups (Option C) control SSID and VLAN assignments per AP cluster but have no impact on inter-controller roaming. HA cluster configuration (Option B) creates SSO redundancy, not roaming capability between separate N+1 controllers. Redundancy port connection (Option D) is used for SSO keepalive and state sync, not mobility tunneling. Reference: WLSD Study Guide — Inter-Controller Mobility, Mobility Tunnels, Layer 3 Roaming and IP Address Preservation.

When conducting a Layer 2 site survey, it is recommended to match the survey to the worst client available. This ensures that the wireless network is designed to provide adequate coverage and performance even for clients with the poorest RF capabilities, thereby providing a consistent user experience for all devices. The worst client typically has fewer antennas, lower receiver sensitivity, and less sophisticated chipsets. By designing to its limitations, the engineer guarantees that every device in the environment meets the minimum performance threshold. Using the best client (Option A) or an average client (Option C) would result in coverage gaps for less capable devices. A phone client (Option B) may have unique characteristics but is not a universally applicable standard for general survey purposes. Reference: WLSD Study Guide — Site Survey Methodology, Client Selection for Survey, Layer 2 Pre-Deployment Survey.

Configuring a high availability SSO pair on Cisco Catalyst 9800 IOS XE WLCs has specific technical prerequisites that must be satisfied for the SSO relationship to form and function correctly. The two critical requirements are: each WLC must have a unique Redundancy Management Interface (RMI) IP address (Option B), and both WLCs must run identical IOS XE software versions (Option D). The Redundancy Management Interface is the dedicated in-band control channel over which the active and standby WLCs exchange state synchronization information, keepalive messages, and configuration updates. Each controller requires its own unique RMI IP address within the same subnet — the active uses one address and the standby uses another. If they shared the same RMI IP (Option C), there would be an IP address conflict preventing the interface from functioning. Identical software versions (Option D) are mandatory because the SSO state synchronization protocol and data structures must be version-compatible between the active and standby controllers. Any mismatch in IOS XE version will prevent SSO formation. License count (Option A) does not need to be identical for SSO. Service port IP addresses (Option E) must be unique per controller, not identical. Reference: WLSD Study Guide — Catalyst 9800 SSO Prerequisites, Redundancy Management Interface Configuration, High Availability Pair Formation Requirements.

For optimized roaming across multiple Wireless LAN Controllers (WLCs) with Cisco 8821 IP phones, two critical settings must be configured. First, configuring mobility groups between WLCs (Option A) allows for seamless inter-controller roaming by establishing mobility tunnels between controllers, enabling them to share client security context, preventing re-authentication when a phone roams from an AP on one WLC to an AP on another. Second, using Cisco Centralized Key Management (CCKM) for authentication (Option B) reduces the time required for re-authentication during roaming from a full 802.1X exchange to a single-message re-key process. CCKM stores the wireless security keys at the WLC level, enabling rapid key re-derivation during roaming without contacting the RADIUS server. AP groups (Option C) control SSID and VLAN assignments per AP cluster but have no impact on inter-controller roaming. AVC profiles (Options D and E) control application visibility and QoS marking — marking voice as best effort (Option E) would actually degrade rather than improve voice quality. Reference: WLSD Study Guide — VoWLAN Mobility Optimization, CCKM Configuration, Mobility Group Design for Multi-Controller Deployments.

This question hinges on a fundamental network engineering constraint: the maximum transmission distance of copper Ethernet cabling. IEEE 802.3 standards specify a maximum segment length of 100 meters (328 feet) for all standard PoE and Ethernet over Category 5e, 6, or 6A UTP copper cabling. The parking lot light poles are approximately 200 meters from the closest wiring closet — more than double the maximum copper distance. This immediately eliminates Options A and D, which specify Category 6 UTP cabling: at 200 meters, UTP copper cannot reliably carry Ethernet at any supported speed, and PoE cannot be delivered over this distance regardless of standard. The correct solution is fiber optic connectivity between the wiring closet and the parking lot, combined with a local AC/DC power module at each pole location. Fiber optic cabling supports single-mode runs of kilometers and multi-mode runs of hundreds of meters at Gigabit speeds — easily spanning 200 meters. At the AP mounting location on the light pole, an AC/DC power module (powered from the pole ' s existing electrical supply) converts AC power to the DC power the AP requires. Option B (fiber with 802.3af) is incorrect because PoE cannot be delivered over fiber — 802.3af requires copper cabling for simultaneous power and data delivery. Reference: WLSD Study Guide — Outdoor AP Deployment, Fiber vs. Copper Distance Limitations, Outdoor Power Solutions.

Raising the minimum data rate to 24 Mbps reduces the effective coverage range of each AP because clients at the cell edge operating at low data rates are effectively excluded from the cell. This shrinks cell size, reducing channel overlap between neighboring APs on the same channel. Using directional antennas limits the coverage area of some APs by focusing RF energy in specific directions rather than radiating omnidirectionally, which directly reduces the lateral overlap between adjacent APs. Increasing AP transmit power (Option B) would worsen overlap, not reduce it. Allowing UNII-2e channels (Option C) provides more channel options but does not reduce the physical cell overlap — it only provides more channels to avoid co-channel interference. Power saving mode (Option E) is a client-side power management feature unrelated to AP cell sizing during a survey. Reference: WLSD Study Guide — Channel Overlap Mitigation, Data Rate Configuration, Directional Antenna Use Cases.

This design scenario requires careful interpretation of the SSO pair function and AP priority semantics. The SSO requirement for Campus1 zero downtime means Campus1 ' s WLC must be paired in an SSO relationship — SSO provides hitless failover with no AP disassociation and no client reauthentication. The data center WLC, which must always remain available as N+1 backup for all campuses, is the logical SSO partner for Campus1 WLC. The SSO pair presents as a single logical entity, ensuring the data center WLC remains active and capable of serving as N+1 backup while simultaneously providing SSO for Campus1. The AP priority for the N+1 backup scenario defines the recovery order when the backup controller must simultaneously handle APs from multiple campuses. In Cisco WLC AP failover priority, priority 1 is Critical (highest). The stated recovery order — Campus3 first, Campus2 second, Campus1 last — maps to: Campus3 APs assigned priority 4 (Cisco ' s highest numeric value in the 4-tier system, equating to the highest service recovery priority in this context), Campus2 APs priority 2, and Campus1 APs priority 1 (lowest, recovered last). Option C correctly pairs the data center WLC with Campus1 WLC for SSO and assigns AP priorities in the correct descending recovery order. Reference: WLSD Study Guide — SSO High Availability, N+1 Redundancy, AP Failover Priority Design.

When designing a wireless network to support diverse services — including data, voice, video, and location tracking — across a distributed enterprise with a main office and 10 branch locations, the two primary design factors directly shaping the RF and capacity architecture are the number of wireless devices requiring access and the type of site where the survey will be performed. The device count (Option B) drives AP density, channel reuse planning, capacity modeling, and controller licensing requirements. Each service type — particularly VoWLAN and video — imposes strict per-client throughput and latency constraints that must be multiplied across the concurrent device population. The type of site (Option C) determines the survey approach, attenuation characteristics, coverage requirements, and antenna selection. A warehouse, hospital, or open-plan office each demands a fundamentally different RF design. Options A and D are organizational considerations, not technical RF design inputs. Option E (power sockets) is an installation logistics concern, not a wireless design factor. Reference: WLSD Study Guide — Requirements Gathering, Site Survey Planning, Capacity and Coverage Design Methodology.

Mobility groups are created by configuring each Wireless LAN Controller (WLC) to use the same mobility domain name (mobility group name) and defining each WLC as a peer in the static mobility members list of every other WLC in the group. This bidirectional configuration establishes the trusted peer relationship and enables WLCs to exchange client information, security credentials, and state data for seamless roaming. The same mobility group name on all WLCs creates a shared identity; the static peer list defines which controllers are trusted mobility partners and provides their management IP addresses and MAC addresses for tunnel establishment. Option A is incorrect because members should run compatible (ideally the same) software versions, not different ones. Option B is incorrect — all WLCs in a mobility group must use the same virtual IP address for proper roaming. Option D is incorrect — in an HA SSO pair, the pair presents as a single logical mobility entity, not as two separate peers. Reference: WLSD Study Guide — Mobility Group Configuration, Peer Configuration Requirements, Mobility Domain Architecture.

Receive Start of Packet (RxSOP) is a Cisco proprietary mechanism that defines the minimum received signal threshold at which an access point will acknowledge an 802.11 frame and begin processing it. In a high-density lecture hall environment with 16 APs and directional antennas on a constrained channel plan, rogue APs operating on the same or adjacent channels contribute directly to elevated channel utilization by causing unnecessary medium contention, virtual carrier sensing via NAV, and clear channel assessment deferral. By raising the RxSOP threshold on the legitimate APs, the engineer creates a higher signal floor requirement — only signals above the configured RxSOP level are processed. Signals from distant rogue APs, arriving below this threshold, are silently discarded rather than processed, preventing them from consuming airtime through CCA deferral and NAV mechanisms. Band select (Option A) encourages dual-band clients to move to 5 GHz but does not address rogue interference. 802.11w (Option B) is a management frame protection standard, not an interference mitigation tool. DFS detection (Option D) is for radar avoidance on UNII-2 channels, not rogue AP mitigation. Reference: WLSD Study Guide — High-Density WLAN Design, RxSOP Configuration, Channel Utilization Management.

For a network supporting both data and voice over wireless, two key Cisco design recommendations apply. First, the 5 GHz radio band is recommended for voice over wireless due to its wider channel bandwidths, allowing for higher data rates and better quality of service for latency-sensitive applications. 40 MHz channels in the 5 GHz band provide significantly higher throughput than 20 MHz channels in 2.4 GHz, making Option B correct for the bandwidth reason stated. Second, setting the cell boundary to -67 dBm ensures sufficient signal strength for reliable voice communication at the cell edge, which is the Cisco standard threshold for VoWLAN coverage. Options C and E are partially correct (24 non-overlapping channels is accurate, 15-20% overlap is standard) but B and D are the primary Cisco recommendations that define the design targets for a predictive survey supporting voice. Reference: WLSD Study Guide — VoWLAN Design Requirements, Predictive Survey Design Criteria, 5 GHz Band Selection.

VLAN Select is a feature that allows for the dynamic assignment of clients to different VLANs from a pool based on various criteria, such as load balancing or location. In a centralized wireless deployment with N+1 high availability, if clients are receiving IP addresses from a different subnet after failover despite the WLANs being configured with the same dynamic interfaces, the issue is that the second controller ' s WLAN interface mapping resolves to a different VLAN or DHCP scope. VLAN Select ensures that client VLAN assignment is consistent regardless of which controller the client connects to, preventing the subnet change behavior observed during failover. Without VLAN Select, even identically named dynamic interfaces on two WLCs may map to different VLANs if the underlying switch configuration differs. RF Protocol (Option A) controls radio parameters. AP Groups (Option B) control SSID and VLAN assignments per AP cluster. AAA Override (Option D) allows RADIUS servers to assign per-user VLANs, which requires authentication — but these SSIDs use open authentication. Reference: WLSD Study Guide — N+1 High Availability Design, VLAN Select Feature, Consistent Client VLAN Assignment Across Controllers.

The Cisco Catalyst 9800 IOS XE WLC uses a tag-based configuration architecture. Three primary tag types are used: site tags, policy tags, and RF tags. The site tag associates an AP with its operational context and contains two specific profile references: the AP join profile (defining AP-level parameters such as NTP, syslog, SSH, LED behavior, and CAPWAP timers) and the flex profile (defining FlexConnect-specific parameters including locally switched VLANs, split tunneling, local authentication settings, and VLAN-ACL mappings). The flex profile within the site tag enables the AP to operate in FlexConnect mode with locally configured switching behavior when WLC connectivity is lost. QoS (Option A) policies are applied at the policy tag level within WLAN policies. NAT (Option B) is not a native profile type in the 9800 tag architecture. VLAN (Option D) configurations are defined within the flex profile or policy profile and are not standalone profile types at the tag level. Understanding the three-tag model is essential for designing and troubleshooting 9800-based deployments. Reference: WLSD Study Guide — Catalyst 9800 Configuration Model, Site Tag Architecture, Flex Profile and AP Join Profile.

Designing for 50-100 clients per cell with 5 Mbps minimum throughput and no 802.11b clients requires two critical optimizations. First, setting minimum mandatory data rates to 12-18 Mbps (Option A) removes legacy lower data rates from the AP ' s supported rate set. When 1, 2, 5.5, and 11 Mbps rates are disabled and 12 Mbps becomes the minimum mandatory rate, legacy 802.11b clients are excluded from the cell, airtime efficiency improves dramatically, and clients connecting at higher rates use less channel time per frame, increasing effective capacity. Second, Flexible Radio Assignment (FRA) for 2.4 GHz reduction (Option D) is critical in high-density environments. FRA allows the WLC to dynamically reassign some 2.4 GHz radios to 5 GHz operation or monitor mode, reducing 2.4 GHz cell size and interference while increasing 5 GHz capacity in the high-density area. Option C directly contradicts the no-802.11b requirement. Option B (6 SSIDs per AP) is a management consideration but does not directly address throughput. Option E (80-160 MHz channels) would consume available spectrum, reducing the number of usable non-overlapping channels and worsening co-channel interference at high density. Reference: WLSD Study Guide — High-Density WLAN Design, Minimum Data Rate Configuration, Flexible Radio Assignment (FRA).