Question 470
Following a supported configuration correction, the original issue was: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. Which observation verifies success?
Explanation
Correct Answer
Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them. This confirms the approved response: Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary. It is relevant because: CSC designs carry another provider's traffic through a backbone without exposing all downstream customer routes into the carrier core.
Incorrect Answers
Two test customers using the same group address receive only their own authorized source streams. This would validate ANOTHER scenario: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. The specific correction here is: Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.
A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes. This would validate ANOTHER scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. The specific correction here is: Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.
A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact. This would validate ANOTHER scenario: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. The specific correction here is: Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.