Fortinet NSE5_FSW_AD-7.6 Practice Test 11
Question 100
A provider configures S-VLAN on a tenant VDOM rather than the VDOM where its FortiLink parent exists. 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.
- A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
- Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
- Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.
Explanation
Correct Answer
C: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.
B: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: Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
D: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: Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
Question 101
An engineer moves a port into a different security group without verifying the FortiGate controller template. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
- Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
- Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
- Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
- Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
Explanation
Correct Answers
C:Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. Verify the action with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. This is the configuration or remediation half of the requested TWO-step pair.
E:Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The paired action is: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. This step concerns Zero-touch provisioning and controller dependency checks and is not part of the required paired solution. The correct action and evidence are: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Together with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
B:Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority. This step concerns QoS ingress classification and trust boundaries and is not part of the required paired solution. The correct action and evidence are: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Together with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
D:Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. This step concerns Firmware and lifecycle preparation for FortiSwitch and is not part of the required paired solution. The correct action and evidence are: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Together with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
Question 102
An MCLAG peer reports a keepalive or peer-link fault even though all physical uplink ports remain up. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A controlled failure test restores approved management and access connectivity through the designed redundant path.
- Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.
Explanation
Correct Answer
A:A controlled failure test restores approved management and access connectivity through the designed redundant path. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone.
Incorrect Answers
B:Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. This result relates to SNMP and sFlow monitoring configuration, not the acceptance condition under test. The relevant result is: A controlled failure test restores approved management and access connectivity through the designed redundant path.
C:All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This result relates to FortiSwitch multi-tier managed topology, not the acceptance condition under test. The relevant result is: A controlled failure test restores approved management and access connectivity through the designed redundant path.
D:FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This result relates to FortiGate one-arm sniffer across managed switching, not the acceptance condition under test. The relevant result is: A controlled failure test restores approved management and access connectivity through the designed redundant path.
Question 103
An unknown device bypasses the intended quarantine profile because a static port policy takes precedence unexpectedly. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
- Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
- Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
Explanation
Correct Answers
C:Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. The paired action is: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. This is the diagnostic or verification half of the requested TWO-step pair.
D: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. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline. This step concerns Zero-touch provisioning and controller dependency checks and is not part of the required paired solution. The correct action and evidence are: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. Together with: Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
B:Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. 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: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. Together with: Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
E:Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. This step concerns FortiSwitch security profile application and precedence and is not part of the required paired solution. The correct action and evidence are: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. Together with: Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
Question 104
A voice rollout advertises the new voice VLAN but its DHCP scope is still unreachable from the phone segment. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
- Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
- Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
- Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
Explanation
Correct Answer
C: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
A: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: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
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: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
D:Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. This action is relevant to FortiGate managed FortiSwitch VLAN interface placement, not the controlling requirement in this case. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. The targeted response is: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
Question 105
A new IoT sensor is placed into a quarantine VLAN without access to the only approved remediation server. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
- Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
- Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
- Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.
Explanation
Correct Answer
B:Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations. Quarantine must be enforced at the right switch and VLAN path; a security-alert label alone does not remove access. Verify the action with: Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria.
Incorrect Answers
A:Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. This action is relevant to DACL RADIUS attribute and per-session enforcement, not the controlling requirement in this case. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. The targeted response is: Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
C: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 a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
D:Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims. This action is relevant to Root guard and loop guard failure response, not the controlling requirement in this case. Root guard and loop guard mitigate different failure cases and should not be enabled indiscriminately on every uplink. The targeted response is: Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
Question 106
A multicast paging VLAN disappears after a template update allowed only the corporate user VLAN. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
- Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
- Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.
- Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
Explanation
Correct Answer
C:Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop. Link up and successful traffic in one VLAN do not prove every VLAN is correctly provisioned on the path. The paired action is: Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
Incorrect Answers
A:Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. These observations are applicable to Controller authorization and pending-switch state, but would not isolate the main failure first. The decisive evidence is: Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.
B:Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. These observations are applicable to VLAN configuration persistence and drift control, but would not isolate the main failure first. The decisive evidence is: Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.
D:Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. These observations are applicable to FortiLink ISL auto-discovery and stack cabling, but would not isolate the main failure first. The decisive evidence is: Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.
Question 107
A FortiSwitch is asked to route between two user VLANs but the gateway addresses were configured only on hosts. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
- Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
- Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
Explanation
Correct Answer
D:Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. The paired action is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
Incorrect Answers
A:Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. These observations are applicable to Managed switch configuration synchronization, but would not isolate the main failure first. The decisive evidence is: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
B:Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. These observations are applicable to Static route and default gateway validation, but would not isolate the main failure first. The decisive evidence is: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
C:Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. These observations are applicable to Layer 2 MAC-learning and forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
Question 108
An operator receives an assigned IP address but assumes that proves the switch is already controller-authorized. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.
- Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
Explanation
Correct Answer
A:Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. The paired action is: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
Incorrect Answers
B: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: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.
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 factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.
D: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: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.
Question 109
A switch learns one user's MAC on VLAN 60 although that access group was provisioned for VLAN 50. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
- Only intended networks are reachable through the configured route and the return path remains valid.
- A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
Explanation
Correct Answer
B:The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated. Link up and successful traffic in one VLAN do not prove every VLAN is correctly provisioned on the path.
Incorrect Answers
A: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: The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
C:Only intended networks are reachable through the configured route and the return path remains valid. This result relates to Static route and default gateway validation, not the acceptance condition under test. The relevant result is: The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
D: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: The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
Question 110
After an office renovation, broadcast rates spike and the same client MAC jumps between two access ports. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
- Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
- Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
- Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
Explanation
Correct Answer
D:Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause. Verify the action with: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
Incorrect Answers
A:Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. This action is relevant to BPDU guard on endpoint-facing ports, not the controlling requirement in this case. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. The targeted response is: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
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: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
C:Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. This action is relevant to FortiSwitch local packet-capture profile and filters, not the controlling requirement in this case. 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 targeted response is: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.