Question 500
At the Eastbrook infrastructure service operator, a provider wants tenant-specific egress queue behavior on a VDOM-shared FortiSwitch port without checking support. How should the organization sustain the improvement?
Explanation
Correct Answer
The continuing safeguard is to review QoS model support for pooled tenant ports. It helps avoid the original condition: not all advanced switch features are available on shared tenant ports.
Incorrect Answers
The suggested preventive check is: Retest the shared-port feature matrix after version changes. Its technical scope concerns: Multi-VDOM shared ports expose a defined subset of switch security capabilities. This question asks how to sustain control over: Not all advanced switch features are available on shared tenant ports. The more targeted safeguard is: Review QoS model support for pooled tenant ports.
Review FortiLink interface assignment after firewall port migrations. That safeguard would help prevent recurrence of: A normal LAN interface does not automatically provide the control plane expected by FortiLink discovery. The risk being reviewed here is instead: Not all advanced switch features are available on shared tenant ports. The matching ongoing control is: Review QoS model support for pooled tenant ports.
Verify peer group configuration after firmware upgrades. That safeguard would help prevent recurrence of: Multi-chassis redundancy requires peers to exchange supported state over their inter-chassis connection. The risk being reviewed here is instead: Not all advanced switch features are available on shared tenant ports. The matching ongoing control is: Review QoS model support for pooled tenant ports.