Question 770
For a multi-tenant data transport provider, operators addressed: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. What is the strongest acceptance evidence?
Explanation
Correct Answer
A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments. This confirms the approved response: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics. It is relevant because: Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.
Incorrect Answers
Policy state selects the highest eligible preference candidate and traffic follows its listed segments. This would validate ANOTHER scenario: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. The specific correction here is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.
The PCC installs only approved delegated candidates and reports their active state back to the PCE. This would validate ANOTHER scenario: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. The specific correction here is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.
RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic. This would validate ANOTHER scenario: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. The specific correction here is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.