RUCKUS RCWA - RUCKUS Certified Wi-Fi Associate Exam

RUCKUS APs running Unleashed firmware cannot be onboarded directly into a SmartZone-managed deployment. They must first be converted from Unleashed firmware to supported standalone, or Solo, firmware before the APs can discover and register with SmartZone. After conversion, SmartZone discovery mechanisms and appropriate controller configuration can be used to complete onboarding. ZoneDirector deployments are different because SmartZone provides migration functionality for supported ZoneDirector APs; therefore, saying that ZoneDirector APs cannot connect is incorrect. SmartZone 7.1 also exposes ZoneDirector migration functionality rather than an equivalent direct Unleashed migration mechanism. Consequently, the required action for the Unleashed site is conversion to Solo firmware before SmartZone onboarding, making option D correct. rcw 3 Ruckus Wireless Documentation

================

SmartZone uses a configuration hierarchy in which an AP Group can override the WLAN Group assigned at the Zone level separately for each radio. Therefore, adding a new SSID to the Zone ' s default WLAN Group does not guarantee that every AP in that Zone will advertise it. If the test AP belongs to an AP Group whose 2.4 GHz and 5 GHz radios override the Zone configuration with another WLAN Group, only WLANs contained in that overridden group will be broadcast. RUCKUS training documentation specifically instructs administrators to enable the AP Group ' s Override zone configuration option and select the required WLAN Group for each radio. Tunnel Mode and DHCP Option 43 do not determine whether the configured SSID is advertised, and routine WLAN Group changes do not require a manual AP reboot. Ruckus Training

================

To throttle download speeds for specific device types—such as ChromeOS devices—and assign them to a dedicated VLAN , the appropriate configuration is to create a Device Policy and apply it to the target WLAN .

According to the RUCKUS One Online Help – Device Policy Management , and RUCKUS AI documentation – Policy Control and Device Analytics , Device Policies can classify client devices based on operating system, MAC OUI, or fingerprinting data . Once identified, administrators can enforce rate limits, VLAN tagging, and access restrictions for that device type.

By applying this policy to the STUDENT SSID , all detected ChromeOS clients will have bandwidth limits applied and their traffic segmented into the configured VLAN for management and security isolation.

Other options—such as Layer 2 ACLs or Application Control Policies —manage packet-level permissions or app-level prioritization, not per-device bandwidth or VLAN segmentation. Creating a new WLAN is unnecessary since RUCKUS policy management allows dynamic device-based enforcement on a single SSID.