352-001 · Question #132
You are creating a network design that will influence the traffic path across the MPLS core on a virtual private LAN. Which parameter is included in your design to manage the traffic?
The correct answer is A. Deploy MPLS traffic engineering and modify the path using the preferred path.. The question tests how MPLS Traffic Engineering is used to influence the forwarding path for VPLS traffic across an MPLS core.
Question
You are creating a network design that will influence the traffic path across the MPLS core on a virtual private LAN. Which parameter is included in your design to manage the traffic?
Options
- ADeploy MPLS traffic engineering and modify the path using the preferred path.
- BDeploy MPLS traffic engineering and modify the path using auto-route, static routing, or PBR.
- CCreate an MPLS traffic engineering tunnel and modify the path using a static route.
- DCreate an MPLS traffic engineering tunnel and modify the path using auto-route announce.
How the community answered
(35 responses)- A43% (15)
- B6% (2)
- C14% (5)
- D37% (13)
Why each option
The question tests how MPLS Traffic Engineering is used to influence the forwarding path for VPLS traffic across an MPLS core.
In a VPLS deployment over an MPLS core, MPLS Traffic Engineering (TE) tunnels can be used to steer pseudowire traffic along specific paths. The preferred path feature allows an operator to explicitly bind a VPLS virtual forwarding instance (VFI) pseudowire to a specific TE tunnel, directly controlling which path the VPLS traffic takes through the core. This is the correct mechanism because preferred path is the parameter specifically designed to associate VPLS pseudowires with TE tunnels.
Auto-route, static routing, and PBR are mechanisms for directing IP unicast traffic into TE tunnels and are not used to manage VPLS pseudowire path selection.
A static route can direct IP traffic into a TE tunnel but cannot control the path of VPLS pseudowire traffic within the MPLS core.
Auto-route announce advertises TE tunnel endpoints into the IGP for IP routing purposes and is not the parameter used to bind VPLS pseudowires to specific TE tunnels.
Concept tested: MPLS TE preferred path for VPLS traffic management
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_l2_vpns/configuration/xe-16/mp-l2-vpns-xe-16-book/mp-vpls-over-mpls-te.html
Topics
Community Discussion
No community discussion yet for this question.