350-101 Exam Preparation Material | Implementing and Operating Cisco Wireless Core Technologies (350-101 WLCOR)v1.0

Explanation:
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.

Explanation:
Device sensitivity in a wireless environment refers to receiver sensitivity: the minimum RF signal level a client or AP radio must receive to successfully detect, demodulate, and decode a transmission. Cisco defines receiver sensitivity as the minimum signal power level, expressed in dBm or mW, required for a receiver to accurately decode a given signal. Cisco RF design guidance further states that sensitivity indicates the lowest received power before the receiver considers the signal unintelligible.
Therefore, option A is correct because sensitivity is fundamentally about the radio’s capability to process a received signal at low power levels. A more sensitive receiver can decode weaker frames, improving effective coverage and receive performance, provided the signal-to-noise ratio and interference conditions remain acceptable. Cisco also notes that individual device sensitivity determines how well a device can hear and demodulate RF energy, which directly affects contention behavior and WLAN performance in dense environments. Redundant gateways, beacon interval synchronization, and key refresh schedules are Layer 3 availability, 802.11 timing, and security-key management topics; they do not define RF receiver sensitivity.
Reference topics: RF Fundamentals ― receiver sensitivity, RSSI, dBm, SNR, demodulation, and WLAN coverage behavior.

Explanation:
FRA (Flexible Radio Assignment) is a feature in Cisco wireless networks designed to optimize the client experience and enhance network coverage. FRA functions by managing roaming behavior and ensuring that clients are connected to the most appropriate access point (AP) based on signal quality and other factors. This helps in ensuring a seamless experience when clients move across coverage areas, by actively guiding them to the best AP.
The key functionality of FRA involves redirecting clients to the appropriate AP when they are experiencing suboptimal performance on the current AP, which is typically influenced by factors such as interference or distance. This optimization helps improve both coverage and user experience by making sure clients stay on the most optimal radio connection.
Option A, which refers to monitoring on the physical interface level, is not directly related to FRA but more to basic radio management.
Option C, which mentions local data path control, refers to how data paths are managed locally within an AP but does not address the dynamic nature of client roaming.
Option D, about dual-band radios, involves how radios are configured but does not directly describe FRA's function.
FRA is vital for dynamically enhancing wireless network performance, particularly in large, dense environments where clients are constantly moving.

Explanation:
The correct configuration is aaa-override followed by nac under the existing Catalyst 9800 wireless policy profile. The exhibit already places the administrator in policy-profile configuration mode with wireless profile policy my-policy, so the missing commands must be policy-profile subcommands, not another profile declaration. Cisco’s Catalyst 9800 configuration examples show the exact sequence: enter wireless profile policy <policy-profile-name>, enable aaa-override, enable nac, then configure VLAN and no shutdown.
aaa-override permits authorization attributes returned by AAA or Cisco ISE, such as VLAN, ACL, QoS, redirect ACL, or posture-related access controls, to override the locally defined policy. Cisco’s documentation explicitly states that AAA override applies policies coming from AAA or ISE servers, while nac enables Network Access Control in the policy profile. This is the required behavior when endpoints must be posture-validated before normal network access is granted. Cisco also notes that NAC State is enabled in the policy profile and can only be enabled when AAA override is enabled.
Option A is invalid because nac-policy is not the correct CLI keyword.
Options B and D omit NAC.
Reference topic: Client Connectivity Configuration ― Catalyst 9800 policy profiles, AAA override, NAC State, posture enforcement, and ISE-based access control.

Explanation:
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.