Question 520
At the Zephyrhaven data network services firm, a tenant operator cannot see an unexported managed FortiSwitch in a nonroot VDOM and assumes the switch failed. Which setting or practice should be reviewed in future?
Explanation
Correct Answer
The team should document control-plane visibility versus tenant access boundaries. That recurring practice targets the same weakness, namely that physical managed FortiSwitch inventory may reside in the controlling VDOM rather than every tenant.
Incorrect Answers
Check documented QinQ feature exclusions before new tenant policies is not the primary recurring safeguard for this problem. The team should document control-plane visibility versus tenant access boundaries. For the Zephyrhaven data network services firm, the direct corrective action is to verify owning root VDOM controller scope and export the permitted resources rather than recreating the switch.
Maintain a tested FortiOS and FortiSwitchOS version matrix. That safeguard would help prevent recurrence of: Firmware version mismatches can break expected FortiLink and feature operation. The risk being reviewed here is instead: Physical managed FortiSwitch inventory may reside in the controlling VDOM rather than every tenant. The matching ongoing control is: Document control-plane visibility versus tenant access boundaries.
Audit island controller binding after HA or site migrations. That safeguard would help prevent recurrence of: Mixed FortiGate ownership within one routed FortiSwitch island violates the topology limitation. The risk being reviewed here is instead: Physical managed FortiSwitch inventory may reside in the controlling VDOM rather than every tenant. The matching ongoing control is: Document control-plane visibility versus tenant access boundaries.