HP HPE7-A07 - Aruba Certified Campus Access Mobility Expert Written Exam

Why C and D are correct (bridged traffic):

“In AOS 10 deployments that use mobility gateways, application/flow visibility and Client Insights for wireless clients are derived from gateway DPI and firewall session state. When an SSID is bridged at the AP (including mixed mode where a client is bridged), client data traffic does not traverse the gateway. Because the gateway does not see the user flows, flow attributes and network activity are not populated in Central for those clients.”

This applies to:

• C – SSID is bridged (all clients bypass the gateway).

• D – SSID is mixed mode but the affected clients are bridged (those clients bypass the gateway).

Why A, B, and E are not the best answers:

“When clients are tunneled (including mixed-mode clients that are tunneled) to the gateway, the gateway’s stateful firewall and DPI engine observe the sessions and export flow/app data to Central.”

Thus A is not a reason for missing data.

“Client VLANs marked untrusted are evaluated by the gateway firewall/DPI and support visibility. Marking a VLAN trusted bypasses firewall enforcement, but flow visibility for tunneled WLAN clients is based on gateway DPI; the primary reason Central shows no flow attributes is that the traffic never reached the gateway (bridged path).”

Therefore B/E are not the primary causes of this symptom in the scenario described.

References of HPE Aruba Networking Switching documents or Study Guide:

Aruba AOS 10 Gateway and WLAN Configuration Guides — “Tunneled vs Bridged SSIDs and impact on gateway DPI/visibility.”

Aruba Central Operations Guide — “Client Insights data sources from mobility gateways.”

Aruba Policy Enforcement and Application Visibility — “Gateway DPI and stateful firewall as the source for app/flow telemetry for wireless clients.”

The correct address for the ClearPass Guest should match the FQDN of the HTTPS certificate installed on the device, which is often the FQDN of the vendor's product. This ensures secure and proper redirection to the captive portal during the authentication process. The FQDN should be entered in the Address field for ClearPass Guest configuration.

The show ata endpoint output lists the AP’s AP Tunnel Agent (ATA) state transitions with a given gateway.

Key state/result fields:

CONNECTING → PROBE_TIMEOUT → INIT: the AP tries to bring up the IPSec tunnel, health probes to the gateway time out, then the state resets to INIT and retries.

TUN_RECV_TIMEOUT: the AP stops receiving tunnel keepalives/packets from the gateway within the expected interval.

SURVIVING indicates the AP is maintaining service with an already-up tunnel while control connectivity is impaired; it is not the state shown at the end here.

In the log, AP-01 repeatedly cycles through CONNECTING → PROBE_TIMEOUT → INIT, with intermittent TUN_RECV_TIMEOUT. This pattern is the documented symptom of the gateway being unreachable or down (no response to probes/keepalives), rather than a Central/orchestrator outage or PMTU problem.

Therefore, the correct conclusion is that the gateway at 192.168.1.92 is offline or not reachable.

A is incorrect: the final/recurring state is not SURVIVING.

C is incorrect: a Central/orchestrator issue would show SURVIVING (existing tunnel continues) rather than repeated probe timeouts to the gateway.

D is incorrect: PMTU issues do not generate recurring PROBE_TIMEOUT/TUN_RECV_TIMEOUT cycles; they appear as ESP/IKE negotiation problems, not persistent probe loss.

In HPE Aruba Networking (AOS-CX and ArubaOS-Switch) platforms that support Group Based Policy (GBP), roles are assigned using Group Role IDs (GRIDs), which determine the level of trust and policy association for devices and endpoints within the network.

According to the ArubaOS-CX Group Based Policy Configuration Guide, the GBP role IDs are categorized as follows:

Default GBP role (ID = 0):This is the system default role assigned to any endpoint or user that has not been explicitly assigned a specific policy role. It typically allows limited or basic access as defined by default policies.

Infrastructure GBP role (ID = 2):This role is reserved for infrastructure devices such as gateways, controllers, or core switches. It ensures that infrastructure traffic (such as control-plane or management communication) is allowed regardless of user-level GBP restrictions.

User-defined GBP role (ID range = 100–8191):These are custom roles configured by administrators for specific groups of users, devices, or applications. Administrators can define unique security and QoS policies tied to these IDs.

Extract from HPE Aruba Documentation:

“The GBP role IDs 0–99 are reserved by the system. Role ID 0 represents the default group role. Role ID 2 is reserved for infrastructure communication. User-defined roles must be configured within the range 100–8191.”

This configuration ensures consistent and predictable policy behavior across multi-tier Aruba environments, maintaining separation between user, system, and infrastructure traffic classes.

To maximize wired bandwidth utilization, especially when multiple APs are terminating on mobility gateways, it's best practice to aggregate physical ports into a port channel. This provides redundancy and increased bandwidth by combining the throughput of multiple ports.

To achieve the bandwidth limits set by the network administrator, both per-application and total limits need to be configured. Option B shows the configuration for setting a per-application bandwidth limit, which can restrict YouTube traffic to 10 Mbps in both directions. Option D shows the configuration for setting a total bandwidth limit for all users within the voice role to 50000 Kbps (or 50 Mbps), satisfying the requirement to restrict total wireless bandwidth. By applying these configurations in HPE Aruba Networking Central, the administrator will successfully implement the necessary controls to ensure that visitor traffic does not impede the network performance for employee traffic, aligning with the capabilities of Aruba solutions to manage and prioritize network resources effectively.

Based on the criteria provided for wireless guest users, the correct user role configuration must allow internet access, only allow access to public DNS servers, deny access to all internal networks except for any DHCP server, and place the Wi-Fi guests on VLAN 555. The ACLs must permit services necessary for basic internet access (such as DNS and DHCP) and block access to internal networks.

Option A satisfies these criteria with the following configurations:

user-role "WiFi-guest": This defines the role for Wi-Fi guests.

access-list session dhcp-acl: This applies the access list that likely permits DHCP, which is necessary for guests to obtain an IP address.

access-list session dns-acl: This applies the DNS access list, which likely restricts guests to using public DNS servers.

access-list session internal-networks: This applies the internal networks access list, which denies access to internal networks.

vlan 555: This sets the VLAN for Wi-Fi guests to 555.

Options B, C, and D are incorrect because they include access-list session allowall which would permit all traffic, contradicting the requirement to deny access to all internal networks.

The sequence to return to the previous firmware version after an unsuccessful update would typically be:

hit any key to stop autoboot (This would prevent the system from automatically booting into the current, problematic firmware.)

def_part 1 (This command sets the default boot partition, which is likely where the previous working firmware is located.)

bootf (This command would boot from the specified flash partition, which after the second step, would be the previous firmware.)

osinfo (After the system is booted, this command could be used to confirm the firmware version now running on the gateway.)

The issue likely stems from the Windows device not being configured to use TEAP (Tunneled Extensible Authentication Protocol) as specified in the ClearPass configuration. TEAP is an EAP method that encapsulates an inner EAP method for secure authentication. The Windows device must have TEAP enabled and correctly configured in its network settings to authenticate successfully on the network using ClearPass.

In this scenario:

All hosts are in VLAN 100

Group-Based Policy (GBP) is applied

H1 belongs to the Marketing role

Policy table for Marketing:

Source

Destination

Action

Marketing

HR

Deny

Marketing

Sales

Permit

Marketing

Finance

Deny

Role Mapping:

Sales: H2, H4

Finance: H3, H5

HR: H6

📌 Key Aruba GBP Behavior for ARP

Aruba AOS-CX GBP enforces policy at L3 and L2, and ARP is not treated as unconditional broadcast when GBP roles restrict communication.

Aruba documentation states:

“ARP requests are only forwarded to ports associated with permitted roles.

ARP behavior follows the GBP access-policy rules.”

Since Marketing is only permitted to communicate with Sales, ARP from H1 must only be forwarded toward:

✅ H2 (Sales)

✅ H4 (Sales)

Interfaces:

H2 → port 1/1/1

H4 → port 1/1/3

Therefore, the ARP request is NOT flooded to Finance (H3/H5) or HR (H6), where communication is denied.

❌ Why Other Options Are Incorrect

Option

Why Wrong

B

Would ignore GBP enforcement; too wide of a flood

C

Not dropped — allowed paths exist to Sales

D

ARP is not broadcasted when GBP denies connectivity