Fortinet NSE5_FSW_AD-7.6 Practice Test 9
Question 80
After an unmanaged bridge is added, the same endpoint MAC repeatedly moves between ports and the team checks only DHCP leases. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
- Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
Explanation
Correct Answer
C:Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The paired action is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
Incorrect Answers
A:Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. These observations are applicable to Voice and data VLAN separation on shared access ports, but would not isolate the main failure first. The decisive evidence is: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
B: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 local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
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 local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Question 81
Guest users can browse the internet but should not access each other's devices on the same Wi-Fi-to-switch VLAN. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Both ends connect at compatible rates with stable errors and required throughput.
- Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
- Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria.
- Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
- Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
Explanation
Correct Answers
D: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. This is the diagnostic or verification half of the requested TWO-step pair.
E:Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured. Verify the action with: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Both ends connect at compatible rates with stable errors and required throughput. This step concerns Switch port speed and duplex commissioning and is not part of the required paired solution. The correct action and evidence are: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. Together with: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
B:Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. 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 supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. Together with: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
C:Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria. This step concerns VLAN security policy and quarantine actions and is not part of the required paired solution. The correct action and evidence are: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. Together with: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
Question 82
A team claims an ACL encrypts traffic instead of recognizing its supported forwarding/filtering actions. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
- Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
- Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
- Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
Explanation
Correct Answer
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.
Incorrect Answers
A: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: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
B:Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. These observations are applicable to Intra-VLAN blocking and isolation boundaries, 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:Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. These observations are applicable to FortiSwitch security profile application and precedence, 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 83
A rogue switch appears as discovered and an administrator considers enabling global auto-authorization without checking its identity. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
- Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions.
- Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
- A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
Explanation
Correct Answer
A:Exactly the intended serial joins managed inventory and receives approved controller settings after authorization. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device.
Incorrect Answers
B:Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions. This result relates to FortiLink transport over nontrivial L2 or L3 paths, not the acceptance condition under test. The relevant result is: Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
C:Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy. This result relates to IPv4 source guard and binding-based packet filtering, not the acceptance condition under test. The relevant result is: Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
D:A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop. This result relates to MCLAG multichassis access redundancy, not the acceptance condition under test. The relevant result is: Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
Question 84
A network engineer selects a breakout option not supported by its FortiSwitch hardware revision. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.
- Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
- Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
- Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
- Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
Explanation
Correct Answers
D:Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model. Verify the action with: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect. This is the configuration or remediation half of the requested TWO-step pair.
E: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. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy. This step concerns Intra-VLAN blocking and isolation boundaries and is not part of the required paired solution. The correct action and evidence are: Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. Together with: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
B:Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. This step concerns RPVST and supported STP mode interoperability and is not part of the required paired solution. The correct action and evidence are: Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. Together with: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
C:Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices. This step concerns Power over Ethernet port controls and budgets and is not part of the required paired solution. The correct action and evidence are: Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. Together with: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
Question 85
A newly patched uplink reports an unexpected LLDP peer from a separate customer zone. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
- Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Explanation
Correct Answer
D:Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The paired action is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
Incorrect Answers
A:Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. These observations are applicable to FortiSwitch diagnostic commands and logs, but would not isolate the main failure first. The decisive evidence is: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
B: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: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
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: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Question 86
A technician chooses a switch port without auto-discovery support and assumes the FortiGate will still detect it by magic. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
- Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
- Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
- Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
- Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
Explanation
Correct Answers
D: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.
E: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
A:A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop. This step concerns MCLAG multichassis access redundancy 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.
B:Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. This step concerns Managed switch port statistics and counter analysis 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.
C:Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. This step concerns FortiLink synchronization and upgrade troubleshooting 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 87
A user plugs a small unmanaged switch into a protected desk outlet and the access port shuts down. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
- Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
- Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
- Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
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: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: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
C:Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. These observations are applicable to MSTP region consistency and designated root, 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 switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. These observations are applicable to Controller authorization and pending-switch state, 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 88
A landlord shares one uplink among tenant VDOMs without restricting customer-tagged VLANs. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
- The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
- Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
- Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
- Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
Explanation
Correct Answers
A: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
B:The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface. This step concerns FortiGate managed FortiSwitch VLAN interface placement 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.
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: 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:Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. This step concerns FortiSwitch multi-tier managed topology 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 89
A managed switch belongs to a common FortiLink while new customer VLANs are assigned to an unrelated FortiGate VDOM. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.
- Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
Explanation
Correct Answers
B:Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants. Verify the action with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. This is the configuration or remediation half of the requested TWO-step pair.
E: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. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity. This step concerns Power over Ethernet port controls and budgets and is not part of the required paired solution. The correct action and evidence are: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. Together with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
C:Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. Together with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
D: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: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. Together with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
Question 90
A contractor requests a full week of unfiltered packet data from a production finance VLAN to diagnose one DHCP issue. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
- Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
- Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
Explanation
Correct Answer
D:Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. The paired action is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
Incorrect Answers
A:Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. These observations are applicable to FortiSwitch local packet-capture profile and filters, but would not isolate the main failure first. The decisive evidence is: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
B:Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. These observations are applicable to Multi-tenant change verification and rollback, but would not isolate the main failure first. The decisive evidence is: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
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: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.