Free HP HPE6-A90 Practice Exam with Questions & Answers | Set: 2

Technical explanation

AirWave was a traditional network management and monitoring product, whereas Central consolidates broader cloud-native configuration, lifecycle management, AI insight and cross-domain operations. A migration requires checking device support, licensing, configuration equivalence and historical monitoring requirements rather than assuming a simple database replacement. ClearPass continues to provide policy and AAA services where deployed, and Mobility Controllers or gateways participate in wireless traffic forwarding; these products are not the legacy management software intended by the question. ClearPass remains an access-policy/AAA product; a Mobility Controller or VPN concentrator forwards or terminates traffic. AirWave is the legacy network-management platform whose visibility and operations Central supersedes for supported deployments.

Official HPE references | Planets in Global Monitoring Page • HPE Aruba Networking Unified Infrastructure - Solution Overview | Study-guide topic: Network Management with HPE Aruba Networking Central

Technical explanation

During a live upgrade, devices download the firmware before carefully sequenced reboot groups reduce the simultaneous coverage loss. Conduct a compatibility and dependency assessment, including whether a BIOS upgrade forces a standard interruption-based procedure. Business-hours execution can be suitable only when coverage, client mobility and supported software conditions are verified; 'live' does not guarantee zero interruption for every station or application. Track roaming, VoIP performance and reconnect attempts during the rollout, not just firmware compliance at completion.

Manual serial work is unrealistic for hundreds of APs. Scheduling an ordinary concurrent upgrade during business hours does not make the upgrade low-impact. Live Upgrade is the relevant mechanism; even then, an engineer should verify density and roaming behavior.

Official HPE references | Creating a Firmware Policy • Live Upgrade | Study-guide topic: Introduction to AOS-10

Technical explanation

Treat member ID 1 as the intended initial conductor in the documented Central VSF configuration workflow, with a second member explicitly assigned for standby resilience. Verify the topology from the VSF Profile view after onboarding rather than relying solely on a label. On failover, another member may temporarily conduct the stack; member number does not dynamically change with that role transition. Ensure both adequate stack-bandwidth design and platform-specific split detection, which prevents duplicate active management planes if the stack fragments.

A conductor is not simultaneously elected on every member, and the highest ID does not automatically own control. “Standby always ID 1” reverses the initial layout. Member ID remains fixed while roles can change after failover.

Official HPE references | VSF Profile • VSF Split Detection | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Technical explanation

A sourced ping confirms IP reachability between the selected AP and destination gateway interface if ICMP is permitted. Examine packet loss, round-trip time and response patterns while validating that the source VRF or interface is correct. A successful ICMP exchange establishes basic Layer 3 reachability but does not prove that user tunnels, RADIUS exchanges or application ports are functional. Where ping is filtered, traceroute or a protocol-specific test is more informative than treating silence as conclusive path failure.

A throughput or speed test addresses capacity, not necessarily basic L3 reachability. The Connectivity card is observational and may aggregate several paths. Source a ping from the AP to its gateway and inspect packet loss and response time.

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

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

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

High 5 GHz retries can reflect co-channel interference, hidden nodes, low SNR, weak client transmit power or congestion even when an AP advertises adequate signal. Expand the performance card to compare channel utilization, noise, retries, PHY rates and client distribution over the relevant interval. Only then decide whether RF optimization, an AP placement change or a client-side fix is justified. Forcing clients to 2.4 GHz may worsen contention, and disabling band steering removes a steering mechanism without addressing underlying airtime loss.

Moving everyone to 2.4 GHz might simply exchange a noisy 5 GHz channel for a more congested band. Band steering changes client preference, not the cause of retries. First determine whether utilization, signal quality, or interference correlates with retries.

Official HPE references | AirMatch • Planets in Global Monitoring Page | Study-guide topic: Introduction to AOS-10

Technical explanation

A VLAN profile allows DHCP helper-address configuration to follow the VLAN's Layer 3 interface requirements rather than attaching IP relay settings to an unrelated physical access port. Ensure that an SVI exists and has Layer 3 reachability to the DHCP server; DHCP relay is meaningful on the routing device that receives the broadcast. Scope the VLAN profile to the intended site and device functions and check whether any switch needs a unique local SVI address. Validate that both request and reply traffic can traverse the VRF and ACL policies. The VLAN profile workflow starts at Configuration > VLANs & Networks > VLAN > Create Profile, with the desired scope and switch function selected.

A port profile describes physical or logical interface attributes, not VLAN-specific relay across all switches. A generic System profile does not replace the VLAN/SVI-facing helper relationship; tie the helper to the routed VLAN at the intended scope. Be precise about the Layer 3 termination: DHCP relay runs where the client VLAN broadcast reaches a routed VLAN interface. Defining a helper on a switch that only transports the VLAN at Layer 2 will not relay those broadcasts.

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

Technical explanation

The timeline allows metrics and events to be viewed within the same historical period as the reported slowdown, making temporal correlation possible. Compare interface throughput, link errors, CPU alarms, client health and configuration changes for the chosen window. A coincident alert is only a lead; corroborate a causative relationship through device counters or reproducible symptoms. The Hardware card is best for component condition, and the Connectivity card may expose the metrics, but the time-range widget is what makes historical comparison practical.

Hardware inventory does not reveal the past throughput curve. Connectivity data is useful only when viewed at the required period; the Timeline widget is the explicit control for changing the observation window.

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

Technical explanation

Place only the front-desk APs for the required sites in the intended configuration group or apply the WLAN profile with an equivalent targeted scope. Confirm that non-front-desk APs do not inherit the SSID inadvertently and that the SSID is enabled on the desired radios. A broadly applied global WLAN followed by manual deletions creates drift and unpredictable inheritance. Separate per-AP copies increase maintenance cost; using a common profile makes subsequent security, portal and radio-setting updates consistent.

A global SSID followed by dozens of deletions is an exception-heavy rollout; per-AP configuration is even less maintainable. A group for front-desk APs gives a stable logical targeting mechanism independent of physical site, provided only intended APs belong to it.

Official HPE references | Multi-Level Hierarchy • System Profiles | Study-guide topic: Introduction to AOS-10