SD-WAN Network
Learning Workspace
Explore SD-WAN architecture, follow application traffic across multiple transports, investigate network failures, and understand how centralised policies influence routing and connectivity.
Learning Control Bar
Navigate five learning stages and track your progress across twelve SD-WAN engineering activities.
Unified SD-WAN Learning Dashboard
Track your progress across five learning stages and twelve interactive SD-WAN engineering activities. Continue from your next incomplete stage.
SD-WAN Learning Pathway
Stage 1 - Understand SD-WAN Architecture and the Fabric
Stage 01 — Understand the Fabric
Before investigating application performance or diagnosing a WAN failure, establish how the SD-WAN fabric is built. Explore branch edges, WAN underlays, encrypted overlays, centralised control and the health signals that determine whether a transport can carry application traffic.
What You Will Investigate
- How branch sites connect through MPLS, Internet and LTE/5G transport networks.
- The difference between physical underlay reachability and logical overlay tunnel availability.
- How SD-WAN control-plane components influence fabric connectivity.
- How latency, jitter, packet loss and tunnel state affect application path eligibility.
Engineering Learning Objective
By the end of Stage 01, you should be able to distinguish underlay failures from overlay failures, interpret transport health, and explain why an application may move from one WAN path to another.
Three Interactive Engineering Activities
Complete each lab before advancingEngineering Investigation
Begin with the Topology Explorer to identify the network architecture. Next, use the Underlay & Overlay Inspector to separate transport failures from tunnel failures. Finally, examine the Health Dashboard to determine which available transport meets the example SLA thresholds and how the selected application path changes.
Interactive SD-WAN Topology Explorer
Explore the relationship between WAN edge devices, transport networks and encrypted overlay tunnels. Select a component to investigate its engineering role.
SD-WAN Underlay & Overlay Inspector
Investigate transport reachability, logical tunnels and controller connectivity. Compare the physical WAN with the SD-WAN control and data planes.
Transport & Tunnel State
| Component | Layer | State | Engineering Impact |
|---|
SD-WAN Fabric Health Dashboard
Investigate transport performance, overlay tunnel availability, SLA thresholds and application path selection. Introduce faults and trace how the SD-WAN responds.
Transport SLA & Tunnel Health
| Transport | Latency | Jitter | Loss | Tunnel | SLA |
|---|
Illustrative SLA for this application: latency ≤ 100 ms, jitter ≤ 30 ms, packet loss ≤ 1%. All three thresholds must pass for the path to qualify.
Application Path Investigation
Begin a trace to follow application traffic from Branch 1 to the Data Centre.
Understand the Fabric
Complete three interactive SD-WAN activities to understand network topology, transport and overlay architecture, and fabric health.
SD-WAN Topology Explorer
Underlay & Overlay Inspector
SD-WAN Fabric Health Dashboard
Stage 2 - Application Traffic and Dynamic Path Selection
Stage 02 — Follow Application Traffic
An SD-WAN fabric can have several available transports, but not every path is equally suitable for every application. Follow application traffic from the branch, through policy classification and SLA evaluation, to the selected WAN transport and destination.
What You Will Investigate
- How SD-WAN identifies and classifies application traffic.
- How business intent and application policies influence path selection.
- How latency, jitter and packet loss affect SLA eligibility.
- How an alternative transport is selected when performance deteriorates.
- How forwarding decisions can be validated using path evidence.
Engineering Learning Objective
By the end of Stage 02, you should be able to trace an application flow through the SD-WAN fabric, explain why a specific WAN transport was selected, and identify when an SLA violation should trigger a different forwarding decision.
Three Interactive Engineering Activities
Follow the traffic investigation sequenceFollow the Application Decision
Use this five-step engineering workflow to understand how an application reaches its destination.
Engineering Investigation
Begin with an application traffic trace. Identify the source, destination and traffic class. Next, compare the available transport paths and their policy preferences. Finally, introduce an SLA violation and determine whether the application remains on its original path or moves to an alternative overlay tunnel. These examples use illustrative policy and telemetry values rather than measurements from a live SD-WAN deployment.
Application Traffic Investigation
Select an application, evaluate policy and transport health, then trace forwarding across the SD-WAN fabric.
Interactive SD-WAN Forwarding Topology
Classify
Policy
SLA
Forward
Verify
Select an application and begin the trace.
Application & Policy Inspector
EvaluatingEngineering Decision
The selected application is evaluated against transport availability, overlay tunnel state and application SLA thresholds.
Reading the latest scenario from the Fabric Health Dashboard.
Identify why a transport was selected and determine whether an underlay failure, tunnel failure or SLA violation changes the forwarding outcome.
Lab 04: Investigate the path, then record completion using the Stage 02 Completion Tracker.
View Completion Tracker →Dynamic Path Selection
Compare MPLS, Internet and LTE/5G paths. Evaluate application policy, transport health and SLA compliance to determine the preferred forwarding path.
SD-WAN Candidate Path Evaluation
Select an application and inspect the preferred path.
Path Decision Inspector
EvaluatingApplication SLA Thresholds
Engineering Decision
Transport selection evaluates overlay availability, SLA compliance and application preference.
Reject paths with unavailable underlays, unavailable overlay tunnels or SLA violations. From the remaining eligible candidates, choose the first transport in the configured preference order.
Candidate Path Evidence
| Transport | Underlay | Overlay | Latency | Jitter | Loss | Decision |
|---|
Lab 05: Compare the candidates, introduce a performance impairment and verify the path decision.
Stage 02 Completion Tracker →SD-WAN SLA Performance Monitor
Examine latency, jitter and packet loss across the SD-WAN fabric. Compare synthetic telemetry against application SLA thresholds and investigate transport eligibility during network impairment.
Transport Telemetry Timeline
Inspect the telemetry charts and compare each metric with the application's SLA threshold.
Application SLA Inspector
EvaluatingCurrent Measurement
Engineering Interpretation
The monitor evaluates availability and application SLA compliance using synthetic transport telemetry.
A path is SLA compliant only when its underlay and overlay are available and latency, jitter and packet loss remain within the application's configured example thresholds.
SLA compliance determines path eligibility in this simplified model. The actual selected forwarding path also depends on application policy and preference order, as demonstrated in Lab 05.
All Transport SLA Comparison
| Transport | Underlay | Overlay | Latency | Jitter | Loss | SLA Result |
|---|
Lab 06: Compare SLA thresholds, investigate performance impairment and verify which WAN paths remain eligible.
Stage 02 Completion Tracker →Follow Application Traffic
Complete three interactive investigations covering application forwarding, dynamic WAN path selection and SLA performance monitoring.
Application Traffic Investigation
Dynamic Path Selection
SD-WAN SLA Performance Monitor
Stage 3 - SD-WAN Troubleshooting, Failure and Recovery
WAN Failure Simulator
Introduce WAN transport and overlay failures, inspect their impact on application forwarding, and investigate how the SD-WAN fabric selects an alternative eligible path.
Interactive WAN Failure Topology
Detect
Evaluate
Reroute
Verify
Select a failure scenario, apply it, and investigate the resulting forwarding decision.
Incident & Recovery Inspector
HealthyEngineering Diagnosis
All three transports are available. Application forwarding follows the preferred path.
Underlay reachability and overlay tunnel state are evaluated independently.
The selected scenario is published to the shared SD-WAN fabric state for the other engineering labs.
Failure Evidence Matrix
| Transport | Underlay | Overlay | Latency | Jitter | Loss | Application SLA |
|---|
Lab 07: Introduce a failure, investigate transport evidence, observe forwarding behaviour and restore the healthy fabric.
Stage 03 Completion Tracker →Tunnel & Control-Plane Inspector
Investigate the relationship between underlay reachability, overlay tunnel establishment, control-plane state and application forwarding. Identify why an apparently healthy WAN transport may still be unable to carry application traffic.
Interactive Tunnel Inspection Topology
Reachability
Tunnel
Control
SLA
Forward
Select a transport and inspection mode, then investigate the network evidence.
Tunnel & Control-Plane Evidence
EvaluatingUnderlay Investigation
Examine whether the transport provides network reachability between SD-WAN edges.
Underlay and overlay state must be evaluated independently.
Control-plane state is not provided by the shared fabric model. It must not be inferred solely from tunnel or underlay reachability.
Transport Evidence Matrix
| Transport | Underlay | Overlay | Latency | Jitter | Loss | SLA |
|---|
Lab 08: Inspect underlay reachability, overlay tunnel state and application eligibility. Distinguish observed evidence from control-plane information that requires separate verification.
Stage 03 Completion Tracker →SD-WAN Troubleshooting Workbench
Investigate an SD-WAN incident using a structured engineering workflow. Collect evidence, test hypotheses, identify the root cause, apply a corrective action and verify application recovery.
SD-WAN Incident Topology
Load an incident and begin the six-step engineering investigation.
Evidence collected during the investigation will appear here.
Incident Analysis Panel
ReadyCollect Diagnostic Evidence
Test a Root-Cause Hypothesis
Transport Evidence Matrix
| Transport | Underlay | Overlay | Latency | Jitter | Loss | Application SLA |
|---|
Lab 09: Identify symptoms, collect evidence, test hypotheses, find the root cause, apply a correction and verify recovery.
Stage 03 Completion Tracker →Diagnose and Recover
Complete three interactive investigations covering WAN failures, overlay and control-plane diagnostics, and structured root-cause troubleshooting.
WAN Failure Simulator
Tunnel & Control-Plane Inspector
SD-WAN Troubleshooting Workbench
Stage 4 - SD-WAN Policy Changes, Segmentation and Security
Make Safe Changes
SD-WAN engineering is not only about restoring connectivity when a network fails. It also involves understanding how routing policies, application requirements and security boundaries interact before introducing configuration changes. In this stage, evaluate proposed changes, predict their impact and verify the resulting forwarding and segmentation behaviour.
From Troubleshooting to Change Engineering
The previous stage focused on diagnosing transport failures, examining tunnel state and restoring application connectivity. Stage 04 introduces a different challenge: making intentional changes without creating new forwarding or security problems.
A policy adjustment may redirect voice traffic from MPLS to the Internet. A segmentation change may allow a new application flow between previously isolated network segments. Both changes can be technically valid while still producing an undesirable engineering outcome.
The objective is to examine the expected result before deployment, compare it with the original behaviour and verify that the change meets the intended requirements.
The Four-Step Safe Change Workflow
Every change in this stage follows a predictable engineering process.
Establish Baseline
Record the current transport selection, application behaviour and security policy.
Propose Change
Modify the intended application-routing or segmentation policy in a simulated environment.
Evaluate Impact
Compare the proposed behaviour against performance, reachability and security requirements.
Verify or Roll Back
Confirm the expected outcome or return to the original configuration when validation fails.
Stage 04 — Interactive Engineering Labs
Complete both practical labs to explore policy changes and segmentation behaviour.
SD-WAN Policy Change Simulator
Explore application-aware routing decisions. Compare existing and proposed transport preferences, evaluate application SLA requirements, inspect the forwarding impact and simulate rollback when a proposed policy introduces an undesirable result.
Segmentation & Security Explorer
Investigate how SD-WAN VPNs and VRFs create logical separation between network segments. Examine permitted and denied application flows, evaluate segmentation policies and identify the consequences of overly permissive access rules.
Engineering Answer — Why Test Before Deployment?
SD-WAN policy changes can alter which transport carries an application, while segmentation changes can alter which systems are permitted to communicate. A healthy tunnel or a reachable destination does not guarantee that the resulting behaviour is correct. Safe change engineering requires a known baseline, an explicit expected outcome, a testable verification process and a rollback option.
What You Should Be Able to Do
Explain how an application-aware policy change affects transport selection and SLA eligibility.
Distinguish intended communication from unintended access across isolated segments.
Compare baseline and proposed behaviour, verify requirements and reverse a change when necessary.
Stage 04: Two practical engineering labs covering policy change and segmentation.
Stage 04 Completion Tracker →SD-WAN Policy Change Simulator
Compare existing and proposed application-aware routing policies. Preview the forwarding impact, validate transport eligibility, apply a simulated policy change and roll back when necessary.
Application-Aware Forwarding Topology
Select an application and proposed preferred transport, then preview the policy change.
Policy Change Inspector
Baseline ActiveChange Risk Assessment
Compare the proposed policy against transport reachability, overlay state and application SLA.
A policy change should be evaluated before deployment and verified after application.
Retain the original application policy and forwarding baseline. If the proposed behaviour is undesirable, restore the original policy and confirm the expected path is selected.
Application SLA & Transport Evidence
| Transport | Underlay | Overlay | Latency | Jitter | Loss | Application SLA |
|---|
Lab 10: Establish a baseline, preview a policy change, validate forwarding eligibility, apply the simulated change and roll back.
Stage 04 Completion Tracker →Segmentation & Security Explorer
Investigate logical VPN/VRF separation, test application flows across network segments, preview access-policy changes and verify whether traffic should be permitted or denied.
Interactive Segmentation Topology
Select a source segment, destination segment and application service, then test the flow.
Segmentation Policy Inspector
Baseline PolicyProposed Security Policy
Modify the access decision for the selected source, destination and service.
Logical VPN/VRF isolation separates routing contexts. Cross-segment communication requires an explicitly designed forwarding and security path.
Verify that the proposed access decision matches the intended business requirement and does not unintentionally expand access.
Baseline Segmentation Policy Matrix
| Source | Destination | Service | Baseline Decision | Policy Explanation |
|---|
Lab 11: Test inter-segment application flows, preview access-policy changes, evaluate security impact and verify rollback.
Stage 04 Completion Tracker →Make Safe Changes
Complete two engineering labs exploring application-aware routing changes, forwarding validation, VPN/VRF segmentation and security policy verification.
SD-WAN Policy Change Simulator
Segmentation & Security Explorer
Stage 5 - SD-WAN Knowledge Check and Engineering Validation
Stage 05 — Test Your Knowledge
You have explored SD-WAN architecture, traced application forwarding, investigated network failures and evaluated policy changes. The final stage brings these engineering concepts together through a structured technical knowledge check.
What You Will Validate
Distinguish underlay reachability from overlay tunnel establishment and identify the evidence needed to assess SD-WAN fabric health.
Explain traffic classification, business policy, transport preference and the influence of latency, jitter and packet loss on forwarding.
Interpret transport and tunnel failures, identify useful diagnostic evidence and apply a structured root-cause investigation.
Evaluate proposed routing changes, verify segmentation boundaries and understand the importance of rollback and least privilege.
The Four-Step Knowledge Validation Workflow
Recall the key engineering principles.
Answer 12 scenario-based questions.
Review explanations and your score.
Record completion and review progress.
Engineering Learning Objective
By the end of Stage 05, you should be able to connect SD-WAN architecture, application performance, fault investigation and safe policy changes into a coherent engineering decision-making process.
Final Interactive Engineering Activity
SD-WAN Knowledge Check
Complete 12 technical questions covering the previous four stages. Each answer includes an engineering explanation. Review your final score and identify subjects requiring additional investigation.
SD-WAN Knowledge Check
Validate your understanding of SD-WAN architecture, underlay and overlay connectivity, application-aware forwarding, SLA monitoring, failure investigation, policy changes and segmentation security.
Assessment Results
Learning Progress and Workspace Completion
Track your progress through five SD-WAN learning stages and 12 interactive activities. Review completed labs, revisit unfinished investigations and follow your progress through the entire SD-WAN Learning Workspace.
SD-WAN Learning Pathway Ready
Complete the interactive activities to track your learning progress.
Don't Just Read the Network. Explore It.
You've explored data centre architecture, routing and resilient design. Now take the next step. Use the interactive simulator to investigate how network components and paths work together. Move beyond diagrams and start exploring network behaviour.
Recommended Reading
Continue beyond the interactive SD-WAN labs with four Network Insight engineering guides covering overlay networking, SD-WAN and SASE integration, software-defined WAN architecture and practical SD-WAN implementation concepts.
SD-WAN Overlay
Explore the relationship between WAN underlay transport and SD-WAN overlay connectivity. Understand how logical tunnels provide connectivity across physical WAN networks, how edge devices participate in the overlay and why transport availability alone does not guarantee application forwarding.
SD-WAN and SASE
Examine the relationship between SD-WAN connectivity and Secure Access Service Edge architecture. Explore how application-aware routing, cloud-delivered security, policy enforcement and secure access can work together across distributed enterprise networks and cloud environments.
WAN SDN
Investigate software-defined networking principles in wide-area networks. Explore centralized policy concepts, separation of control and forwarding functions, WAN programmability and the architectural foundations that influenced modern SD-WAN approaches.
SD-WAN Tutorial
Build a broader understanding of SD-WAN architecture, WAN edge connectivity, centralized management, transport selection and application-aware policies. Connect the concepts introduced throughout the interactive workspace with practical enterprise WAN design considerations.