An Application Policy in SmartZone defines actions applied to identified applications or categories of traffic traversing a WLAN. Using Deep Packet Inspection (DPI) , RUCKUS APs recognize application types and enforce predefined behaviors.

According to RUCKUS One Online Help – Application Policy Configuration , the supported rule actions include:

(A) QoS: Assigns priority levels to traffic (Voice, Video, Best Effort, Background) for latency and throughput management.

(B) Deny: Blocks specific applications or categories (e.g., streaming or gaming) to preserve network performance.

(D) Rate Limit: Restricts bandwidth available to defined applications, ensuring fair use of airtime and bandwidth resources.

Local Breakout and VLAN Assignment are functions of traffic forwarding and device policy , not application policy. URL filtering is managed under separate content control modules, not part of Application Policies.

The IEEE 802.11k amendment enhances Wi-Fi client roaming by allowing an AP to share information about nearby access points with connected clients. This process, known as the Neighbor Report , provides a list of available APs that the client can use to make faster, more informed roaming decisions.

When a client device receives this neighbor list, it can scan fewer channels , reducing latency and improving the handoff experience—especially in enterprise networks managed by RUCKUS One , SmartZone , or RUCKUS Cloud . According to RUCKUS One Online Help and RUCKUS AI documentation , enabling 802.11k/v/r features together allows for fast and seamless roaming , as 802.11k supplies discovery data, 802.11v assists with steering decisions, and 802.11r enables fast re-authentication.

Option C is correct because 802.11k’s core function is to help clients identify the best potential APs to roam to. The other options describe unrelated functions: encryption caching relates to 802.11r, ignoring weak clients is an AP policy function, and forcing disconnections occurs during load balancing or steering—not through 802.11k.

In this SmartZone 5.2 onboarding scenario:

San Mateo (200.7.10.202.121): These APs are running Unleashed firmware , which cannot directly join a SmartZone controller. According to the RUCKUS One Online Help – AP Firmware Migration , Unleashed APs must first be converted to Standalone (Solo) mode using CLI (set director ip < SZ_IP > or set scg ip) before they can connect. Thus, D (San Mateo devices can use ap-mode commands to onboard) is correct.

Toronto (102.0.0.0.5): This firmware version represents ZoneDirector (ZD) code. APs on ZD firmware communicate using LWAPP , and to migrate them, administrators must perform a firmware conversion process (using set scg ip) for SmartZone compatibility. Therefore, E (Toronto devices will use LWAPP to communicate to SmartZone) is correct.

Mexico City (5.2.0.0.1412): These APs already match the SmartZone firmware family (5.2.x), meaning they are currently or can immediately be managed by this SmartZone cluster. Therefore, F is correct.

The AP Manager Log within SmartZone is dedicated to monitoring access point registration, join processes, firmware version checks, and heartbeat communication with the controller.

As stated in the RUCKUS One Online Help – Log Categories and Troubleshooting and the RUCKUS Analytics 3.5 User Guide – Device Connectivity Diagnostics , the AP Manager Log records messages about:

AP registration attempts

Join authorization success/failure

Firmware mismatch detection and upgrade triggers

The System Log covers controller-level events, the Events Log records systemwide notifications, and the Control Plane Log captures traffic flow analytics.

Admin Domains in SmartZone provide role-based access control (RBAC) by dividing system management into separate administrative scopes. Each Admin Domain can contain specific zones, WLANs, and devices, with access limited to assigned administrators.

As outlined in RUCKUS One Online Help – Administrative Domains and Roles , this feature enables organizations or MSPs to securely delegate management tasks to different teams or customers while maintaining full isolation between configurations.

Partner Domains exist only in vSZ-H (multi-tenant environments), while Cluster Roles manage global system functions. AP Groups are configuration containers but not access control boundaries.

The maximum theoretical throughput of a Wi-Fi link is primarily defined by the channel width (e.g., 20, 40, 80, or 160 MHz) and the Modulation and Coding Scheme (MCS) rate selected by the device.

As stated in the RUCKUS One Online Help – PHY and Data Rate Concepts , throughput increases with wider channels and higher modulation (e.g., 1024-QAM in Wi-Fi 6). However, achieving these rates depends on sufficient SNR , which influences the MCS level that can be sustained.

RUCKUS Analytics collects PHY rate metrics to validate link efficiency and helps determine whether MCS downgrades are caused by environmental noise or interference.

Transmit power and beacon timing affect stability, not raw throughput.

In SmartZone High-Scale (vSZ-H) environments, the Domain Hierarchy defines the organizational and administrative structure for managing distributed networks and multi-tenant operations.

According to RUCKUS One Online Help – SmartZone Domain and Role Management and SmartZone High-Scale Administration Guide , the following apply:

(A) Each Domain defines an administrative boundary that determines which network components (zones, WLANs, APs) specific administrators can access or modify.

(D) A Domain can contain sub-domains and AP Zones , allowing hierarchical management layers for large service provider or enterprise environments.

(F) Partner Domains (exclusive to vSZ-H) allow configuration inheritance from the System Domain , while providing the flexibility to customize local settings and policies for tenants or customers.

Options B , C , and E are incorrect because all domain types (not only Partner Domains) can contain AP Zones, and SmartZone supports multi-level hierarchies beyond just System and Zone levels.

The Wi-Fi Alliance (WFA) is the global organization responsible for testing and certifying interoperability of wireless LAN products based on the IEEE 802.11 standards. While the IEEE develops and maintains the technical specifications (e.g., 802.11a/b/g/n/ac/ax), it does not perform certification or compliance testing. Instead, the Wi-Fi Alliance ensures that certified devices from different manufacturers operate together seamlessly under the “Wi-Fi CERTIFIED™” program.

According to RUCKUS One Online Help and the RUCKUS AI documentation , RUCKUS access points and controllers undergo Wi-Fi Alliance certification to ensure compatibility with a wide range of client devices, including those using WPA3, Wi-Fi 6 (802.11ax), and Wi-Fi 6E technologies. This certification is critical for enterprise environments where heterogeneous client ecosystems exist.

The IETF focuses on internet protocols (e.g., IP, TCP), and the ISO handles broader international standards, not wireless interoperability. Therefore, the Wi-Fi Alliance is the correct organization ensuring cross-vendor interoperability for Wi-Fi.

SmartCast is RUCKUS’s patented traffic classification and Quality of Service (QoS) technology. It dynamically prioritizes network packets based on type, marking delay-sensitive applications such as voice or video for prioritized transmission.

Per RUCKUS One Online Help – SmartCast Traffic Prioritization , SmartCast identifies traffic categories using Deep Packet Inspection (DPI) and applies corresponding 802.1p/DSCP markings across wired and wireless segments.

This ensures consistent service quality for time-sensitive applications even during network congestion. BeamFlex+ , PD-MRC , and ChannelFly operate at the RF level and do not manage traffic prioritization or QoS policies.

In SmartZone , WLAN Groups define which SSIDs (WLANs) are broadcast by specific APs or AP Groups. However, for an AP Group to actually broadcast the WLANs from a WLAN Group, that WLAN Group must be explicitly assigned to the AP Group’s radio interfaces (2.4 GHz, 5 GHz, or 6 GHz).

According to RUCKUS One Online Help – WLAN Group Configuration and SmartZone Administrator Guide , when an AP Group does not have a WLAN Group bound to its radios, the SSIDs in that group will not be broadcast—even if both exist within the same Zone.

Creating the WLAN Group at the Domain level or Zone level is valid, but broadcasting depends on association at the AP Group radio level.