HPE Networking Central HPE6-A90 Exam Questions

Answer : B

Technical explanation

Configure a VSX LAG on both core peers and a matching LACP bundle on the access switch. The logical LAG can use available links to both core chassis simultaneously without ordinary spanning-tree blocking one of the uplinks. A peer failure leaves the remaining physical member operational provided the access switch and VLAN design are correct. Ensure consistent VLAN tagging, LACP parameters and an adequately designed VSX ISL/keepalive. Independent VLANs do not offer equivalent transparent redundancy, and static routes cannot replace a Layer 2 aggregated access uplink. With one member to each VSX core, an access switch can forward across both links. If one core fails, the LAG retains the surviving member instead of waiting for STP to unblock a redundant standalone trunk.

Putting each uplink into different access VLANs is segmentation, not a shared resilient bundle. Static routes to an access switch do not aggregate the pair's L2 member links. A VSX LAG presents a logical LACP endpoint spanning the two cores.

Official HPE references | VSX and VSF Connectivity Design - Validated Solution Guide * Creating a VSX Pair | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Answer : B

Technical explanation

A cloud-native management plane integrates deployment, monitoring, troubleshooting, security posture and software maintenance across geographically separated sites. AI-based correlations help focus investigations, while APIs allow authorized external workflows to inventory devices, retrieve statistics or make controlled configuration updates. Unified operation does not depend on SNMPv3 alone; SNMP is one management protocol and cannot supply all policy, firmware and client-experience functions. Workspaces govern administrative organization and delegation, but they do not themselves replace the multi-site management architecture.

A workspace defines organizational separation, not by itself an operating model for coordinated multi-site management. SNMPv3 secures one management protocol but does not produce Central's configuration inheritance, AI analysis, and cross-domain workflows.

Official HPE references | Application Programming Interface (API) FAQ * Multi-Level Hierarchy | Study-guide topic: Network Management with HPE Aruba Networking Central

Answer : A

Technical explanation

Cloud applications, IoT sensors, mobile devices and real-time collaboration increase east-west and internet-bound dependencies across the network. The result is higher demand for secure identity-based access, predictable wireless performance, visibility and rapid incident response. Digital transformation does not eliminate routing, switching, authentication or operational telemetry; it makes availability and observability more consequential. Centralized management helps maintain consistent policies and detect cross-domain faults, especially when locations lack onsite networking specialists. Cloud adoption does not eliminate network troubleshooting; it redistributes dependencies. Applications are generally not executed on ordinary campus switches, and self-service connectivity does not remove IT responsibility for enterprise access policy and service quality.

Official HPE references | Planets in Global Monitoring Page * Device Health Card | Study-guide topic: Network Management with HPE Aruba Networking Central

Answer : C

Technical explanation

Build a reusable Port Profile containing interface administrative state, speed/duplex behavior, PoE settings, applicable spanning-tree options and associated VLAN/security parameters. Assign it through the appropriate Interface Profile or interface selection according to device family and UI workflow. Compare effective configuration on representative switches before deploying widely because uplinks, phones and ordinary edge hosts require different policy. A global alias without an applied profile carries no operational intent, while configuring every port independently raises drift and audit risk.

An alias does not automatically carry an entire port configuration, and editing every interface by hand invites drift. Profiles bind the required switchport intent to a reusable object; assignment to actual ports remains necessary. Open Configuration > Interfaces > Port Profile > Create profile, define the switch settings, then apply the profile from Switch Interface Configuration.

Official HPE references | Creating a Port Profile for Switches * Creating a VLAN Profile | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Answer : C

Technical explanation

A global firmware policy captures the intended version and device-function targeting so compliance can be monitored consistently across the managed estate. Confirm model compatibility, exceptions, upgrade scheduling and whether the hardware supports the selected image before enforcement. Sites with specialized requirements may need explicit model or scope exceptions; forcing an incompatible universal version would undermine standardization. AI Insights may recommend remediation but should not be treated as a silent, universal firmware installer. Inspect deployment state and post-upgrade reachability in the policy workflow.

AI Insights does not silently enforce a software version. A general system profile governs operating settings, not the firmware lifecycle. A Global firmware policy defines the target release and enforcement schedule, unless a more specific scope overrides it. For the common target version, use Menu > Firmware Management > Manage > Global > Create Firmware Policy. Define the device function, version and schedule.

Official HPE references | Creating a Firmware Policy * Live Upgrade | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Answer : A

Technical explanation

WPA3-Enterprise enables 802.1X/EAP-based per-user authentication rather than a shared preshared key. Select EAP-TLS when the policy mandates client certificates; provision trusted PKI roots, server certificates, identity mappings and renewal procedures. EAP-TLS offers mutual certificate-based validation and avoids the password-only model, but WPA3-Enterprise is the WLAN security family and EAP-TLS is the specific authentication method. WPA3-Personal is password-oriented, and transition mode or RadSec transport alone does not impose employee certificate authentication.

WPA3-Personal relies on SAE with a shared passphrase, not enterprise EAP-TLS identity. WPA3 transition options address interoperability and RadSec secures RADIUS transport; neither alone establishes the requested client-certificate mode.

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

Answer : C

Technical explanation

Authentication diagnosis requires a timestamped transaction trail. Look for EAP-start, identity exchange, RADIUS reject, timeout, certificate-related messages and the eventual assigned role or VLAN. Pair the failure entries with server-side accounting and authorization logs to confirm whether an error originates at the client, AP/gateway, transport path or policy engine. RF Health can confirm basic signal conditions but cannot explain a backend rejection, while AI Insights typically aggregates recurring behavior rather than exposing every individual transaction.

AI Insights can identify a pattern across many users, but the client's event record identifies an actual authentication failure and its timestamp. RF Health reports radio quality, which cannot distinguish a RADIUS reject from an EAP timeout.

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