Question 450
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A migration from SR-MPLS to SRv6 requires a border gateway to translate service context, but the design treats label and SID semantics as identical. Which observable result most directly verifies that this network issue was resolved?
Explanation
Correct Answer
For this scenario, the observed situation is: A migration from SR-MPLS to SRv6 requires a border gateway to translate service context, but the design treats label and SID semantics as identical. The most directly supported response is: Implement documented interworking gateway behavior preserving VPN identifiers and forwarding intent. Technical basis: SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. Evidence of success: A cross-domain service packet traverses the gateway and retains correct customer isolation. Ongoing protection: Test bidirectional VPN connectivity and tenant separation during mixed-domain migration.
Incorrect Answers
The proposed test would be relevant to: LDP and segment routing may coexist during migration but require compatible FEC and SID mapping mechanisms. The reported problem follows from: SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. Instead, verify: A cross-domain service packet traverses the gateway and retains correct customer isolation.
That observation tests a different mechanism: Path computation depends on the attributes advertised or otherwise provided to its topology database. It cannot establish this case, whose mechanism is: SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. The needed verification is: A cross-domain service packet traverses the gateway and retains correct customer isolation.
That observation tests a different mechanism: RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. It cannot establish this case, whose mechanism is: SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. The needed verification is: A cross-domain service packet traverses the gateway and retains correct customer isolation.