A branch needs SaaS traffic to exit locally with corporate application traffic routed through a Gateway. Which configuration will achieve this?
Options:
A.
Full tunnel for all applications to the gateway
B.
Bridge mode for all traffic from the AP
C.
Split-tunnel with app-based traffic steering
Answer:
C
Explanation:
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.
HPE Aruba Networking Central flags “High Retry Rate on 5 GHz.” What’s the best next action?
Options:
A.
Move clients to 2.4 GHz.
B.
Disable band steering.
C.
Use the expanded AP Connectivity Performance card to verify the RF environment.
Answer:
C
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