Question 190
A hypothetical customer planning meeting reports: A carrier WAN unintentionally advertises a customer VRF prefix into a different company's L3VPN. Which architectural weakness BEST accounts for this customer outcome?
Explanation
Correct Answer
A carrier WAN unintentionally advertises a customer VRF prefix into a different company's L3VPN. L3VPN segmentation depends on controlled per-VRF route distribution and route-target policy. Repair VRF membership and import/export route-target policy with explicit tenant separation. Routes and traffic are visible only in authorized VPN contexts during isolation tests.
Incorrect Answers
A carrier WAN unintentionally advertises a customer VRF prefix into a different company's L3VPN. Campus topology should match segmentation, scale, operations and resiliency requirements rather than a fixed diagram, whereas L3VPN segmentation depends on controlled per-VRF route distribution and route-target policy.
Access, provider edge and core router roles have distinct scale, control and service responsibilities, while L3VPN segmentation depends on controlled per-VRF route distribution and route-target policy.
Unmeasurable service promises cannot guide topology choice or objective acceptance testing, but L3VPN segmentation depends on controlled per-VRF route distribution and route-target policy.