Cisco 350-101 Exam Dumps

Optimized roaming is a Cisco WLC feature designed to reduce sticky-client behavior. A sticky client remains associated to an AP even after moving far enough away that another AP would provide better RF service. Cisco describes optimized roaming as actively monitoring client data RSSI and disconnecting clients when received signal strength falls below the configured threshold. The official Catalyst 9800 documentation states that optimized roaming ''disassociates client when the RSSI is lower than the set threshold,'' which directly matches option A.

This function does not calculate device location through peer-to-peer beaconing, does not depend on external experience services, and is not static load balancing. It is an RF/client-roaming enforcement mechanism controlled by the wireless infrastructure. In practical operation, the AP/WLC evaluates client signal quality and, when the configured optimized roaming criteria are met, forces the client to disconnect so it can reassess the RF environment and roam to a better AP. Cisco also notes that optimized roaming helps maintain client connectivity by managing disassociationn based on RSSI and data-rate thresholds. Reference topics: Client Connectivity Configuration --- client roaming behavior, sticky-client mitigation, RSSI thresholds, and WLC roaming optimization

Bridge mode in a Cisco wireless mesh deployment allows access points to operate as mesh infrastructure nodes, typically as a Root AP (RAP) or Mesh AP (MAP), so Ethernet segments can be connected across a wireless backhaul. Cisco's mesh design documentation states that in a point-to-point bridging scenario, a mesh AP can extend a remote network by using the backhaul radio ''to bridge two segments of a switched network.'' This directly maps to option A: point-to-point communication between network segments.

In Catalyst 9800 mesh deployments, Cisco documents converting an AP to bridge mode with capwap ap mode bridge, after which the AP rejoins the controller in bridge mode and can be assigned a mesh role. Cisco also defines the RAP as the AP with the wired connection toward the WLC, while the MAP joins through its radio path toward the RAP. Option B is incorrect because bridge mode does not force all traffic to 2.4 GHz; Cisco mesh backhaul can use configured backhaul radios. Option C describes RRM/TPC behavior, not bridge mode. Option D incorrectly associates mesh bridge mode with WAN edge functions. Reference topics: Wireless Network Implementation --- mesh AP roles, RAP/MAP operation, wireless backhaul, and Ethernet bridging.

'

SNMP monitoring provides centralized visibility and event notification for Cisco wireless infrastructure. On Cisco Catalyst 9800 wireless controllers, SNMP traps are used to send alert messages from SNMP-enabled devices to an SNMP manager, and Cisco specifically documents wireless trap support for access points, clients, mesh, RF, rogue, mobility, RRM, and controller events. Cisco also states that AP-related traps such as crash, register, and no-radio-card events are enabled by default, and that configuring AP traps helps monitor AP status and troubleshoot issues.

Therefore, the direct operational benefit is alerts on access point status. SNMP is not limited to hardware-only metrics; it can expose client counts, joined AP counts, processor usage, memory usage, and wireless event notifications through supported OIDs and traps. Manual log review is the opposite of SNMP's purpose because traps automate notification to a network management system. Fragmented statistics are also incorrect because SNMP enables centralized polling and trap collection across managed devices. Reference topics: Wireless Monitoring and Management --- SNMP, MIB/OID monitoring, Catalyst 9800 wireless traps, AP status monitoring, and NMS integration.

For Cisco Catalyst 9176 APs deployed at remote sites without DHCP option 43, automatic WLC discovery can be accomplished using DNS-based CAPWAP controller discovery. By creating a DNS A record named cisco-capwap-controller.<domain> that resolves to the WLC management IP address, APs can query DNS and locate their centralized controller automatically, eliminating the need for site visits or manual configuration. This method is preferred for large-scale or satellite deployments where APs may exist on different subnets and traditional DHCP-based discovery is unavailable. Option A is impractical because manually assigning static IPs to hundreds of APs is operationally complex and error-prone. Option B, using a multicast group, is not supported for cross-subnet controller discovery in CAPWAP; multicast is limited to local subnets. Option D (ap-discovery) is not a recognized standard for WLC discovery; Cisco specifically documents cisco-capwap-controller as the required DNS entry for CAPWAP-based automatic discovery. This approach ensures zero-touch provisioning, simplifies network operations, and guarantees that APs join the correct controller, supporting centralized management and consistent configuration across multiple campuses. Reference topics: Wireless Network Implementation --- CAPWAP discovery, DNS-based controller discovery, Catalyst 9800 WLC onboarding, zero-touch provisioning.