Question 400
To prevent recurrence of this provider network issue: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. Which control should be retained?
Explanation
Correct Answer
Maintain an inventory of per-hop encapsulation support and interworking validation tests. This helps prevent recurrence of the issue: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. Acceptance evidence should be: A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable.
Incorrect Answers
Check subscriber access-media type before selecting aggregation hardware and automation profiles. That is a sensible control for ANOTHER scenario: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. It is less targeted to this issue than: Maintain an inventory of per-hop encapsulation support and interworking validation tests.
Review optical and routing timer interaction in multilayer failure drills. That is a sensible control for ANOTHER scenario: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. It is less targeted to this issue than: Maintain an inventory of per-hop encapsulation support and interworking validation tests.
Require postboot image attestation and rollback readiness in change acceptance. That is a sensible control for ANOTHER scenario: After an IOS XE image update, the route processor boots but a router retains an old package set because the team updated the boot variable without verifying install mode. It is less targeted to this issue than: Maintain an inventory of per-hop encapsulation support and interworking validation tests.