352-001 · Question #797
Which MPLS TE design consideration is true?
The correct answer is C. MPLS TE optimizes the routing of IP traffic, given the constraints imposed by backbone capacity. The core purpose of MPLS Traffic Engineering is to route IP traffic optimally across a backbone by enforcing constraints such as available bandwidth and administrative policy.
Question
Which MPLS TE design consideration is true?
Options
- AMPLS TE replaces LDP and the dependency of the IGP to identify the best path.
- BMPLS TE provides link and node protection
- CMPLS TE optimizes the routing of IP traffic, given the constraints imposed by backbone capacity
- DMPLS TE requires Layer 3 VPN full-mesh topology deployment
How the community answered
(34 responses)- A3% (1)
- B12% (4)
- C82% (28)
- D3% (1)
Why each option
The core purpose of MPLS Traffic Engineering is to route IP traffic optimally across a backbone by enforcing constraints such as available bandwidth and administrative policy.
MPLS TE does not replace LDP; both can coexist on the same network, with LDP handling label distribution for standard forwarding and RSVP-TE handling TE tunnel signaling.
Link and node protection is provided by MPLS TE Fast Reroute (FRR), which is an optional feature built on top of TE - protection is not an inherent characteristic of MPLS TE itself.
MPLS TE uses RSVP-TE to signal explicit Label Switched Paths (LSPs) that follow constraint-based routes computed by CSPF, allowing traffic to be placed on paths that satisfy capacity and policy constraints rather than just the IGP shortest path. This optimization of traffic placement relative to backbone capacity is the fundamental design goal of MPLS TE.
MPLS TE operates independently of L3 VPN topology; it can be used with hub-and-spoke, partial-mesh, or any other VPN topology and does not mandate full-mesh deployment.
Concept tested: MPLS Traffic Engineering constraint-based routing purpose
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_te/configuration/xe-16/mp-te-xe-16-book/mp-te-overview.html
Topics
Community Discussion
No community discussion yet for this question.