Question 740
A core network change board wants to avoid: 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. Which ongoing safeguard fits best?
Explanation
Correct Answer
Retest primary and backup preference whenever CE prefixes change. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.
Incorrect Answers
Inspect per-VRF service-label mapping after platform or route-policy changes. That is a sensible control for ANOTHER scenario: An L3VPN PE advertises a VPNv4 route but the egress fails to associate the received VPN label with the correct customer VRF, causing the route to appear in the wrong context. It is less targeted to this issue than: Retest primary and backup preference whenever CE prefixes change.
Require overlapping-address negative tests before new VPN attachments. That is a sensible control for ANOTHER scenario: Two customers use the same 10.10.0.0/16 prefix but a PE leaks VPNv4 routes into its global table, incorrectly merging their routing contexts. It is less targeted to this issue than: Retest primary and backup preference whenever CE prefixes change.
Test DR state when changing multicast LAN interfaces. That is a sensible control for ANOTHER scenario: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. It is less targeted to this issue than: Retest primary and backup preference whenever CE prefixes change.