Question 210
For a multi-tenant data transport provider, operators addressed: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. What is the strongest acceptance evidence?
Explanation
Correct Answer
Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked. This confirms the approved response: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points. It is relevant because: E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.
Incorrect Answers
A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers. This would validate ANOTHER scenario: A carrier backbone applies provider bridging with 802.1ah MAC-in-MAC but its edge fails to strip the outer backbone header, so customer switches receive unknown backbone addresses. The specific correction here is: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.
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: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.
An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree. This would validate ANOTHER scenario: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. The specific correction here is: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.