When deployingSmartZone-Essentials (SZ-100/SZ-144)forRUCKUS ICX switch management, the switches establish a secure HTTPS-based connection to the controller using theSmartZone registrar IP. A common issue preventing connection occurs whenSmartZone is not configured to accept self-signed certificates-which are typically used by ICX switches by default for initial onboarding.
As described in theRUCKUS One Online Help - SmartZone Switch Management SetupandRUCKUS AI documentation, administrators must explicitly enable the option to"Allow Self-Signed Certificates"in the controller'sSwitch 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-Essentialsfully supports ICX management;SmartZone High Scaleis not required.
Thus, the correct answer isC- the connection fails because the controller is not set to accept self-signed certificates from the switch.
References:
RUCKUS One Online Help - SmartZone Switch Management and Onboarding Configuration RUCKUS Analytics 3.5 User Guide - Device Connection and Registration Monitoring RUCKUS AI Documentation - ICX Switch Onboarding with SmartZone Essentials

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.
Reference:
RUCKUS One Online Help - GRE Tunnel Profile Configuration and Zone Binding RUCKUS Analytics 3.5 User Guide - Tunnel Status and Performance Metrics RUCKUS AI Documentation - GRE Tunneling Architecture and Troubleshooting

PD-MRC (Polarization Diversity - Maximal Ratio Combining)is a patented RUCKUS technology that enhances Wi-Fi signal reception bylistening to client transmissions on both the horizontal and vertical polarization planes. This approach helps overcome signal degradation caused by multipath, reflections, and client device orientation.
According to theRUCKUS One Online HelpandRUCKUS AI technical documentation, PD-MRC dynamically selects and combines the signal from both polarization domains to maximize the received signal- to-noise ratio (SNR). This technology works synergistically withBeamFlex, RUCKUS's adaptive antenna system, to provide optimal signal gain and link reliability per client.
SmartCastis used for traffic prioritization and QoS management,ChannelFlyhandles dynamic channel selection using machine learning, andTx Beamformingoptimizes transmit signal direction. However, none of these specifically analyze both horizontal and vertical planes simultaneously.
Therefore,PD-MRCis the correct answer-it provides improved reception performance and overall RF robustness, especially for mobile clients in variable orientations.
References:
RUCKUS One Online Help - BeamFlex and PD-MRC Overview
RUCKUS Analytics 3.5 User Guide - RF Performance and Signal Quality Metrics RUCKUS AI Documentation - Advanced RF Technologies: BeamFlex, PD-MRC, and ChannelFly

The exhibit shows a virtual SmartZone (vSZ) configuration running in a VMware environment with three separate virtual NICs (vNICs), each mapped to a different port group: Management, Control, and Cluster.
According to RUCKUS One Online Help - SmartZone Interface Configuration and RUCKUS AI Documentation - SmartZone High-Scale Architecture, this design is specific to vSZ-H (High-Scale) deployments, which require three distinct network interfaces for distributed control, management, and cluster synchronization.
The three NIC mappings confirm physical or virtual separation of traffic for scalability and redundancy (A and E). vSZ-E (Essentials) requires only two interfaces (Management and Control) and does not use a dedicated cluster interface, distinguishing it from vSZ-H (D).
There is no indication of a four-node cluster in the exhibit, and SmartZone appliances typically show node counts under the Cluster Dashboard, not at the NIC configuration stage.
Thus, based on the configuration, this is a vSZ-H system with three NICs and three port groups, each serving a dedicated function.
Reference:
RUCKUS One Online Help - SmartZone vSZ-H Network Interface Roles
RUCKUS Analytics 3.5 User Guide - Controller Connectivity and Cluster Interfaces RUCKUS AI Documentation - vSZ-H Deployment Topologies and Port Group Mapping

The RUCKUS H Series access points are specifically designed for environments such as hospitality, student housing, and multi-dwelling units, where compact, in-room installation is ideal. A distinctive feature of the H Series-such as the RUCKUS H550 and H510 models-is their PoE output port, allowing the AP to power downstream devices like IP phones, set-top boxes, or security cameras directly through Ethernet.
This design minimizes cabling and infrastructure costs while maintaining enterprise-grade Wi-Fi performance. According to the RUCKUS One Online Help and the official RUCKUS AI documentation, the H550 supports 802.3af/at PoE input and provides 802.3af PoE output on one of its Ethernet ports. The feature is highlighted as part of RUCKUS's integrated wired and wireless connectivity solution, combining dual-band Wi-Fi 6 access with switch-like wired connectivity for room-based deployments.
The R Series and E Series are ceiling-mounted APs primarily used for large-area coverage and typically do not include PoE passthrough functionality. The M Series (outdoor mesh APs) are designed for outdoor coverage extension, also lacking this downstream PoE capability.
Reference:
RUCKUS One Online Help - Access Point Hardware Descriptions (H550, H510) RUCKUS Analytics 3.5 User Guide - Device Inventory and AP Capability Data RUCKUS AI Documentation - H550 Technical Overview (docs.cloud.ruckuswireless.com/RUCKUS-AI/userguide/index.html)