Question 700
After addressing: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. Which recurring service assurance check is most useful?
Explanation
Correct Answer
Maintain validated micro-segment encoding templates per software release. This helps prevent recurrence of the issue: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. Acceptance evidence should be: A test packet advances through the micro-segment sequence and exits at the intended service SID.
Incorrect Answers
Test locator route advertisement whenever new SRv6 functions are provisioned. That is a sensible control for ANOTHER scenario: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.
Check SR policy candidate selection and actual prefix steering in acceptance. That is a sensible control for ANOTHER scenario: A Segment Routing policy is installed but no customer route is steered to its binding SID, so measured traffic still follows ordinary IGP shortest paths. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.
Test the exact failure class named in each protection service objective. That is a sensible control for ANOTHER scenario: An MPLS TE bypass tunnel is administratively configured but the protected service shows no local protection because node protection was requested and only link protection is available. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.