Question 540
After addressing: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. Which recurring service assurance check is most useful?
Explanation
Correct Answer
Monitor delegated LSP ownership and controller reachability. This helps prevent recurrence of the issue: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. Acceptance evidence should be: The PCC installs only approved delegated candidates and reports their active state back to the PCE.
Incorrect Answers
Verify control-plane service route labels and locator reachability across interdomain handoffs. That is a sensible control for ANOTHER scenario: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. It is less targeted to this issue than: Monitor delegated LSP ownership and controller reachability.
Keep segment-type validation with path computation requests. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Monitor delegated LSP ownership and controller reachability.
Include TE database completeness checks during IGP maintenance. That is a sensible control for ANOTHER scenario: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. It is less targeted to this issue than: Monitor delegated LSP ownership and controller reachability.