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

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.

An active ping survey is used to validate network performance by sending and receiving data packets to measure end-to-end network performance, including latency, packet loss, and throughput. Ekahau site survey tools can perform active ping surveys to test the connectivity and performance of the wireless network while the surveyor walks the floor plan, producing a geographically correlated map of network performance metrics. This differs fundamentally from passive surveys, which only measure signal strength from beacons. A GPS-assisted survey (Option A) is used for large outdoor areas to automate location tracking. Spectrum analysis (Option B) identifies Layer 1 RF conditions but does not measure network performance. A passive survey (Option C) measures RSSI and SNR but does not test actual data connectivity or throughput. Active ping is the correct tool for validating that the network delivers the expected end-to-end service levels. Reference: WLSD Study Guide — Ekahau Survey Types, Active Survey Methodology, Post-Deployment Validation.

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.

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.

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.

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.

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.

In Cisco ' s AP controller preference hierarchy, each AP can be configured with a primary, secondary, and tertiary controller designation. The AP will attempt to join controllers in this exact order: primary first, secondary second, and tertiary third. When no controllers from the preference list are available, the AP may fall back to any reachable controller through standard CAPWAP discovery. In this hospital deployment, the service/development controller must be the controller of last resort — it should only receive AP associations when all other options are exhausted. Configuring the service/dev controller as the tertiary controller in the APs ' preference configuration ensures exactly this behavior: APs will attempt the SSO pair (primary) first, then the third production WLC joined via mobility tunnel (secondary), and only then the service/dev controller (tertiary). This prevents development traffic from disrupting production service, and ensures production APs do not inadvertently join the service environment during partial outages. Configuring it as primary (Option A) or secondary (Option C) would allow APs to join the service controller before exhausting production options. AP failover priority (Option D) governs which APs are processed during controller recovery, not the controller preference order during join. Reference: WLSD Study Guide — AP Controller Preference Configuration, Primary/Secondary/Tertiary WLC Assignment, Hospital WLAN High Availability Design.

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.

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.

Metal doors cause the most signal attenuation among common building materials due to the fundamental electromagnetic properties of metal. Metal is highly reflective and absorptive of radio frequency signals — it creates what is effectively a Faraday cage effect around any room or space it encloses. In wireless design attenuation modeling tools such as Ekahau, metal is assigned the highest attenuation value among standard building materials, typically 30+ dB per surface. Cinder block walls (Option A) are dense and provide significant attenuation (10-15 dB) but are not as RF-impenetrable as solid metal. Glass walls (Option C) and office windows (Option D) have relatively low attenuation values (2-4 dB) due to the minimal RF-absorbing properties of glass. When engineers model attenuation materials in predictive survey tools, metal doors and metal-containing structures consistently produce the highest per-surface attenuation values, making them the primary barrier obstacles to plan around. Reference: WLSD Study Guide — RF Signal Attenuation, Building Material Attenuation Values, Predictive Survey Material Modeling.

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.

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 Ekahau Site Survey, passive mode involves listening to beacon frames and probe responses from deployed APs without the survey laptop actively associating to any SSID. This is significantly faster than active mode because no association, DHCP, or throughput test overhead is introduced — the surveyor simply walks the floor while Ekahau passively captures signal strength data from all visible APs simultaneously. Using two wireless adapters in passive mode provides a critical speed advantage: one adapter scans 2.4 GHz channels while the second adapter simultaneously scans 5 GHz channels. Without dual adapters, a single adapter must time-multiplex between bands, reducing the sample rate per band and either slowing the survey walk or producing sparser data. Active mode (Options B and C) is used when throughput measurements are required for specific application validation such as voice or video, but it is inherently slower due to association overhead and sequential testing. The combination of passive scanning and dual adapter configuration delivers the highest possible data collection rate per unit of walk time. Reference: WLSD Study Guide — Ekahau Site Survey Modes, Passive vs. Active Survey Methodology, Multi-Adapter Survey Configuration.

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.

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.

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.

The issue described indicates that there are more critical priority access points than the backup Cisco WLC can accommodate with its available AP licenses. The backup WLC has only 10 licenses available, but 7 APs are set to critical failover priority and 5 to high failover priority — a total of 12 APs attempting to join. Even though critical priority APs are processed before high priority APs, the backup WLC can only accept 10 APs total (its license limit). Since there are 7 critical priority APs and only 10 total licenses, all 7 critical APs will fail over successfully — but if the scenario involves additional critical APs beyond the license limit, the excess will not be able to join. The oversubscription of the critical priority AP count relative to available backup WLC capacity is the root cause. AP failover priority being disabled (Option D) would mean all APs have equal priority, not that critical APs fail to join. ' network ap-priority set to enable ' (Option B) enables the priority processing globally, which would be required for the feature to work at all. Reference: WLSD Study Guide — AP Failover Priority, N+1 Redundancy License Planning, WLC License Capacity Management.

To optimize roaming in a wireless network with multiple controllers, it is essential to use the same WLAN name (SSID) across all controllers. When SSIDs differ between controllers, clients perceive them as different networks and must perform a full re-association and re-authentication when roaming between APs managed by different controllers. This causes a roaming disruption equivalent to connecting to an entirely new network. By using identical SSID names on both controllers, clients can seamlessly roam between APs on different controllers within the same mobility group — the controllers exchange client state information via the mobility tunnel, enabling seamless handoff. In the scenario described, ' Copr-NET390595865WLC-1 ' and ' Copr-NET6837l638WLC-2 ' are different SSIDs, meaning clients cannot roam transparently between them. Making both controllers broadcast the same SSID name (and using a mobility group to connect the controllers) resolves this. Reference: WLSD Study Guide — SSID Consistency Across Controllers, Inter-Controller Roaming, Mobility Group Configuration.

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 a significantly greater number of 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. 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.

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.

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.

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.

In a mixed deployment where a Cisco Catalyst 9800 IOS XE WLC operating in SSO is required to establish a mobility peer relationship with a legacy AireOS WLC, the critical configuration requirement is that the 9800 SSO pair presents a single, consistent mobility MAC address to all peer WLCs. When the 9800 is in SSO mode, the active and standby controllers function as a single logical entity, but AireOS WLCs identify mobility peers by MAC address. If the MAC address changes during an SSO switchover, the AireOS peer will detect the change and tear down the mobility tunnel, disrupting inter-controller client roaming. The command ' wireless mobility mac-address < MAC > ' configures a static, persistent mobility MAC address on the 9800 SSO pair that remains constant regardless of which physical unit is active. This ensures the AireOS WLC always identifies the 9800 pair by the same MAC address, maintaining the mobility tunnel and enabling seamless client roaming. Option A configures the HA interface for SSO synchronization but not for AireOS mobility interoperability. Option B sets a default gateway. Option D enables management gateway failover, unrelated to mobility peer identification. Reference: WLSD Study Guide — IOS XE WLC SSO Configuration, AireOS to 9800 Migration, Mobility Peer MAC Address Management.

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.

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.

Cisco Application Visibility and Control (AVC) is a deep packet inspection and traffic classification framework integrated into the Cisco WLC and AP platform. AVC performs real-time analysis of wireless client traffic, classifying applications based on Layer 4-7 signatures using the NBAR2 (Network Based Application Recognition) engine. This provides the network administrator with granular visibility into exactly which applications are consuming bandwidth — enabling data-driven decisions about network congestion remediation, link utilization management, and infrastructure investment planning. For example, AVC can reveal that a video streaming application is consuming 60% of available wireless bandwidth during peak hours, informing the decision to implement QoS rate limiting for that application class or upgrade the backhaul infrastructure. AVC also supports control functions through per-application QoS policies, rate limiting, and traffic shaping — directly addressing congestion reduction. Band selection (Option A) steers dual-band clients to 5 GHz but provides no application-level analysis. QoS (Option B) implements traffic prioritization but requires prior application identification — it does not perform the analysis itself. 802.11r (Option D) is a fast roaming protocol with no relevance to traffic analysis or congestion management. Reference: WLSD Study Guide — Application Visibility and Control, NBAR2 Integration, Wireless Traffic Analysis and Management.

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.