Question 400
At the Birchhaven data network services firm, a small office introduces a managed FortiSwitch but installs redundant layers and a second controller without a business requirement. Which setting or practice should be reviewed in future?
Explanation
Correct Answer
For the Birchhaven data network services firm, this maintenance action preserves the fix: reassess topology only when availability requirements grow. It should be revisited as the workload evolves.
Incorrect Answers
Validate port-specific topology constraints before branch construction is not the primary recurring safeguard for this problem. The team should reassess topology only when availability requirements grow. For the Birchhaven data network services firm, the direct corrective action is to use the supported single FortiGate to single FortiSwitch FortiLink topology with clear uplink role.
Review FortiGate administrator roles each quarter. That safeguard would help prevent recurrence of: Excess controller privileges allow unintended changes to managed switch configurations. The risk being reviewed here is instead: A simple managed site can be operated without unnecessary high-availability interconnections. The matching ongoing control is: Reassess topology only when availability requirements grow.
The suggested preventive check is: Review QoS model support for pooled tenant ports. Its technical scope concerns: Not all advanced switch features are available on shared tenant ports. This question asks how to sustain control over: A simple managed site can be operated without unnecessary high-availability interconnections. The more targeted safeguard is: Reassess topology only when availability requirements grow.