352-001 · Question #726
A large enterprise customer has more than 300 worldwide locations, each with at least two different WAN connections to their five regional data centers across US, Europe, and Asia. These data…
The correct answer is B. Use LISP over the current WAN. LISP separates endpoint identity from location and enables centralized, policy-driven application path selection from the data center, avoiding per-site configuration across 300+ locations.
Question
A large enterprise customer has more than 300 worldwide locations, each with at least two different WAN connections to their five regional data centers across US, Europe, and Asia. These data centers offer different application services and work as primary, with a remote data center as backup. You must provide a solution to securely select the traffic path for specific applications based on an IT policy. Which solution allows the easiest management of the path decision from the data center sites?
Options
- AApply policy-based routing at each remote site
- BUse LISP over the current WAN
- CSet up each center with its own AS and use BGP AS-PATH prepend configuration
- DAdd Cisco MPLS TE devices in the data centers and activate Cisco MPLS TE
How the community answered
(48 responses)- A19% (9)
- B67% (32)
- C6% (3)
- D8% (4)
Why each option
LISP separates endpoint identity from location and enables centralized, policy-driven application path selection from the data center, avoiding per-site configuration across 300+ locations.
Policy-based routing at each remote site requires individual route-map and ACL configuration on every one of the 300+ devices, creating massive operational overhead and no central management point.
LISP (Locator/ID Separation Protocol) allows the data centers to act as map servers and proxy tunnel routers, centrally controlling how remote site traffic is steered toward specific application services based on IT policy without touching individual branch device configs. This centralized control model scales to hundreds of sites because path decisions are pushed from the data center tier rather than requiring configuration on each remote device.
BGP AS-PATH prepend influences inbound path preference for eBGP peers but does not support granular, application-aware traffic steering based on IT policy.
Cisco MPLS TE requires adding specialized label-switching hardware and configuring traffic engineering tunnels throughout the WAN path, making it operationally impractical at this scale.
Concept tested: LISP centralized application-aware path policy management
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_lisp/configuration/xe-3s/irl-xe-3s-book.html
Topics
Community Discussion
No community discussion yet for this question.