Fortinet NSE5_FSW_AD-7.6 Practice Test 22
Question 210
An old switch runs a different STP variant and the peer unexpectedly blocks the voice VLAN only. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.
- Every relevant VLAN converges without loops and redundant paths unblock only when needed.
- A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
- Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
Explanation
Correct Answer
B:Every relevant VLAN converges without loops and redundant paths unblock only when needed. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up.
Incorrect Answers
A:Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional. This result relates to Static port ACL forwarding decisions, not the acceptance condition under test. The relevant result is: Every relevant VLAN converges without loops and redundant paths unblock only when needed.
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: Every relevant VLAN converges without loops and redundant paths unblock only when needed.
D:Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path. This result relates to STP incident recovery with MAC flap evidence, not the acceptance condition under test. The relevant result is: Every relevant VLAN converges without loops and redundant paths unblock only when needed.
Question 211
An engineer enables authorization during business hours without recognizing that the switch may reboot into FortiLink mode. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
- Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
- Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
Explanation
Correct Answer
A: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.
Incorrect Answers
B: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: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
C:Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. This action is relevant to Firmware and lifecycle preparation for FortiSwitch, not the controlling requirement in this case. A successful image upload does not prove switch operation or controller compatibility after reboot. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
D:Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. This action is relevant to DHCP snooping trust-boundary enforcement, not the controlling requirement in this case. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
Question 212
A broad profile overrides a more specific guest device rule and grants a larger VLAN scope than planned. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
- Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
- Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
Explanation
Correct Answer
B:Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. The paired action is: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
Incorrect Answers
A:Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path. These observations are applicable to Static port ACL forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
C:Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load. These observations are applicable to Storm-control thresholds and broadcast containment, but would not isolate the main failure first. The decisive evidence is: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
D: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 port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
Question 213
A client manually assigns a privileged subnet address and tries to send packets through an access port. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
- Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
- Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
Explanation
Correct Answer
B:Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. Verify the action with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
Incorrect Answers
A: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: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
C:Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This action is relevant to Storm-control thresholds and broadcast containment, not the controlling requirement in this case. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. The targeted response is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
D:Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. This action is relevant to FortiSwitch multi-tier managed topology, not the controlling requirement in this case. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. The targeted response is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
Question 214
A branch switch appears offline although its uplink remains green because FortiLink management frames are blocked. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
- Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
- Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions.
- Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
Explanation
Correct Answers
A:Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working. Verify the action with: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial. This is the configuration or remediation half of the requested TWO-step pair.
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. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. This step concerns Config backup and firmware inventory evidence and is not part of the required paired solution. The correct action and evidence are: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. Together with: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
D:Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions. 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: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. Together with: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
E:Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. This step concerns FortiSwitch local packet-capture profile and filters and is not part of the required paired solution. The correct action and evidence are: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. Together with: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
Question 215
A cabinet with many cameras exceeds its switch PoE watt budget although enough physical ports exist. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
- Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
- Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
- Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
Explanation
Correct Answer
C: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
A:Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. These observations are applicable to MCLAG peer-link topology for managed access switches, 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.
B:Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. These observations are applicable to BPDU guard on endpoint-facing ports, 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:Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles. These observations are applicable to FortiLink HA and MCLAG topology faults, 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 216
A branch's FortiLink interface has no route or reachable controller IP and the managed switch never appears. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
- Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
- Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.
Explanation
Correct Answer
B:Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. The paired action is: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
Incorrect Answers
A:Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. These observations are applicable to HA FortiGate pair managing switch topology, but would not isolate the main failure first. The decisive evidence is: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
C: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: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
D:Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization. These observations are applicable to Zero-touch provisioning and controller dependency checks, but would not isolate the main failure first. The decisive evidence is: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
Question 217
An operator assumes that separate VLAN IDs automatically establish the intended FortiGate policy boundaries for tenants. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
- Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
Explanation
Correct Answer
C:Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants. The paired action is: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
Incorrect Answers
A:Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. These observations are applicable to Discovered versus authorized FortiSwitch state, but would not isolate the main failure first. The decisive evidence is: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
B:Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. These observations are applicable to Firmware and lifecycle preparation for FortiSwitch, but would not isolate the main failure first. The decisive evidence is: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
D: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 controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
Question 218
A switch has IGMP snooping enabled but no effective querier and group entries age out unexpectedly. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
- Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
- Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
Explanation
Correct Answer
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.
Incorrect Answers
B:Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. This action is relevant to FortiSwitch local packet-capture profile and filters, not the controlling requirement in this case. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port. The targeted response is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
C:Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. This action is relevant to Voice and data VLAN separation on shared access ports, not the controlling requirement in this case. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN. The targeted response is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
D: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: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
Question 219
A firmware image is upgraded successfully but the switch does not reconnect to the FortiGate management controller. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
- Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
- Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
- Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
- The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.
Explanation
Correct Answers
B:Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. Managed switches can be reachable at Layer 2 yet show stale policy after incompatible upgrade or failed controller push. Verify the action with: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. This is the configuration or remediation half of the requested TWO-step pair.
C:Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. Managed switches can be reachable at Layer 2 yet show stale policy after incompatible upgrade or failed controller push. The paired action is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. This step concerns LLDP and MAC forwarding table extraction and is not part of the required paired solution. The correct action and evidence are: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. Together with: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
D:Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. This step concerns Capture and confidentiality limits in incident response and is not part of the required paired solution. The correct action and evidence are: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. Together with: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
E:The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them. This step concerns DACL RADIUS attribute and per-session enforcement and is not part of the required paired solution. The correct action and evidence are: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. Together with: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
Question 220
A team posts complete captures containing authentication tokens into a public support thread. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
- Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
- FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.
- The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
Explanation
Correct Answer
B:Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process.
Incorrect Answers
A:Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. This result relates to SNMP and sFlow monitoring configuration, not the acceptance condition under test. The relevant result is: Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
C:FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This result relates to FortiGate one-arm sniffer across managed switching, not the acceptance condition under test. The relevant result is: Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
D:The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed. This result relates to Stack failure isolation and switch-to-switch port roles, not the acceptance condition under test. The relevant result is: Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.