Technical explanation

The licensing distinction must be read against the actual entitlement matrix, not assumed from feature names. HPE lists base AI Insights under Foundation, while its official Classic Central AP license table lists Unified Communications and Collaboration (UCC) and Live Upgrades under Advanced. UCC visibility concerns voice/video collaboration experience; Live Upgrade is a firmware-maintenance orchestration capability. The test’s answer key singles out UCC, but the wording admits another Advanced-only selection in that documented matrix.

The Foundation license includes AI Insights, making C ineligible as an Advanced-only distinction. However, HPE’s official Classic Central license table places both UCC and Live Upgrades in the Advanced column. Accordingly, A is the supplied key but B also satisfies the literal wording; the question is not unambiguous as a single-choice item.

Source-specific qualification: HPE’s AP Foundation and Advanced License table places both UCC and Live Upgrades under Advanced. A single-answer interpretation of this question therefore requires the intended curriculum/release context.

Official HPE references | AP Foundation and Advanced License – HPE Aruba Networking Central • Dynamic Application Prioritization Profile | Study-guide topic: Introduction to AOS-10

Technical explanation

Run tests and, where authorized, command sessions from Troubleshooting so their timestamps, device context and results appear in History. The session record allows comparison before and after an intervention and can be exported as operational evidence. For accountability, also consult Audit Trail, which records administrative actions rather than being a substitute for diagnostic output. Preserve results externally when a regulatory or investigation retention period exceeds Central's operational history retention window. Central records troubleshooting sessions under Troubleshoot > History; select a session ID to read its outputs and any associated notes.

A configuration-change event cannot replay the output of a cable test or ping. The site timeline helps correlate incidents but is not a test archive. History contains prior sessions and can be reviewed for repeated diagnostics or handover.

Official HPE references | Troubleshooting Tools • Troubleshooting History | Study-guide topic: Network Management with HPE Aruba Networking Central

Technical explanation

Check RADIUS server reachability and latency from the actual authenticator, which could be an AP or gateway depending on SSID forwarding and AAA design. Confirm server address, shared-secret or certificate relationship, firewall path, configured authentication ports and load. A timeout means a response did not arrive in the allotted window; an invalid credential should usually produce a recorded reject instead. Client VLAN and DNS may affect later stages of access, but they are not the first hypotheses for a backend EAP response timeout.

DNS misconfiguration causes resolution failures but is not the usual first explanation of RADIUS/EAP timeout. VLAN assignment normally happens at or after authorization; it cannot explain why the authentication backend never answers. Confirm latency, UDP reachability and server health.

Official HPE references | Troubleshooting Tools • Configuring VLAN Settings for WLAN SSID in Tunnel and Mixed Mode | Study-guide topic: Introduction to AOS-10

Technical explanation

AirMatch is the Central-hosted RF optimization service that computes channel, bandwidth and EIRP plans from aggregated radio telemetry. It can optimize neighboring radios together rather than having each AP operate on purely local observations. The service normally calculates scheduled improvements and can react to urgent RF events, subject to regulatory channel constraints and deployment settings. ARM is an earlier local RF-management approach, while ClientMatch primarily addresses client-to-AP association and steering rather than the overall channel/power plan.

ARM is the legacy/local RF adjustment concept, while ClientMatch steers associations among available APs. AirMatch plans channels, channel widths, and transmit powers using network-wide conditions; that is the AOS-10 RF management component.

Official HPE references | AirMatch • AOS-10 Cloud Services | Study-guide topic: Introduction to AOS-10

Technical explanation

A tunneled SSID sends the relevant wireless user traffic to a gateway cluster, where the gateway can evaluate its stateful role-based policies. Confirm that the client's role is assigned at authentication, that the correct rules are installed at the gateway, and that user VLANs terminate on the cluster. Bridged forwarding keeps the datapath local, so policies on a remote gateway cannot inspect those frames. Mixed mode may tunnel selected VLANs, but the simple and unambiguous choice for all affected users is tunneled forwarding. If gateway inspection is mandatory for every client in the given role, mixed forwarding introduces an avoidable bypass condition because a locally bridged VLAN can avoid the gateway datapath.

Microbranch patterns provide selective site forwarding but do not automatically place every target session in the gateway datapath. Mixed mode can bridge some clients locally, bypassing centralized inspection. Tunnel mode makes gateway-side enforcement the explicit default path.

Official HPE references | Configuring VLAN Settings for WLAN SSID in Tunnel and Mixed Mode • AOS-10 Cloud Services | Study-guide topic: Introduction to AOS-10

Technical explanation

The client summary provides a population-level view of association and connectivity patterns within the selected time window. Narrow the view by SSID, site, AP or client identity to distinguish widespread service instability from a handful of devices. Inspect detailed client events to identify whether drops are tied to reassociation, authentication failures, DHCP renewals or AP connectivity loss. A topology map is useful for path context but not as a primary history plot; RF optimization focuses on the physical radio environment instead of user sessions.

A topology map reveals AP connectivity but does not itself chart a client’s connection history. RF Optimization diagnoses radio conditions; it cannot substitute for a time-ordered list of session drops for the specific SSID and clients.

Official HPE references | Troubleshooting Tools • Troubleshooting History | Study-guide topic: Network Management with HPE Aruba Networking Central

Technical explanation

A GreenLake workspace defines the organizational boundary containing services, users, resource associations and access controls. Establish the workspace, grant appropriate administrator rights and then onboard or assign devices and subscriptions to the Central application. Subscription tier selection remains an important later step but is not the organizational prerequisite asked here. Ensure that invited users and devices are associated with the correct workspace to avoid accidental cross-tenant visibility or assigning entitlements to an unintended environment.

Assigning subscriptions and enabling auto-assignment follow the existence of an organizational workspace. Compliance data upload is not the prerequisite to creating a Central service. Workspace and roles establish the management boundary first.

Official HPE references | Multi-Level Hierarchy • HPE Aruba Networking Unified Infrastructure - Solution Overview | Study-guide topic: Network Management with HPE Aruba Networking Central

Technical explanation

A managed device needs an administrative location and a policy context so Central can place it in the correct monitoring and configuration population. Site assignment supports local health, geographical grouping and reporting; Device Group associates consistent configurations across devices that may occupy separate sites. Check inventory ownership, valid subscription, device function, reachability and the intended scope before activation. SNMPv3 credentials and management VRFs are optional design elements, not universal onboarding prerequisites for every AP, switch and gateway.

SNMPv3 profiles are not universal onboarding prerequisites, and many sites do not use a management VRF. Correct site/group association gives devices configuration and operational context; the exact order of assignment can depend on the onboarding workflow.

Official HPE references | Multi-Level Hierarchy • System Profiles | Study-guide topic: Network Management with HPE Aruba Networking Central

Technical explanation

The switch faceplate condenses a large port table into physical positions that resemble the chassis. Link coloring distinguishes connected, down, and disabled interfaces; selecting a port exposes negotiated speed/duplex, neighboring devices and other relevant interface diagnostics. If a port unexpectedly negotiates at a lower speed, check transceiver type, auto-negotiation, cabling and peer settings. Hardware health reports CPU, fans, temperature and power supplies, which are important but do not substitute for per-interface link visibility.

The Hardware card addresses chassis components, and Device Health summarizes operational condition. Neither presents the port-by-port speed/status layout needed by operations. On AOS-CX the card also separates RJ45 and QSFP port groups. In Central, open the managed switch’s Network dashboard and expand Wired Interfaces; the faceplate hover fields include speed/duplex and PoE status.

Official HPE references | Wired Interfaces Card for Switches • Troubleshooting Tools | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Technical explanation

Examine stability-related insights alongside the actual reboot timestamps, reason codes, crash records and PoE history. Multiple APs rebooting after a switch power event indicate an upstream dependency; only one firmware build exhibiting exceptions suggests a software defect. Look for temperature thresholds, watchdog resets, memory exhaustion and unexpected power interruptions. A network topology view can identify a common switch, while RF Health addresses radio quality and will rarely establish why the AP operating system restarted.

The topology viewer may point to a shared PoE switch but has no reboot-reason classification. RF Health is primarily a radio-quality view. Stability-related insights, complemented by reboot reason and power history, best fit repeated restarts.

Official HPE references | Device Health Card • Troubleshooting Tools | Study-guide topic: Network Management with HPE Aruba Networking Central