Saturday, May 16, 2026

CCDE Enterprise Case Study Part 7: Hybrid WAN vs SD-WAN Design for Business Continuity

CCDE Enterprise Case Study Part 7 - Hybrid WAN and SD-WAN Benefits for Jacobs

CCDE Enterprise Case Study Part 7 - Hybrid WAN and SD-WAN Benefits for Jacobs

Modern enterprise networking is rapidly shifting from static WAN architectures toward intelligent application-aware networking models. In this CCDE enterprise case study, we analyze why Jacobs is considering a migration toward Hybrid WAN and SD-WAN technologies, and why business continuity becomes one of the most important strategic advantages of this transition.

This article continues the long-running Jacobs enterprise architecture series.

Table of Contents

Question 6 Overview

If Jacobs did move to an SD-WAN type of solution with a combination of MPLS and Internet circuits per store for Jacobs and Toolmate stores and Internet-only circuits for independent stores, what would be a major benefit?

The correct answer is:

✅ Correct Answer

Business continuity could be facilitated natively.

What Problems Is Jacobs Trying to Solve?

To understand why business continuity becomes the optimal answer, we must first understand the architectural pain points currently affecting Jacobs.

Current Problems

  • Multiple MPLS providers
  • Separate WAN architectures
  • Limited interconnectivity between business entities
  • Expensive MPLS operations
  • Manual QoS change management
  • Centralized policy bottlenecks
  • Firewall scaling concerns
  • Lack of fast application-aware path steering
  • No unified WAN visibility
  • No intelligent failover between WAN transports

Traditional MPLS WANs are highly static. Every routing change, QoS modification, or application prioritization request often requires:

  • Provider involvement
  • Change management approvals
  • Manual CLI changes
  • Maintenance windows
  • Risk analysis

This creates operational friction.

Jacobs specifically mentions: 

"Network changes are taking too long for simple items such as 
bandwidth and QoS changes"

This is one of the strongest indicators that the organization has reached the operational scalability limits of traditional WAN architecture.

What Is Hybrid WAN?

A Hybrid WAN combines multiple transport technologies together:

  • MPLS
  • Broadband Internet
  • Fiber Internet
  • 5G/LTE
  • Satellite

Instead of relying on a single transport, applications can dynamically choose the best available path.

Traditional MPLS Architecture

$$ Traffic \rightarrow MPLS \rightarrow Data\ Center $$

Hybrid WAN Architecture

$$ Traffic \rightarrow \{ MPLS,\ Internet,\ LTE \} $$

The key idea is transport abstraction.

Applications should not care which physical WAN circuit carries their traffic.

What Is SD-WAN?

Software-Defined WAN (SD-WAN) introduces centralized policy-driven intelligence into WAN architecture.

Traditional WANs make forwarding decisions primarily based on:

  • Destination IP
  • Routing tables
  • Administrative distance
  • Metrics

SD-WAN makes forwarding decisions based on:

  • Application type
  • Latency
  • Jitter
  • Packet loss
  • Business priority
  • SLA requirements
  • Real-time path quality

Core SD-WAN Concept

$$ Best\ Path = f(Latency,\ Jitter,\ PacketLoss,\ Policy) $$

This means traffic engineering becomes application-aware instead of topology-aware.

Why Business Continuity Is the Correct Answer

This is the most important architectural takeaway in the entire question.

The existing Jacobs architecture has major dependency risks:

  • Toolmate depends heavily on the Toolmate DC
  • Jacobs depends heavily on the Jacobs DC
  • MPLS providers are isolated
  • DC Internet access is isolated
  • No unified overlay exists

Currently:

$$ Failure\ of\ DC \Rightarrow Loss\ of\ Service $$

With SD-WAN:

$$ Failure\ of\ Transport \neq Loss\ of\ Application $$

This is a massive architectural improvement.

Why?

Because SD-WAN overlays abstract the physical underlay.

Applications no longer depend on:

  • Single MPLS provider
  • Single Internet circuit
  • Single DC path
  • Single transport technology

Example Failure Scenario

Current MPLS Environment

If the Toolmate DC fails:

  • Toolmate stores lose access
  • VoIP services fail
  • Applications become unavailable
  • Routing convergence becomes complex

With SD-WAN

Traffic can dynamically reroute:

$$ Toolmate\ Store \rightarrow Internet \rightarrow Jacobs\ DC $$

Then traverse:

$$ Jacobs\ DC \rightarrow DCI \rightarrow Toolmate\ Services $$

This creates native business continuity.

VoIP Latency and SD-WAN

VoIP is one of the most important constraints in the entire case study.

Jacobs specifically mentions: 

100ms latency from stores to London DCs

This is extremely important.

Industry VoIP Guidelines

Latency VoIP Quality
0-150ms Excellent
150-300ms Acceptable
300ms+ Poor

Latency Formula

$$ Total\ Delay = Propagation + Serialization + Queuing + Processing $$

In hub-and-spoke VPN architectures:

$$ StoreA \rightarrow DC \rightarrow StoreB $$

This doubles latency.

If:

$$ Store \rightarrow DC = 100ms $$

Then:

$$ Total\ VoIP\ Delay = 100 + 100 = 200ms $$

This exceeds ideal VoIP thresholds.

Why SD-WAN Helps VoIP

Modern SD-WAN solutions provide:

  • Direct branch-to-branch tunnels
  • Application-aware QoS
  • Dynamic path optimization
  • Packet duplication
  • Forward error correction
  • Jitter buffering

This enables:

$$ StoreA \rightarrow StoreB $$

Instead of:

$$ StoreA \rightarrow DC \rightarrow StoreB $$

Reducing latency dramatically.

Application Aware Routing

One of the strongest advantages of SD-WAN is application steering.

James Medina specifically says: 

"We’d need the ability to steer traffic over specific links on an application basis."

This is essentially the definition of SD-WAN.

Traditional WAN Routing

Destination-based forwarding

SD-WAN Routing

Application-based forwarding

Example Policy

Application Preferred Path
VoIP MPLS
Office 365 Internet
Backups Low-cost broadband
ERP Lowest latency path

Machine Learning in SD-WAN

Modern SD-WAN solutions increasingly use machine learning for:

  • Traffic prediction
  • Anomaly detection
  • Link quality forecasting
  • Application fingerprinting
  • Capacity planning

These concepts are heavily related to:

Modern AI-assisted WAN optimization can model WAN behavior:

$$ QoE = f(PacketLoss,\ Jitter,\ RTT,\ Congestion) $$

This allows predictive traffic steering.

WAN Mathematics and Capacity Planning

Bandwidth Utilization Formula

$$ Utilization = \frac{Traffic}{Capacity} \times 100 $$

If Bluesky MPLS utilization reaches:

$$ 8Gbps $$

On:

$$ 10Gbps $$

Then:

$$ Utilization = \frac{8}{10} \times 100 = 80\% $$

This is already high for enterprise WANs.

Why High Utilization Is Dangerous

As utilization increases:

$$ Delay \propto \frac{1}{1 - Utilization} $$

Queueing delay rises exponentially.

This directly affects:

  • VoIP
  • Video
  • Real-time applications
  • Cloud services

SD-WAN SLA Monitoring

SD-WAN continuously measures:

  • RTT
  • Packet loss
  • MOS scores
  • Jitter

Packet Loss Formula

$$ PacketLoss = \frac{Packets_{sent} - Packets_{received}}{Packets_{sent}} $$

Mean Opinion Score (MOS)

VoIP quality can be approximated:

$$ MOS \approx 4.5 - (DelayFactor + LossFactor) $$

Higher MOS values indicate better voice quality.

Why Other Answers Are Incorrect

❌ Option B — 90% Cost Savings

This answer makes assumptions.

CCDE exams test architecture decisions using ONLY supplied information.

No cost comparison exists.

Therefore:

$$ Assumption \neq Valid\ Design\ Decision $$

❌ Option C — Single MPLS Provider

Reducing to a single MPLS provider introduces:

  • Fate sharing
  • Single provider dependency
  • Reduced diversity
  • Potential resilience issues

The question never states that all providers would be consolidated.

❌ Option D — Security Improvements

This is actually the opposite of reality.

Moving from private MPLS transport to Internet transport increases:

  • Attack surface
  • DDoS exposure
  • Encryption requirements
  • Certificate management complexity
  • Public edge exposure

Security becomes more complicated, not simpler.

CCDE Thinking Process

The CCDE exam is NOT testing memorization.

It tests:

  • Architectural reasoning
  • Business alignment
  • Operational awareness
  • Tradeoff analysis
  • Scalability evaluation

Key CCDE Principle

The technically coolest solution is not always the correct architectural solution.

For Jacobs:

  • Business continuity matters
  • VoIP quality matters
  • Operational simplicity matters
  • Application agility matters
  • Integration matters

SD-WAN directly addresses these requirements.

Traditional WAN vs SD-WAN

Feature Traditional WAN SD-WAN
Routing Destination-based Application-aware
QoS Static Dynamic
Failover Slow/manual Automated
Visibility Limited Centralized analytics
Transport MPLS only Any transport
Cloud optimization Poor Excellent

Why Application Topology Matters

James Medina references: 

"Movement from network topology toward application services topology"

This is one of the most important modern networking concepts.

Traditional networking focuses on:

$$ Network\ Reachability $$

Modern networking focuses on:

$$ Application\ Experience $$

This transition changes how networks are designed entirely.

CLI Examples

Example SD-WAN Application Policy


policy
 application VoIP
  preferred-path MPLS
  backup-path Internet
 !

 application Office365
  preferred-path Internet
  backup-path MPLS
 !

Example SLA Monitoring


sla-class VOICE
 latency threshold 150
 jitter threshold 30
 loss threshold 1

Example DMVPN Spoke-to-Spoke


interface Tunnel0
 ip nhrp redirect
 ip nhrp shortcut
 tunnel mode gre multipoint
 tunnel protection ipsec profile DMVPN

CLI Output Example

Show SD-WAN Path Statistics 

Site-ID: London-Store-44

Application: VoIP
Preferred Path: MPLS
Current Latency: 42ms
Packet Loss: 0.2%
Jitter: 5ms
MOS Score: 4.3

Backup Path: Internet
Current Latency: 88ms
Packet Loss: 1.1%
Jitter: 18ms
MOS Score: 3.7

Key Takeaways

  • Hybrid WAN combines MPLS and Internet transports.
  • SD-WAN introduces application-aware routing.
  • Business continuity becomes easier with overlay networking.
  • VoIP requires low latency and spoke-to-spoke optimization.
  • Internet-only WANs increase security complexity.
  • CCDE focuses on business-driven architecture decisions.
  • Application experience is now more important than raw topology.

Additional CCIE and Networking References

Final Thoughts

This case study represents a classic enterprise transition scenario from legacy MPLS-centric networking toward modern intent-driven WAN architecture.

The key lesson is not that SD-WAN automatically replaces MPLS.

The real lesson is:

$$ Modern\ WANs = Application\ Experience + Business\ Continuity + Operational\ Agility $$

That mindset is exactly what the CCDE exam is designed to evaluate.

By at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Featured Post

How HMT Watches Lost the Time: A Deep Dive into Disruptive Innovation Blindness in Indian Manufacturing

The Rise and Fall of HMT Watches: A Story of Brand Dominance and Disruptive Innovation Blindness The Rise and Fal...

Popular Posts