Practice Free HPE6-A90 HPE Networking Central Exam Exam Questions Answers With Explanation

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

Live upgrade orchestrates staged AP restarts so coverage from unaffected neighbors continues serving users. Verify AP clustering or other supported live-upgrade prerequisites, firmware path, image availability and Advanced licensing when required by the deployed platform. Schedule the execution with awareness of RF design: in a poorly overlapped area, even one AP reboot can disrupt clients. Maintain deployment monitoring and post-change authentication checks. Manually reimaging each AP or relocating devices into a test site is operationally unnecessary and introduces more risk.

Console-based reflashing does not scale to a campus fleet, and relocating APs to a test site creates monitoring and policy confusion. Live Upgrade sequences eligible APs while the remaining radios continue serving much of the coverage area.

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

Technical explanation

Design overlapping coverage cells such that a client can detect and associate to an alternative AP if a neighbor fails. Validate the secondary AP's signal strength, channel availability and capacity under a failure scenario rather than relying on a fixed overlap percentage. Survey from client height and account for wall attenuation, antenna patterns and voice-roaming requirements. Setting maximum EIRP everywhere tends to enlarge contention domains, while forcing all radios onto one channel undermines spatial reuse and reliable failover.

A single shared channel causes more co-channel contention, not resilient coverage. Maximum transmit power may make APs visible from farther away while clients still lack a viable return link. Redundancy requires usable neighboring coverage with capacity to absorb failures.

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

Technical explanation

The Remote Console tab creates a browser-based SSH session to a supported device through Central's diagnostic workflow. Credentials and permissions remain necessary; the service is not the same as an out-of-band Ethernet management link. Use CLI commands to inspect interface status, routes, neighbor tables and control-plane health, preferably starting with non-disruptive show commands. Save or export the session record when needed. Template MultiEdit modifies configuration at scale; it is neither a real-time interactive console nor an equivalent troubleshooting access path.

Out-of-band management is a transport/design capability rather than the named browser CLI feature. Template groups and MultiEdit configure devices at scale; they do not provide an interactive shell for incident response. Site > Network > [device] > Troubleshoot > Remote Console is the documented workflow in the new interface; access still depends on permissions and support.

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

Technical explanation

A mixed-mode SSID supports both bridged and tunneled forwarding, selected according to the client VLAN and deployment configuration. Put POS endpoints in the locally bridged role/VLAN where latency-sensitive branch processing must remain onsite; tunnel the guest VLAN toward a DMZ gateway cluster where centralized inspection is required. Ensure guest VLANs terminate on gateways and are not accidentally carried onto the AP's local switching trunk. Mixed mode is not arbitrary per-packet application steering; the forwarding selection must match the actual WLAN/VLAN policy. Under mixed forwarding, the relevant VLAN assignment decides the datapath. Ensure POS VLANs are permitted on the local AP uplink, while the guest VLAN is present on the gateway cluster for tunneling.

All-tunnel forwarding would backhaul the POS transactions unnecessarily; all-bridge forwarding would bypass the DMZ gateway for guests. Mixed forwarding is selected per VLAN/client role, so different VLANs require the intended bridge/tunnel mapping and uplink support. The AOS-10 WLAN wizard exposes Traffic Forwarding Mode = Mixed in its VLAN settings, with a primary gateway cluster for tunneled VLANs.

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

Technical explanation

Gateway clustering couples high-availability datapath behavior with user state synchronization, load distribution and WLAN mobility support. Client traffic can be anchored and balanced across available gateways, and the cluster can preserve service through supported node failures or controlled software upgrades. Confirm that enough cluster capacity remains when a member is lost and that every gateway has consistent roles and tunnel reachability. RF channel planning belongs to AirMatch; DHCP snooping and spanning-tree are separate switching/security mechanisms rather than principal gateway-cluster benefits. A cluster maintains user-to-gateway mappings and shares relevant state across peers, improving failure recovery and distributing load. A design without valid cluster connectivity cannot provide that continuity simply because two gateways are online.

RF power/channel algorithms belong to radio management, and DHCP snooping or ARP inspection belong to switch security. Spanning tree and stack monitoring are Layer 2 infrastructure functions. Cluster value is the coordinated client state and traffic continuity between gateway peers.

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

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

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 series shorthand is a quick screening question rather than a migration compatibility matrix. Supported AOS-10 hardware spans selected 3xx, 5xx, and 7xx families. A serial-number inventory should be matched with HPE’s model-level support table and software release before scheduling AOS-10 adoption. Some older 3xx hardware has minimum or final supported releases; family membership does not override the exact SKU restrictions.

The options name broad hardware families rather than exact SKUs. The 2xx generation is outside the supported AOS-10 set, and “4xx series” is not included in the referenced supported-series choices. A 3xx selection still demands model-level and release-level validation.

Official HPE references | Supported Access Point Platforms for AOS-10 • AOS-10 Cloud Services | Study-guide topic: Introduction to AOS-10

Technical explanation

The Device Health summary provides an immediate qualitative assessment and can be expanded into the metrics or counts driving the classification. Review whether poor health is caused by uptime, hardware alarms, temperature, stack state or other supported indicators. The Hardware card exposes component detail but does not provide the same concise overall health categorization. The topology map answers where devices connect; health scoring answers which managed components require attention. Cross-check the classification against current device reachability before declaring an outage.

The Hardware card examines physical components, whereas the topology view is concerned with connection relationships. Neither replaces the direct health summary used for first-pass switch triage.

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

Technical explanation

The central entity represents the context from which the operator is exploring relationships, while surrounding planets or objects provide contextual navigation to clients, devices, sites and applications. Changing the selected site or device changes the perspective, not necessarily the physical network topology. This visualization should be understood as an information-architecture mechanism rather than a literal routing map. A primary gateway, the internet edge or a severe alarm can be an object of interest, but none universally defines the central point. An internet edge, a gateway cluster, or an alert source may be visible in a given context but does not universally anchor the solar representation. The center represents the object currently being explored, allowing the surrounding relationships to shift.

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

Technical explanation

In a Layer 3 routed Microbranch design, client source addresses remain visible end-to-end and the enterprise must advertise or otherwise route the local client subnet toward return traffic. In an L3 NATed design, the AP translates outbound sessions to a tunnel or uplink address, reducing the need to distribute a route for every branch WLAN subnet. NAT simplifies routing but can limit source-IP visibility and inbound connection behavior. Choose the mode based on enterprise identity, application reachability and route-scale requirements rather than treating both modes as equivalent forwarding. In a routed Microbranch subnet, the VPN concentrator or upstream network needs a return route toward the branch client pool. With NAT, outside services instead see the AP translated address, reducing route advertisement needs but obscuring individual client addressing.

Option A reverses source translation and route-advertisement behavior. Option C concerns gateway-client balancing, not Microbranch routing modes, and D incorrectly assumes corporate DHCP/L2 simulation is intrinsic to both L3 modes. The deciding factor is whether upstream networks see the client subnet or an AP-translated address.

Official HPE references | Layer 3 Microbranch - Validated Solution Guide • Configuring VLANs - Microbranch | Study-guide topic: Introduction to AOS-10

Technical explanation

Port Profile creation follows the functional configuration areas of general properties, VLAN/network settings, authentication/security and loop-prevention parameters. General settings include administrative status, PoE and MTU; network settings define VLAN modes; security associates relevant 802.1X or MAC-authentication policy; loop protection controls spanning-tree and safeguard behavior. The wizard's exact visual organization may evolve by Central release or switch family, but these concerns form the intended design sequence. Save the profile and associate it with the correct interface/device scope before expecting changes on hardware.

System/routing, inventory/licensing, and BFD/VRF lists describe other workflows. This question refers to the switch port profile’s general, VLAN, authentication, and loop-prevention stages—not generic onboarding or Layer 3 design.

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

Select the interval matching the overnight complaint and inspect event timestamps against authentication failures, DHCP activity, uplink transitions, AP restarts and configuration pushes. Correlating several event categories avoids mistaking the symptom for its cause. For example, multiple client disconnects coinciding with a PoE switch reboot indicate a likely shared infrastructure problem, not dozens of individual WLAN faults. Remember that dashboards may aggregate or delay telemetry; use raw device logs or system audit records when minute-level ordering matters.

A neighbor count reports adjacency, not the precise start and end of an incident. Subscription expiry is useful for licensing administration but cannot explain a ten-minute night-time interruption unless associated with specific device events.

Official HPE references | Troubleshooting Tools • Troubleshooting History | 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

Instant AP groups traditionally use a local elected virtual conductor or equivalent cluster coordination model. AOS-10 APs do not select a local AP conductor for these centralized functions; configuration, RF planning, neighbor coordination and key-management services are orchestrated by Central. This does not imply that an AP is helpless during a cloud outage: existing datapath and configuration continue to operate within documented survivability limits. Some new coordination operations may be deferred until Central connectivity returns, whereas previously synchronized roaming information may remain available.

An elected AP conductor is the Instant model being contrasted, not the AOS-10 architecture. Peer-only telemetry and local controller-based roaming do not describe Central’s cloud-supported services; individual APs maintain their datapaths while Central provides relevant shared services.

Official HPE references | AOS-10 Cloud Services • Roaming and the Key Management Service | Study-guide topic: Introduction to AOS-10

Technical explanation

Interpret the card as a triage tool: percentages place the sites with more severe health impact at the top, so an administrator can focus on locations needing action. The underlying site-health computation combines device health with client experience, rather than relying solely on offline device counts. A site without active clients may be evaluated using device health alone. When comparing apparently similar sites, open the underlying health bar and examine affected populations before prioritizing remediation exclusively from the ordering.

Option A puts alphabetic order before health severity; C moves names ahead of fair-health severity; D ranks fair above poor. The specified sort is severity-first, fair-health second, then name to resolve the remaining tie.

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

Technical explanation

The onboarding workflow begins with a device visible in the GreenLake workspace inventory. Assign that asset to the appropriate Central application instance, then allocate a compatible, available subscription to authorize management. Verify serial number, device model, intended tenant and the service assignment before provisioning. A device being present in GreenLake does not automatically imply that its Central management entitlement is active. Licensing can be subject to subscription auto-assignment policies, but the essential administrative concept remains explicit service association and entitlement.

Inventory synchronization does not imply an automatic usable Central entitlement. Support intervention is not the normal provisioning path. Assign the asset to the service and allocate an eligible subscription; auto-assignment rules, when configured, may simplify the second operation.

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

For supported live upgrade, the gateways stage their software images and restart sequentially rather than taking every tunnel termination point offline together. Cluster-state synchronization and surviving forwarding capacity let clients continue through another member during each transition. Monitor tunnel health, role state and datapath recovery between restarts; a healthy cluster is a prerequisite for claiming minimal disruption. Buffering all client traffic on APs or pausing AAA for the entire maintenance interval is not an equivalent continuity strategy and may cause application-level failure. Stateful failover depends on supported cluster topology, synchronization health and firmware compatibility. It minimizes service interruption rather than guaranteeing that every individual packet survives a gateway reboot.

Simultaneous gateway reboot would break the cluster’s availability benefit. Authentication pauses and AP traffic buffering are not a substitute for an active peer holding client sessions. The peer state must be synchronized before taking each gateway offline.

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

Technical explanation

Open the affected client context and use its event history to align 802.11 association, EAP exchange, RADIUS responses, role assignment and disconnect causes. Distinguish an authentication reject from a timeout or radio-layer disassociation: each leads to a different diagnostic path. Confirm client MAC, username, SSID, AP and timestamps because roaming can transfer the same session across radios. AP-load insights help diagnose capacity, whereas a topology drawing does not capture the per-attempt authentication failure sequence.

An overloaded AP can certainly degrade experience, but AP-load analytics do not supply EAP rejects or server-response timings. Topology traces device relationships rather than the client’s authentication exchange. The event record is the evidence to start with.

Official HPE references | Troubleshooting Tools • Troubleshooting History | Study-guide topic: Network Management 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

Developer Hub provides API documentation and a live request facility. After choosing an endpoint, an operator can supply an access token and cluster and execute the API call. A GET may simply read telemetry; a write-capable request with the right privileges can modify cloud-managed objects or configuration. For that reason, the portal must be handled with the same safeguards as a production automation client. HPE’s API FAQ expressly describes execution of API calls from the API Reference page.

The sample-code-only claim in B is contradicted by the authenticated “try out” workflow. C is equally misleading: calls are real requests, although only a write-capable endpoint changes configuration. Option A therefore needs that HTTP-method qualification.

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

Technical explanation

An 802.1Q trunk must interpret untagged frames consistently at both ends. Matching native VLAN configuration prevents an untagged frame from being mapped to different VLANs across the link. Also compare the allowed VLAN list, tagged/untagged treatment and whether the platform tags the native VLAN by explicit policy. Symmetric tagging may be valid as a separate design decision, but it is not a substitute for agreement on VLAN semantics. Test management and user reachability after any trunk change to detect silent VLAN leakage or blackholing. Native VLAN is a deliberate configuration, not something the switch dynamically chooses from broadcasts. Using different native VLANs can leak untagged traffic into unintended segments. Tagging the native VLAN on both sides is a separate compatible design, not the general consistency rule the question tests.

Official HPE references | Creating a VLAN Profile • Step 3—Configuring VLANs and Port Profiles | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Technical explanation

BPDU Guard is appropriate on edge interfaces that should never receive spanning-tree bridge protocol data units. If somebody connects a downstream switch or another bridge that sends a BPDU, the guard transitions the port to a protected state, limiting a potential topology disturbance. It does not detect every possible loop between ordinary ports when no BPDU is emitted; loop protection or storm control may also be required. Do not enable edge BPDU Guard on legitimate switch-to-switch uplinks.

BPDU Filter suppresses information STP needs, potentially hiding a loop. Root Guard protects bridge-root selection on specified ports, not arbitrary edge patching. BPDU Guard disables an unexpected bridge-facing edge port when a BPDU appears.

Official HPE references | Creating a Port Profile for Switches • Step 3—Configuring VLANs and Port Profiles | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Technical explanation

Create a VSX pair in the aggregation tier and a VSX LAG/MC-LAG extending to each aggregation member, while the access stack uses LACP toward the two peers. The access device sees a single logical bundle even though the links terminate on different chassis. Correct ISL, peer keepalive, VLAN membership and LACP settings are essential for deterministic failover. Separate unaffiliated access ports force spanning-tree or routed-design considerations and do not deliver the same active-active link aggregation behavior.

Two independent access ports are not an LACP bundle across two chassis. Making a separate VRF for each link only isolates routing state. VSX with a multi-chassis LAG supports forwarding on both uplinks while preserving peer independence. For acceptance, disconnect each upstream aggregation peer in turn and confirm the LACP bundle remains up on the other peer. An undersized VSX ISL or incorrectly routed keepalive can defeat the intended resilience.

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