Fortinet NSE5_FSW_AD-7.6 Practice Test 60
Question 590
A branch cascades managed switches but connects a ring without checking the supported FortiLink stacking design. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
- Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
- Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
- Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
Explanation
Correct Answer
C:Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. The paired action is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
Incorrect Answers
A: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: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
B:Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. These observations are applicable to MAC-based authentication and restricted legacy devices, but would not isolate the main failure first. The decisive evidence is: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
D: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: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
Question 591
An operator applies an edge-port policy to a FortiLink upstream interface and disrupts normal peer BPDUs. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
- Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
- Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
- Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
Explanation
Correct Answer
B:Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. The paired action is: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
Incorrect Answers
A:Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. These observations are applicable to Switch port speed and duplex commissioning, but would not isolate the main failure first. The decisive evidence is: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
C:Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. These observations are applicable to Optic compatibility and laser diagnostic evidence, but would not isolate the main failure first. The decisive evidence is: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
D: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: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
Question 592
A FortiGate template updates native VLANs but a switch shows an outdated port mapping after synchronization. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
- Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
- Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
- Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
Explanation
Correct Answer
A:Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. Verify the action with: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
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: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
C:Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. This action is relevant to LLDP-MED voice network policy advertisements, not the controlling requirement in this case. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP. The targeted response is: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
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: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
Question 593
An added FortiSwitch uplink remains individual because its peer LACP mode is incompatible. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
- Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
- Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
- Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
Explanation
Correct Answer
C: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.
Incorrect Answers
A: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: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
B:Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. These observations are applicable to Stack failure isolation and switch-to-switch port roles, but would not isolate the main failure first. The decisive evidence is: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
D:Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. These observations are applicable to FortiSwitch native VLAN versus allowed VLANs, but would not isolate the main failure first. The decisive evidence is: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
Question 594
An old switch runs a different STP variant and the peer unexpectedly blocks the voice VLAN only. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
- Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
- Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
- Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
Explanation
Correct Answer
B:Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. The paired action is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
Incorrect Answers
A:Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence. These observations are applicable to DHCP server allowlist and Option 82 validation, but would not isolate the main failure first. The decisive evidence is: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
C: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 local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
D: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 local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
Question 595
Two remote sites share overlapping prefixes and a broad static route inadvertently sends traffic to the wrong location. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
- Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
- Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
- Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
Explanation
Correct Answer
A:Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. Verify the action with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
Incorrect Answers
B:Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. This action is relevant to Single FortiGate and single FortiSwitch topology, not the controlling requirement in this case. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded. The targeted response is: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
C: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: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
D:Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. This action is relevant to IGMP snooping and multicast receivers, not the controlling requirement in this case. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. The targeted response is: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
Question 596
An authorized replacement is still pending because the switch serial was entered incorrectly in controller inventory. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
- Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
- Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
- Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
Explanation
Correct Answer
B: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:Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. These observations are applicable to Capture and confidentiality limits in incident response, 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:Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. These observations are applicable to FortiGate one-arm sniffer across managed switching, 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.
D:Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. These observations are applicable to FortiSwitch native VLAN versus allowed VLANs, 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 597
A trunk expects double-tagged frames but the upstream switch strips the outer service tag. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Only intended networks are reachable through the configured route and the return path remains valid.
- Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Explanation
Correct Answer
B:Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ.
Incorrect Answers
A: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 customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
C:All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This result relates to FortiSwitch multi-tier managed topology, not the acceptance condition under test. The relevant result is: Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
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: Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
Question 598
A team claims an ACL encrypts traffic instead of recognizing its supported forwarding/filtering actions. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
- Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
- Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
- Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
- The handset and attached workstation use the intended separate networks and retain their authorized access.
Explanation
Correct Answers
A:Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied. Verify the action with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path. This is the configuration or remediation half of the requested TWO-step pair.
D: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. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. This step concerns FortiSwitch 802.1X port-based authentication and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
C:Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. This step concerns MAC-based authentication and restricted legacy devices and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
E:The handset and attached workstation use the intended separate networks and retain their authorized access. This step concerns Voice and data VLAN separation on shared access ports and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
Question 599
An engineer trusts every edge port to stop false positives, removing the anti-spoofing boundary. 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.
- Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
- Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
- Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
Explanation
Correct Answer
D:Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. DAI validation needs a reliable binding or exception policy; enabling it blindly can interrupt static-IP devices. Verify the action with: Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
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: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
B:Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This action is relevant to FortiSwitch diagnostic commands and logs, not the controlling requirement in this case. A log message without source device, time and relevant state is not adequate to prove root cause. The targeted response is: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
C: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 supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
Question 600
A rogue switch appears as discovered and an administrator considers enabling global auto-authorization without checking its identity. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
- Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
- Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
Explanation
Correct Answer
B: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
A:Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. This action is relevant to Single FortiGate and single FortiSwitch topology, not the controlling requirement in this case. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
C:Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. This action is relevant to LLDP neighbor discovery and location information, not the controlling requirement in this case. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
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: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.