Question 490
At the Dunbridge data network services firm, a multi-tenant port design depends on DHCP snooping directly on FortiSwitch ports exported for VDOM sharing. Which explanation best accounts for the concern?
Explanation
Correct Answer
The strongest explanation is that the documented shared FortiSwitch port feature set does not include DHCP snooping. This accounts for the outcome and supports the action to choose a supported topology or alternate guardrail because DHCP snooping is unavailable on shared ports.
Incorrect Answers
Although the GUI does not expose every cross-VDOM native VLAN assignment supported by FortiOS, the presented symptoms do not support that as the primary cause; they indicate that the documented shared FortiSwitch port feature set does not include DHCP snooping. For the Dunbridge data network services firm, the direct corrective action is to choose a supported topology or alternate guardrail because DHCP snooping is unavailable on shared ports.
The offered principle is: Two physical uplinks to independent peers are not a coordinated aggregate by default. In the source material it is associated with: Two physical uplinks to independent peers are not a coordinated aggregate by default. This case has a different controlling cause: The documented shared FortiSwitch port feature set does not include DHCP snooping. Its keyed mechanism is: The documented shared FortiSwitch port feature set does not include DHCP snooping.
A linear FortiLink chain has single-link failure dependencies for devices beyond the break. That may occur elsewhere, but the evidence at the Dunbridge data network services firm instead points to the fact that the documented shared FortiSwitch port feature set does not include DHCP snooping.