Question 330
At the Claremont network modernization program, a newly cabled FortiSwitch is discovered by FortiGate but stays unauthorized and does not receive production VLANs. Which underlying issue most directly explains this situation?
Explanation
Correct Answer
The strongest explanation is that fortiLink discovery does not itself guarantee the switch is authorized to receive configuration. This accounts for the outcome and supports the action to authorize the intended switch serial number through the FortiGate controller after confirming physical identity.
Incorrect Answers
The offered principle is: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. In the source material it is associated with: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. This case has a different controlling cause: FortiLink discovery does not itself guarantee the switch is authorized to receive configuration. Its keyed mechanism is: FortiLink discovery does not itself guarantee the switch is authorized to receive configuration.
A port exported to a pool may need a tenant claim step before use. That is not the mechanism that accounts for the stated failure at the Claremont network modernization program.
Although a stale VDOM port assignment leaves residual tenant access and operational ownership, the presented symptoms do not support that as the primary cause; they indicate that fortiLink discovery does not itself guarantee the switch is authorized to receive configuration. For the Claremont network modernization program, the direct corrective action is to authorize the intended switch serial number through the FortiGate controller after confirming physical identity.