Spectrum Monitor is an Aruba AP mode that is sending captured RF data to Aruba Central for waterfall plot.
Spectrum Monitor is a mode that allows an AP to scan all channels in both 2.4 GHz and 5 GHz bands and collect information about the RF environment, such as interference sources, noise floor, channel utilization, etc. The AP then sends this data to Aruba Central, which is a cloud- based network management platform that can display the data in various formats, including waterfall plot. Waterfall plot is a graphical representation of the RF spectrum over time, showing the frequency, amplitude, and duration of RF signals. The other options are incorrect because they are either not AP modes or not sending RF data to Aruba Central.

Aruba Central is a cloud-based networking solution that empowers IT with AI-powered insights, intuitive visualizations, workflow automation, and edge-to-cloud security to manage campus, branch, remote, data center, and IoT networks from one dashboard. Aruba Central also provides a mobile app that allows users to easily onboard and monitor devices. The app enables users to scan the barcode of a device (such as an AP or a switch) and add it to their network in Aruba Central. The app also lets users monitor the details of Aruba wireless access points and switches and their clients on their network. Therefore, the application that the office manager must use on their phone to complete the task of onboarding all the new hardware into Aruba Central is the Aruba Central App.

MPSK stands for Multi Pre-Shared Key, and it is a feature that allows different devices to connect to the same SSID with different pre-shared keys. This improves the security and scalability of the network, as each device can have its own key and role without requiring 802.1X authentication or an external policy engine. MPSK can be configured either locally on the AP or centrally on Aruba Central.

To load-balance VLANs with MSTP, you need to configure the same VLAN-to-instance mapping on all switches in the same MST region. This means that you need to assign different VLANs to different MST instances, and then adjust the spanning tree parameters (such as priority, cost, or port role) for each instance to achieve the desired load balancing. For example, you can make one switch the root for instance 1 and another switch the root for instance 2, and then map half of the VLANs to instance 1 and the other half to instance 2.