Fortinet NSE5_FSW_AD-7.6 Practice Test 39
Question 380
An administrator raises MAC limits on every port instead of diagnosing one device creating random source addresses. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
- A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.
- The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
- An unexpected additional device is restricted or signaled without knocking out approved business equipment.
Explanation
Correct Answer
D:An unexpected additional device is restricted or signaled without knocking out approved business equipment. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs.
Incorrect Answers
A:Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable. This result relates to DHCP server allowlist and Option 82 validation, not the acceptance condition under test. The relevant result is: An unexpected additional device is restricted or signaled without knocking out approved business equipment.
B:A session's effective access changes only when the authorization result is accepted and policy is installed on hardware. This result relates to RADIUS change of authorization and applied session policy, not the acceptance condition under test. The relevant result is: An unexpected additional device is restricted or signaled without knocking out approved business equipment.
C:The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface. This result relates to FortiGate managed FortiSwitch VLAN interface placement, not the acceptance condition under test. The relevant result is: An unexpected additional device is restricted or signaled without knocking out approved business equipment.
Question 381
A technician changes the VLAN directly on a FortiLink-managed switch and loses it after reboot. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
- Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
- Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
- Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
Explanation
Correct Answer
C:Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. The paired action is: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
Incorrect Answers
A: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: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
B: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: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
D:Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. These observations are applicable to HA FortiGate pair managing switch topology, but would not isolate the main failure first. The decisive evidence is: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
Question 382
A new tenant's DHCP VLAN is permitted but an old customer unexpectedly loses service due to a broad template overwrite. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
- Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
- Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
- Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
Explanation
Correct Answer
C:Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. The paired action is: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
Incorrect Answers
A:Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. These observations are applicable to Firmware and lifecycle preparation for FortiSwitch, but would not isolate the main failure first. The decisive evidence is: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
B:Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. These observations are applicable to QinQ outer and inner VLAN tenant mapping, but would not isolate the main failure first. The decisive evidence is: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
D:Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy. These observations are applicable to SNMP and sFlow monitoring configuration, but would not isolate the main failure first. The decisive evidence is: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
Question 383
An engineer accidentally configures the laptop's analyzer port as a production access uplink rather than the monitor destination. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
- Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
- Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
- Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Explanation
Correct Answers
C:Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic. Verify the action with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. This is the configuration or remediation half of the requested TWO-step pair.
D:Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic. The paired action is: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. This step concerns Capture-based DHCP and ARP path isolation and is not part of the required paired solution. The correct action and evidence are: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. Together with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
B:Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision. This step concerns QinQ outer and inner VLAN tenant mapping and is not part of the required paired solution. The correct action and evidence are: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. Together with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
E: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: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. Together with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
Question 384
A new conference phone reboots when its extra display turns on despite a stable Ethernet link. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
- Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
Explanation
Correct Answer
A:Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The paired action is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
Incorrect Answers
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 switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
C:Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. These observations are applicable to Discovered versus authorized FortiSwitch state, but would not isolate the main failure first. The decisive evidence is: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
D: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: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
Question 385
A technician changes a phone port to a trunk but fails to restrict unrelated management VLANs. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
- Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
- Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
- Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
Explanation
Correct Answer
C:Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN. The paired action is: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
Incorrect Answers
A:Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. These observations are applicable to STP incident recovery with MAC flap evidence, but would not isolate the main failure first. The decisive evidence is: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
B: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: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
D:Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. These observations are applicable to FortiSwitch multi-tier managed topology, but would not isolate the main failure first. The decisive evidence is: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
Question 386
Two service customers both use inner VLAN 10 but one S-VLAN is omitted during handoff. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
- Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
- Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.
- Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
Explanation
Correct Answer
B:Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. Verify the action with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
Incorrect Answers
A: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: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
C:Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies. This action is relevant to FortiSwitch standalone versus FortiLink managed L3 ownership, not the controlling requirement in this case. Direct edits on a managed switch can be overridden; standalone configuration must be maintained and backed up independently. The targeted response is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
D:Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. This action is relevant to FortiGate VDOM-based FortiSwitch tenant assignment, not the controlling requirement in this case. 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 targeted response is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
Question 387
A network map says a printer connects to switch A but its MAC is learned on switch C's access port. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
- Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
- A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
- Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
Explanation
Correct Answers
B: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. This is the diagnostic or verification half of the requested TWO-step pair.
E:Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. Verify the action with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. This step concerns Controller authorization and pending-switch state and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
C: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: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
D:Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. This step concerns SNMP and sFlow monitoring configuration and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Question 388
The only switch backup was taken before a year of VLAN changes and restore loses critical networks. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
- Controller and switch return to supported synchronized software and configuration with test-client services restored.
- A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
- Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
Explanation
Correct Answer
C:A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work.
Incorrect Answers
A:Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. This result relates to FortiSwitch SVI routing and connected routes, not the acceptance condition under test. The relevant result is: A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
B:Controller and switch return to supported synchronized software and configuration with test-client services restored. This result relates to FortiLink synchronization and upgrade troubleshooting, not the acceptance condition under test. The relevant result is: A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
D:Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications. This result relates to Capture and confidentiality limits in incident response, not the acceptance condition under test. The relevant result is: A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
Question 389
FortiSwitch reaches its maximum combined static and dynamic ACL entry budget and silently leaves some intended policy uninstalled. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
- Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
- Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
- Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
Explanation
Correct Answer
B:Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. Verify the action with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
Incorrect Answers
A:Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This action is relevant to QinQ outer and inner VLAN tenant mapping, not the controlling requirement in this case. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The targeted response is: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
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: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
D:Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. This action is relevant to DHCP snooping trust-boundary enforcement, not the controlling requirement in this case. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. The targeted response is: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
Question 390
An approved static-IP server is blocked because its switch port lacks a binding entry after enabling source guard. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
- Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
Explanation
Correct Answer
A:Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security.
Incorrect Answers
B:Exactly the intended serial joins managed inventory and receives approved controller settings after authorization. This result relates to Discovered versus authorized FortiSwitch state, not the acceptance condition under test. The relevant result is: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
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: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
D:Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer. This result relates to DHCP snooping trust-boundary enforcement, not the acceptance condition under test. The relevant result is: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.