Question 720
A newly patched uplink reports an unexpected LLDP peer from a separate customer zone. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The paired action is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. This is the diagnostic or verification half of the requested TWO-step pair.
Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. Verify the action with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy. This step concerns SNMP and sFlow monitoring configuration and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. This step concerns PoE and LLDP-MED endpoint power coordination and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This step concerns FortiSwitch diagnostic commands and logs and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.