Question 760
At the Lakehaven data network services firm, users blame FortiSwitch QoS for a slow application but no one has confirmed packet loss or retransmission. Which setting or practice should be reviewed in future?
Explanation
Correct Answer
The team should collect baseline retransmission measurements for critical applications. That recurring practice targets the same weakness, namely that application slowness cannot be attributed to switching congestion without traffic-level evidence.
Incorrect Answers
Confirm address and VLAN bindings at the start of a capture is not the primary recurring safeguard for this problem. The team should collect baseline retransmission measurements for critical applications. For the Lakehaven data network services firm, the direct corrective action is to capture the appropriate TCP flow and correlate retransmissions with interface error and queue counters.
Monitor switch system resource trends during peak hours. That safeguard would help prevent recurrence of: Control-plane resource contention can cause slow management and protocol updates without saturated data links. The risk being reviewed here is instead: Application slowness cannot be attributed to switching congestion without traffic-level evidence. The matching ongoing control is: Collect baseline retransmission measurements for critical applications.
Record MAC movement information during desk-move incidents. That safeguard would help prevent recurrence of: Layer 2 forwarding learns MAC locations dynamically rather than from static room labels alone. The risk being reviewed here is instead: Application slowness cannot be attributed to switching congestion without traffic-level evidence. The matching ongoing control is: Collect baseline retransmission measurements for critical applications.