CCDE Enterprise Case Study Part 2 – Main Issues Facing Jacobs Enterprise Network
In this part of the CCDE enterprise architecture case study, we analyze one of the most important aspects of enterprise design interviews and CCDE practical examinations:
🎯 Identifying the REAL Business Problems
Many engineers focus immediately on:
- Routing protocols
- WAN links
- QoS policies
- Firewall rules
However, enterprise architects must first identify:
- Business pain points
- Operational bottlenecks
- Strategic limitations
- Long-term scalability issues
- Organizational inefficiencies
The question asks:
Which are the main issues facing Jacobs currently? (Choose two.)
- a. Business continuity ✅
- b. Excessive number of network providers ❌
- c. Multiple single points of failure for independent stores ❌
- d. Lack of VoIP system access for independent stores ❌
- e. No integration of Toolmate and independent store IT systems ✅
Table of Contents
- 1. Understanding the Enterprise Context
- 2. Why Business Continuity Is a Major Issue
- 3. Why Lack of IT Integration Is a Major Issue
- 4. Why Multiple Providers Are NOT the Main Problem
- 5. Why Independent Store SPOFs Are Acceptable
- 6. Why VoIP Access Is NOT a Requirement
- 7. Enterprise Architecture Thinking
- 8. Enterprise Networking Mathematics
- 9. Routing and WAN CLI Examples
- 10. Key Takeaways
- 11. Related Articles
1. Understanding the Enterprise Context
Before selecting answers in a CCDE scenario, the architect must evaluate:
- Business objectives
- Operational dependencies
- Revenue impact
- Technical limitations
- Organizational constraints
Jacobs currently operates:
- 203 Jacobs stores
- 78 Toolmate stores
- 102 Independent stores
This means:
$$ Total\\ Sites = 203 + 78 + 102 $$ $$ Total\\ Sites = 383 $$Managing 383 enterprise locations across multiple WAN providers and multiple business entities introduces significant architectural complexity.
Enterprise Complexity Formula
$$ Complexity \propto Sites + WANs + Applications + Policies + Acquisitions $$2. Why Business Continuity Is a Major Issue
Business continuity is one of the correct answers because Jacobs has multiple critical dependencies on the central Jacobs data center.
Critical Observations
- No disaster recovery data center exists
- No secondary active enterprise core exists
- Toolmate relies heavily on Jacobs DC
- VoIP systems are centralized
- HR and intranet systems are centralized
The documentation explicitly states:
Toolmate stores and online systems broker sales for Jacobs products and services which is seen as crucial to the Jacobs business model.
This means:
- The business depends on inter-DC communication
- The DCI is mission critical
- The Jacobs DC is a single operational dependency
💡 Critical CCDE Insight
Enterprise architects must identify:
- Revenue-generating dependencies
- Application dependencies
- Operational dependencies
The Jacobs DC is not just a technical component.
It is a business-critical operational dependency.
Failure Scenario Analysis
| Failure | Impact |
|---|---|
| DCI failure | Toolmate loses access to Jacobs services |
| Firewall failure | Inter-DC communication breaks |
| Jacobs DC outage | Large-scale business disruption |
| Call Manager failure | VoIP impact across enterprise |
Availability Mathematics
Single DC availability:
$$ Availability = 1 - Failure\\ Probability $$But with no DR:
$$ Business\\ Risk \uparrow $$because:
$$ Recovery\\ Dependency = Single\\ Site $$DCI Dependency
The architecture currently uses:
- Dual 1Gbps Layer 3 DCI links
- OSPF peering
- Firewall-based policy control
However:
- Firewalls are near CPU capacity
- Firewalls are approaching end of life
- Changes require dual approval processes
This introduces:
$$ Operational\\ Risk + Technical\\ Risk $$Code Example – DCI OSPF Peering
router ospf 100 network 10.255.0.0 0.0.255.255 area 0
router ospf 100 router-id 10.10.10.10 network 10.255.0.0 0.0.255.255 area 0 passive-interface default no passive-interface TenGigabitEthernet0/0 no passive-interface TenGigabitEthernet0/1
Why DCI Stability Is Critical
The DCI carries:
- Sales transactions
- VoIP traffic
- HR system access
- Intranet connectivity
- Application synchronization
Therefore:
$$ DCI = Mission\\ Critical $$3. Why Lack of IT Integration Is a Major Issue
The second correct answer is:
✅ No integration of Toolmate and independent store IT systems
This issue appears throughout the documentation repeatedly.
Evidence from the Case Study
- Toolmate operates separately
- Independent stores use legacy systems
- Separate WAN providers exist
- Separate routing domains exist
- Separate operational teams exist
The document explicitly states:
There is a current drive to rationalize and integrate the existing networks, reduce cost, and provide simplification across the compute and network infrastructure.
This is extremely important.
🎯 CCDE Exam Strategy
Whenever documentation explicitly says:
- “current drive”
- “strategic initiative”
- “business objective”
- “executive priority”
You should treat it as a major architectural issue.
Current Fragmentation Problems
| Area | Problem |
|---|---|
| WAN | Multiple MPLS providers |
| Routing | OSPF + EIGRP + BGP |
| Security | Firewall dependency |
| Operations | Dual change approvals |
| Applications | Partial integration only |
| Cloud | No unified strategy |
Operational Complexity Formula
$$ Operational\\ Complexity \propto Routing\\ Domains + Providers + Security\\ Policies + Change\\ Processes $$Business Impact of Poor Integration
- Slow operational changes
- Increased costs
- Poor scalability
- Inconsistent security
- Cloud migration difficulties
The enterprise is essentially operating:
$$ Three\\ Different\\ Networks $$instead of:
$$ One\\ Unified\\ Enterprise $$4. Why Multiple Providers Are NOT the Main Problem
This option is incorrect.
Why?
Multiple providers do increase:
- Operational complexity
- Vendor management
- Troubleshooting difficulty
However:
- No major outage is directly linked to providers
- No evidence suggests providers are failing
- No business complaint references provider count
💡 Important Architecture Principle
Not every complexity is a business problem.
CCDE focuses on:
- Business impact
- Strategic risk
- Operational pain
5. Why Independent Store SPOFs Are Acceptable
This answer is also incorrect.
The documentation clearly states:
Independent stores can suffer outages to the Jacobs DC for up to six business hours without significant impact to business.
This is extremely important.
The business has already accepted:
- Reduced resiliency
- Single WAN circuits
- Limited integration
Business Criticality Formula
$$ Resiliency \propto Business\\ Dependency $$Since independent stores use:
- Local payment systems
- Local telephony systems
- Independent operations
their architecture intentionally prioritizes:
$$ Low\\ Cost > High\\ Availability $$6. Why VoIP Access Is NOT a Requirement
This option is incorrect because:
- No requirement exists for independent stores to use VoIP
- Independent stores already use traditional telephony
- No operational pain is identified
CCDE questions often include distractors like this.
🎯 CCDE Exam Tip
Do NOT assume requirements.
Only use:
- Explicitly stated business requirements
- Explicitly stated technical limitations
- Explicitly stated operational concerns
7. Enterprise Architecture Thinking
This question teaches one of the most important enterprise architecture skills:
Identifying Root Problems
The real issues are:
- Lack of resiliency
- Lack of integration
- Operational inefficiency
- Aging infrastructure
NOT:
- Minor technical details
- Assumed future requirements
- Acceptable business tradeoffs
Architecture Decision Formula
$$ Correct\\ Answer = Business\\ Impact + Operational\\ Impact + Strategic\\ Importance $$8. Enterprise Networking Mathematics
Availability Formula
$$ Availability = \frac{MTBF}{MTBF + MTTR} $$Operational Delay Formula
$$ Delay = Approval + Change + Validation $$Enterprise Integration Complexity
$$ Complexity \propto Systems + Protocols + Vendors $$Business Dependency Formula
$$ Criticality \propto Revenue\\ Dependency $$9. Routing and WAN CLI Examples
Example – BGP Redistribution
router bgp 64556 redistribute ospf 1
router bgp 64556 neighbor 192.168.1.1 remote-as 65000 redistribute ospf 1 route-map MPLS-EXPORT
Example – VRRP Configuration
interface vlan100 vrrp 100 ip 10.1.1.254
interface vlan100 ip address 10.1.1.1 255.255.255.0 vrrp 100 ip 10.1.1.254 vrrp 100 priority 120 vrrp 100 preempt
Why VRRP Is Used
VRRP provides:
- Gateway redundancy
- Fast failover
- Operational simplicity
10. Key Takeaways
💡 Final Answer Summary
The correct answers are:
- ✅ Business continuity
- ✅ No integration of Toolmate and independent store IT systems
Why?
- The enterprise depends heavily on the Jacobs DC
- No DR strategy exists
- DCI dependencies are mission critical
- Infrastructure is fragmented
- Operations are inefficient
- Integration is incomplete
11. Related Articles
CCDE Case Study Series
- CCDE Enterprise Case Study Part 1 – Full Enterprise Architecture
- CCDE Enterprise Case Study Part 3: Improving Network Scalability and Reducing Operational Overhead
Related CCIE and Enterprise Networking Articles
- Complete MPLS L3VPN Configuration Guide
- Complete MPLS Traffic Engineering
- DMVPN Phase 3 Enhancing Scalability
- OSPF Area Types Explained
- Reliable BGP Peering
- Complete Cisco IOS XR Segment Routing
Final Conclusion
This question demonstrates the difference between:
- Network engineering thinking
- Enterprise architecture thinking
Network engineers often focus on:
- Protocols
- Links
- Configurations
Enterprise architects focus on:
- Business continuity
- Operational scalability
- Strategic integration
- Long-term transformation
That distinction is the foundation of CCDE-level design thinking.
No comments:
Post a Comment