Free Cisco 300-110 Practice Exam with Questions & Answers | Set: 2

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.

To focus the coverage heat map on the desired coverage threshold, the engineer should use the RSSI slider to set the heat map to the desired cutoff filter. This action adjusts the display to show only the signal levels that meet or exceed the specified RSSI value, effectively filtering out weaker signals and highlighting areas with sufficient coverage. In Ekahau and similar survey tools, the RSSI slider provides a dynamic way to set minimum signal thresholds, allowing the engineer to quickly validate whether coverage meets design targets such as -67 dBm for voice or -70 dBm for data. Changing the color scheme (Option A) only modifies the visual representation without filtering data. The RSSI calibration tool (Option B) adjusts how the tool perceives signal levels, not the display filter. Filtering by AP (Option D) would remove APs from the view, potentially hiding coverage gaps. Reference: WLSD Study Guide — Post-Deployment Survey, Ekahau Heat Map Tools, RSSI Coverage Filtering.

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.

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.

The eping command is used on Cisco Wireless LAN Controllers to verify that the redundancy peer in a Stateful Switchover (SSO) pair of controllers is up and connected. This command sends ECHO packets (EoIP echo packets) to the peer controller to ensure the data path connectivity is functioning. In an SSO configuration, eping verifies the EoIP tunnel between the active and standby controllers, which is critical for state synchronization and seamless failover. If eping succeeds, it confirms that both the network path and the EoIP data encapsulation between the controllers are functional. The standard ping command (Option B) tests basic IP connectivity but does not validate the EoIP data path used by the SSO redundancy mechanism. The mping command (Option D) tests mobility control path connectivity between mobility group peers, not the SSO redundancy path. The rping command (Option A) is not a standard Cisco WLC command for testing SSO peer connectivity. Reference: WLSD Study Guide — WLC SSO Troubleshooting, eping Command, Redundancy Peer Connectivity Validation.

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.

Raising the minimum data rate to 24 Mbps reduces the effective coverage range of each AP because clients at the cell edge operating at low data rates are effectively excluded from the cell. This shrinks cell size, reducing channel overlap between neighboring APs on the same channel. Using directional antennas limits the coverage area of some APs by focusing RF energy in specific directions rather than radiating omnidirectionally, which directly reduces the lateral overlap between adjacent APs. Increasing AP transmit power (Option B) would worsen overlap, not reduce it. Allowing UNII-2e channels (Option C) provides more channel options but does not reduce the physical cell overlap — it only provides more channels to avoid co-channel interference. Power saving mode (Option E) is a client-side power management feature unrelated to AP cell sizing during a survey. Reference: WLSD Study Guide — Channel Overlap Mitigation, Data Rate Configuration, Directional Antenna Use Cases.

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.

When configuring high availability on a Cisco access point, the AP can be configured with a maximum of three controllers: a primary controller, a secondary controller, and a tertiary controller. This three-tier hierarchy defines the failover order — the AP first attempts to join its primary controller, then the secondary if the primary is unavailable, and finally the tertiary if both the primary and secondary are unreachable. After exhausting all three configured options, the AP enters a discovery process to find any available controller. This three-controller configuration (primary, secondary, tertiary) allows network engineers to implement N+1 redundancy where critical APs can be directed to specific backup controllers in a deliberate sequence. Limiting the configuration to only 2 controllers (as stated in Option B which would be incorrect) would reduce redundancy options for environments with geographically distributed controllers requiring specific failover paths. Reference: WLSD Study Guide — AP High Availability Configuration, Primary/Secondary/Tertiary Controller Assignment, AP Failover Design.

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.