Fortinet NSE5_FSW_AD-7.6 Practice Test 2
Question 10
An installer assumes any FortiSwitch port will auto-discover FortiLink despite model-specific discovery defaults. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Latency-sensitive flows improve under representative load while other business services remain functional.
- Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
- Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
Explanation
Correct Answer
C: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:Latency-sensitive flows improve under representative load while other business services remain functional. This result relates to Egress priority scheduling and congestion visibility, 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.
B:Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. This result relates to Storm-control thresholds and broadcast containment, 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: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: Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
Question 11
Guest users can browse the internet but should not access each other's devices on the same Wi-Fi-to-switch VLAN. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
- Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
Explanation
Correct Answer
C:Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured. The paired action is: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
Incorrect Answers
A:Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. These observations are applicable to Layer 2 MAC-learning and forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
B:Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. These observations are applicable to NAC dynamic port policy device classification, but would not isolate the main failure first. The decisive evidence is: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
D:Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. These observations are applicable to FortiSwitch 802.1X port-based authentication, but would not isolate the main failure first. The decisive evidence is: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
Question 12
A gigabit analyzer drops mirrored frames from multiple saturated 10G sources and the engineer misreads the capture as true link loss. 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.
- The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
- Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution.
- The analyzer receives the intended copies while production forwarding remains unchanged.
Explanation
Correct Answer
D:The analyzer receives the intended copies while production forwarding remains unchanged. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic.
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 analyzer receives the intended copies while production forwarding remains unchanged.
B:The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. This result relates to FortiLink discovery failure and physical uplink path, not the acceptance condition under test. The relevant result is: The analyzer receives the intended copies while production forwarding remains unchanged.
C:Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution. This result relates to Dynamic ARP inspection with DHCP snooping bindings, not the acceptance condition under test. The relevant result is: The analyzer receives the intended copies while production forwarding remains unchanged.
Question 13
A network map says a printer connects to switch A but its MAC is learned on switch C's access port. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
- Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
Explanation
Correct Answer
D: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.
Incorrect Answers
A: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: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
B:Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This action is relevant to Managed switch port statistics and counter analysis, not the controlling requirement in this case. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The targeted response is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
C:Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This action is relevant to FortiLink transport over nontrivial L2 or L3 paths, not the controlling requirement in this case. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The targeted response is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
Question 14
A voice ACL blocks the signaling network because a new permit rule was placed after a broader deny. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
- Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
- Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
- Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
Explanation
Correct Answer
B:Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied. The paired action is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
Incorrect Answers
A:Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. These observations are applicable to RADIUS change of authorization and applied session policy, but would not isolate the main failure first. The decisive evidence is: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
C:Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. These observations are applicable to IGMP snooping and multicast receivers, but would not isolate the main failure first. The decisive evidence is: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
D:Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. These observations are applicable to FortiSwitch 802.1X port-based authentication, but would not isolate the main failure first. The decisive evidence is: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
Question 15
A FortiGate cluster has HA heartbeats but only the failed member owns a working FortiLink path. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
- A controlled failure test restores approved management and access connectivity through the designed redundant path.
- Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
Explanation
Correct Answers
A:Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. Verify the action with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. This is the configuration or remediation half of the requested TWO-step pair.
E:Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. The paired action is: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. This step concerns Discovered versus authorized FortiSwitch state and is not part of the required paired solution. The correct action and evidence are: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
C:Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. This step concerns Multi-tenant change verification and rollback and is not part of the required paired solution. The correct action and evidence are: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
D:A controlled failure test restores approved management and access connectivity through the designed redundant path. This step concerns FortiLink HA and MCLAG topology faults and is not part of the required paired solution. The correct action and evidence are: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
Question 16
The active FortiGate is restarted before the team verifies how managed-switch authorization behaves on the peer. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.
- Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
- Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
- Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
- Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
Explanation
Correct Answers
A:Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. Verify the action with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. This is the configuration or remediation half of the requested TWO-step pair.
E:Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. The paired action is: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. This step concerns Managed switch configuration synchronization and is not part of the required paired solution. The correct action and evidence are: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
C:Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
D:Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. This step concerns Firmware and lifecycle preparation for FortiSwitch and is not part of the required paired solution. The correct action and evidence are: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
Question 17
A high-power access point boots but shuts down once its additional radio activates. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
- Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
Explanation
Correct Answer
A:Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events. Not every FortiSwitch model or port supports identical PoE allocation or every attached device's peak draw. The paired action is: Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
Incorrect Answers
B:Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. These observations are applicable to IGMP snooping and multicast receivers, but would not isolate the main failure first. The decisive evidence is: Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
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 power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
D:Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. These observations are applicable to Static route and default gateway validation, but would not isolate the main failure first. The decisive evidence is: Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
Question 18
A receiver moved to another port stops getting a stream because its membership reports are not observed. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
- Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
- An unexpected additional device is restricted or signaled without knocking out approved business equipment.
- Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
- Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
Explanation
Correct Answers
A:Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. Verify the action with: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. This is the configuration or remediation half of the requested TWO-step pair.
E:Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. The paired action is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. This step concerns Layer 2 MAC-learning and forwarding decisions and is not part of the required paired solution. The correct action and evidence are: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. Together with: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
C:An unexpected additional device is restricted or signaled without knocking out approved business equipment. This step concerns Port MAC learning-limit and violation controls and is not part of the required paired solution. The correct action and evidence are: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. Together with: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
D:Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. This step concerns FortiGate managed FortiSwitch VLAN interface placement and is not part of the required paired solution. The correct action and evidence are: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. Together with: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
Question 19
The network plan assumes every port-security feature is supported for a multi-VDOM shared port on every model. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
- Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
- Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
- Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
Explanation
Correct Answers
C:Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release. The paired action is: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. This is the diagnostic or verification half of the requested TWO-step pair.
D:Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release. Verify the action with: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization. This step concerns FortiSwitch security profile application and precedence and is not part of the required paired solution. The correct action and evidence are: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. Together with: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
B:Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. This step concerns FortiLink management interface provisioning and is not part of the required paired solution. The correct action and evidence are: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. Together with: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
E:Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. This step concerns FortiGate VDOM-based FortiSwitch tenant assignment and is not part of the required paired solution. The correct action and evidence are: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. Together with: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
Question 20
A guest laptop marks all packets EF and monopolizes a priority queue on a shared access port. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
- Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.
- Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
- The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
Explanation
Correct Answer
C:Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently.
Incorrect Answers
A:Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision. This result relates to QinQ outer and inner VLAN tenant mapping, not the acceptance condition under test. The relevant result is: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
B:Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. This result relates to PoE and LLDP-MED endpoint power coordination, not the acceptance condition under test. The relevant result is: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
D: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: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.