Fortinet NSE5_FSW_AD-7.6 Practice Test 7
Question 60
A handset supports LLDP-MED but the access switch is configured only to receive LLDP and not advertise local policy. 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.
- Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
- 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: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: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
B:Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This action is relevant to QoS ingress classification and trust boundaries, not the controlling requirement in this case. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently. 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 61
A FortiSwitch is asked to route between two user VLANs but the gateway addresses were configured only on hosts. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Both ends connect at compatible rates with stable errors and required throughput.
- Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.
- The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
Explanation
Correct Answer
D:Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN.
Incorrect Answers
A:Both ends connect at compatible rates with stable errors and required throughput. This result relates to Switch port speed and duplex commissioning, not the acceptance condition under test. The relevant result is: Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
B:Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot. This result relates to FortiSwitch standalone versus FortiLink managed L3 ownership, not the acceptance condition under test. The relevant result is: Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
C:The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. This result relates to FortiLink discovery failure and physical uplink path, not the acceptance condition under test. The relevant result is: Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
Question 62
A monitoring host receives no packets because the chosen mirror direction captures only ingress while the failing frames are egress. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
- Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
- Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
- An unexpected additional device is restricted or signaled without knocking out approved business equipment.
- Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
Explanation
Correct Answers
A: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.
E: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.
Incorrect Answers
B:Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. This step concerns FortiSwitch diagnostic commands and logs 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.
C: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.
D:An unexpected additional device is restricted or signaled without knocking out approved business equipment. This step concerns Port MAC learning-limit and violation controls 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 63
A PoE access switch can power legacy phones but sheds newer high-power access points after lunch. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.
- The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
- Every relevant VLAN converges without loops and redundant paths unblock only when needed.
- Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
Explanation
Correct Answer
A:Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints.
Incorrect Answers
B:The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed. This result relates to Stack failure isolation and switch-to-switch port roles, not the acceptance condition under test. The relevant result is: Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.
C:Every relevant VLAN converges without loops and redundant paths unblock only when needed. This result relates to RPVST and supported STP mode interoperability, not the acceptance condition under test. The relevant result is: Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.
D:Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access. This result relates to NAC dynamic port policy device classification, not the acceptance condition under test. The relevant result is: Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.
Question 64
An engineer enables legacy public read-write SNMP community strings to save time and exposes management data. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
- Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
- The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
- A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
Explanation
Correct Answer
B:Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed.
Incorrect Answers
A:A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies. This result relates to FortiGate VDOM-based FortiSwitch tenant assignment, not the acceptance condition under test. The relevant result is: Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
C:The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This result relates to FortiSwitch diagnostic commands and logs, not the acceptance condition under test. The relevant result is: Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
D:A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior. This result relates to Config backup and firmware inventory evidence, not the acceptance condition under test. The relevant result is: Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
Question 65
A switch has a supported breakout cable yet its configured phy-mode and child speeds do not match the attached peers. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
- Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
- Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
- Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.
- Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
Explanation
Correct Answers
B: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.
E: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.
Incorrect Answers
A:Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. This step concerns Switch port speed and duplex commissioning 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:Exactly the intended serial joins managed inventory and receives approved controller settings after authorization. This step concerns Discovered versus authorized FortiSwitch state 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.
D:Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. This step concerns Optic compatibility and laser diagnostic evidence 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 66
FortiSwitch reaches its maximum combined static and dynamic ACL entry budget and silently leaves some intended policy uninstalled. 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.
- Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
- Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
Explanation
Correct Answer
A:Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. The paired action is: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
Incorrect Answers
B: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 RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
C:Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. These observations are applicable to Port MAC learning-limit and violation controls, but would not isolate the main failure first. The decisive evidence is: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
D: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 RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
Question 67
A branch telephone gets a guest address because its access port native VLAN was changed during replacement. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.
- Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
- The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
- Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
Explanation
Correct Answers
B:Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The paired action is: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This is the diagnostic or verification half of the requested TWO-step pair.
E:Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. Verify the action with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log. 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: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
C:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This step concerns FortiSwitch SVI routing and connected routes and is not part of the required paired solution. The correct action and evidence are: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
D:The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. 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: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
Question 68
Two customer groups with overlapping subnet plans are connected as if VDOM segmentation automatically fixes routing collisions. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
- Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
- Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
- Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
Explanation
Correct Answer
B: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.
Incorrect Answers
A:Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. This action is relevant to Voice and data VLAN separation on shared access ports, not the controlling requirement in this case. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN. The targeted response is: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
C: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: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
D: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: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
Question 69
Two phones receive different QoS hints after being attached to ports using different LLDP profiles. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
- Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
- Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
- 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:Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. This action is relevant to Firmware and lifecycle preparation for FortiSwitch, not the controlling requirement in this case. A successful image upload does not prove switch operation or controller compatibility after reboot. The targeted response is: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
B:Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic. This action is relevant to Egress priority scheduling and congestion visibility, not the controlling requirement in this case. QoS prioritizes scarce link capacity but cannot create bandwidth beyond the physical egress rate. The targeted response is: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
C:Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. This action is relevant to Stack failure isolation and switch-to-switch port roles, not the controlling requirement in this case. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic. The targeted response is: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
Question 70
One upstream switch loses power and all child switches disappear from the FortiGate management screen. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
- Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
Explanation
Correct Answer
C:Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. The paired action is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
Incorrect Answers
A:Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial. These observations are applicable to FortiLink discovery failure and physical uplink path, but would not isolate the main failure first. The decisive evidence is: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
B: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: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
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: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.