352-001 · Question #543
A service provider is designing a new backbone based on an IGP and MPLS what are two valid reasons for implementing MPLS-TE as well? (Choose two)
The correct answer is C. MPLS-TE is required to route different MPLS QoS Service classes through different paths D. MPLS-TE is required to create backup paths independently from the IGP. MPLS-TE is justified in a service provider backbone when operators need to steer different QoS service classes over distinct paths or build explicit backup LSPs that bypass IGP shortest-path constraints.
Question
A service provider is designing a new backbone based on an IGP and MPLS what are two valid reasons for implementing MPLS-TE as well? (Choose two)
Options
- AMPLS-TE is required to reroute traffic within less than 1 second in case of a link failure inside the
- BMPLS-TE can detect and react to neighbor failures faster than IGPs can
- CMPLS-TE is required to route different MPLS QoS Service classes through different paths
- DMPLS-TE is required to create backup paths independently from the IGP
- EMPLS-TE is a prerequisite for implementing RSVP in the backbone
How the community answered
(29 responses)- A17% (5)
- B3% (1)
- C72% (21)
- E7% (2)
Why each option
MPLS-TE is justified in a service provider backbone when operators need to steer different QoS service classes over distinct paths or build explicit backup LSPs that bypass IGP shortest-path constraints.
Sub-second rerouting is delivered by the MPLS-TE Fast Reroute (FRR) feature, which is one capability within MPLS-TE rather than a standalone justification; alternative mechanisms such as IP FRR and Loop-Free Alternates can also achieve sub-second recovery without deploying full MPLS-TE.
MPLS-TE has no role in detecting neighbor failures faster than IGPs; rapid failure detection is the responsibility of BFD, which operates independently of whether MPLS-TE is present.
MPLS-TE allows operators to signal separate label-switched paths (LSPs) for different QoS service classes, enabling differentiated forwarding across distinct network paths - something a pure IGP cannot do because it routes all traffic on the same shortest path regardless of traffic type.
MPLS-TE uses RSVP-TE to establish explicit LSPs following administrator-defined paths that are completely independent of the IGP topology, enabling pre-provisioned backup tunnels that protect against link or node failures without relying on IGP reconvergence.
RSVP serves as the signaling protocol used by MPLS-TE to establish LSPs, so MPLS-TE depends on RSVP - not the reverse; RSVP can also be deployed for other purposes without MPLS-TE.
Concept tested: MPLS-TE use cases for QoS routing and path independence
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_te_core/configuration/xe-16/mp-te-core-xe-16-book/mpls-te-overview.html
Topics
Community Discussion
No community discussion yet for this question.