Which two reasons for implementing Cisco MPLS TE in a service provider MPLS backbone are valid? (Choose two.)

Question

Accepted Answer

C. when Cisco MPLS TE is required to route different MPLS QoS service classes through different MPLS TE allows operators to constrain LSPs along explicit paths, enabling different QoS service classes to traverse physically separate routes with distinct bandwidth reservations and delay characteristics - a capability that IGP shortest-path routing alone cannot provide. This is a primary design driver for TE in multi-class service provider cores. D. when Cisco MPLS TE is required to reroute traffic within less than 1 second in case of a link MPLS TE Fast Reroute (FRR) pre-computes and pre-signals backup LSPs so traffic can be switched to an alternate path in under 50 milliseconds upon a link or node failure, far faster than waiting for IGP reconvergence to complete. This sub-second recovery SLA is a defining benefit of deploying MPLS TE.

Answer

A. when Cisco MPLS TE is a prerequisite for implementing RSVP in the backbone RSVP is a prerequisite signaling protocol that enables MPLS TE, not an outcome of it; you deploy RSVP because you need MPLS TE, not the reverse.

Answer

B. when Cisco MPLS TE is required to create backup paths independently from the IGP MPLS TE backup paths are not independent of the IGP topology - they rely on IGP extensions such as OSPF-TE or IS-IS-TE to flood TE link attributes used during path computation.

Answer

E. when Cisco MPLS TE can detect and react to neighbor failures faster than IGPs can Faster neighbor failure detection is the function of BFD (Bidirectional Forwarding Detection), not MPLS TE; MPLS TE relies on IGP or RSVP Hello mechanisms for failure awareness.

Which two reasons for implementing Cisco MPLS TE in a service provider MPLS backbone are valid? (Choose two.)

Question

Options

How the community answered

Why each option

Topics

Community Discussion