Cisco 300-110 Dumps

The Cisco Catalyst 9300-48HX is a high-density PoE switch specifically designed for Cisco Catalyst 9100 Series AP deployments. The 48HX variant features 48 Multi-Gigabit PoE ports with IEEE 802.3bt (PoE++) support, providing up to 90W per port. The Cisco 9166 Access Point is a Wi-Fi 6E AP that requires IEEE 802.3bt (PoE++) power to achieve full radio functionality — enabling all three radios including the 6 GHz radio. In a two-switch stack of 48HX units, the total PoE budget is designed and rated to support full-port utilization with Cisco 9100 series APs simultaneously. The design intent is to connect APs to all ports on all switches — maximizing the deployment density and ensuring every AP runs with full functionality. Connecting to only half the ports on one switch (Option B), half of each switch (Option C), or all ports on only one switch (Option D) would underutilize the infrastructure and fail to achieve the full deployment density that the switch stack was architected to deliver. The AP naming scheme requiring sequential area numbering requires all APs to be connected and fully operational across the entire stack. Reference: WLSD Study Guide — Catalyst 9300 PoE Infrastructure, 9166 AP Power Requirements, High-Density Wired Infrastructure Design.

The primary concern when upgrading to 802.11ac Wave 2 capable APs with existing switches that only provide IEEE 802.3at (PoE+, 30W maximum) is the output power limitation. 802.11ac Wave 2 APs, particularly Cisco ' s 3800 and 4800 series, can require significantly more power than 30W to operate all radios and capabilities at full capacity. The Wave 2 standard introduced features such as Multi-User MIMO (MU-MIMO), beamforming, and additional spatial streams, all of which increase power consumption. When an AP doesn ' t receive sufficient power, it may reduce transmit power, disable radios, or reduce the number of spatial streams — directly degrading wireless performance. Interface throughput (Option A) may also be a concern with multi-gigabit capable APs, but the question specifically asks about the limitation introduced by 802.3at, which is directly a power delivery constraint. Collision domains (Option C) and high availability (Option B) are unrelated to the PoE standard. Reference: WLSD Study Guide — PoE Upgrade Planning, 802.11ac Wave 2 Infrastructure Requirements, Switch Power Budget Considerations.

The design requirements — optimized performance, interference avoidance, high-density support, and roaming capability — collectively point to a dual-band strategy using narrow channel widths. For 5 GHz operation (Option A), 20 MHz channels are the correct choice for high-density and campus-scale deployments. The 5 GHz band has significantly more non-overlapping channels compared to 2.4 GHz (up to 24 non-overlapping 20 MHz channels in UNII-1, UNII-2, and UNII-3), enabling a robust channel reuse plan with minimal co-channel interference and excellent roaming cell separation. Wider 5 GHz channels (Options C and E — 80 MHz and 40 MHz) would consume multiple channel blocks, dramatically reducing the number of available non-overlapping channels and increasing co-channel interference in dense deployments. For 2.4 GHz operation (Option B), 20 MHz channels are mandatory — there are only three non-overlapping 20 MHz channels (1, 6, 11) in the 2.4 GHz band. Using 40 MHz channels in 2.4 GHz (Option D) eliminates all non-overlapping channel separation, causing massive co-channel interference and is universally contraindicated in enterprise designs. Reference: WLSD Study Guide — Channel Planning, High-Density Design, Frequency Band Selection.

After creating a new predictive survey project and importing the floor plan, the next mandatory step is to set the scale of the floor plan. Setting the scale is critical because all subsequent measurements — AP coverage radius, cell overlap calculations, and distance-based attenuation modeling — depend on the accuracy of the floor plan ' s physical dimensions. If the scale is incorrect, the predictive model will place APs at incorrect distances relative to each other and produce inaccurate coverage predictions. The scale is typically set by the engineer clicking on two known points on the floor plan and entering the real-world distance between them, calibrating the software ' s measurement system. Analyzing the network (Option A) and placing APs (Option C) come after the scale is established. Identifying the coverage area (Option B) is often done simultaneously with scale setting or immediately after. Setting the scale first ensures all subsequent work is based on accurate physical dimensions. Reference: WLSD Study Guide — Ekahau Predictive Survey Workflow, Floor Plan Import and Scale Setting, Pre-Deployment Survey Methodology.

A brownfield deployment scenario involves an existing operational wireless network where a physical remodel will change the RF environment. The engineer ' s task is to assess the impact of new furniture and wall materials on the existing AP placement — a scenario requiring a predictive re-analysis of how changed materials will alter propagation from the existing AP locations. Using a survey tool such as Ekahau with the known AP positions superimposed on updated floor plans, the engineer can reconfigure material attenuation properties to reflect new construction materials and re-run the predictive propagation model. This produces a before/after comparison identifying coverage gaps or interference hotspots introduced by the remodel without requiring physical downtime or temporary infrastructure changes. Option A (sweep analysis) measures existing signal strength but does not model future material changes. Option B (neighbor AP statistics) evaluates the current RF environment using WLC data, not future conditions. Option C (throughput measurements) tests current performance, not future RF impact. Reference: WLSD Study Guide — Brownfield Survey Methodology, Material Attenuation Modeling, Post-Remodel RF Impact Analysis.

When Cisco WLCs are configured to use multicast for mobility group communications, all WLCs participating in the same mobility group must be configured with an identical multicast group IP address. The mobility multicast mode allows a WLC to send a single multicast frame received simultaneously by all other WLCs in the group, rather than sending individual unicast copies to each peer. For this to function correctly, every WLC in the group must join the same IP multicast group address, and the underlying network infrastructure must be configured to support IP multicast routing or IGMP snooping for that specific group address. If any WLC is configured with a different multicast IP address, it will join a different multicast group and will not receive mobility messages from the other WLCs, effectively isolating it from the group ' s communication plane. Service port IP addresses (Option A) are unique per controller. Interface IDs (Option B) are locally significant identifiers. Management IP addresses (Option C) are unique per WLC and identify each peer in unicast configurations. Reference: WLSD Study Guide — Mobility Group Configuration, Multicast Mobility Messaging, WLC Peer Communication.

Non-802.11 device detection on the 5 GHz band without a dedicated spectrum analyzer is possible through Cisco ' s CleanAir technology, which is embedded as an RF ASIC in many Cisco AP models including the 9120 series. CleanAir operates at the hardware layer — below the 802.11 MAC — enabling the APs to detect, classify, and report non-802.11 interference sources such as cordless phones, microwave ovens, video cameras, radar, and other unlicensed RF emitters in the 5 GHz spectrum. The WLC aggregates CleanAir reports from all APs and provides a consolidated interference device list accessible through the WLC ' s monitoring interface. Since the question specifies the 5 GHz band, the relevant 802.11 protocol for 5 GHz is 802.11a (and its successors 802.11n and 802.11ac). Exporting the list of 802.11a interferers from the WLC using the CleanAir RF ASIC correctly targets the 5 GHz band and identifies non-802.11 devices detected there. Option A incorrectly references 802.11b, which operates only on 2.4 GHz. Options B and C attempt to use the WLAN adapter for non-802.11 detection, but a standard WLAN adapter in monitor mode can only capture 802.11 frames — it cannot detect non-802.11 RF energy without a spectrum analyzer chipset. Reference: WLSD Study Guide — Cisco CleanAir Technology, Non-802.11 Interference Detection, Post-Deployment Survey Methodology.

Warehouse wireless deployments present unique RF engineering challenges: extremely high ceilings (often 25-45 feet), dense metallic shelving systems that create specular reflections and RF shadows, narrow aisles between rack systems, and the need to cover linear travel paths for RF scanner devices. The recommended Cisco antenna strategy for warehouses is wall-mounted patch (directional) antennas. Patch antennas provide a forward-facing radiation pattern that can be aimed precisely down warehouse aisles, delivering concentrated RF energy where RF scanners actually operate — in the aisles between shelving — rather than dispersing energy into metallic shelving structures. Wall mounting at intermediate height (typically 10-15 feet on aisle-end walls) places the antenna at a height that aligns the main lobe with the working zone of handheld scanners. Ceiling-mounted omnidirectional antennas (Options A and C) at warehouse ceiling height suffer from excessive path loss to floor-level devices and metal shelving obstructions. Low-gain wall-mounted omnidirectional antennas (Option B) lack the directivity needed to focus energy down specific aisles. Reference: WLSD Study Guide — Warehouse Wireless Design, Antenna Selection and Placement, Industrial RF Environment Considerations.

The design challenge is enabling IEEE 802.11r Fast BSS Transition for the new iPads (the standards-based fast roaming method) while maintaining backward compatibility for legacy RF scanners that may not support 802.11r. The SSID uses WPA2 Personal (PSK), not 802.1X enterprise authentication — therefore the correct Fast Transition variant is FT PSK (pre-shared key), not FT 802.1X (Options A and B). The critical configuration parameter is setting Fast Transition to Adaptive mode rather than mandatory. Adaptive mode is a Cisco feature that allows the AP and SSID to support both 802.11r-capable clients (which will use FT PSK for fast roaming) and non-802.11r legacy clients (which will use the standard pre-FT roaming process). In Adaptive mode, legacy scanners that cannot negotiate 802.11r during association will fall back transparently to standard roaming, while the new iPads leverage FT PSK for minimal-interruption handoffs. If Fast Transition is set to mandatory, legacy clients that do not support 802.11r will fail to associate entirely. Option C uses optimized roaming globally, which is a different mechanism and does not address the iPads ' specific need for a standards-based fast roaming solution. Reference: WLSD Study Guide — 802.11r Fast BSS Transition, FT PSK Configuration, Adaptive Fast Transition for Mixed Client Environments.

The Cisco Aironet 4800 Series Access Point is a tri-radio, high-performance access point designed for high-density environments. It draws significantly more power than older dual-radio APs and requires IEEE 802.3bt (also known as PoE++), which provides up to 90W per port at the Power Sourcing Equipment. IEEE 802.3af (Type 1 PoE) delivers only 15.4W and 802.3at (Type 2 PoE+) provides up to 30W — both are insufficient for full functionality of the 4800 series, which has a dedicated third scanning radio that requires the additional power budget provided by 802.3bt. IEEE 802.3ac is a standard related to VLAN tagging and is entirely unrelated to Power over Ethernet. Engineers designing wired infrastructure for Cisco 4800 deployments must ensure switches support 802.3bt Type 3 or Type 4 to guarantee full AP functionality across all three radios simultaneously. Reference: WLSD Study Guide — Wired Infrastructure Design, PoE Standards and Power Budget Planning, Cisco 4800 Series AP Specifications.

For a high-density classroom deployment using 5 GHz with channel bonding in groups of two (40 MHz channels), the correct configuration is to set the channel width for 802.11a (5 GHz) to 40 MHz and set the 24 Mbps data rate to Mandatory. Channel bonding refers to combining two adjacent 20 MHz channels into a single 40 MHz channel, doubling the channel width. Since the requirement specifies 5 GHz operation (where high-density design is appropriate), this must be applied to the 802.11a radio profile, not 802.11b (which operates only on 2.4 GHz). Setting 24 Mbps as Mandatory ensures that APs transmit management frames (beacons, probe responses, and other control frames) only at 24 Mbps — this is how the ' only allow APs to send 802.11 management frames at 24 Mbps ' requirement is implemented. Setting it as Supported (Options B and D) would allow the AP to use lower rates for management frames. Options A and D incorrectly target 802.11b, which does not support 40 MHz channels. Reference: WLSD Study Guide — High-Density WLAN Design, 802.11a Channel Configuration, Data Rate and Channel Width Settings.

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.

This WGB (Workgroup Bridge) design scenario requires satisfying multiple simultaneous constraints. EAP-FAST (Flexible Authentication via Secure Tunneling) is the correct authentication protocol because it provides enterprise-grade 802.1X security using protected access credentials (PAC) without requiring a certificate to be installed on each AP or WGB device — directly satisfying the enterprise-grade security without certificates requirement. EAP-TLS (Options B and D) requires client certificates on every authenticating device, which is explicitly excluded. Mobile station mode is required rather than static mode (Options C and D) because mobile station mode enables the WGB to aggressively scan and roam to optimal mesh neighbors dynamically, evaluating neighbor signal quality and switching to better RAPs/MAPs as the truck moves along its path. Static mode fixes the WGB to a specific channel or AP, preventing the aggressive scanning and roaming required for the latency-sensitive application. The dot1q-capable switch connection supports multiple clients in different VLANs via 802.1Q VLAN tagging between the WGB and the truck ' s local network switch. Reference: WLSD Study Guide — Workgroup Bridge Design, EAP-FAST Authentication, Mobile vs. Static WGB Mode, Industrial Wireless Design.

Cisco WLC AP Failover Priority governs the order in which APs are processed when a WLC recovers and APs begin re-associating. The priority levels are: Critical, High, Medium, and Low. During recovery situations, the WLC will accept and process AP join requests in order of priority — Critical priority APs are processed first, before all other priority levels. In a deployment where the WLC is located in a remote data center connected via WAN, the join process for all APs is slower due to WAN latency and potential bandwidth constraints. Under these conditions, assigning Critical priority to executive office APs ensures they are at the front of the processing queue and restore service before lower-priority APs. The executive office designation implies business-critical operations requiring the fastest possible wireless restoration — a requirement that directly maps to the Critical priority level. High priority (Option A) would position the executive APs second in the queue behind any Critical priority APs. Medium (Option B) and Low (Option C) would place them further down the processing order. Reference: WLSD Study Guide — AP Failover Priority Configuration, N+1 and SSO Redundancy Design, WAN-Linked Controller Deployments.

On the Cisco Catalyst 9800 IOS XE WLC platform, the tag-based configuration model uses site tags to associate APs with specific profiles including a flex profile and an AP join profile. The site tag is a fundamental binding element — when any component of a site tag is modified, including renaming the flex profile associated with that tag, the WLC treats this as a material configuration change requiring the AP to re-evaluate its operational parameters. Specifically, the AP must disconnect its existing DTLS (Datagram Transport Layer Security) control plane tunnel to the WLC and re-establish it. This DTLS session disconnect and rejoin cycle is equivalent to a full AP rejoin: CAPWAP discovery, DTLS handshake, join request, configuration download, and image verification. Client service is interrupted on the affected AP during this process. Firmware updates (Option A) occur via a separate image download process. Temporary SSID disable (Option B) is not a defined behavior for profile name changes. Switching to a backup controller (Option C) requires AP failover conditions, not configuration changes. Understanding the disruptive nature of site tag modifications is essential for change management in production 9800 deployments. Reference: WLSD Study Guide — Catalyst 9800 Tag-Based Configuration Model, Site Tag Architecture, Flex Profile and AP Join Profile Management.

RF Profiles are a Cisco WLC configuration construct that allows administrators to define a customized set of Radio Resource Management (RRM) parameters and apply them to a subset of APs operating in a specific environment or coverage zone. Within a university high-density deployment — where a lecture hall, outdoor quad, cafeteria, and library may each require fundamentally different RF settings — RF Profiles enable differentiation without globally modifying all RRM parameters. An RF Profile can define custom values for: minimum mandatory data rates, maximum transmit power, minimum transmit power, channel width (20/40/80 MHz), RxSOP thresholds, client load balancing parameters, and coverage hole detection sensitivity. This allows the engineer to apply aggressive interference mitigation settings to high-density assembly areas while maintaining full-coverage settings for perimeter zones. AP Groups (Option A) assign WLANs and interface mappings to subsets of APs but do not directly control RF parameters. RF Groups (Option B) are automatically formed by RRM and represent a cluster of APs coordinating channel and power assignment. AP Profiles (Option C) define AP behavior parameters such as NTP and SSH settings, not RF optimization parameters. Reference: WLSD Study Guide — RF Profile Configuration, High-Density WLAN Design, RRM Parameter Customization.

Flex+Bridge mode is a specialized AP operating mode that combines two distinct Cisco wireless capabilities: FlexConnect (for local switching of client data traffic and central authentication via the WLC) and Bridge/Mesh mode (enabling wireless backhaul when no wired Ethernet uplink is available). In a branch environment without wired backhaul, a standard FlexConnect AP (Option D) cannot operate because FlexConnect still requires an Ethernet connection for its control plane. Bridge mode alone provides mesh backhaul but does not support the local switching with central authentication model required here. MAP (Option A) is a Mesh Access Point role for wireless backhaul, and RAP (Option C) is a Root Access Point with a wired connection — neither meets the no-wired-backhaul requirement with local switching. Flex+Bridge uniquely satisfies both requirements: the Flex component allows locally switched VLANs to be bridged directly to the access layer without traversing the WAN, while the Bridge component enables the AP to use a wireless mesh link for its backhaul uplink. Central authentication is maintained via the CAPWAP control tunnel over the mesh link. Reference: WLSD Study Guide — FlexConnect Design, Mesh Networking, Flex+Bridge Mode Configuration and Use Cases.

Floor loss calculation is a fundamental skill in multi-floor wireless site survey methodology. The floor attenuation value represents the signal power reduction caused by penetrating through a single floor structure including the floor decking, subfloor, ceiling material, plenum space, and any structural elements. In this measurement scenario, the engineer has two data points: -45 dBm measured at the ground level of the floor containing the access point (the signal level just below the AP ' s floor) and -50 dBm measured at the ceiling level of the floor below (the signal level just after passing through the floor structure). The floor loss is simply the difference between these two measurements: (-45 dBm) - (-50 dBm) = -45 + 50 = 5 dB. The result is expressed as a positive value (5 dB) representing attenuation — signal power decreases by 5 dB when passing through the floor. Expressing it as -5 dB (Option B) would incorrectly imply a signal gain. The 95 dB values (Options A and D) result from incorrectly adding rather than subtracting the dBm values — a common error when working with negative dBm figures. This floor attenuation value (5 dB) would then be entered into Ekahau ' s floor material properties to improve predictive model accuracy. Reference: WLSD Study Guide — Multi-Floor Signal Propagation, Floor Attenuation Factor (FAF), Ekahau Floor Loss Measurement Methodology.

Cisco ' s WLAN location and asset tracking architecture (based on Cisco Spaces or legacy Cisco MSE/CMX) relies on the ability to receive and measure the RF signal from tagged assets at multiple APs simultaneously. For accurate location determination using triangulation or trilateration algorithms, a minimum of three APs must receive the tag ' s signal with sufficient RSSI. Monitor mode APs are dedicated to passive RF listening — they do not transmit client-serving SSIDs and focus their full radio attention on scanning all channels for signal measurement. Placing monitor mode APs specifically on the perimeter of an asset tracking area provides the spatial diversity and boundary detection capability needed to accurately triangulate assets throughout the interior, without requiring any modifications to the existing data/voice serving APs. Adding monitor mode APs at the perimeter as an overlay ensures the existing 2.4 GHz and 5 GHz voice/data design is entirely undisturbed. Adding local mode APs (Option B) would serve clients and compete for channel capacity. Grouping APs closer (Option C) reduces capacity and increases co-channel interference. Increasing transmit power (Option D) worsens hidden node conditions without improving location accuracy. Reference: WLSD Study Guide — Cisco Location Services, Monitor Mode APs, Asset Tracking and WLAN Overlay Design.

A pre-site survey questionnaire is used to gather information before the physical survey begins, helping to define design requirements. The two most important information points it should contain are the access point density required and the applications that will run over the wireless network. Access point density (Option C) must be understood early because it depends on the number and types of users in each area, directly influencing the survey approach and AP placement strategy. Applications (Option E) are critical because they define the QoS requirements — a company developing code may run video conferencing, large file transfers, and real-time collaboration tools, each with distinct bandwidth and latency requirements that shape the RF design criteria. The total number of existing APs (Option A) and the current controller model (Option D) are inventory questions, not design requirement inputs. Client device types (Option B) are important but are a subset of the application question — applications drive the specific device capability requirements. Reference: WLSD Study Guide — Pre-Site Survey Requirements Gathering, Customer Questionnaire, Design Requirements Definition.

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.

IEEE 802.11v BSS Transition Management is the standard that enables the network (via the AP) to actively provide roaming recommendations and suggestions to associated clients. When enabled on a SSID, the AP can send BSS Transition Management Request frames to clients, informing them of preferred target APs ranked by signal quality, load, and channel conditions. Critically, BSS Transition Management is a voluntary mechanism — clients that support 802.11v can act on the AP ' s recommendation, while clients that do not support 802.11v simply ignore the BSS Transition Request frames and continue operating normally. This selective applicability directly satisfies the requirement that non-VoWLAN clients must not be impacted. 802.11k (Option A) enables clients to build neighbor lists through measurement reports — this is a client-initiated process, not an AP-to-client recommendation. CCKM (Option B) is a Cisco proprietary fast roaming mechanism for legacy clients, unrelated to roaming guidance. 802.11r (Option D) accelerates the re-association handshake during roaming but does not provide proactive roaming recommendations. Reference: WLSD Study Guide — VoWLAN Design, 802.11v BSS Transition Management, Roaming Optimization Protocols.

The scenario presents a critical distinction in where Cisco WLC features are configured. Optimized roaming on Cisco WLC is a radio-level feature that monitors connected client RSSI and, when a client ' s signal falls below the configured threshold (-72 dBm), triggers a disassociation to force the client to reconnect to a stronger AP. However, without a mechanism to guide the client proactively before reaching the threshold, clients that disassociate simply reconnect to whatever AP their device selects, potentially causing the reported frequent disconnections. BSS Transition Management (802.11v) is configured at the SSID level and provides the complementary mechanism: before the client reaches the RSSI threshold, the AP sends a BSS Transition Management Request pointing the client toward a specific target AP with stronger signal. The correct architecture requires: optimized roaming configured at the radio level (triggering disconnection when RSSI falls too low) combined with BSS transition enabled at the SSID level (guiding the client to a better AP before forced disconnection). Options C and D incorrectly reverse the configuration levels for these features. Disabling coverage hole detection (Option B) addresses a different problem and would not resolve the disconnection issue. Reference: WLSD Study Guide — Optimized Roaming Configuration, BSS Transition Management (802.11v), Client Roaming Architecture on Cisco WLC.

The Cisco WLAN site survey methodology follows a structured, sequential process. The initial walkthrough — sometimes called the discovery or orientation phase — is the first step, during which the engineer physically tours the facility to understand its physical characteristics: building materials, structural layout, potential AP mounting locations, wiring closet positions, and environmental factors. After completing the initial walkthrough, the next logical phase is the predeployment survey (also referred to as a pre-deployment or predictive survey). The predeployment survey uses the information gathered during the walkthrough to create a detailed design plan — either through a manual AP placement plan or a predictive survey tool such as Ekahau, where floor plans are annotated with materials and attenuation values and APs are virtually placed to model coverage. The predeployment survey output is the design document that drives the actual physical installation. A post-deployment survey (Option A) validates coverage after installation — it cannot precede deployment. Active and passive surveys (Options B and D) are physical measurement techniques conducted either pre-deployment (with temporary APs) or post-deployment (with installed APs) — they do not logically follow immediately after a walkthrough before any design work is done. Reference: WLSD Study Guide — WLAN Site Survey Process, Predeployment Survey Phase, Airport Wireless Design Considerations.

The Cisco Aironet 2800 Series APs feature a dual-radio architecture with a dedicated 5 GHz radio (slot 1) and a Flexible Radio Assignment (XOR) radio (slot 0) that can operate in either 2.4 GHz or 5 GHz, or be assigned to monitor mode for scanning functions. Since all existing SSIDs and services are 5 GHz only, the slot 1 (dedicated 5 GHz) radio is responsible for all current client connectivity — it must remain in Client Serving mode to maintain uninterrupted 5 GHz WLAN service. The XOR radio (slot 0), currently either idle or operating as a secondary 5 GHz radio, can be repurposed without impacting client service. Setting the XOR radio to Monitor mode enables it to continuously scan all channels across both the 2.4 GHz and 5 GHz spectrum for rogue AP detection, using the embedded CleanAir and WIDS capabilities. In Monitor mode, the XOR radio operates full-time as a dedicated scanner, providing rogue detection coverage on 2.4 GHz (previously uncovered since all services were 5 GHz) and supplementary scanning on 5 GHz. This eliminates the need for additional dedicated monitor mode APs. Options A, C, and D either place the slot 1 radio in a non-client-serving role (disrupting existing connectivity) or use the inappropriate Sniffer mode instead of Monitor mode for rogue detection. Reference: WLSD Study Guide — Cisco 2800 XOR Radio Architecture, Monitor Mode for Rogue Detection, Flexible Radio Assignment, WIDS Design.

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.

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.

Cisco Catalyst Center uses a tiered licensing model — Essentials and Advantage — applied to both switching and wireless infrastructure. To enable a fully fabric-enabled (SD-Access) deployment with centralized management, the Cisco Catalyst Advantage license is required across all device types. The Advantage tier unlocks Software-Defined Access fabric capabilities including macro and micro-segmentation, integration with Cisco ISE for policy enforcement, AI/ML-driven analytics via DNA Spaces and Assurance, and automated provisioning. The Essentials license provides only basic device management, inventory, and software image management — it does not unlock SD-Access fabric functionality. Since the branch design specifically extends an existing fabric-enabled network, the Essentials tier for either the switch or APs would create a licensing gap preventing full fabric participation. Options B, C, and D all create asymmetric licensing that would partially disable fabric capabilities. The correct design mandates Catalyst Advantage for the Catalyst 9300 switch and all 25 APs. Reference: WLSD Study Guide — Cisco Catalyst Center Licensing, SD-Access Design, Fabric-Enabled Wireless Architecture.