Question 780
At the Northport managed-network provider, an engineer creates a packet capture filter for a retired endpoint IP and concludes the FortiSwitch forwards nothing. Which ongoing control best prevents this issue from recurring?
Explanation
Correct Answer
The needed prevention is to confirm address and VLAN bindings at the start of a capture. It directly sustains the original change to validate the endpoint's current IP and correct the capture filter before diagnosing a link fault.
Incorrect Answers
That routine supports tcp retransmission analysis, but the relevant ongoing risk requires the team to confirm address and VLAN bindings at the start of a capture. For the Northport managed-network provider, the direct corrective action is to validate the endpoint's current IP and correct the capture filter before diagnosing a link fault.
Test upgrade compatibility in a staging environment first is not the primary recurring safeguard for this problem. The team should confirm address and VLAN bindings at the start of a capture. For the Northport managed-network provider, the direct corrective action is to validate the endpoint's current IP and correct the capture filter before diagnosing a link fault.
Audit management VLAN changes on inter-switch trunks. That safeguard would help prevent recurrence of: User VLAN forwarding can survive while the specific controller management path is broken. The risk being reviewed here is instead: An overly narrow or outdated filter can hide valid traffic from the analyst. The matching ongoing control is: Confirm address and VLAN bindings at the start of a capture.