✅ 6.
Practice Scenario Questions
Here are examples to practice:
Q: How would you ensure minimal downtime during the Aruba to SD-WAN cutover?
A: I’d use a dual WAN strategy with both Aruba and SD-WAN circuits active,
gradually shifting traffic using BGP/OSPF weight/cost manipulation, or route maps,
and verifying paths before the full switchover.
Q: How do you troubleshoot application performance in SD-WAN?
A: I’d use vManage to monitor path performance (latency/loss/jitter), check control
connections, tunnel health, and application path stats, then tweak app policies
accordingly.
✅ 1. How would you design an SD-WAN architecture for 100+ branches?
Suggested Answer:
For a 100+ branch deployment, I would implement a centralized SD-WAN architecture
using a controller-based platform like Cisco SD-WAN (vManage). I’d deploy:
Redundant controllers (vManage, vSmart, vBond) in a data center or cloud
cEdge/vEdge routers at branches, each with dual WAN uplinks (MPLS + DIA/LTE)
Templates and policies to standardize provisioning across sites
Overlay VPNs to segment traffic (e.g., corp, guest, voice)
Use application-aware routing to prioritize critical apps and steer them over best-
performing paths
Enable zero-touch provisioning (ZTP) to simplify branch onboarding
You can follow-up with:
I'd also design high availability for branches using dual WAN links and hardware
redundancy where needed. Monitoring and alerting would be handled through vManage
or integrated into NMS platforms.
✅ 2. How do you handle QoS and application policies in SD-WAN vs Aruba?
Suggested Answer:
In Aruba, QoS and application policies are typically tied to roles and user-based
access control, often using ClearPass and local gateway policies.
In SD-WAN, the focus shifts toward application performance and path quality. SD-WAN
platforms use:
Application recognition via DPI
App-aware routing policies: direct apps over the best link based on
latency/loss/jitter
QoS profiles applied to WAN edges for voice, video, etc.
Traffic shaping and per-tunnel bandwidth allocation
You can add:
The key difference is that SD-WAN enforces QoS and steering dynamically based on
real-time link conditions, while Aruba is more static and user-identity focused.
✅ 3. What challenges do you foresee in migrating from Aruba to SD-WAN?
Suggested Answer:
There are a few major challenges:
Interoperability during transition — Ensuring Aruba and SD-WAN gear can coexist
temporarily during phased migration.
Configuration translation — Rebuilding equivalent policies (e.g., routing, QoS,
ACLs) from Aruba in SD-WAN format.
Training and support — Teams may need upskilling on SD-WAN tools like vManage or
FortiManager.
Connectivity gaps — Circuit changes (e.g., replacing MPLS with DIA) may require
provider coordination.
Monitoring shift — Aruba Central → SD-WAN monitoring, new dashboards, alerting,
etc.
You can follow-up with:
I’d address these by doing a detailed discovery and mapping, running a pilot site,
and setting up parallel infrastructure for a clean cutover.
✅ 4. Have you worked with vManage or a similar SD-WAN controller?
Suggested Answer (if yes):
Yes, I’ve worked with Cisco vManage. I’ve used it to:
Onboard cEdge routers using ZTP and device templates
Push centralized feature templates (VPN, BGP, OSPF, QoS)
Monitor tunnel health, application performance, and device logs
Apply policies for DIA breakout and path preference
If no, you can say:
I haven’t worked directly with vManage, but I’ve studied it in depth and understand
its architecture and workflows. I’m confident I can pick it up quickly, especially
since I have strong experience with other controller-based platforms like Aruba
Central or Fortinet SD-WAN.
✅ Questions You Can Ask Them (Interview or Meeting)
➤ Are we moving from Aruba wireless or Aruba SD-Branch?
Why ask: Clarifies whether the change is focused on WAN/routing or wireless access.
If SD-Branch: You know it’s a full LAN/WAN stack replacement.
If Wireless: Migration may only involve WAN edge gear, keeping Aruba APs.
➤ Are we keeping any of the Aruba gear post-migration?
Why ask: Understand what needs integration or what can be decommissioned.
If keeping Aruba wireless, consider how SD-WAN integrates with existing
LAN/wireless networks.
➤ What underlay transport types do we have (MPLS, DIA, LTE)?
Why ask: This defines tunnel setup, policy design, and failover planning.
Example response you could give after asking:
Knowing that, I’d set up transport VPNs for each underlay and apply SLA-based app
steering to optimize performance.
➤ What are the top priorities—cost, performance, visibility?
Why ask: This helps tailor your architecture. For example:
If cost, consider replacing MPLS with DIA
If performance, prioritize QoS and path redundancy
If visibility, highlight vAnalytics or integration with tools like Splunk or
SolarWinds
