Question 870
At the Cedarport managed-network provider, a standalone FortiSwitch has an unexpected default route causing application timeouts. Which underlying issue most directly explains this situation?
Explanation
Correct Answer
The strongest explanation is that routing decisions depend on active installed routes and reachable next hops. This accounts for the outcome and supports the action to inspect the supported routing table and selected next-hop rather than changing VLAN definitions immediately.
Incorrect Answers
The offered principle is: A healthy port can be intentionally blocked by spanning tree to prevent a loop. In the source material it is associated with: A healthy port can be intentionally blocked by spanning tree to prevent a loop. This case has a different controlling cause: Routing decisions depend on active installed routes and reachable next hops. Its keyed mechanism is: Routing decisions depend on active installed routes and reachable next hops.
Management associations are tied to switch serial identity and cannot be assumed transferable. That is not the mechanism that accounts for the stated failure at the Cedarport managed-network provider.
Although fortiLink over Layer 3 does not support NAT between the FortiSwitch and controller, the presented symptoms do not support that as the primary cause; they indicate that routing decisions depend on active installed routes and reachable next hops. For the Cedarport managed-network provider, the direct corrective action is to inspect the supported routing table and selected next-hop rather than changing VLAN definitions immediately.