Question 460
At the Greystone regional network integrator, a second-tier managed switch loses FortiLink after its parent switch is replaced without preserving the intended ISL. Which setting or practice should be reviewed in future?
Explanation
Correct Answer
After implementation, the team should document every downstream dependency when replacing an upstream switch as the appropriate recurring safeguard against the identified issue.
Incorrect Answers
Reassess topology only when availability requirements grow. That safeguard would help prevent recurrence of: A simple managed site can be operated without unnecessary high-availability interconnections. The risk being reviewed here is instead: Second-tier management depends on the operational first-tier inter-switch path. The matching ongoing control is: Document every downstream dependency when replacing an upstream switch.
The suggested preventive check is: Forecast FortiLink address capacity before fleet expansion. Its technical scope concerns: Switch discovery and controller communication require nonconflicting usable management addresses. This question asks how to sustain control over: Second-tier management depends on the operational first-tier inter-switch path. The more targeted safeguard is: Document every downstream dependency when replacing an upstream switch.
Document control-plane visibility versus tenant access boundaries. That safeguard would help prevent recurrence of: Physical managed FortiSwitch inventory may reside in the controlling VDOM rather than every tenant. The risk being reviewed here is instead: Second-tier management depends on the operational first-tier inter-switch path. The matching ongoing control is: Document every downstream dependency when replacing an upstream switch.