Cisco lightweight and Catalyst access points use CAPWAP for AP-to-controller discovery and join operations. For AP-side preconfiguration, Cisco documents the syntax as capwap ap {primary-base | secondary-base | tertiary-base} controller-name controller-ip-address, specifically for configuring primary, secondary, and tertiary controllers on the AP. This matches option B exactly because it includes the CAPWAP AP command, the controller priority keyword, the controller name, and the controller management IP address. (Cisco) The Catalyst 9800 AP join process also recognizes these configured controller entries in priority order:
primary controller using capwap ap primary-base, secondary controller using capwap ap secondary-base, and tertiary controller using capwap ap tertiary-base. (Cisco) This allows the AP to attempt a backup controller when the preferred controller is unavailable, which is appropriate for remote sites with intermittent WAN reachability. Option A uses obsolete or invalid setcontroller syntax. Option C invents an ap join command format. Option D incorrectly inserts wlc into the AP CAPWAP command. Reference topics:Wireless Network Implementation -CAPWAP discovery, AP join process, Catalyst 9800 controller redundancy, and AP CLI provisioning.

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

The fault domain is DHCP forwarding, not RF, client-side addressing, or AP discovery. Cisco explains that when a wireless client associates, it sends a DHCP Discover broadcast, and depending on AP mode, that traffic is either forwarded through the WLC or passed to the next hop. Cisco further states that if no DHCP server exists in the client's local Layer 2 domain, the router or SVI for the client VLAN must forward DHCP discovery traffic using an IP helper address.
Because the APs are inLocal mode, client traffic is centrally switched through CAPWAP to the WLC, where the client VLAN/SVI path must correctly relay DHCP toward the DHCP server. Cisco's Catalyst 9800 DHCP configuration guide shows DHCP relay configuration under the client VLAN SVI by entering the IPv4 helper address, and the CLI example usesip helper-address < ip-address > to forward UDP broadcasts such as DHCP requests.
Option C resolves the issue because all clients are affected and none receive a DHCP offer, indicating the DHCP Discover is not reaching the DHCP server or the offer is not returning through the relay path. DHCP option 43 is for AP controller discovery, not client DHCP addressing. Reference topics:DHCP relay, Local mode AP forwarding, Catalyst 9800 client VLANs, and wireless client IP assignment.

In a Cisco wireless fabric architecture, fabric edge nodes are responsible for terminating user data traffic at the network edge. These nodes act as the first point of contact for client devices, handling tasks such as encryption
/decryption, VLAN tagging, Quality of Service (QoS) enforcement, and traffic forwarding to the appropriate destination within the fabric. The design centralizes control-plane functions in fabric control nodes, while edge nodes focus on data-plane operations to reduce latency and optimize network performance. Option A, authenticating TLS connections for management, is handled by management or control-plane components rather than edge nodes. Option B, enabling multicast snooping, is a network switch function but not a core responsibility of fabric edge nodes. Option D, converting Layer 2 to Layer 3 addresses, is part of routing functions and not a dedicated role of the wireless fabric edge node in client data processing. Cisco Wireless Core Technologies emphasize that by terminating user data at the edge, fabric edge nodes enable efficient traffic handling, secure processing, and scalable wireless deployment, which is critical in high-density enterprise environments. Reference topics:Wireless Network Operation - Cisco wireless fabric architecture, fabric edge node role, user data termination, data-plane operations.

The correct answer isCbecause trend deviation in Cisco Catalyst Center AI Analytics is designed to identify behavior that differs from expected network baselines. Cisco AI Network Analytics uses machine learning to establish baselines that are specific to the network and site, then compares live operational telemetry against those learned expectations. Cisco states that AI-driven issues are triggered based on deviations from the predicted baseline for the specific network environment.
For wireless operations, this is valuable because deviations in onboarding, association, DHCP, AAA, radio throughput, AP performance, client experience, retries, SNR, or similar KPIs can surface before they become broad user-impacting incidents. Cisco also describes Trend Deviations as a Trends and Insights function that determines global patterns and deviations to provide system-generated insights. This gives operations teams earlier awareness of abnormal wireless behavior and allows proactive investigation rather than waiting for help-desk tickets or hard threshold alarms.
The other options are unrelated. Time synchronization is handled by NTP, threshold export is not the core function of trend deviation, and log backup is a separate operational process. Reference topic:Wireless Monitoring and Management - Catalyst Center Assurance, AI Network Analytics, trend deviation, anomaly detection, wireless baselining, and proactive operations.