HP HPE6-A90 Based on Real Exam Environment

Technical explanation

AOS-10 APs send operating state, radio channel and transmit-power parameters, RF noise/retry indicators, client counts and related performance telemetry to Central. Analytics services aggregate these measurements for RF optimization, health scoring, anomaly detection and troubleshooting. Authentication secrets are not normal monitoring telemetry, and AP reporting is not a replacement for extracting arbitrary upstream router tables. When connectivity to Central is disrupted, APs can continue their currently applied forwarding and RF plans, although cloud-dependent optimizations may be delayed. A useful operational validation is to compare AP-reported RF counters and connectivity status before and after a known interference or availability event. The resulting time-series permits trend diagnosis without copying authentication credentials into the management platform.

DHCP lease information and learned routes can exist elsewhere in the topology but are not the defining AOS-10 AP telemetry category. Secret authentication material is not a routine performance-telemetry feed. Radios report operational metrics used in health and RF decisions.

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

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

Troubleshooting History preserves the session identifier, device context, executed test and results so a diagnostic run can be compared with earlier observations. Operators can export relevant records for incident notes or maintenance evidence. Historical tests reveal changes in latency, reachability or cable status, whereas an audit trail primarily records who performed an action and when. Retention is version-dependent, so export sessions that must survive the platform's history window and record the requested time range in the incident ticket. From a site, open Network, select the device, launch Troubleshoot, then choose History to reopen earlier sessions.

Audit Trail answers who changed configuration; it is not the archive of test output. A Network overview Events card records network events, not earlier diagnostic command results. History in Troubleshoot is where a second engineer retrieves a prior session.

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

Technical explanation

Creating an SVI directly for a particular switch requires a device-appropriate local profile so its unique routed address is not unintentionally imposed on every switch that shares the VLAN definition. Reusable VLAN identity and shared subnet policy can remain centrally defined while the interface IP is assigned locally or through a device-specific alias. Validate address uniqueness and routing adjacency after deployment. A Library object cannot independently carry a unique per-device address without appropriate scope or alias resolution, and disabling the VLAN defeats the logical SVI's Layer 2 association.

A Library profile is normally a reusable template, not the place for every switch’s unique SVI address. Disabling the VLAN destroys the L3 VLAN interface’s purpose. The Switch Interface Configuration profile is related to applying profiles to interfaces, but the per-switch IP is entered as local SVI 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