Fortinet NSE5_FSW_AD-7.6 Practice Test 78
Question 770
An administrator enables DHCP snooping without checking whether the expected relay path is exempted correctly. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
- Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
- Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
- Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
Explanation
Correct Answer
A: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.
Incorrect Answers
B:Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. This action is relevant to DHCP server allowlist and Option 82 validation, not the controlling requirement in this case. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay. The targeted response is: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
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: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
D:Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. This action is relevant to NAC dynamic port policy device classification, not the controlling requirement in this case. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. The targeted response is: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
Question 771
An office printer sends DHCP Discover repeatedly but never sees an Offer after a trust-boundary change. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
- A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
- The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
- Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions.
Explanation
Correct Answer
C:The exact dropped direction or incorrect address binding is evidenced before changing a security feature. A DHCP lease failure can originate at the client, switch, relay or server; capturing at one side alone is not always conclusive.
Incorrect Answers
A: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 exact dropped direction or incorrect address binding is evidenced before changing a security feature.
B:A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior. This result relates to Config backup and firmware inventory evidence, not the acceptance condition under test. The relevant result is: The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
D:Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions. This result relates to FortiLink transport over nontrivial L2 or L3 paths, not the acceptance condition under test. The relevant result is: The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
Question 772
A distribution uplink carries VLAN 40 locally but the peer excludes VLAN 40 from its allowed list. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
- Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
- Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
Explanation
Correct Answer
D:Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The paired action is: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
Incorrect Answers
A:Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. These observations are applicable to Managed tenant troubleshooting across controller and access layer, but would not isolate the main failure first. The decisive evidence is: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
B:Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. These observations are applicable to PoE and LLDP-MED endpoint power coordination, but would not isolate the main failure first. The decisive evidence is: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
C:Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. These observations are applicable to FortiSwitch SVI routing and connected routes, but would not isolate the main failure first. The decisive evidence is: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
Question 773
A security role policy rejects sessions after a RADIUS change but no one examines switch authentication events. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
- Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.
- Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
- Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
Explanation
Correct Answer
D:Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. A log message without source device, time and relevant state is not adequate to prove root cause. Verify the action with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
Incorrect Answers
A:Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations. This action is relevant to VLAN security policy and quarantine actions, not the controlling requirement in this case. Quarantine must be enforced at the right switch and VLAN path; a security-alert label alone does not remove access. The targeted response is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
B:Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. This action is relevant to FortiLink HA and MCLAG topology faults, not the controlling requirement in this case. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone. The targeted response is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
C:Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This action is relevant to FortiGate one-arm sniffer across managed switching, not the controlling requirement in this case. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The targeted response is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
Question 774
A core maintenance event disconnects one MCLAG peer link and the operator checks only client ping. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
- Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
- Both ends connect at compatible rates with stable errors and required throughput.
- Management control and authorized user traffic work over the direct connection without confusing them.
Explanation
Correct Answer
A:A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop. MCLAG requires peer coordination and correct downstream aggregation; it is not equivalent to connecting independent switches in parallel.
Incorrect Answers
B:Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade. This result relates to Firmware and lifecycle preparation for FortiSwitch, not the acceptance condition under test. The relevant result is: A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
C:Both ends connect at compatible rates with stable errors and required throughput. This result relates to Switch port speed and duplex commissioning, not the acceptance condition under test. The relevant result is: A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
D:Management control and authorized user traffic work over the direct connection without confusing them. This result relates to Single FortiGate and single FortiSwitch topology, not the acceptance condition under test. The relevant result is: A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
Question 775
A switch trunk is green but the second member carries no packets due to mismatched VLAN membership. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
- Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
- Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
- Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
- Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
Explanation
Correct Answers
B:Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. The paired action is: Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This is the diagnostic or verification half of the requested TWO-step pair.
E:Repair LACP member settings and physical port errors independently before increasing aggregate traffic. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. Verify the action with: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. This step concerns SNMP and sFlow monitoring configuration and is not part of the required paired solution. The correct action and evidence are: Repair LACP member settings and physical port errors independently before increasing aggregate traffic. Together with: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
C:Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. This step concerns BPDU guard on endpoint-facing ports and is not part of the required paired solution. The correct action and evidence are: Repair LACP member settings and physical port errors independently before increasing aggregate traffic. Together with: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
D:Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. This step concerns FortiSwitch split port breakout mode and is not part of the required paired solution. The correct action and evidence are: Repair LACP member settings and physical port errors independently before increasing aggregate traffic. Together with: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
Question 776
A printer is moved to a new patch panel but its MAC keeps appearing on an old trunk member. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
- Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
- Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
- Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
Explanation
Correct Answer
C:Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port. Verify the action with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
Incorrect Answers
A:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This action is relevant to FortiSwitch SVI routing and connected routes, not the controlling requirement in this case. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. The targeted response is: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
B:Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. This action is relevant to Capture and confidentiality limits in incident response, not the controlling requirement in this case. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. The targeted response is: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
D:Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. This action is relevant to Static route and default gateway validation, not the controlling requirement in this case. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. The targeted response is: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
Question 777
An unknown switch appears discovered after a contractor accidentally connected equipment to the FortiLink port. 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 incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
- Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
Explanation
Correct Answer
D:Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The paired action is: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
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 switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
B:Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters. These observations are applicable to QoS ingress classification and trust boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
C:Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy. These observations are applicable to FortiLink control and client VLAN transport separation, but would not isolate the main failure first. The decisive evidence is: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
Question 778
A switch has a supported breakout cable yet its configured phy-mode and child speeds do not match the attached peers. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
- The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
- All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
- Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.
Explanation
Correct Answer
C:All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model.
Incorrect Answers
A:Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. This result relates to FortiSwitch SVI routing and connected routes, not the acceptance condition under test. The relevant result is: All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
B: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: All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
D:Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN. This result relates to Layer 2 MAC-learning and forwarding decisions, not the acceptance condition under test. The relevant result is: All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
Question 779
A branch cascades managed switches but connects a ring without checking the supported FortiLink stacking design. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
- Every relevant VLAN converges without loops and redundant paths unblock only when needed.
- Only intended networks are reachable through the configured route and the return path remains valid.
Explanation
Correct Answer
B:Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane.
Incorrect Answers
A:Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. This result relates to FortiSwitch 802.1X port-based authentication, not the acceptance condition under test. The relevant result is: Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
C:Every relevant VLAN converges without loops and redundant paths unblock only when needed. This result relates to RPVST and supported STP mode interoperability, not the acceptance condition under test. The relevant result is: Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
D:Only intended networks are reachable through the configured route and the return path remains valid. This result relates to Static route and default gateway validation, not the acceptance condition under test. The relevant result is: Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
Question 780
Two MCLAG peers disagree on allowed client VLANs and the same client reaches different gateways depending on active link. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
- A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
- The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
Explanation
Correct Answer
B:A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation.
Incorrect Answers
A:Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. This result relates to FortiSwitch 802.1X port-based authentication, not the acceptance condition under test. The relevant result is: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
C:A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration. This result relates to Root guard and loop guard failure response, not the acceptance condition under test. The relevant result is: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
D:The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface. This result relates to FortiGate managed FortiSwitch VLAN interface placement, not the acceptance condition under test. The relevant result is: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.