Question 130
A route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. Which cause-and-remedy pairing reflects the observed problem?
Explanation
Correct Answer
Because mPLS relies on selected underlay transport reachability and policy eligibility, the best response is to restore the required transport route and inspect label-signaling and next-hop state. A reviewer can close the technical case only after confirming that the transport endpoint again resolves and a labeled probe succeeds.
Incorrect Answers
The proposed principle concerns another network fault: Label stack changes can be legitimate parts of LSP forwarding design. Here, mPLS relies on selected underlay transport reachability and policy eligibility. The most direct correction is to restore the required transport route and inspect label-signaling and next-hop state, confirmed by the transport endpoint again resolves and a labeled probe succeeds.
That result would be useful for a different failure, namely: A provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state. The current case specifically calls for: Restore the required transport route and inspect label-signaling and next-hop state. The required observed result is: The transport endpoint again resolves and a labeled probe succeeds.
This response would target a different source scenario: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. It cannot establish the current acceptance requirement, which is: The transport endpoint again resolves and a labeled probe succeeds. The relevant action is: Restore the required transport route and inspect label-signaling and next-hop state.