Question 430
At the Glenbrook regional network integrator, an organization plans switch-controller NAC enforcement on a remote FortiLink over Layer 3 island. Which explanation best accounts for the concern?
Explanation
Correct Answer
The situation shows that fortiSwitch NAC is not supported in the documented FortiLink over Layer 3 island design, rather than merely a monitoring or presentation issue. Remediation is to choose a supported deployment or alternate enforcement design rather than assuming FortiSwitch NAC functions over Layer 3.
Incorrect Answers
The offered principle is: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. In the source material it is associated with: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. This case has a different controlling cause: FortiSwitch NAC is not supported in the documented FortiLink over Layer 3 island design. Its keyed mechanism is: FortiSwitch NAC is not supported in the documented FortiLink over Layer 3 island design.
Although separate VLAN labels do not independently guarantee tenant Layer 3 policy isolation, the presented symptoms do not support that as the primary cause; they indicate that fortiSwitch NAC is not supported in the documented FortiLink over Layer 3 island design. For the Glenbrook regional network integrator, the direct corrective action is to choose a supported deployment or alternate enforcement design rather than assuming FortiSwitch NAC functions over Layer 3.
Manual per-device setup increases configuration drift and delays consistent provisioning. That may occur elsewhere, but the evidence at the Glenbrook regional network integrator instead points to the fact that fortiSwitch NAC is not supported in the documented FortiLink over Layer 3 island design.