
SD-WAN interview questions test how you explain WAN architecture, application-aware routing and troubleshooting. This guide covers 15 questions with sample answers, from underlay versus overlay to branch failover and voice-quality scenarios. Adapt the answers to the vendor and role in the job description.
Basic SD-WAN Interview Questions
1. What is SD-WAN and why was it introduced?
SD-WAN stands for Software-Defined Wide Area Network. It separates the control plane (decision-making) from the data plane (traffic forwarding), and lets a central controller manage routing policy across all branch sites.
Many organisations adopted SD-WAN to simplify branch policy and use multiple transports for cloud and site-to-site traffic. Costs, provisioning time and traffic paths depend on the existing WAN design; traditional WANs do not universally require internet backhaul.
2. How is SD-WAN different from a traditional WAN?
| Point | Traditional WAN | SD-WAN |
|---|---|---|
| Transport | MPLS, internet or other transports; cost depends on the service | Any transport: MPLS, broadband, LTE/5G |
| Management | Often device-focused; central management is also possible | Centralized controller/orchestrator |
| Path selection | Static or dynamic routing; capabilities depend on the design | Application-aware, dynamic path selection |
| Cloud traffic | Local or central egress, depending on design | Can break out locally to the internet |
| Provisioning | Varies by automation and circuit availability | Fast, often zero-touch |
3. What is Zero Touch Provisioning (ZTP) in SD-WAN?
ZTP lets a new SD-WAN device at a branch site connect to the internet, authenticate with the central controller, and pull its configuration automatically — without an engineer manually configuring it on site. This is one of SD-WAN’s biggest operational advantages over traditional WAN rollouts.
4. What are the typical SD-WAN architecture components?
- Edge device (CPE): sits at the branch, handles traffic forwarding
- Controller/Orchestrator: central brain that pushes policy to all edges
- Management console: where admins configure and monitor the fabric
- Overlay tunnels: encrypted tunnels between edge devices, usually over IPsec
In Cisco Catalyst SD-WAN, SD-WAN Manager (formerly vManage) provides management, SD-WAN Controller (formerly vSmart) handles the control plane, and SD-WAN Validator (formerly vBond) supports orchestration. The WAN Edge forwards traffic. Other vendors use different architectures and names.
Intermediate SD-WAN Interview Questions
5. What is application-aware routing in SD-WAN?
Instead of routing every packet based only on destination IP, SD-WAN identifies the actual application (such as Zoom, Salesforce, or a VoIP call) and applies a routing policy specific to that application. For example, VoIP traffic can be sent over the lowest-latency link, while bulk file transfers go over a cheaper broadband link.
6. What is local internet breakout, and why does it matter?
Local breakout means sending internet-bound traffic (like SaaS or general browsing) directly out from the branch, instead of routing it back through a central data center first. This reduces latency and saves WAN bandwidth, which matters a lot since so much enterprise traffic now goes to cloud applications rather than internal servers.
7. What is the difference between underlay and overlay in SD-WAN?
The underlay is the actual physical transport — MPLS, broadband, LTE — that carries traffic between sites. The overlay is the virtual network SD-WAN builds on top of it, typically encrypted IPsec tunnels, so applications see one logical network regardless of which underlying transport is used.
8. How does SD-WAN handle link failover?
SD-WAN can monitor loss, latency and jitter and use policy to select an eligible path. Behaviour depends on the measurement windows, thresholds, available alternate paths and product configuration. Do not promise a universal failover time or uninterrupted calls; test degraded-link and hard-failure cases separately.
9. Can SD-WAN work over MPLS?
Yes. SD-WAN doesn’t replace MPLS by default, it works alongside it. A common design keeps MPLS for critical, latency-sensitive traffic while adding broadband or LTE links for less critical traffic, with SD-WAN deciding dynamically which link each type of traffic should use.
10. What routing protocols are commonly used with SD-WAN?
Separate the fabric control protocol from site-side routing. Cisco Catalyst SD-WAN uses OMP (Overlay Management Protocol) in its overlay control plane. BGP and OSPF can be used for site or transport routing depending on the deployment. Read our OSPF versus BGP comparison to revisit their differences. Other SD-WAN vendors may work differently.
Scenario-Based SD-WAN Interview Questions
11. A branch office has two internet links: a 100 Mbps broadband and a 20 Mbps LTE backup. How would you design the SD-WAN policy?
A reasonable approach: set broadband as the primary path for all traffic, with LTE reserved as a backup for internet breakout. Business-critical, real-time applications (VoIP, video conferencing) get priority queuing and the lowest-latency path available at any given time. Keep bulk updates and backups off metered LTE unless business requirements permit them. Apply bandwidth limits and decide explicitly what happens if neither path meets the application SLA. A 100 Mbps link is not automatically the lower-latency or better-quality path.
12. How would you troubleshoot a branch site where voice calls keep dropping but the internet otherwise works fine?
Start by checking real-time path metrics (latency, jitter, packet loss) on the active link for that site, since voice is sensitive to even small degradation that wouldn’t be noticeable in general browsing. Confirm the SD-WAN policy is actually classifying the voice traffic correctly and steering it onto the best-performing link. If metrics look fine but calls still drop, check for interface errors, QoS misconfiguration, or an issue with the voice application itself rather than the network path.
Worked example. Voice calls break up while web browsing still works. On Cisco Catalyst SD-WAN, compare the active tunnel’s BFD-measured loss, latency and jitter with the SLA class assigned to voice. Suppose broadband shows 3% loss and 40 ms jitter, while the backup tunnel stays within the configured voice thresholds. These figures are hypothetical. Check whether the policy classifies the voice flow and whether the backup is eligible. If the policy selects it, confirm the new path and test voice in both directions. If the flow still breaks up on an eligible path, check interface drops, QoS queues and the voice service itself.
13. Why might a company choose to keep some MPLS circuits even after deploying SD-WAN?
Some applications are genuinely latency-sensitive and benefit from a predictable, dedicated circuit rather than best-effort internet transport. Certain compliance or contractual requirements may also call for a private circuit. A hybrid design — MPLS for critical traffic, broadband/LTE for everything else — is common precisely because it balances cost savings with reliability where it matters most.
SD-WAN Vendor and Tooling Questions
14. Name a few SD-WAN vendors you’re aware of.
Examples include Cisco Catalyst SD-WAN, Fortinet Secure SD-WAN, Palo Alto Prisma SD-WAN and Versa. Use the current documentation for the product named in the job description; controller roles, policy behaviour and troubleshooting commands are not interchangeable.
15. Is SD-WAN the same as SASE?
No, though they’re related. SD-WAN focuses on WAN connectivity and path optimization. SASE (Secure Access Service Edge) is a broader framework that combines SD-WAN with cloud-delivered security functions like a firewall, secure web gateway and zero-trust access, all managed from the cloud. SD-WAN is often described as one building block within a SASE architecture, not a replacement for it.
Frequently Asked Questions
1. Is SD-WAN knowledge required for CCNA or CCNP?
SD-WAN isn’t a core CCNA topic, but it’s increasingly relevant at the CCNP Enterprise level and in real enterprise network roles. A solid grounding in routing and WAN concepts makes SD-WAN much easier to pick up.
2. Do I need to know a specific vendor’s SD-WAN product for interviews?
It depends on the job posting. Concepts matter more than vendor-specific commands at most interview stages, but if the job explicitly mentions a vendor (Cisco, Fortinet, VMware), it’s worth getting familiar with that platform’s terminology and console.
3. What’s the most common mistake candidates make in SD-WAN interviews?
Describing SD-WAN purely as “cheaper than MPLS” without explaining the architecture — the overlay/underlay separation, centralized control, and application-aware routing are what interviewers are actually listening for.
4. How much hands-on practice is needed before an SD-WAN interview?
Reading concepts helps with theory questions, but scenario-based questions are much easier to answer confidently after lab practice — configuring policies, simulating link failures, and observing how traffic gets steered.
Conclusion
SD-WAN interview questions tend to reward candidates who understand the “why” behind the technology, not just definitions. If you want structured, hands-on SD-WAN training that covers architecture, policy design and real troubleshooting scenarios, check out the SD-WAN course at PM Networking.
Technical reference: Cisco Catalyst SD-WAN Design Guide explains Cisco component roles, underlay and overlay routing, OMP and transport monitoring. The policy examples above are suggested interview reasoning, not a tested production configuration.

0 Comments