HPE6-A90 Exam Dumps - HPE Networking Questions and Answers

Technical explanation

A coverage-hole alert identifies regions or client observations with insufficient effective service, not necessarily an instruction to raise EIRP. Check floor-plan accuracy, AP transmit power, antenna orientation, obstructions, user density and measured client RSSI/SNR. Confirm whether the hole reflects a failed AP, a newly blocked corridor or an original design gap. Moving or adding APs may be appropriate once the physical pattern is known. An estate-wide power increase can increase interference and impair channel reuse elsewhere.

Maximum transmit power across the campus is not a targeted coverage remedy; it can worsen interference. Raising minimum data rates normally shrinks the usable coverage area. Validate floor plans against measurements before changing cell size or adding hardware.

Official HPE references | AirMatch • AOS-10 Cloud Services | 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

Firmware policy allows administrators to select devices by deployment scope, desired image and an upgrade mechanism. A live upgrade organizes participating APs into reboot sets rather than restarting the entire RF neighborhood together. Prechecks include supported AP hardware, appropriate licensing, access to image distribution and sufficient overlapping coverage. Schedule sites in controlled waves, observe client experience between waves and retain a backout plan. BIOS-dependent transitions and unsupported combinations may require a standard maintenance-window upgrade. For forty sites, stagger upgrade waves by RF coverage and criticality; avoid putting neighboring radios into the same reboot wave. Check the actual release supports the desired live-upgrade procedure for the APs involved.

Manually touching every AP multiplies administrative effort and risk across forty sites. An unscheduled global push can take adjacent radios offline together. A planned live-upgrade sequence is designed to preserve coverage while individual APs change software.

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

Technical explanation

The client's Events card builds a chronology of connection transitions, enabling operators to correlate disassociation, failed authentication, roaming and IP address assignment. Preserve the client's MAC address and the interval under review because randomized MAC behavior can make a user appear as multiple identities. A device configuration page shows intended WLAN settings, and the RF dashboard captures environmental data, but neither provides the direct per-client event sequence. Use the timeline to identify the first failing stage before investigating downstream services.

RF Health aggregates environmental conditions; AP Configuration describes intended parameters. The client Events card is concerned with time-stamped association, authentication and disconnection activity, the sequence needed to diagnose one station.

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

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

NSLookup from the AP's troubleshooting context checks whether that network device can reach its configured resolver and translate the requested hostname. Use an internal and external test name to distinguish local-zone problems from general DNS reachability. Record the query result, resolver address, timeout behavior and source network. A successful AP DNS test does not guarantee client DNS works if clients use a different VLAN, resolver, ACL or captive-portal role; test the client path independently when symptoms remain.

Event logs might suggest a DNS timeout but do not execute an actual lookup, and firmware compliance is unrelated to resolver behavior. AP-based NSLookup tests the AP’s DNS context; client VLANs and resolvers still require their own verification.

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

Technical explanation

A user role is the attachment point for one or more firewall policies, and every policy consists of an ordered sequence of match/action rules. Match criteria can involve source/destination objects, protocols, ports and application identification; outcomes can include allow, deny, redirect or additional traffic treatment. Evaluation order matters because broader permissions placed before a specific restriction can defeat the intended access boundary. Verify the role assigned by AAA and whether the enforcement location is the AP, switch or gateway before assessing effective security behavior. Consider a role named GUEST: it references an internet-access policy, whose first rule denies RFC1918 management networks and later rules allow required services. Changing the policy changes the role’s effective forwarding behavior.

Rules do not contain nested policies; roles do not reference loose rules independently of policy organization. Nor do policies “inherit” role membership in the reverse direction. Roles bind policy objects, and each policy evaluates an ordered sequence of matching rules.

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

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

Accept Invite begins the account activation and identity verification process for an invited GreenLake user who has not yet completed registration. The invitation associates a person with the organization's workspace but does not automatically grant administrator privileges in every Central application. Role assignment and identity-provider configuration remain separate authorization concerns. If the recipient already has an HPE identity, the exact flow can involve signing in rather than creating a duplicate account; verify the destination workspace and permitted application scopes after acceptance.

Accepting the invite is not blanket access without identity creation or sign-in, and it does not confer administrator status by default. The invited person is guided into the GreenLake account/acceptance process with separately assigned permissions.

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