The correct action is to expose only encrypted management services: HTTPS for WebUI administration and SSH for remote CLI administration. The exhibit confirms the WLC wireless management interface is VLAN
10 with IP address 10.10.1.2, but interface placement alone does not enforce secure management protocol policy. Cisco Catalyst 9800 documentation identifies web admin settings as controller management configuration that determines administrator access, protocols, and interfaces for remote management. Cisco further states that administrators can connect securely over HTTPS, while HTTP "is not a secure connection," and that HTTPS encrypts data to and from the server.
For CLI access, Cisco's Catalyst 9800 Secure Shell guidance states that SSH enables secure remote access, and usingtransport input sshprevents non-SSH Telnet connections, limiting the device to SSH-only access.
Therefore, options A and B violate policy because they permit Telnet and/or HTTP. Option C fails because console access is local, not remote, and disabling only HTTP still leaves Telnet exposure unresolved.
Reference topics:Wireless Monitoring and Management - WLC management access, secure administration, HTTPS, SSH, and management-plane hardening.

A line-of-sight (LOS) RF connection requires a clear, unobstructed path between the transmitter and receiver.
This ensures that the transmitted signal reaches the receiving device without attenuation, reflection, or diffraction caused by physical obstacles such as walls, furniture, or other structures. LOS conditions are critical for high-frequency RF links, particularly in the 5 GHz band, where signals cannot easily penetrate objects. While multipath propagation (Option A) and MIMO (Option B) techniques enhance throughput and reliability in non-line-of-sight environments, they do not satisfy the definition of LOS. Reflections (Option C) actually introduce delays, fading, and interference, which can degrade signal quality. In Cisco Wireless Core Technologies, understanding LOS is foundational for designing point-to-point wireless backhaul links, outdoor Wi-Fi deployments, and high-performance campus networks. Ensuring LOS minimizes path loss, maximizes received signal strength, and supports predictable coverage patterns. Proper site surveys, RF planning, and AP placement are used to maintain LOS where required, particularly for directional antennas or high-gain links. Reference topics:RF Fundamentals - Line-of-Sight (LOS), RF propagation, path loss, multipath effects, MIMO considerations.

In RF communications,propagation delayrefers to the finite time required for a signal to travel from the transmitter to the receiver over a given medium. This delay depends on the distance between the endpoints and the speed at which electromagnetic waves propagate through the medium, typically close to the speed of light in air (approximately 3 × 10# m/s). Propagation delay is fundamental in calculating network latency, timing synchronization in protocols, and designing wireless coverage, especially in large-scale enterprise networks.
Reflection (option A) occurs when RF waves encounter surfaces and bounce back, potentially causing multipath interference. Scattering (option C) refers to signal dispersion caused by small objects or irregularities in the medium, which affects signal quality but not the direct travel time. Link speed (option D) represents the maximum data rate supported by a wireless link and is unrelated to the time taken for the signal to propagate.
Cisco wireless design guides emphasize propagation delay considerations when planning high-density deployments, especially in large campuses or long-range point-to-point links, to ensure timing-sensitive applications (e.g., VoIP, video conferencing) maintain acceptable performance. Propagation delay must be factored into QoS and RF design decisions to minimize latency and optimize throughput. Reference topic:RF Fundamentals - signal propagation, latency, multipath effects, and timing in wireless networks.

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.

The correct answer isD. On a Cisco Catalyst 9800 WLC, FlexConnect behavior is configured throughwireless policy profiles, not legacy AireOS-style config wlan ... syntax. Cisco documents that FlexConnect is intended for remote-office deployments where APs are managed centrally across the WAN, while still being capable of switching traffic locally and performing local client authentication when controller connectivity is lost.
For local authentication on a Catalyst 9800 policy profile, the correct CLI action is to enter wireless profile policy < policy-name > and apply no central authentication. Cisco's configuration guide states that no central authentication disables central authentication and enables local authentication. This directly satisfies the requirement that clients authenticate locally during WAN outages while the AP remains part of a centrally managed 9800 deployment when connectivity is restored.
Option C uses descriptive terminology but not the correct Catalyst 9800 parser syntax. Option A resembles older AireOS-style WLAN configuration and does not configure local authentication. Option B is not a valid
9800 FlexConnect authentication command. In a complete production branch design, local switching and Flex profile/site tag mapping must also be validated, but the command required for the authentication behavior shown in the options isno central authentication. Reference topic:Wireless Network Implementation - FlexConnect, Catalyst 9800 policy profiles, local authentication, WAN resiliency, and branch AP design.