Question 740
At the Stonehaven infrastructure service operator, a technician sees untagged traffic in an access-port capture and concludes the trunk is stripping every 802.1Q tag. How should the organization sustain the improvement?
Explanation
Correct Answer
For the Stonehaven infrastructure service operator, this maintenance action preserves the fix: record capture location when interpreting tagging evidence. It should be revisited as the workload evolves.
Incorrect Answers
The suggested preventive check is: Remove mirrors and delete expired sensitive captures after each incident. Its technical scope concerns: Network diagnostic captures may expose credentials or customer information unrelated to the incident. This question asks how to sustain control over: Access-port observations may not include tags that are present on inter-switch trunks. The more targeted safeguard is: Record capture location when interpreting tagging evidence.
That routine supports fortiswitch dhcp snooping binding table, but the relevant ongoing risk requires the team to record capture location when interpreting tagging evidence. For the Stonehaven infrastructure service operator, the direct corrective action is to capture on the trunk or a supported mirrored path where VLAN tags should be visible.
Monitor switch-controller process health and FortiLink sessions. That safeguard would help prevent recurrence of: A shared controller service problem can affect several managed devices at once. The risk being reviewed here is instead: Access-port observations may not include tags that are present on inter-switch trunks. The matching ongoing control is: Record capture location when interpreting tagging evidence.