Fortinet NSE5_FSW_AD-7.6 Practice Test 18
Question 170
A new FortiSwitch is connected to a port that was not enabled as FortiLink on FortiGate. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
- Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
- Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
- Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
Explanation
Correct Answer
C:Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working. The paired action is: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
Incorrect Answers
A:Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. These observations are applicable to Config backup and firmware inventory evidence, but would not isolate the main failure first. The decisive evidence is: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
B:Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path. These observations are applicable to Single FortiGate and single FortiSwitch topology, but would not isolate the main failure first. The decisive evidence is: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
D:Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. These observations are applicable to FortiSwitch local packet-capture profile and filters, but would not isolate the main failure first. The decisive evidence is: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
Question 171
A new low storm-control threshold prevents otherwise healthy phones from obtaining DHCP leases. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
- The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
- Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
- An unexpected additional device is restricted or signaled without knocking out approved business equipment.
Explanation
Correct Answer
C:Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy.
Incorrect Answers
A:Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy. This result relates to IPv4 source guard and binding-based packet filtering, not the acceptance condition under test. The relevant result is: Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
B:The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors. This result relates to Optic compatibility and laser diagnostic evidence, not the acceptance condition under test. The relevant result is: Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
D:An unexpected additional device is restricted or signaled without knocking out approved business equipment. This result relates to Port MAC learning-limit and violation controls, not the acceptance condition under test. The relevant result is: Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
Question 172
A rogue laptop runs a DHCP server and offers incorrect gateways to clients on an access switch. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
- Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
- Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
- Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
- Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
Explanation
Correct Answers
B:Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. Verify the action with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. This is the configuration or remediation half of the requested TWO-step pair.
C:Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. The paired action is: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs. This step concerns Dynamic ARP inspection with DHCP snooping bindings and is not part of the required paired solution. The correct action and evidence are: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Together with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
D:Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Together with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
E:Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs. This step concerns BPDU guard on endpoint-facing ports and is not part of the required paired solution. The correct action and evidence are: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Together with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
Question 173
A new conference phone reboots when its extra display turns on despite a stable Ethernet link. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
- The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
- Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
Explanation
Correct Answers
D:Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The paired action is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. This is the diagnostic or verification half of the requested TWO-step pair.
E:Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. Verify the action with: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This step concerns QoS ingress classification and trust boundaries and is not part of the required paired solution. The correct action and evidence are: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. Together with: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
B:The suspect device is restricted without interrupting unrelated tenants and can be restored after review. This step concerns VLAN security policy and quarantine actions and is not part of the required paired solution. The correct action and evidence are: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. Together with: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
C:Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. This step concerns Stack failure isolation and switch-to-switch port roles and is not part of the required paired solution. The correct action and evidence are: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. Together with: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
Question 174
A tenant laptop obtains a valid lease but cannot reach services because its gateway interface belongs to another VDOM. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
- The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
Explanation
Correct Answers
A:Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2. The paired action is: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. This is the diagnostic or verification half of the requested TWO-step pair.
C:Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2. Verify the action with: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
B:Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. This step concerns FortiLink transport over nontrivial L2 or L3 paths and is not part of the required paired solution. The correct action and evidence are: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. Together with: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
D:Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. Together with: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
E:The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. This step concerns FortiLink discovery failure and physical uplink path and is not part of the required paired solution. The correct action and evidence are: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. Together with: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
Question 175
A PoE access switch can power legacy phones but sheds newer high-power access points after lunch. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path.
- Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
- Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
Explanation
Correct Answer
D:Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The paired action is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
Incorrect Answers
A:Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path. These observations are applicable to FortiLink split-interface and standby path design, but would not isolate the main failure first. The decisive evidence is: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
B:Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. These observations are applicable to Voice and data VLAN separation on shared access ports, but would not isolate the main failure first. The decisive evidence is: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
C:Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters. These observations are applicable to Capture-based DHCP and ARP path isolation, but would not isolate the main failure first. The decisive evidence is: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
Question 176
An engineer enables authorization during business hours without recognizing that the switch may reboot into FortiLink mode. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
- Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
- Both ends connect at compatible rates with stable errors and required throughput.
- Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
Explanation
Correct Answers
D:Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. Verify the action with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. This is the configuration or remediation half of the requested TWO-step pair.
E:Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. The paired action is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. This step concerns Managed tenant troubleshooting across controller and access layer and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
B:Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. This step concerns FortiGate VDOM-based FortiSwitch tenant assignment and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
C:Both ends connect at compatible rates with stable errors and required throughput. This step concerns Switch port speed and duplex commissioning and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
Question 177
A wireless bridge carries a FortiLink interswitch segment but does not forward expected discovery multicast frames. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
- Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
- Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
Explanation
Correct Answer
B:Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. Verify the action with: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
Incorrect Answers
A:Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. This action is relevant to Zero-touch provisioning and controller dependency checks, not the controlling requirement in this case. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. The targeted response is: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
C:Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. This action is relevant to Shared port multi-VDOM policy boundaries, not the controlling requirement in this case. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release. The targeted response is: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
D:Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. This action is relevant to VLAN access isolation and troubleshooting of membership, not the controlling requirement in this case. Link up and successful traffic in one VLAN do not prove every VLAN is correctly provisioned on the path. The targeted response is: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
Question 178
A new FortiSwitch is connected to a port that was not enabled as FortiLink on FortiGate. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
- Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
- Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Explanation
Correct Answer
A:The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working.
Incorrect Answers
B:Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications. This result relates to Capture and confidentiality limits in incident response, not the acceptance condition under test. The relevant result is: The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
C:Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. This result relates to FortiLink control and client VLAN transport separation, not the acceptance condition under test. The relevant result is: The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
D:The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. This result relates to FortiLink management interface provisioning, not the acceptance condition under test. The relevant result is: The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
Question 179
A trunk member reports no traffic despite all LACP member LEDs appearing green. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
- The expected known switch becomes authorized and synchronizes without accepting an unrelated device.
- The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
- The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
Explanation
Correct Answer
D:The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy.
Incorrect Answers
A:Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer. This result relates to DHCP snooping trust-boundary enforcement, not the acceptance condition under test. The relevant result is: The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
B:The expected known switch becomes authorized and synchronizes without accepting an unrelated device. This result relates to Controller authorization and pending-switch state, not the acceptance condition under test. The relevant result is: The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
C:The exact dropped direction or incorrect address binding is evidenced before changing a security feature. This result relates to Capture-based DHCP and ARP path isolation, not the acceptance condition under test. The relevant result is: The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
Question 180
A contractor requests a full week of unfiltered packet data from a production finance VLAN to diagnose one DHCP issue. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
- Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
- Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
- Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
Explanation
Correct Answer
B:Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. Verify the action with: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
Incorrect Answers
A:Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. This action is relevant to LLDP and MAC forwarding table extraction, not the controlling requirement in this case. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The targeted response is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
C:Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. This action is relevant to Config backup and firmware inventory evidence, not the controlling requirement in this case. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work. The targeted response is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
D:Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. This action is relevant to FortiSwitch security profile application and precedence, not the controlling requirement in this case. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. The targeted response is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.