Fortinet NSE5_FSW_AD-7.6 Practice Test 70
Question 690
A user moves between ports and the stale binding on the old port rejects the new legitimate lease. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
- Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
Explanation
Correct Answer
B:Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The paired action is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
Incorrect Answers
A: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: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
C: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: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
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: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
Question 691
A standalone FortiSwitch has local management access but cannot reach its NTP server off-subnet. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
- Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
Explanation
Correct Answer
C:Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. The paired action is: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
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: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
B: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: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
D: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: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
Question 692
A managed switch belongs to a common FortiLink while new customer VLANs are assigned to an unrelated FortiGate VDOM. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
- Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
- Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
Explanation
Correct Answer
A: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
B:Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path. These observations are applicable to Single FortiGate and single FortiSwitch topology, but would not isolate the main failure first. The decisive evidence is: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
C:Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. These observations are applicable to FortiSwitch port mirroring to network analyzer, 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:Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. These observations are applicable to Shared port multi-VDOM policy boundaries, 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 693
One 100G interface is split into smaller links but the automation still targets the original parent port name. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
- Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
- Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
Explanation
Correct Answer
C:Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model. The paired action is: Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
Incorrect Answers
A:Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters. These observations are applicable to DACL RADIUS attribute and per-session enforcement, but would not isolate the main failure first. The decisive evidence is: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
B:Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. These observations are applicable to VLAN configuration persistence and drift control, but would not isolate the main failure first. The decisive evidence is: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
D: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 hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
Question 694
A VLAN on the firewall has an IP but no approved intra-VLAN or inter-VLAN policy for the intended client traffic. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
- Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
- Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
- Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
Explanation
Correct Answer
A:Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. Verify the action with: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
Incorrect Answers
B:Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. This action is relevant to FortiSwitch split port breakout mode, not the controlling requirement in this case. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model. The targeted response is: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
C:Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This action is relevant to IPv4 source guard and binding-based packet filtering, not the controlling requirement in this case. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The targeted response is: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
D:Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This action is relevant to FortiSwitch native VLAN versus allowed VLANs, not the controlling requirement in this case. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The targeted response is: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
Question 695
A technician disables STP on one interswitch uplink because it shows blocking during normal redundancy. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
- The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.
- Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
- Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.
- Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
Explanation
Correct Answers
C: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. This is the diagnostic or verification half of the requested TWO-step pair.
E:Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. Verify the action with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings. This step concerns LLDP-MED voice network policy advertisements and is not part of the required paired solution. The correct action and evidence are: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
B: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: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
D:Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims. This step concerns Root guard and loop guard failure response and is not part of the required paired solution. The correct action and evidence are: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
Question 696
A management SVI is assigned an address in a subnet already used by a different switch interface. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
- The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
- Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
- Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
- Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
Explanation
Correct Answers
A:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. Verify the action with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. This is the configuration or remediation half of the requested TWO-step pair.
E:Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. The paired action is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. This step concerns Managed switch configuration synchronization and is not part of the required paired solution. The correct action and evidence are: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Together with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
C: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 switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Together with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
D:Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency. This step concerns Egress priority scheduling and congestion visibility and is not part of the required paired solution. The correct action and evidence are: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Together with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
Question 697
A static-IP printer loses connectivity after DAI is turned on with no manual binding exception. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
- Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
- Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
- Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
Explanation
Correct Answer
A: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
B:Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. This action is relevant to DACL RADIUS attribute and per-session enforcement, not the controlling requirement in this case. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. The targeted response is: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
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: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
D:Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. This action is relevant to Managed switch configuration synchronization, not the controlling requirement in this case. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The targeted response is: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
Question 698
When a distribution uplink fails, three downstream switches disappear from the FortiGate controller together. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
- Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
Explanation
Correct Answer
A:Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic. Verify the action with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
Incorrect Answers
B:Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. This action is relevant to MCLAG peer-link topology for managed access switches, not the controlling requirement in this case. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. The targeted response is: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
C:Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. This action is relevant to LACP negotiation on FortiSwitch FortiLink trunks, not the controlling requirement in this case. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. The targeted response is: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
D: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 stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
Question 699
An infected kiosk continues reaching payroll servers despite showing a quarantine label in the controller. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
- The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
Explanation
Correct Answer
B:The suspect device is restricted without interrupting unrelated tenants and can be restored after review. Quarantine must be enforced at the right switch and VLAN path; a security-alert label alone does not remove access.
Incorrect Answers
A: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: The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
C: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: The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
D:The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. This result relates to Managed switch configuration synchronization, not the acceptance condition under test. The relevant result is: The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
Question 700
A firmware image is upgraded successfully but the switch does not reconnect to the FortiGate management controller. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
- Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
Explanation
Correct Answer
B: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.
Incorrect Answers
A:Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. These observations are applicable to FortiLink transport over nontrivial L2 or L3 paths, but would not isolate the main failure first. The decisive evidence is: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
C:Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. These observations are applicable to FortiSwitch port mirroring to network analyzer, but would not isolate the main failure first. The decisive evidence is: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
D:Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. These observations are applicable to Managed switch port statistics and counter analysis, but would not isolate the main failure first. The decisive evidence is: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.