This question requires straightforward wireless capacity engineering calculation. The total throughput requirement is 100 users × 1 Mbps per user = 100 Mbps aggregate. Each channel in the design can support 20 Mbps of usable throughput - this is the per-cell, per-channel allocation defined in the design parameters, representing usable throughput prior to RF overhead as stated in the question. The number of channels required is therefore: total required throughput divided by throughput per channel = 100 Mbps ÷ 20 Mbps per channel = 5 channels. In practice, each channel corresponds to a non-overlapping frequency assignment in the
5 GHz band. With 5 channels and 20 Mbps per channel, the design provides exactly 100 Mbps of aggregate capacity for 100 concurrent users at 1 Mbps each. This calculation methodology is foundational to Cisco ' s high-density WLAN design approach, where the number of spatial streams, channel allocations, and AP placement are all derived from the per-user throughput requirement multiplied by the concurrent user population. Reference: WLSD Study Guide - High-Density WLAN Capacity Planning, Per-User Throughput Calculation, Channel Planning and Spatial Reuse.

To support high availability with client SSO (Stateful Switchover) and no interruption to live services during failover, the design must incorporate two requirements. First, redundant WLCs (Option A) are essential - without a physical standby controller, there is no entity to take over when the primary WLC fails. In an SSO configuration, one WLC is active and one is standby, and the standby must be ready to assume the active role instantaneously. Second, the high availability pair requires one of the WLCs to have a valid AP count license (Option B). In a Cisco WLC SSO pair, the standby controller ' s AP count license applies when it becomes active - without a valid license on at least one WLC in the pair, APs cannot join after failover. A 10-second RTT maximum (Option C) is a latency requirement for the redundancy link but is not a primary design requirement that addresses the overall high availability architecture. A back-to-back direct connection (Option D) is one way to connect the redundancy ports but is not mandatory if a low-latency switch connection is used. Code version 7.5 or newer (Option E) is a requirement for specific legacy SSO platforms but not a general design principle. Reference: WLSD Study Guide - WLC SSO High Availability Design, AP License Requirements, Redundant Controller Architecture.

Cisco Catalyst Center ' s AI-driven network management capabilities - including AI Analytics, AI-Enhanced RRM (Radio Resource Management), location analytics (DNA Spaces integration), and automated RF profile management - are exclusively available under the Catalyst Advantage license tier. The Advantage tier builds upon the Essentials tier and adds access to the full suite of AI/ML-powered assurance and optimization features. Specifically, AI-Enhanced RRM leverages machine learning models trained on historical RF telemetry to predict and prevent RF issues, dynamically adjust channel and power assignments, and automate RF profile selection - capabilities that cannot be activated without the Advantage license. Location analytics through Catalyst Center integrates with Cisco Spaces to provide real-time client location tracking, asset tracking, and spatial analytics. Catalyst Essentials (Option C) provides basic device management, software image management, and network plug-and-play provisioning - it does not include AI Analytics or advanced RRM automation. Right-To-Use (Option B) is a legacy licensing model not applicable to Catalyst Center.
SNTC SmartNet (Option D) is a support and maintenance contract, not a software feature license. Reference:
WLSD Study Guide - Cisco Catalyst Center Licensing, AI-Enhanced RRM, Catalyst Advantage Feature Set.

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.