Free HP HPE Networking Central HPE6-A90 Exam Questions

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

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

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

A role refers to one or more policies composed of ordered match/action rules. Place an explicit deny for protected internal subnets before an otherwise permissive internet-access entry, while permitting infrastructure services needed for DHCP, DNS and captive portal as appropriate. A final default allow can be valid only when the earlier internal-deny rules reliably match the protected networks. Validate the applied role, destination address objects and rule counters; the rule set is ineffective if bound to the wrong SSID or enforcement point. For example, a policy can deny guest access to 10.0.0.0/8 and 172.16.0.0/12 before a general internet permit. It must still allow the required DNS and DHCP services for a usable guest session.

With first-match rules, adding a deny after an earlier broad permit can make it ineffective. Setting the entire default policy to allow-all without an early internal-networks deny violates the restriction. Match specific protected prefixes first, then permit the required public destinations.

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

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

When many access ports share the same traffic role, centrally define admin state, speed/MTU, access or trunk VLAN mode, QoS, authentication and protection in a reusable Port Profile. Association of that profile with the desired interfaces yields repeatable intent and easier compliance inspection. Separate templates should be maintained for users, voice/phones, printers and uplinks where the behavior differs. A unique or short-lived diagnostic change on one port does not justify broad profile reuse and may cause unintended outages if inherited. Under Configuration > Interfaces > Port Profile, use Create profile for the shared baseline and assign it to eligible switch interfaces.

A unique uplink or a temporary lab change needs local handling rather than a shared policy object. Reading counters and LLDP is a monitoring task, not a profile-deployment task. Profiles pay off when many ports must share a stable baseline.

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 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

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

Application-aware traffic steering selects appropriate paths according to intended access: internet/SaaS sessions exit directly at the branch, while protected corporate destinations traverse a secure tunnel to the central gateway or VPNC. Define the traffic identification, routing policy and NAT behavior so enterprise prefixes are not accidentally leaked onto the public internet. Validate DNS steering and failover when the primary tunnel becomes unavailable. Full tunneling adds needless SaaS backhaul, while bridging everything removes the central enterprise inspection and reachability requested. For a SaaS call, local breakout avoids an unnecessary detour through the data center, while a private ERP connection remains tunneled. Validate DNS steering and how the return traffic selects its route.

A full tunnel hairpins SaaS traffic to the corporate gateway; pure bridging loses the desired corporate tunnel path. Application-aware split tunneling distinguishes the two destinations. VPN reachability, DNS behavior, and return routes must support both paths.

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

Technical explanation

DPI identifies traffic according to application signatures and behavioral characteristics beyond traditional IP-address, port and protocol matches. That classification enables role-based rules and QoS decisions for applications such as collaboration, streaming or file sharing, even when services reuse common transport ports. DPI should not be equated with universal SSL interception; decryption requires separate, explicit capabilities and trust arrangements. Nor does it perform DHCP address allocation or Wi-Fi channel selection, which belong to different network subsystems.

DHCP relaying and RF channel selection are separate functions. Decrypting arbitrary SSL traffic is not implied by DPI; that would require additional TLS-interception capabilities and trust. DPI is useful because recognized application identities can be inputs to traffic policy.

Official HPE references | Application Visibility * AOS-10 Cloud Services | Study-guide topic: Introduction to AOS-10