Question 30
At the Tarnbridge managed-network provider, a provider handoff must transport several customer VLANs through one carrier service but engineers plan a simple access VLAN. Which underlying issue most directly explains this situation?
Explanation
Correct Answer
The evidence indicates that an ordinary access VLAN cannot preserve multiple independent customer VLAN identities across a provider handoff. The appropriate response is to evaluate supported QinQ VLAN stacking with correct outer tag and customer tag preservation and demonstrate that traffic from two customer VLANs crosses with distinct inner identifiers intact.
Incorrect Answers
Untagged frames enter the configured native VLAN rather than the VLAN assumed by the workstation. That is not the mechanism that accounts for the stated failure at the Tarnbridge managed-network provider.
The offered principle is: FortiLink aggregate requirements are topology-specific and ordinary client LAG assumptions may not apply. In the source material it is associated with: FortiLink aggregate requirements are topology-specific and ordinary client LAG assumptions may not apply. This case has a different controlling cause: An ordinary access VLAN cannot preserve multiple independent customer VLAN identities across a provider handoff. Its keyed mechanism is: An ordinary access VLAN cannot preserve multiple independent customer VLAN identities across a provider handoff.
Although IGMP snooping in one VLAN does not build a routed multicast path between subnet boundaries, the presented symptoms do not support that as the primary cause; they indicate that an ordinary access VLAN cannot preserve multiple independent customer VLAN identities across a provider handoff. For the Tarnbridge managed-network provider, the direct corrective action is to evaluate supported QinQ VLAN stacking with correct outer tag and customer tag preservation.