Cisco 350-101 Practice Exam Questions & Answers

The correct answer is reduction of co-channel interference. AI-RRM in Cisco Catalyst Center is designed for RF optimization, not IP addressing, software scheduling, or user identity classification. Cisco describes AI-enhanced RRM as applying artificial intelligence and machine learning to optimize RF environments and automate/adapt RF parameter tuning for Cisco wireless networks. This is directly tied to operational RF outcomes such as improved channel planning, transmit power behavior, channel width decisions, and better spectrum utilization.

Co-channel interference occurs when multiple AP radios operate on the same channel within hearing range, forcing devices to share airtime and increasing contention. AI-RRM uses telemetry, analytics, and learned RF behavior to recommend or apply more optimal RF configurations. Cisco specifically states that AI-enhanced RRM optimization can produce improvements such as up to a 40 percent reduction in co-channel interference and SNR gains for wireless clients. Cisco's AI-RRM deployment guidance also identifies AP radio distribution and utilization analysis as critical for minimizing co-channel interference and optimizing wireless performance.

Therefore, option B is the only operational outcome aligned with AI-RRM's purpose. Reference topic: Automation and AI --- Cisco Catalyst Center AI-RRM, RF analytics, RRM automation, channel optimization, and wireless AIOps.

Migrating a Cisco Catalyst AP to Meraki cloud management requires issuing a specific CLI command on the WLC to switch the AP's management mode. The correct syntax is ap management mode meraki force noprompt, which instructs the controller to transition the AP to Meraki mode, bypassing validation prompts that normally require manual confirmation. The force keyword ensures the command is executed even if the AP is actively associated or configured, and noprompt suppresses confirmation dialogues for unattended migration. Options A, C, and D are invalid syntax or improperly order the parameters, which would result in a CLI error. Cisco Wireless Core Technologies recommend this approach during enterprise migration scenarios where multiple APs are moved from Catalyst WLC management to cloud-based Meraki management, enabling centralized configuration and monitoring in a large-scale deployment. Using this command ensures a seamless transition without service disruption, while maintaining inventory consistency and supporting automation for mass AP migrations. Reference topics: Wireless Network Implementation --- AP management mode migration, Meraki cloud integration, CLI AP management, Catalyst 9176 WLC migration.

When deploying a Lightweight Access Point (LWAPP) in a Cisco wireless network, proper Layer 3 configuration is essential for management and connectivity to the Wireless LAN Controller (WLC). Each LWAPP requires a valid IP address, subnet mask, and default gateway to communicate beyond its local subnet. In the exhibit, the AP is assigned 172.16.100.104/24, but the previously configured gateway was incorrect, preventing communication with the WLC. Cisco IOS XE requires that the AP's IP interface be configured with the correct default gateway to route traffic properly. The correct syntax is capwap ap ip <AP-IP> <Subnet-Mask> <Default-Gateway>. Option D matches the IP, subnet mask, and gateway for the given network, ensuring the AP can reach the WLC for LWAPP registration. Option A only changes the gateway without setting the IP explicitly, which is insufficient if the IP needs adjustment. Option B incorrectly configures the controller's IP, which does not affect the AP's default gateway. Option C uses an incorrect subnet mask (255.255.255.192), which would place the AP in a different subnet, breaking connectivity. Proper default gateway configuration is critical to avoid registration failures and management issues. Reference topics: Client Connectivity Configuration --- LWAPP AP IP configuration, default gateway, WLC communication, Layer 3 reachability.

IEEE 802.11ax, also known as Wi-Fi 6, introduces several advancements to improve network performance, particularly in dense environments. Among these, OFDMA (Orthogonal Frequency Division Multiple Access) is a key feature introduced by 802.11ax. OFDMA allows more efficient use of the available spectrum by enabling multiple users to share the same channel simultaneously. This is done by subdividing the channel into smaller sub-channels, allowing data to be transmitted to multiple devices at the same time, improving overall throughput and reducing latency.

Option A: 60 GHz utilization refers to Wi-Fi standards like 802.11ad and 802.11ay, which use the 60 GHz band, but 802.11ax focuses on improving efficiency in the 2.4 GHz and 5 GHz bands, not the 60 GHz band.

Option B: Wi-Fi multimedia is related to Wi-Fi features that prioritize multimedia traffic, but it is not a new attribute specifically introduced by 802.11ax.

Option D: MIMO (Multiple Input, Multiple Output) is a technology that allows multiple antennas to be used at both the transmitter and receiver, and while MIMO is supported in 802.11ac, it was enhanced in 802.11ax with MU-MIMO (Multi-User MIMO) for uplink, not a new technology introduced by 802.11ax.

Therefore, OFDMA (Option C) is the correct answer, as it is a key feature that 802.11ax introduces to improve network efficiency and capacity.

WPA2 Personal (PSK) authentication relies on a shared secret (preshared key) configured on both the wireless LAN controller (WLC) and the client device. In the exhibit, the WLAN is configured with WPA2 and PSK (set-key ascii MyKey123), which means the network expects clients to use the same preshared key to authenticate. To enable client connectivity, the preshared key must be manually entered on each client device; this aligns the client and WLC authentication parameters. Options B, C, and D are unrelated to WPA2 Personal: MAC filtering is a security policy mechanism, Active Directory integration supports WPA2 Enterprise with 802.1X authentication, and client certificates are used for certificate-based EAP methods, not PSK. Cisco Wireless Core Technologies emphasize that PSK deployments require consistent key configuration across the WLAN and clients, and that the preshared key is the critical element for successful authentication. This ensures secure, encrypted communication while providing simple setup for small or branch deployments without an enterprise RADIUS infrastructure. Reference topics: Client Connectivity Configuration --- WPA2 Personal, preshared key authentication, WLAN configuration, branch deployment WLAN security.

When deploying Meraki APs, it is essential to claim each AP in the Meraki dashboard to ensure that they are automatically assigned to the correct network and can be managed remotely. This process involves registering the APs with the Meraki cloud, which is done by adding the AP serial numbers to the network within the Meraki dashboard before physically installing them at the branch.

Option B: 'Add the AP serial numbers to the required network within the Meraki dashboard.'

This is the correct answer. Before the APs are physically connected, the administrator needs to log into the Meraki dashboard and add the serial numbers of the new APs to the intended network. This ensures that once the APs are powered on and connected, they automatically join the correct network and are ready for monitoring and management without requiring further configuration.

Option A: 'Activate mesh networking mode for all the new APs before installation.'

Mesh networking mode is used when APs need to communicate wirelessly to extend coverage, but it is not a requirement for the deployment and registration process. The APs should be connected normally for initial setup, and mesh mode can be enabled later if needed.

Option C: 'Preconfigure SSID names and VLAN tags on the local page of each AP in the Meraki dashboard.'

While configuring SSID and VLAN settings is essential, this is not the first action required for ensuring the APs are claimed by the correct network. The priority is to add the AP serial numbers to the Meraki dashboard for proper network assignment.

Option D: 'Create a separate DHCP scope for all the new APs on the local server.'

DHCP scope configuration is important for assigning IP addresses, but this is not the primary step for ensuring the APs are correctly registered in the Meraki dashboard. The APs can obtain IP addresses from an existing DHCP scope once they are connected and claimed in the dashboard.

Therefore, the best approach is Option B, as it ensures that the APs are correctly assigned to the intended network in the Meraki cloud, ready for management and monitoring once connected.

The missing command is radius server external-radius. On a Catalyst 9800 WLC, the external RADIUS server object must be declared first with radius server <server-name>. The following lines, address ipv4 10.10.10.100 auth-port 1812 acct-port 1813 and key radiuskey, are subcommands entered under that RADIUS server configuration mode. Cisco's Catalyst 9800 802.1X configuration workflow starts by declaring the RADIUS server, then adding it to a RADIUS server group, then creating the authentication method list, and finally mapping that list to the WLAN. Cisco's configuration guide example uses the same IOS XE structure: radius server <name>, followed by address ipv4 ... auth-port 1812 acct-port 1813 and key ....

The server group later references server name external-radius, so the RADIUS server object must be named external-radius exactly. Option C would incorrectly create a server named RADIUS-GRP, which is already the AAA server group name, not the RADIUS server object. Options B and D are invalid IOS XE syntax. PEAP-MSCHAPv2 itself is handled through the 802.1X/EAP exchange with the RADIUS server; the WLC acts as the authenticator and forwards authentication requests through the configured AAA method list. Reference topic: Client Connectivity Configuration --- WPA2-Enterprise, 802.1X, RADIUS server objects, AAA groups, and WLAN authentication-list binding.