Fortinet NSE5_FSW_AD-7.6 Practice Test 55
Question 540
A manager wants all discovered switches automatically authorized even though the site uses untrusted wiring closets. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
- Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
- Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
- Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria.
Explanation
Correct Answer
C: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: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 switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
B: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 switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
D:Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria. These observations are applicable to VLAN security policy and quarantine actions, 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 541
A managed FortiSwitch loses VLAN policy after reboot because prior local CLI edits never entered FortiGate configuration. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- An access host receives the right subnet while only approved tagged VLANs traverse the uplink.
- Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
- 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.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
Explanation
Correct Answers
C: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.
D: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:An access host receives the right subnet while only approved tagged VLANs traverse the uplink. This step concerns FortiSwitch native VLAN versus allowed VLANs 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.
B:Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This step concerns Controller authorization and pending-switch state 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:Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. This step concerns FortiSwitch port mirroring to network analyzer 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 542
A small branch has a single FortiSwitch connected to FortiGate but the user subnet is never assigned to ports. 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 FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
- Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
Explanation
Correct Answer
B:Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded. The paired action is: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
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 FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
C:Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. These observations are applicable to FortiLink management interface provisioning, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
D:Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. These observations are applicable to FortiGate VDOM-based FortiSwitch tenant assignment, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
Question 543
An attacker spoofs an authorized IoT MAC to test whether the switch applies any additional restrictions. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- The current neighboring device and optional endpoint location are visible and match approved cabling documentation.
- Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
- Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
- Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
- Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
Explanation
Correct Answers
C:Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. Verify the action with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. This is the configuration or remediation half of the requested TWO-step pair.
E:Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. The paired action is: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:The current neighboring device and optional endpoint location are visible and match approved cabling documentation. This step concerns LLDP neighbor discovery and location information and is not part of the required paired solution. The correct action and evidence are: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. Together with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
B:Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. This step concerns Intra-VLAN blocking and isolation boundaries and is not part of the required paired solution. The correct action and evidence are: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. Together with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
D:Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. This step concerns FortiSwitch security profile application and precedence and is not part of the required paired solution. The correct action and evidence are: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. Together with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
Question 544
MAC addresses oscillate between two uplinks after a newly installed unmanaged bridge creates a loop. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
- Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
- Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.
- Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
- Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
Explanation
Correct Answers
B:Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port. The paired action is: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. This is the diagnostic or verification half of the requested TWO-step pair.
D:Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port. Verify the action with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable. This step concerns DHCP server allowlist and Option 82 validation and is not part of the required paired solution. The correct action and evidence are: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. Together with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
C:Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies. This step concerns FortiSwitch standalone versus FortiLink managed L3 ownership and is not part of the required paired solution. The correct action and evidence are: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. Together with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
E:Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. This step concerns FortiSwitch SVI routing and connected routes and is not part of the required paired solution. The correct action and evidence are: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. Together with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
Question 545
Two service customers both use inner VLAN 10 but one S-VLAN is omitted during handoff. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.
- Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
- A moved device is traced to its current approved port and incorrect cross-connection is identified.
- The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
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:Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation. This result relates to Shared port multi-VDOM policy boundaries, 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:A moved device is traced to its current approved port and incorrect cross-connection is identified. This result relates to LLDP and MAC forwarding table extraction, 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 offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. This result relates to Managed tenant troubleshooting across controller and access layer, 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 546
A capture filter excludes ARP and the team incorrectly concludes the gateway has no address resolution activity. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
- Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
- The handset and attached workstation use the intended separate networks and retain their authorized access.
- Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
- Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
Explanation
Correct Answers
A:Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. 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. Verify the action with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. This is the configuration or remediation half of the requested TWO-step pair.
E:Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. 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 paired action is: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B: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: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Together with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
C: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: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Together with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
D: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: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Together with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
Question 547
A phone ignores a newly created voice VLAN because the switch advertises an obsolete LLDP-MED network policy. 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.
- Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
- Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
- Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
Explanation
Correct Answer
D:Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP. Verify the action with: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
Incorrect Answers
A:Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. This action is relevant to Discovered versus authorized FortiSwitch state, not the controlling requirement in this case. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. The targeted response is: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
B: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: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
C:Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior. This action is relevant to FortiLink split-interface and standby path design, not the controlling requirement in this case. FortiLink split-interface behavior depends on topology; enabling it blindly for same-peer LAG links can break intended aggregation. The targeted response is: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
Question 548
The configured FortiLink aggregate connects to a single switch but its split-interface setting does not match the topology. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
- A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.
- A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Explanation
Correct Answer
D:The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone.
Incorrect Answers
A: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: The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
B:A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic. This result relates to FortiSwitch local packet-capture profile and filters, not the acceptance condition under test. The relevant result is: The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
C:A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning. This result relates to HA FortiGate pair managing switch topology, not the acceptance condition under test. The relevant result is: The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Question 549
After an office renovation, broadcast rates spike and the same client MAC jumps between two access ports. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
- A planned alternate link remains blocked and takes over predictably without a broadcast storm.
- Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
Explanation
Correct Answer
D:Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause.
Incorrect Answers
A: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: Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
B: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: Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
C:A planned alternate link remains blocked and takes over predictably without a broadcast storm. This result relates to MSTP region consistency and designated root, not the acceptance condition under test. The relevant result is: Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
Question 550
A branch cascades managed switches but connects a ring without checking the supported FortiLink stacking design. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
- Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
- Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
Explanation
Correct Answer
D:Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. Verify the action with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
Incorrect Answers
A:Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This action is relevant to Controller authorization and pending-switch state, not the controlling requirement in this case. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The targeted response is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
B:Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior. This action is relevant to FortiLink split-interface and standby path design, not the controlling requirement in this case. FortiLink split-interface behavior depends on topology; enabling it blindly for same-peer LAG links can break intended aggregation. The targeted response is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
C:Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. This action is relevant to PoE and LLDP-MED endpoint power coordination, not the controlling requirement in this case. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The targeted response is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.