350-101 Implementing and Operating Cisco Wireless Core Technologies (350-101 WLCOR)v1.0 Question and Answers

The correct configuration issecurity wpa wpa2 ciphers gcmp256. The WLAN already contains WPA3, SAE, FT-SAE, SAE-EXT-KEY, and FT-SAE-EXT-KEY AKMs, so adding another SAE-EXT-KEY command is not the missing element. For Wi-Fi 7 operation, Cisco states that WPA3-Personal requiresGCMP256 with SAE-EXT-KEY and/or FT + SAE-EXT-KEY, and that AES/CCMP128 clients do not operate as Wi-Fi 7 clients when the required stronger cipher combination is absent. Cisco’s Catalyst 9800 WPA3 security enhancement guide gives the CLI syntax directly:security wpa wpa2 ciphers gcmp256, which configures GCMP-256 cipher support.

Option D is therefore the only valid WLC command that enables the required cipher for Wi-Fi 7-capable client operation and higher throughput behavior. Option A uses incorrect syntax and is already functionally represented in the exhibit assecurity wpa akm sae ext-key. Options B and C use invalid cipher constructs; TKIP is legacy and incompatible with modern high-throughput WLAN operation. Reference topics:802.11be/Wi-Fi 7 security requirements, WPA3-Personal, SAE-EXT-KEY, GCMP-256 cipher support, and Catalyst 9800 WLAN security configuration.

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.

When a radio wavebends around an obstaclein its path, this phenomenon is calleddiffraction. Diffraction allows the RF signal to reach areas that are not in the direct line of sight of the transmitter, such as behind walls, corners, or other obstructions. The amount of bending depends on the wavelength of the signal relative to the size of the obstacle—longer wavelengths (lower frequencies) diffract more effectively than shorter wavelengths.

This property is crucial in wireless network design, especially in enterprise or mesh deployments, because it enables coverage in complex indoor environments and around obstructions where direct line-of-sight communication is impossible. Diffraction differs from other RF phenomena:absorption(option A) occurs when RF energy is partially absorbed by materials, reducing signal strength;diffusion(option B) refers to scattering of the signal in multiple directions; andreflection(option C) occurs when RF waves bounce off surfaces like walls or ceilings, which can lead to multipath interference.

Cisco wireless design guides emphasize understanding diffraction forcoverage planning, AP placement, and optimizing signal propagationin indoor and campus deployments, ensuring that signals can adequately reach shadowed or obstructed areas without excessive loss or dead spots. Reference topic:RF Fundamentals — diffraction, reflection, absorption, and indoor wireless propagation.

In a centrally switched deployment, the WLAN traffic is tunneled via CAPWAP from the AP to the WLC, where VLAN assignment occurs. To ensure that client devices are placed into the correct VLAN (in this case, VLAN 10), the WLAN policy profile must define the VLAN mapping. This allows the WLC to tag client traffic appropriately when forwarding to the upstream switch. Option C is correct because it configures the WLAN profile (policy profile) with VLAN 10, ensuring all clients associating with the WLAN are mapped to the proper VLAN automatically. Option A is incorrect because VLAN tagging is managed centrally on the WLC, and access ports at the AP are typically trunked or transparent in central switching mode. Option B is invalid; manually configuring VLAN on client devices is not feasible or scalable in enterprise deployments and does not integrate with CAPWAP central switching. Option D is also incorrect; relying on MAC-based redirection introduces complexity and is not standard practice for VLAN assignment in centrally switched networks. Cisco Wireless Core Technologies recommend using policy profiles to centrally enforce VLANs, simplifying management, ensuring security compliance, and supporting consistent enterprise Wi-Fi connectivity. Reference topics:Client Connectivity Configuration — VLAN assignment, WLAN policy profiles, centrally switched deployments, Cisco Catalyst 9800 WLC.

The correct action is to create a dedicated guest interface/VLAN and bind it to the guest WLAN through the Catalyst 9800 policy profile. In Catalyst 9800 architecture, the WLAN defines the SSID and wireless security parameters, while the policy profile defines client forwarding policy, VLAN mapping, DHCP-related behavior, and access policy. Cisco’s Catalyst 9800 VLAN configuration procedure places the VLAN selection under thePolicy Profile > Access Policiessection, where a VLAN or VLAN group is mapped to the WLAN policy profile. Cisco also documents that DHCP can be configured per interface or per WLAN and recommends using the DHCP server address assigned to the relevant interface for WLAN client addressing.

A dedicated guest VLAN backed by the 10.20.30.0/24 DHCP scope provides up to 254 usable addresses, satisfying the 200-client requirement while keeping guest users separated from corporate users at Layer 3/VLAN boundaries. Option A and C are wrong because a shared DHCP pool violates the requirement for a guest-only subnet; DHCP option 43 is for AP/controller discovery, not client addressing. Option D is not scalable and does not define DHCP allocation. Reference topics:Catalyst 9800 policy profiles, WLAN-to-policy mapping, guest VLAN segmentation, DHCP scopes, and guest network isolation.

On Cisco Catalyst 9800 Series WLCs running IOS XE 17.x, WLAN-specific client management parameters are configured under thewlan configuration context. To increase the number of client connections on the XYZ-Guest WLAN, the correct command iswlan XYZ-Guest 1 XYZ-Guest client association limit 50(orclient max-association 50depending on IOS XE version), which explicitly sets the maximum number of clients allowed per AP on this WLAN. To extend session durations and prevent frequent disconnections, theclient session timeoutcommand is applied under the same WLAN context with the desired timeout in seconds, e.g.,wlan XYZ-Guest 1 XYZ-Guest client session timeout 2800.

Profile-based session commands (options B and D) are part of wireless policy profiles, which define broader policy elements like QoS, radio settings, and security, butdo not directly enforce client association limits or session timeouts on the WLAN itself. Configuring these parameters at the WLAN level ensures that all APs associated with this WLAN apply the limits and timeout settings consistently. This approach aligns with Cisco best practices forClient Connectivity Configuration — WLAN client limits, session management, and IOS XE WLC optimization for guest networks.

To enforce endpoint compliance using Cisco ISE, the WLC must allow AAA policies configured on the ISE tooverride the WLAN default access policies. Enablingaaa-overrideon the WLAN allows the WLC to apply RADIUS-supplied attributes from Cisco ISE, including user roles, VLAN assignment, and posture evaluation outcomes, to connected clients. This is essential for enterprise environments where a posture policy (e.g., checking device security posture, anti-virus status, OS updates) must be applied prior to granting full network access.

Without enablingaaa-override, the WLC would ignore the RADIUS-supplied attributes and enforce only the WLAN-level defaults, preventing compliance-based enforcement. Option B (wireless profile policy WLAN-Staffnac) is invalid syntax; the WLAN profile must be configured via AAA overrides rather than a standalone NAC profile. Options C and D incorrectly attempt to manipulate radius enable commands at the WLAN or profile level but do not facilitate endpoint posture assessment enforcement.

Cisco’s official wireless deployment guides recommendaaa-overridewhenever integration with Cisco ISE or other RADIUS servers is used for role assignment, VLAN mapping, or posture policy enforcement. Reference topic:Client Connectivity Configuration — WLAN AAA override, Cisco ISE integration, posture policy enforcement, and compliance-based access.

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.

The correct expression isaccessPoints[0].interfaces[1] .macAddress. The JSON object contains a top-level key namedaccessPoints, whose value is an array. Array indexing begins at zero, soaccessPoints[0]selects the first access point object,ap-west-1. Inside that object, theinterfaceskey also contains an array. Therefore,interfaces[1] selects the second interface object, which hasslot: 1,status: "down", andmacAddress: "CC:FA:00:11:22:34". The final selector,.macAddress, returns that MAC address value.

This structure is directly aligned with Cisco automation workflows, where RESTCONF and Catalyst Center APIs exchange structured data in JSON. Cisco documents that Catalyst Center REST API payloads are JSON-formatted, and its example describes JSON as key-value data separated by colons. Cisco also states that Catalyst 9800 RESTCONF uses structured XML or JSON with YANG models for programmatic device access. Option B selectsap-east-2. Option C selects the first interface onap-west-1. Option D references a non-existent second interface onap-east-2. Reference topics:Automation and AI — JSON parsing, REST APIs, Catalyst Center programmability, RESTCONF, and wireless telemetry data structures.

The correct command iskey 0 MySecretKey123under RADIUS server configuration mode. On a Catalyst 9800 WLC, the RADIUS server is defined with radius server < radius-server-name > , then the server address and ports are configured, and the shared secret is applied with the key < shared-key > command. Cisco’s Catalyst 9800 802.1X configuration workflow shows the exact sequence: radius server < radius-server-name > , address ipv4 < radius-server-ip > auth-port 1812 acct-port 1813, and key < shared-key > .

Cisco IOS XE command examples also show Device(config-radius-server)# key 0 cisco, with Cisco describing it as setting the clear-text key for the RADIUS authentication server. The 0 indicates that the key is entered in clear-text form at the CLI; it does not mean “no security.” The value must match the shared secret configured for the WLC network device in Cisco ISE, otherwise RADIUS Access-Request messages are rejected or ignored. Options A, B, and C are not valid Catalyst 9800 RADIUS server subcommands. Reference topic:Client Connectivity Configuration — WPA2/WPA3 Enterprise, 802.1X, Cisco ISE integration, RADIUS server objects, AAA method lists, and shared-secret configuration.

A high-gain patch antenna is a directional antenna that concentrates RF energy into a defined coverage area rather than radiating equally in all directions. Cisco’s Wireless RF Reference Guide explains that antenna gain determines how RF power is radiated and that higher-gain antennas do not create additional transmit power; they focus existing power in a given direction. Cisco also distinguishes omnidirectional high-gain patterns, which flatten coverage, from directional antennas, which focus energy toward a target area.

That makes option C correct: a patch antenna imparts a focused beam, typically useful for covering a hallway, warehouse aisle, seating section, point-to-point link, or defined flat service area. Cisco’s antenna documentation also states that higher-gain antennas provide longer coverage distance but with a coverage-area tradeoff, especially in a particular direction. Option A is incorrect because antenna gain does not restrict operation to a single narrow frequency; frequency support is determined by antenna design and radio band. Option B describes channel overlap, not antenna behavior. Option D does not describe a standard patch antenna radiation pattern. Reference topics:RF Fundamentals — antenna gain, directional antennas, patch antenna radiation patterns, beamwidth, and coverage-cell design.

The failure is occurring during WPA/WPA2 key management, not during mobility anchoring. The radioactive trace showsFailed to validate eapol mic. MIC mismatchfollowed byFailed to validate eapol key m2, which means the authenticator and supplicant derived different key material during the PSK handshake. Cisco’s Catalyst 9800 client-connectivity troubleshooting maps this log pattern directly to a wrong password condition and lists the corrective actions as fixing the password on the endpoint or on the SSID/WLAN. The11r MIC validation failedphrase does not automatically make 802.11r the root cause; it only shows that the failed MIC validation occurred while Fast Transition key logic was in use. Disabling 802.11r would be a workaround only for client capability or FT interoperability issues, but the trace points to PSK mismatch. Removing the anchor WLC would break the intended DMZ anchoring design, and matching WLANs on foreign and anchor is required for anchor deployments, but it would not produce this EAPOL M2 MIC failure. The correct remediation is to ensure the client-entered PSK matches the WLAN PSK. Reference topics: WPA/WPA2-PSK authentication, EAPOL 4-way handshake, Catalyst 9800 radioactive trace analysis, and client connectivity troubleshooting.

After assigning an IP address to the management interface of a Cisco 9800 WLC, the next step in Day-0 deployment is configuring the default route to ensure management traffic can reach devices outside the local subnet. The correct command isip route 0.0.0.0 0.0.0.0 < gateway > , which establishes a default route for all traffic destined for networks not explicitly known in the routing table. In this case,ip route 0.0.0.0 0.0.0.0 10.1.10.1sets the upstream router at 10.1.10.1 as the default gateway, allowing the WLC to communicate with the broader network for management and client services. Option A,route add default gw, is Cisco IOS classic syntax but not valid in IOS XE WLC CLI. Option B is invalid syntax for default routing. Option C,ip default-gateway, is only used for Layer 2 management devices without routing capabilities, whereas a WLC requires a proper Layer 3 route. Configuring the default route ensures that remote administration, SNMP, syslog, and device registration functions operate correctly. Cisco Wireless Core Technologies recommend this step as part of initial WLC setup to establish full network reachability for management access. Reference topics:Wireless Network Implementation — Day-0 WLC setup, management interface configuration, default route, IP routing in Cisco 9800 IOS XE.

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.

MIMO, or Multiple-Input Multiple-Output, is a core 802.11n and later wireless technology that uses multiple transmit and receive radio chains and antennas to improve wireless performance. Cisco’s Wireless RF Reference Guide explains that IEEE 802.11n introduced MIMO, replacing the older single-radio SISO model with multiple radios, each using its own antenna, to increase data rates and improve reception in multipath environments. Cisco also notes that weak or distorted multipath signals can be received by more than one radio and reconstructed, improving decode quality and reliability.

This directly supports option A: MIMO exploits multiple RF paths rather than treating multipath as purely destructive. Depending on implementation, MIMO can use spatial diversity, maximal ratio combining, and spatial streams to increase throughput, improve signal-to-noise ratio, reduce retries, and make more efficient use of airtime. Cisco describes spatial stream notation such as 4x4:4 as four transmitters, four receivers, and four spatial streams. Option B describes frequency hopping, not MIMO. Option C is not a MIMO function. Option D is the opposite of MIMO because MIMO deliberately uses multiple antennas and radio paths. Reference topics:802.11 Technology Fundamentals — MIMO, spatial streams, multipath, SISO versus MIMO, and 802.11n/ac/ax PHY enhancements.

Client exclusion is a feature in Cisco Catalyst 9800 WLCs that allows the administrator to temporarily block clients exhibiting misbehavior, such as excessive retries, excessive bandwidth usage, or roaming issues. The IOS XE CLI command for enabling client exclusion in a WLAN policy isclient-exclusion < timeout > , where < timeout > defines the duration (in seconds) the client is prevented from associating with the WLAN. Option D correctly usesclient-exclusion 120to block the misbehaving clients for 120 seconds. Option A (exclude 120) is not valid IOS XE syntax. Option B (exclusionlist timeout 120) is also incorrect as it refers to internal exclusion lists, not the WLAN policy applied to live clients. Option C (security exclusion timeout 120) is invalid and does not configure client exclusion at the WLAN policy level. Cisco Wireless Core Technologies emphasize using client exclusion policies during high-density events or temporary network congestion to ensure network fairness, protect overall WLAN performance, and maintain connectivity for well-behaving clients. Reference topics:Client Connectivity Configuration — Client exclusion, WLAN policy, misbehaving client mitigation, Cisco Catalyst 9800 IOS XE.

Cisco Catalyst Center uses its Event Notifications framework to alert operations teams when Assurance detects client, device, or wireless issues. The correct workflow is not a simple email-address entry under Issue Settings; it is an event subscription that binds selected issue events to a notification channel such as EMAIL. Cisco’s Catalyst Assurance documentation states that, when a specific Assurance issue is triggered and its status changes, Assurance can generate REST or email notifications, and the workflow opens thePlatform > Developer Toolkit > Event Notificationswindow from Manage Subscription. The same guide confirms that EMAIL is one of the supported notification channels and that the EMAIL notification details include sender, recipient, and subject fields. Cisco’s Platform User Guide also defines Event Notifications as the place to “view and subscribe to specific events” and gives the GUI path asPlatform > Developer Toolkit > Event Notifications. Therefore, option B is correct. SMTP/email destination configuration may be a prerequisite, but the required alerting action is creating the event notification subscription. Reference topics: Catalyst Center Assurance, Event Notifications, Wireless Monitoring and Management.

The correct configuration isaaa-overridefollowed bynacunder 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.

The switch interfaces connected to the APs must be configured as 802.1Q trunk ports. The requirement states that AP management and guest Wi-Fi traffic must remain separate, and additional VLANs for IoT and voice are expected. An access port supports only one VLAN, so it cannot scale for multiple locally tagged client VLANs. Cisco’s Catalyst AP guidance states that when multiple VLANs are used for client traffic, the AP switch port should trunk the VLANs, and management traffic is untagged; when a management VLAN is used, it should be configured as the native VLAN on the switch port. Cisco’s Catalyst 9800 FlexConnect documentation also shows the AP connected to a trunk port with a native VLAN for AP IP connectivity and a separate VLAN for locally switched client traffic.

Option C is therefore correct: configure a trunk, set the AP management VLAN as native, and restrict the allowed VLAN list to only required management and client VLANs such as guest, IoT, and voice. This supports segmentation and prevents unnecessary internal VLAN exposure. Reference topics:AP switch-port design, 802.1Q trunks, native VLANs, client VLAN tagging, FlexConnect/local switching, and guest traffic segmentation.

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.

Dynamic endpoint profiling in Cisco wireless networks is used to classify devices based on type, behavior, and attributes, enabling policy enforcement that adapts to device posture. In a deployment integrated with Cisco ISE, profiling groups are created to define rules and categories for device types such as smartphones, laptops, printers, and IoT devices. These profiling groups allow the wireless controller to map devices to the correct ISE policy sets dynamically, ensuring that security policies, VLAN assignments, and access controls are applied according to the device profile. Option A (device-type groups) is a generic categorization that does not fully leverage ISE dynamic profiling capabilities. Option C (user ID groups) focuses on user identity rather than device characteristics. Option D (endpoint group mapping) is typically applied after device profiling and classification, but initial enforcement requires creating profiling groups. By configuring profiling groups, the IT team ensures that the network can classify endpoints automatically, enforce access policies consistently, and integrate with ISE for context-aware security and compliance monitoring. Reference topics:Wireless Monitoring and Management — Dynamic endpoint profiling, Cisco ISE policy integration, profiling groups, device classification for secure access.

The correct command issecurity dot1x authentication-list RADIUS_AUTH_LIST. On a Catalyst 9800 WLC, the WLAN configuration must bind the WLAN’s 802.1X authentication process to an AAA authentication method list. Cisco’s Catalyst 9800 802.1X configuration workflow shows the WLAN entered with wlan < profile-name > < wlan-id > < ssid-name > , followed by the command security dot1x authentication-list < dot1x-list-name > . Cisco configuration guide examples also show the same syntax under WLAN configuration mode as Device(config-wlan)# security dot1x authentication-list auth-list-name.

In the exhibit, security wpa akm dot1x enables 802.1X as the key-management method, while security wpa wpa2 and security wpa wpa2 ciphers aes establish WPA2/AES security. These statements define the WLAN security framework, but they do not identify which AAA method list will be used to reach the RADIUS backend. The missing command must therefore attach the named authentication list RADIUS_AUTH_LIST to dot1x authentication. Options A, B, and C are parser-invalid or incorrectly ordered IOS XE syntax. Reference topic:Client Connectivity Configuration — WPA2-Enterprise WLAN configuration, 802.1X authentication, AAA method lists, RADIUS-backed client access, and Catalyst 9800 WLAN security commands.

The correct answer isfast BSS transition protocol, which is IEEE 802.11r Fast Transition. Cisco describes 802.11r BSS Fast Transition as the mechanism used to provide seamless roaming for wireless clients by reducing the time required to roam between access points. It achieves this by allowing keying material to be prepared or cached so that the client does not perform a full authentication exchange every time it moves to another AP within the same mobility domain.

This is specifically relevant to Layer 2 roaming because the client remains in the same Layer 2 network while reassociating to a different BSS. Fast Transition reduces roam latency, which is critical for voice, video, collaboration, barcode scanners, and other real-time applications. Cisco also classifies fast secure roaming as the method used to accelerate client roaming when Layer 2 security is configured on the WLAN. Increased beacon intervals do not provide handoff acceleration. Optimized roaming helps with sticky-client behavior but is not the secure handoff protocol. Deferred probe response is an RF/client steering behavior, not an 802.11 Layer 2 roaming key-transition method. Reference topics:802.11r Fast BSS Transition, Layer 2 roaming, fast secure roaming, WLAN mobility, and Catalyst 9800 roaming design.

The command that enables web-based client authentication on the WLAN issecurity web-auth. Cisco’s Catalyst 9800 Web-Based Authentication guide shows the WLAN configuration workflow: enter WLAN configuration mode, disable WPA security for the open Layer 2 guest WLAN, then “Enable web authentication for WLAN” usingsecurity web-auth. Cisco then applies the authentication list and parameter map withsecurity web-auth authentication-list ...andsecurity web-auth parameter-map ..., which refine the WebAuth method and portal behavior after WebAuth itself is enabled.

Cisco’s LDAP authentication example mirrors the exhibit exactly:wlan webauth 2 webauth, removal of WPA/802.1X Layer 2 security,security web-auth,security web-auth authentication-list ldapauth, andsecurity web-auth parameter-map global. Option B only creates or enters the WLAN profile with WLAN ID 2 and SSID name. Options C and D disable WPA2 and 802.1X AKM; they do not authenticate clients. Reference topics:Client Connectivity Configuration — guest WLAN authentication, WebAuth, Layer 3 security, authentication lists, parameter maps, and Catalyst 9800 WLAN security configuration.

The requirement is guest client isolation, not merely guest authentication or internet breakout. On a Catalyst 9800 WLC, peer-to-peer blocking is the correct control because it prevents wireless clients associated to the same WLAN from communicating directly with one another. Cisco defines peer-to-peer blocking as a WLAN security feature applied to individual WLANs, where each client inherits the WLAN’s P2P blocking behavior, and traffic can be bridged locally, dropped, or forwarded upstream. For this scenario, the appropriate action is thedropbehavior, because guest-to-guest file sharing must be prohibited while upstream internet access remains available.

The dedicated guest VLAN, VLAN 30, provides traffic segmentation from production networks and creates a clean policy boundary for VisitorAccess. Cisco’s Catalyst 9800 configuration model maps WLANs to policy profiles, and the policy profile defines client network and switching policy, including VLAN association. Options B, C, and D do not solve client isolation: local authentication validates users, FlexConnect/local switching changes traffic forwarding behavior, and multicast/RADIUS does not block unicast guest-to-guest traffic. Reference topics:Client Connectivity Configuration — guest WLAN design, P2P blocking, VLAN segmentation, and Catalyst 9800 WLAN-to-policy mapping.

When deploying Meraki APs, it is essential to claim each AP in the Meraki dashboard to ensure that they are automatically assigned to the correct network and can be managed remotely. This process involves registering the APs with the Meraki cloud, which is done by adding the AP serial numbers to the network within the Meraki dashboard before physically installing them at the branch.

Option B: "Add the AP serial numbers to the required network within the Meraki dashboard."This is the correct answer. Before the APs are physically connected, the administrator needs to log into the Meraki dashboard and add the serial numbers of the new APs to the intended network. This ensures that once the APs are powered on and connected, they automatically join the correct network and are ready for monitoring and management without requiring further configuration.

Option A: "Activate mesh networking mode for all the new APs before installation."Mesh networking mode is used when APs need to communicate wirelessly to extend coverage, but it is not a requirement for the deployment and registration process. The APs should be connected normally for initial setup, and mesh mode can be enabled later if needed.

Option C: "Preconfigure SSID names and VLAN tags on the local page of each AP in the Meraki dashboard."While configuring SSID and VLAN settings is essential, this is not the first action required for ensuring the APs are claimed by the correct network. The priority is to add the AP serial numbers to the Meraki dashboard for proper network assignment.

Option D: "Create a separate DHCP scope for all the new APs on the local server."DHCP scope configuration is important for assigning IP addresses, but this is not the primary step for ensuring the APs are correctly registered in the Meraki dashboard. The APs can obtain IP addresses from an existing DHCP scope once they are connected and claimed in the dashboard.

Therefore, the best approach isOption B, as it ensures that the APs are correctly assigned to the intended network in the Meraki cloud, ready for management and monitoring once connected.

The correct answer isMake-before-break handover logic. This is a key feature in Cisco's Ultra-Reliable Wireless Backhaul (URWB) process that allows devices to establish a connection to the next AP (Access Point) before disconnecting from the current AP. This seamless transition ensures that there is no disruption in the wireless connection as the client roams between APs, which is especially important in environments where consistent, low-latency connectivity is essential, such as in real-time applications (e.g., voice or video).

Option A (Open roaming)refers to a method of allowing devices to roam freely across networks, but it doesn't address the specific need for a seamless handover process.

Option B (Fast client handoff)refers to methods used to speed up the roaming process, but it doesn’t specifically ensure that the next AP is connected before disconnecting from the current one.

Option C (802.11v high speed roaming)is an IEEE standard feature that helps optimize roaming behavior for fast-moving devices, butmake-before-break handover logicis the specific mechanism that allows for a seamless roaming experience.

Therefore,Make-before-break handover logic(Option D) is the correct answer as it directly addresses the need for devices to establish a reliable connection to the next AP during roaming before losing connectivity with the current one.