RUCKUS Updated RCWA Exam Questions and Answers by persephone

When deploying SmartZone-Essentials (SZ-100/SZ-144) for RUCKUS ICX switch management , the switches establish a secure HTTPS-based connection to the controller using the SmartZone registrar IP . A common issue preventing connection occurs when SmartZone is not configured to accept self-signed certificates —which are typically used by ICX switches by default for initial onboarding.

As described in the RUCKUS One Online Help – SmartZone Switch Management Setup and RUCKUS AI documentation , administrators must explicitly enable the option to “Allow Self-Signed Certificates” in the controller’s Switch Management settings . Without this configuration, the SmartZone rejects the ICX connection request during SSL/TLS handshake, causing registration failure.

SNMPv3 configuration and DHCP options are unrelated to initial controller registration. Additionally, SmartZone-Essentials fully supports ICX management; SmartZone High Scale is not required.

Thus, the correct answer is C — the connection fails because the controller is not set to accept self-signed certificates from the switch.

In SmartZone , Generic Routing Encapsulation (GRE) tunnels are used to encapsulate client traffic and forward it to a remote gateway, typically for security or centralized routing.

As described in RUCKUS One Online Help – GRE Tunneling Configuration , a tunnel profile becomes available for WLAN association only when it is explicitly linked to an AP Zone . This ensures that all APs in the zone can apply the correct tunnel endpoint and keying parameters.

If a GRE profile is not mapped to a zone, it will not appear in the WLAN configuration dropdown , even if successfully created.

Other options are incorrect because SmartZone supports GRE for WLANs by design, split-tunnel profiles are optional, and tunnel count limitations are far higher than typical enterprise use.

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.

DPSK (Dynamic Pre-Shared Key) technology in RUCKUS SmartZone provides individual or group-based pre-shared keys to enhance WLAN security while maintaining user simplicity.

According to the RUCKUS One Online Help – DPSK Configuration and SmartZone WLAN Authentication Guide , a Group DPSK allows multiple devices to authenticate using a single passphrase while still maintaining encryption isolation per device. This feature is typically used in shared-device environments such as classrooms, labs, or conference rooms.

The Bound DPSK type is assigned to specific devices or user accounts, ensuring individual control, while Unbound DPSKs are not tied to any particular user or MAC address.

Group DPSKs balance security and convenience by permitting shared access under one key but with independent encryption sessions, which prevents data leakage among group members.