Fortinet NSE5_FSW_AD-7.6 Practice Test 16
Question 150
An administrator assumes a new FortiSwitch model accepts the same firmware image as an older campus model. 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.
- Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
- The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
- The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
Explanation
Correct Answer
B:Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade. A successful image upload does not prove switch operation or controller compatibility after reboot.
Incorrect Answers
A:Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. This result relates to PoE and LLDP-MED endpoint power coordination, not the acceptance condition under test. The relevant result is: Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
C:The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. This result relates to Managed switch configuration synchronization, not the acceptance condition under test. The relevant result is: Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
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: Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
Question 151
A dynamic port-policy rule intended for printers matches all newly connected laptops due to a broad condition. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
- Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
- Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
- Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
Explanation
Correct Answer
C:Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. Verify the action with: Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
Incorrect Answers
A: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: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
B:Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. This action is relevant to FortiSwitch 802.1X port-based authentication, not the controlling requirement in this case. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. The targeted response is: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
D: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: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
Question 152
An access switch accidentally becomes root because its bridge priority is lower than planned core devices. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
- Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
- Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
- Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
- Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
Explanation
Correct Answers
A:Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. Different MST configuration identifiers split regions even if switch ports are physically connected. The paired action is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. This is the diagnostic or verification half of the requested TWO-step pair.
D:Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Different MST configuration identifiers split regions even if switch ports are physically connected. Verify the action with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
B:Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. This step concerns STP incident recovery with MAC flap evidence and is not part of the required paired solution. The correct action and evidence are: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
C:Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. This step concerns RPVST and supported STP mode interoperability and is not part of the required paired solution. The correct action and evidence are: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
E:Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access. This step concerns NAC dynamic port policy device classification and is not part of the required paired solution. The correct action and evidence are: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
Question 153
A branch begins firmware rollout on every downstream switch without checking supported controller compatibility. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
- Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
- Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
- Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
Explanation
Correct Answer
B:Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. A successful image upload does not prove switch operation or controller compatibility after reboot. Verify the action with: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
Incorrect Answers
A:Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. This action is relevant to Zero-touch provisioning and controller dependency checks, not the controlling requirement in this case. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. The targeted response is: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
C:Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. This action is relevant to LACP negotiation on FortiSwitch FortiLink trunks, not the controlling requirement in this case. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. The targeted response is: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
D:Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. This action is relevant to FortiLink management interface provisioning, not the controlling requirement in this case. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. The targeted response is: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
Question 154
Two customer groups with overlapping subnet plans are connected as if VDOM segmentation automatically fixes routing collisions. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
- Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
- Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
- Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.
Explanation
Correct Answer
B: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.
Incorrect Answers
A: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: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
C:Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. These observations are applicable to Managed tenant troubleshooting across controller and access layer, but would not isolate the main failure first. The decisive evidence is: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
D:Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log. These observations are applicable to Root guard and loop guard failure response, but would not isolate the main failure first. The decisive evidence is: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
Question 155
A managed FortiSwitch learns an unauthorized DHCP server from a neighboring guest kiosk. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
- Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
- Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
- The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.
Explanation
Correct Answer
B:Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay.
Incorrect Answers
A: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: Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
C: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: Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
D:The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them. This result relates to DACL RADIUS attribute and per-session enforcement, not the acceptance condition under test. The relevant result is: Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
Question 156
A new routed VLAN exists but its SVI stays down because no participating port is operational. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
- Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
Explanation
Correct Answer
C:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. Verify the action with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
Incorrect Answers
A:Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. This action is relevant to Capture and confidentiality limits in incident response, not the controlling requirement in this case. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. The targeted response is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
B: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: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
D:Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. This action is relevant to VLAN configuration persistence and drift control, not the controlling requirement in this case. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. The targeted response is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
Question 157
An administrator gives every traffic class strict priority and then cannot explain which queue is actually served. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Latency-sensitive flows improve under representative load while other business services remain functional.
- A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
- Both ends connect at compatible rates with stable errors and required throughput.
- Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization.
Explanation
Correct Answer
A:Latency-sensitive flows improve under representative load while other business services remain functional. QoS prioritizes scarce link capacity but cannot create bandwidth beyond the physical egress rate.
Incorrect Answers
B: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: Latency-sensitive flows improve under representative load while other business services remain functional.
C: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: Latency-sensitive flows improve under representative load while other business services remain functional.
D:Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization. This result relates to FortiSwitch security profile application and precedence, not the acceptance condition under test. The relevant result is: Latency-sensitive flows improve under representative load while other business services remain functional.
Question 158
A desk phone and PC are daisy-chained, yet both obtain addresses from the guest subnet. 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.
- Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
- Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
- Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
Explanation
Correct Answer
A:Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN. Verify the action with: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
Incorrect Answers
B:Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This action is relevant to FortiSwitch native VLAN versus allowed VLANs, not the controlling requirement in this case. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The targeted response is: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
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: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
D:Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This action is relevant to FortiGate one-arm sniffer across managed switching, not the controlling requirement in this case. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The targeted response is: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
Question 159
A user changes departments and the RADIUS server issues CoA but the switch continues enforcing the old access role. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
- Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
- Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
- Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
Explanation
Correct Answer
B:Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions. The paired action is: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
Incorrect Answers
A:Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. These observations are applicable to MAC-based authentication and restricted legacy devices, but would not isolate the main failure first. The decisive evidence is: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
C:Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. These observations are applicable to LACP negotiation on FortiSwitch FortiLink trunks, but would not isolate the main failure first. The decisive evidence is: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
D:Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. These observations are applicable to FortiSwitch 802.1X port-based authentication, but would not isolate the main failure first. The decisive evidence is: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
Question 160
A firewall analyst captures only the routed interface while the failure occurs between two hosts in one switch VLAN. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
- Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
Explanation
Correct Answer
A:Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The paired action is: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
Incorrect Answers
B: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: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
C: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: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
D:Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. These observations are applicable to LLDP neighbor discovery and location information, but would not isolate the main failure first. The decisive evidence is: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.