Cisco Updated 350-101 Exam Questions and Answers by lawson

The correct method issoftware image management workflows, specifically Cisco Catalyst Center Software Image Management, commonly referenced as SWIM. Cisco documents SWIM as the mechanism used to manage software upgrades and maintain consistency of image versions across the network. It provides an image repository, golden-image assignment, image distribution, activation, readiness checks, and scheduled execution. Cisco’s wireless automation guidance specifically states that SWIM is used to update Catalyst 9800 Series Wireless Controller software by distributing the image from the Catalyst Center repository to wireless controllers and upgrading the images running on those controllers; both stages can run immediately or be scheduled for a defined maintenance window.

Option C is also validated by Catalyst Center’s update-status and workflow views. Cisco documentsImage Update Statusas the view that shows all update tasks, filters by in-progress, success, or failure, and displays a progress bar for active updates. The workflow view then exposes distribution and activation task status, timing, prechecks, postchecks, checksum verification, and AP pre-image download details. Inventory snapshots and templates do not execute controller firmware upgrades, and “lifecycle workflow” is too generic. Reference topics:Wireless Monitoring and Management — Catalyst Center SWIM, image compliance, golden images, controller upgrade automation, and update progress reporting.

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 withcapwap 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.

‘

For campus wireless monitoring deployments involving Cisco Spaces, ISE, and Catalyst Center appliances, strict separation of management traffic from user data is required to maintain security and service continuity. The correct approach is to configure the switch interfaces connecting these appliances as access ports assigned to the dedicated management VLAN. This ensures that management and telemetry traffic is isolated from production WLAN traffic, preventing any disruption to end users if configuration changes are made. Assigning the management VLAN as the native VLAN on trunk ports (Option B) is inappropriate because the native VLAN still transmits untagged traffic and could allow accidental bridging with user traffic, violating security policies. PortFast (Option A) is used for rapid STP convergence on end-user ports but does not enforce VLAN separation or management isolation. Port Aggregation Protocol (Option C) is intended for link bundling and redundancy, not VLAN segmentation. Cisco Wireless best practices emphasize access port configuration for management appliances in a dedicated VLAN to guarantee security, telemetry reliability, and non-disruptive network operations. Proper implementation involves assigning a unique VLAN ID for all monitoring and management devices and configuring the switch port as an access port, ensuring consistent isolation and predictable behavior in a high-density campus environment. Reference topics:Wireless Monitoring and Management — Cisco Spaces deployment, ISE integration, management VLAN isolation, switch access port configuration.

The correct authentication method isEAP-TLS. WPA2-Enterprise uses 802.1X/EAP authentication rather than a pre-shared key, and the supplicant, authenticator, and RADIUS authentication server participate in the enterprise authentication exchange. Cisco documentation states that in enterprise WPA/WPA2 operation, 802.1X/EAP is used for authentication and provides strong authentication between the client and authentication server.

The decisive requirement in the question iscertificate-based mutual authentication requiring both client and server certificates. Cisco explicitly describes EAP-TLS as requiring both server-side and client-side certificates, while PEAP requires only a server-side certificate and normally authenticates the client with password-based credentials inside the protected tunnel. Cisco Secure ACS documentation also states that EAP-TLS uses the certificates of the authentication server and the end-user client, enforcing mutual authentication.

MSCHAPv2 is a password-based inner authentication method, not certificate-based mutual authentication. PEAP protects credential exchange with a server certificate but does not inherently require a client certificate. TEAP can support flexible tunneled authentication, but the strict client-and-server certificate requirement maps directly toEAP-TLS. Reference topic:Client Connectivity Configuration — WPA2-Enterprise, 802.1X supplicant configuration, EAP methods, certificates, and RADIUS authentication.