Question 510
At the Thornfield managed-network provider, a tenant design enables DHCP snooping directly on a FortiSwitch QinQ port and expects normal behavior. Which underlying issue most directly explains this situation?
Explanation
Correct Answer
The strongest explanation is that fortiSwitch QinQ mode has documented restrictions on several Layer 2 inspection features. This accounts for the outcome and supports the action to move that inspection to a supported boundary because DHCP snooping is not supported with QinQ.
Incorrect Answers
The offered principle is: Multi-VDOM shared ports expose a defined subset of switch security capabilities. In the source material it is associated with: Multi-VDOM shared ports expose a defined subset of switch security capabilities. This case has a different controlling cause: FortiSwitch QinQ mode has documented restrictions on several Layer 2 inspection features. Its keyed mechanism is: FortiSwitch QinQ mode has documented restrictions on several Layer 2 inspection features.
Management-plane routing and access controls are separate from user data forwarding. That is not the mechanism that accounts for the stated failure at the Thornfield managed-network provider.
Although downstream management discovery depends on operational and permitted upstream switching paths, the presented symptoms do not support that as the primary cause; they indicate that fortiSwitch QinQ mode has documented restrictions on several Layer 2 inspection features. For the Thornfield managed-network provider, the direct corrective action is to move that inspection to a supported boundary because DHCP snooping is not supported with QinQ.