300-110 Exam Dumps - Designing Cisco Wireless Networks (300-110 WLSD) v1.2

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.

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 design requirements specify a multi-LAG configuration where each LAG connects to a single switch, different VLANs are assigned to different LAGs, the controller must dynamically learn partner LAG capabilities per port, and standby ports provide redundancy upon active port failure. These requirements collectively point to IEEE 802.3ad LACP (Link Aggregation Control Protocol) as the correct protocol. LACP is the industry-standard IEEE protocol that enables dynamic negotiation of LAG membership between endpoints — the WLC and each Catalyst 9300 switch exchange LACP PDUs (LACPDUs) to discover port capabilities, negotiate bundle membership, and monitor link status. LACP supports active and passive port states where active ports initiate negotiation and passive ports respond, and it provides the standby port mechanism through its hot-standby capability for link redundancy within the bundle. The requirement to ' learn the identity of partners that can support LAG capabilities ' is the defining characteristic of LACP ' s standardized PDU exchange mechanism. PAgP (Option C) is a Cisco proprietary port aggregation protocol that, while functionally similar, is not the IEEE standard and is incompatible with non-Cisco equipment in mixed environments. OSPF (Option B) and BGP (Option D) are Layer 3 routing protocols entirely unrelated to port channel negotiation. Reference: WLSD Study Guide — Catalyst 9800 LAG Configuration, LACP IEEE 802.3ad, Multi-LAG High Availability Design.

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.

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.

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.

In Cisco ' s guest anchor WLC deployment model, multiple anchor controllers can be configured in a DMZ to provide redundancy for guest WLAN traffic. The anchor priority value determines which anchor controller is preferred for establishing the guest mobility tunnel from the foreign WLC. Cisco ' s anchor priority system assigns the highest preference to the lowest numerical priority value. Priority 1 is the highest priority, meaning the foreign WLC will prefer Anchor1 when establishing the CAPWAP mobility tunnel for anchoring guest client traffic. Priority 2 would be assigned to Anchor2, and Priority 3 to Anchor3, creating a deterministic failover hierarchy. If Anchor1 becomes unreachable, the foreign controller automatically falls over to Anchor2, then to Anchor3. Priority 0 is not a valid anchor priority value in the Cisco WLC configuration. This design pattern is critical for enterprise guest deployments where DMZ anchor redundancy must be maintained without manual intervention. Reference: WLSD Study Guide — Guest Wireless Architecture, Anchor WLC Configuration, Mobility and DMZ Design.

Link Aggregation Group (LAG) is the correct design approach for a single Cisco 9800-40 WLC that requires high availability between the WLC and the core switch in the event of a cable failure. LAG combines multiple physical ports on the WLC into a single logical channel, providing both redundancy (traffic automatically redistributes across remaining links when one fails) and load balancing (traffic is distributed across all active links). Importantly, LAG operates transparently to AP management — APs see a single logical uplink regardless of which physical port their traffic traverses. With a single WLC, Multi-LAG (Option B) is not applicable — Multi-LAG is a feature of the Catalyst 9800 that allows multiple separate LAG bundles for different network connections, typically used with SSO pairs. LACP (Option C) is the protocol used to negotiate LAG member links — it is the mechanism within LAG, not an independent design approach. PAgP (Option D) is a Cisco proprietary alternative to LACP for port aggregation but the question asks for the design approach, which is LAG. Reference: WLSD Study Guide — Catalyst 9800 LAG Design, Port Redundancy and Load Balancing, Single-Controller High Availability.