Question 660
At the Fairhaven managed-network provider, a publicly accessible port advertises detailed switch identity and management information unnecessarily. Which ongoing control best prevents this issue from recurring?
Explanation
Correct Answer
This control works beyond the initial remediation because it requires the team to review LLDP policy on ports repurposed for public access.
Incorrect Answers
That routine supports arp source binding stale, but the relevant ongoing risk requires the team to review LLDP policy on ports repurposed for public access. For the Fairhaven managed-network provider, the direct corrective action is to restrict LLDP advertisements or exposed TLVs on untrusted ports while preserving infrastructure discovery.
Audit multi-host port modes after desk topology changes. That safeguard would help prevent recurrence of: Port-level authorization can allow multiple devices once the port itself authenticates. The risk being reviewed here is instead: Unrestricted discovery data can reveal network topology and device details to unknown endpoints. The matching ongoing control is: Review LLDP policy on ports repurposed for public access.
Recheck ACL API and CLI syntax with firmware changes is not the primary recurring safeguard for this problem. The team should review LLDP policy on ports repurposed for public access. For the Fairhaven managed-network provider, the direct corrective action is to restrict LLDP advertisements or exposed TLVs on untrusted ports while preserving infrastructure discovery.