Question 480
To prevent recurrence of this provider network issue: A remote customer site can send packets toward the Internet exit in a shared services VRF but the exit has no return route for the private customer prefix. Which control should be retained?
Explanation
Correct Answer
Include forward and return path checks in shared-services acceptance. This helps prevent recurrence of the issue: A remote customer site can send packets toward the Internet exit in a shared services VRF but the exit has no return route for the private customer prefix. Acceptance evidence should be: An approved Internet test flow completes both directions without exposing other tenants' internal networks.
Incorrect Answers
Retest primary and backup preference whenever CE prefixes change. That is a sensible control for ANOTHER scenario: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. It is less targeted to this issue than: Include forward and return path checks in shared-services acceptance.
Include stale route and next-hop cleanup in VPN site migrations. That is a sensible control for ANOTHER scenario: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. It is less targeted to this issue than: Include forward and return path checks in shared-services acceptance.
Review RPL ownership and ring state during ring expansion. That is a sensible control for ANOTHER scenario: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring. It is less targeted to this issue than: Include forward and return path checks in shared-services acceptance.