YANG is a vendor-neutral, human-readable data modeling language that defines the structure of configuration and operational data manipulated by NETCONF on Cisco wireless controllers and other devices.

B. NETCONF uses SSH for security; YANG is not a security protocol.

C. NETCONF always operates on data models such as YANG; it does not transport raw, model-less data.

D. YANG is an IETF standard (RFC 6020/7950), not a Cisco-proprietary scripting language.

1. RFC 6020: YANG—A Data Modeling Language for the NETCONF Protocol, sec. 1.

2. Cisco IOS XE Programmability Configuration Guide, Rel 17.3, “NETCONF/RESTCONF and YANG,” pp. 1-3.

3. MIT 6.829 Computer Networks lecture notes, Spring 2022, “NETCONF and Model-Driven Telemetry,” slide 7 (defines YANG).

In Cisco wireless mesh, Bridge mode turns a Mesh Access Point into a layer-2 bridge, extending an Ethernet segment over the wireless backhaul. This provides transparent point-to-point or point-to-multipoint connectivity between network segments that are separated physically.

B. Radio band selection is unrelated; bridge mode does not default traffic to 2.4 GHz.

C. RF transmit-power control (TPC) is part of RRM, not a bridge-mode function.

D. Communicating with the WAN edge is routing, whereas bridge mode operates purely at Layer 2.

1. Cisco “Indoor and Outdoor Mesh Access Point Deployment Guide,” Rev 3, p.12-13, section “Bridge Mode.”

2. Cisco Aironet APs Command Reference, IOS 15.3(3)JA, “bridge-group” description.

Peer-to-Peer (P2P) blocking in the policy profile prevents frames from one wireless client being forwarded to another on the same SSID, achieving guest isolation. Mapping VisitorAccess to VLAN 30 meets the dedicated-guest-VLAN requirement and scales automatically across all APs controlled by the 9800.

B – Local authentication does not isolate guests from each other.

C – FlexConnect/local switching not necessary; central switching already scales and isolation still required.

D – Multicast/RADIUS settings do not stop client-to-client traffic.

1. Cisco Catalyst 9800 Series Configuration Guide, “Configure Peer-to-Peer Blocking,” p. 75 (IOS XE 17.9).

2. Cisco Guest Access Design Guide, 2022, Sec. “Guest User Isolation with P2P Blocking,” para. 2.

In Catalyst 9800 telemetry configuration, the receiver statement is entered inside the Spaces profile with the syntax “receiver ip address protocol tls-native profile ”. This line specifies the destination IP, port 57555, use of the native TLS transport, and binds it to the previously created Spaces profile, thereby enabling encrypted export of location telemetry.

A. Puts keywords in the wrong order and omits the port number.

B. Places “protocol” before the IP/port, which is syntactically invalid.

D. Attempts to start with ‘profile … receiver’, an unsupported command structure.

1. Cisco Catalyst 9800 Series Config Guide, 17.9, “Cisco Spaces Connector”, Example 5 – receiver ip address 198.51.100.10 57555 protocol tls-native profile spaces-profile.

2. Cisco IOS XE “telemetry ietf” Command Reference, rev 2023-07, receiver syntax definition, p. 14.

Cisco Catalyst Center’s Software Image Management (SWIM) workflow lets administrators define golden images, stage and schedule controller upgrades across redundant pairs, and provides real-time compliance and progress reporting—automating the entire structured firmware update cycle while minimizing operational effort.

A. Inventory snapshots only report current hardware; they neither stage nor orchestrate image updates.

B. Software templates configure device settings, not firmware images or upgrade sequencing.

D. “Lifecycle workflow” is a Prime Infrastructure term; Catalyst Center uses SWIM for image life-cycle tasks.

1. Cisco Catalyst Center 2.3.5 User Guide, Chapter “Manage Software Images (SWIM),” Sections “Create Upgrade Workflow” & “Monitor Image Deployment.”

2. Cisco, “Automating Software Image Management with Cisco DNA Center,” White Paper C11-744143-02, pp. 2-4.

3. Cisco Live Session BRKNET-3011, “Operationalizing Controller Upgrades with DNA Center,” slides 18-23, 2022.

Mobility anchoring requires that the same WLAN (SSID, WLAN-ID, security type, PSK, and policy) exist on both the foreign and the anchor WLC. If the anchor lacks a matching WLAN, the mobility tunnel creation fails and the client association is rejected, which is what the Radioactive Trace is reporting. Creating the identical WLAN on the anchor resolves the issue.

A. 802.11r only affects fast-roam hand-shakes; it does not stop the initial association of all clients.

B. PSK mismatch is checked at the foreign WLC/AP, independent of anchoring; the trace points to mobility failure, not bad keys.

C. Removing the anchor breaks the required DMZ design goal rather than fixing the authentication failure.

1. Cisco Wireless LAN Controller Config Guide, Rel 8.10, “Configuring Mobility Anchors”, section “WLAN Requirements” – “The same WLAN ID, SSID and security parameters must be configured on both foreign and anchor, or clients cannot associate.”

2. Cisco Live BRKEWN-2033, 2022, slide 36 “Client fails when anchor WLAN absent/mismatched – seen in RA trace as WLAN-ID mismatch.”

3. Cisco TAC Case Collection, Doc ID 116419, “Association denied when anchor lacks matching WLAN”, para 3.

Wi-Fi antenna gain is expressed in dBi—decibels referenced to an ideal isotropic radiator. The dB measurement quantifies how much stronger the antenna’s peak radiation is compared with this isotropic reference, providing a standardized way to compare antenna performance.

A. Physical length alone does not measure gain; only correlates for certain designs.

C. dBm measures power, not antenna gain; voltage comparison is irrelevant.

D. “Blend of analog and digital signals” is unrelated to gain measurement.

1. Cisco White Paper “Antenna Basics and Radio Fundamentals”, 2014, p.4-5: definition of dBi for antenna gain – cisco.com

2. Cisco CCNA Wireless (WIFUND) Official Cert Guide, ISBN 978-1-58714-467-7, Ch. 9 “Antenna Concepts”, pp. 236-237: dBi as standard gain metric.

TACACS+ centralizes administrator authentication and authorization so the same credentials and role definitions apply consistently across routers, switches, firewalls, and other Cisco platforms, greatly simplifying and unifying device access management.

A. TACACS+ supports granular role-based authorization, not static undifferentiated groups.

B. TACACS+ consolidates—rather than fragments—access statistics and logs.

D. TACACS+ separates network-user (AAA services) from device-admin authentication, not merges them into one user.

1. Cisco IOS Security Configuration Guide, “Configuring TACACS+ for Device Administration”, section “Benefits”, bullet 1 “Provides centralized, consistent administrator access across multiple devices.”

2. RFC 8907 – TACACS+ Protocol, §1.3, “centralized AAA for network devices allows uniform admin experience”.

AI Enhanced RRM extends classic Radio Resource Management by exporting telemetry from Catalyst 9800 controllers to Cisco AI Cloud Analytics. Machine-learning models analyze historical and real-time RF data, predict environmental changes, and push optimized channel, power, and threshold settings back to the controller. This closed-loop, cloud-driven approach proactively maximizes performance and mitigates interference—capabilities unavailable with static thresholds or on-box algorithms alone.

A. Classic RRM uses reactive thresholds; AI-Enhanced adds cloud ML and is not static.

B. Optimization balances coverage and interference; it does not simply raise transmit power.

C. Feature retains dynamic channel/power control; it is not disabled for fixed settings.

1. Cisco Technical Brief “AI Enhanced RRM on Catalyst 9800,” v1.2, Dec 2022, p. 3 “Machine Learning & Cloud Analytics Workflow.”

2. Cisco Live Session BRKEWN-2011, 2023, slide 18 “AI-Enhanced RRM Architecture—Predictive Optimization.”

3. Cisco Catalyst 9800 Configuration Guide, 17.10, “Enabling AI-Enhanced RRM,” overview section.

Optimized Roaming forces clients to roam sooner by monitoring their RSSI. When a client’s RSSI drops below the configured threshold (or packet loss exceeds a set value), the AP immediately sends a disassociation frame, compelling the client to search for a stronger AP and improving overall WLAN performance.

B – Feature is local to WLC/AP, no external integration required.

C – Uses RSSI/packet loss, not peer-to-peer beacons, for location.

D – No static load balancing; clients make dynamic roam decisions.

1. Cisco Optimized Roaming Deployment Guide, v1.2, p. 3 “AP disassociates clients below RSSI threshold.”

2. Cisco Catalyst 9800 Series Configuration Guide, “Configure Optimized Roaming,” Sec. “client-disconnect-threshold,” IOS XE 17.9.