Cisco 3800 Series APs support IEEE 802.11ac Wave 2, which can deliver throughput exceeding 1 Gbps. Fast Ethernet switches are limited to 100 Mbps per port, creating a severe bottleneck. The two actions that provide maximum support are replacing with mGig switches (Option A) and replacing with gigabit switches with 10G uplinks (Option B). mGig (Multi-Gigabit Ethernet) switches support 2.5G and 5G speeds over existing CAT 6A cabling, allowing the full throughput of 802.11ac Wave 2 APs to be utilized without replacing the existing cable plant. Gigabit switches with 10G uplinks ensure that the access layer can support 1 Gbps per AP port while providing sufficient uplink capacity. Since the existing cabling is already CAT 6A, which supports 10 Gbps over short distances and 5 Gbps over 100 meters, there is no need to replace the wiring (Option D eliminates). The 100-meter distance limitation (Option C) already applies to standard Ethernet and is met by CAT 6A — this is not an action but a constraint check. Option E (55 meters) is only relevant for specific 5GBASE-T configurations and doesn ' t maximize support compared to A and B. Reference: WLSD Study Guide — mGig Infrastructure, 802.11ac Wave 2 Infrastructure Design, Switch Upgrade Planning.

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.

This question requires a straightforward PoE power budget calculation. The IEEE 802.3at standard (PoE+) delivers a maximum of 30W at the Power Sourcing Equipment (PSE/switch port). Cisco 9100 Series access points such as the C9120, C9130, and C9136 are designed to operate with full functionality using PoE+ at 30W per AP. The total PoE power requirement for 12 APs is calculated as: 12 APs × 30W per AP = 360W. This figure represents the total power draw that the Cisco 3800 Series PoE+ switch must be capable of supplying across the connected AP ports simultaneously. The Cisco Catalyst 3800 Series switches offer a total PoE power budget that must be validated against this 360W requirement during the design phase. Note that some Cisco 9100 APs support higher power modes through IEEE 802.3bt (PoE++), which can provide up to 90W — but the question specifies PoE+ (802.3at) for the switch infrastructure, making 30W × 12 = 360W the correct answer. Option D (720W) would correspond to 24 APs at 30W each. Option B (1080W) would represent 36 APs. Option C (184.8W) corresponds to a non-standard per-AP power value. Reference: WLSD Study Guide — PoE Power Budget Planning, Cisco 9100 Series AP Power Requirements, Wired Infrastructure Design for Wireless Deployments.

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.

To test whether mobility control packets can reach between WLC peers in a mobility group (used to validate the anchor controller DMZ setup), two steps are required. First, the mping (mobility ping) command (Option A) is the Cisco WLC CLI tool specifically designed to test mobility control path connectivity between WLC peers. Running mping on both WLCs verifies that mobility control messages (UDP port 16666) can be exchanged bidirectionally. Second, UDP port 16666 must be open between the WLCs (Option C) — mping uses this port, and if it is blocked by a firewall (which is common when the anchor is in a DMZ), the mobility control path cannot be established. These two steps together — sending mping packets and confirming the firewall permits UDP 16666 — validate mobility control plane connectivity. The eping (EoIP ping) command (Option B) tests the data path tunnel, not the control path. IP Protocol 97 (Option D) is for the data plane in legacy mobility mode. Tracert (Option E) traces routing paths but does not validate mobility protocol connectivity. Reference: WLSD Study Guide — Mobility Group Troubleshooting, mping Command, UDP 16666 Firewall Requirements.

When a data path mobility tunnel fails to come up between WLCs, one of the key troubleshooting steps is to verify whether the necessary ports are open through firewalls in the path. Cisco AireOS mobility tunnels use UDP port 16666 for mobility control traffic and IP Protocol 97 (EtherIP) for mobility data traffic in legacy mode. Establishing a Telnet connection from a local PC to the firewall on port 16666 tests whether the control path port is reachable and not being blocked by the firewall. If the Telnet connection fails, it confirms that the firewall is blocking port 16666, which would prevent the mobility control tunnel from establishing — a prerequisite for the data tunnel. While a Telnet test to port 16666 specifically tests the control path, in practice this is the first verification performed when the data path cannot establish (since the data path depends on the control path being operational). IP Protocol 97 cannot be tested via Telnet (which is TCP). The mping command (Option D, not ' mapping ' ) tests mobility tunnel connectivity from the WLC itself after the tunnel is established. Reference: WLSD Study Guide — Mobility Tunnel Troubleshooting, Firewall Port Requirements, UDP 16666 and IP Protocol 97.

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.

In Cisco mesh networking architecture, access points are classified into two primary roles: Root Access Points (RAP) and Mesh Access Points (MAP). A RAP is an access point that maintains a wired Ethernet backhaul connection back to the network infrastructure, while a MAP operates wirelessly, relying on mesh backlinks to upstream RAPs. When an engineer needs to change an AP mode — such as switching to bridge mode to extend the mesh — the AP role must first be defined correctly. The AP must be designated as a RAP before any mode-level configuration changes are applied. This sequencing is critical because the AP role defines the fundamental backhaul path; changing the mode without first establishing the role results in misconfiguration and potential connectivity loss. The RAP communicates directly with the wired infrastructure via its Ethernet port, making it the gateway for all downstream MAPs in the mesh topology. Options A (monitor), C (bridge), and D (local) refer to AP modes, not roles, and cannot be configured until the role is properly defined. Reference: WLSD Study Guide — Mesh Networking Fundamentals, Outdoor Wireless Design, AP Role and Mode Configuration.

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.

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.