Question 860
At the Maplehaven multisite IT support team, a desk port negotiates unexpectedly low speed following a patch-panel change. How should the organization sustain the improvement?
Explanation
Correct Answer
The team should run cable diagnostics after repeated CRC incidents. That recurring practice targets the same weakness, namely that copper faults can affect negotiation independently of Layer 2 configuration.
Incorrect Answers
Keep a version-specific diagnostic command reference. That safeguard would help prevent recurrence of: Controller-side diagnostic information can distinguish authorization management and link problems. The risk being reviewed here is instead: Copper faults can affect negotiation independently of Layer 2 configuration. The matching ongoing control is: Run cable diagnostics after repeated CRC incidents.
That routine supports fortilink island l2 span assumption, but the relevant ongoing risk requires the team to run cable diagnostics after repeated CRC incidents. For the Maplehaven multisite IT support team, the direct corrective action is to use the supported FortiSwitch cable test and physical interface counters before altering VLAN policies.
Monitor discovery protocol changes after uplink moves. That safeguard would help prevent recurrence of: Missing or altered discovery frames can prevent automatic topology association. The risk being reviewed here is instead: Copper faults can affect negotiation independently of Layer 2 configuration. The matching ongoing control is: Run cable diagnostics after repeated CRC incidents.