NSE5_FSW_AD-7.6
Free NSE5_FSW_AD-7.6 practice questions
10 questions from our NSE5_FSW_AD-7.6 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, FortiSwitch Concepts
Which spanning tree protocol does FortiSwitch run by default, allowing interoperability with switches that use RSTP?
- APVST+, which runs a separate rapid instance for every VLAN configured on the switch ports
- BLegacy 802.1D STP, which RSTP neighbours detect and then downgrade their own ports to match
- CNo STP at all, because FortiSwitch relies only on its loop guard feature to prevent switching loops
- DMSTP, which falls back to RSTP behaviour toward neighbours that do not use MST regions Correct answer
Answer and explanation: FortiSwitch uses MSTP (802.1s) by default, which is backward compatible with RSTP and treats non-MST neighbours as a separate region. FortiSwitch does not run per-VLAN spanning tree as its protocol (it can only interoperate with Rapid PVST+ neighbours), it does not default to legacy 802.1D, and loop guard is an extra feature for ports where STP is not running rather than a replacement for STP.
Question 2 of 10, FortiSwitch Concepts
Voice traffic marked with DSCP EF must leave a FortiSwitch port before bulk data, but bulk data must not be starved completely during congestion. Which egress queue configuration fits best?
- AMap EF to a high queue and use strict scheduling for all queues, so lower queues are served only when idle
- BTrust 802.1p on the port and disable the egress policy, letting the IP phone decide the transmission order
- CMap EF to queue 0 and use strict scheduling, assuming the scheduler always serves queue 0 ahead of every higher-numbered queue
- DMap EF to a high queue and use weighted scheduling, giving that queue the largest weight without starving lower queues Correct answer
Answer and explanation: Weighted scheduling lets the queue carrying EF receive most of the bandwidth while still guaranteeing some service to other queues, which meets the no-starvation requirement. Strict scheduling for all queues can starve lower queues under congestion, mapping EF to the lowest queue gives it the worst treatment, and trusting markings without an egress policy does not control transmission order.
Question 3 of 10, FortiSwitch Concepts
A 100G port on a FortiSwitch must connect to four servers using a breakout cable. What must the administrator expect when configuring the split port?
- AThe port is split into four interfaces immediately, and each one inherits the 100G speed of the parent
- BThe port is split into two 50G interfaces only, because four-way breakout is limited to 40G ports
- CThe breakout is negotiated automatically by the transceiver and cable, so no split-port configuration is needed
- DThe port is split into four lower-speed interfaces, and the switch must reboot before the new ports appear Correct answer
Answer and explanation: Configuring split ports changes the physical port layout, and FortiSwitch requires a reboot for the new sub-ports to become available; a 100G port typically breaks out into four 25G lanes. The sub-ports cannot keep the full parent speed, the split is not auto-negotiated by the transceiver, and four-way breakout is supported on capable 100G ports as well as 40G ports.
Question 4 of 10, Deployment and Management
Two tier-1 FortiSwitch units form an MCLAG pair, and the FortiGate connects to both with one FortiLink aggregate. What makes this design work as a single logical link from the FortiGate's point of view?
- AFortiLink split interface mode, which keeps one aggregate member active and the other member in standby at all times
- BA hardware switch on the FortiGate that bridges both members and relies on loop guard to stop loops
- CSTP on the FortiGate aggregate, which blocks one member until the active switch fails over
- DThe ICL between the two switches lets them present one LACP partner, so both FortiLink members stay active Correct answer
Answer and explanation: In an MCLAG, the inter-chassis link synchronizes the peer switches so they appear as one LACP partner, allowing an active-active aggregate to the FortiGate. Split interface mode is used when the two switches are not an MCLAG pair and keeps only one link active, the FortiGate does not run STP on the aggregate for this purpose, and a hardware switch would create a bridge rather than a LAG.
Question 5 of 10, Deployment and Management
A new FortiSwitch appears on the FortiGate's Managed FortiSwitches page shortly after being cabled to the FortiLink port, but it does not receive any configuration. What step is still required?
- AAuthorize the switch on the FortiGate so that it becomes a managed member of the FortiLink Correct answer
- BRegister the switch serial number with FortiGuard so the FortiGate is allowed to push VLANs
- CUpgrade the switch to the FortiGate firmware build number before it can join the stack
- DCreate a firewall policy from the FortiLink interface to the switch so CAPWAP can pass
Answer and explanation: Discovered switches stay unauthorized until an administrator authorizes them (or they are pre-authorized), and only then does the FortiGate push configuration. FortiGuard registration is not required for FortiLink authorization, FortiLink control traffic does not need a firewall policy, and FortiSwitchOS and FortiOS use separate firmware versions checked against a compatibility matrix.
Question 6 of 10, Deployment and Management
An administrator wants a FortiSwitch to be accepted and configured automatically the moment it is plugged into the FortiLink at a branch, without anyone logging in to authorize it. What should be done before shipping the switch?
- AAdd the switch to FortiLAN Cloud and then plug it into the FortiGate so both manage it jointly
- BPre-authorize the switch on the FortiGate by entering its serial number and the desired port settings Correct answer
- CFactory reset the switch and set it to standalone mode so that it pulls its configuration from the DHCP server at boot
- DEnable auto-isl on the FortiGate FortiLink interface so any discovered switch authorizes itself
Answer and explanation: Pre-authorization (pre-provisioning) by serial number lets the FortiGate accept the switch as soon as it is discovered and apply the configuration prepared in advance. Auto-ISL forms inter-switch links but does not authorize switches, standalone mode prevents FortiLink management, and a switch is managed by either FortiLAN Cloud or a FortiGate, not both at once.
Question 7 of 10, Layer 2 Control and Security
A RADIUS server must place authenticated engineering users into VLAN 40 and finance users into VLAN 50 on the same FortiSwitch ports. What enables this?
- ADynamic VLAN assignment, where RADIUS returns tunnel attributes naming the VLAN for each user Correct answer
- BA native VLAN per port, which the switch changes when it learns the user's DHCP hostname
- CA guest VLAN, which RADIUS changes per user group by sending an Access-Reject with a VLAN ID
- DAn egress ACL per VLAN, which rewrites the VLAN tag after authentication succeeds on the port
Answer and explanation: With dynamic VLAN assignment, RADIUS includes Tunnel-Type, Tunnel-Medium-Type and Tunnel-Private-Group-Id in Access-Accept, and FortiSwitch puts the session into that VLAN. A guest VLAN is used for devices without a supplicant or failed authentication, the switch does not change native VLANs based on DHCP hostnames, and ACLs are not the mechanism for RADIUS-driven VLAN placement.
Question 8 of 10, Layer 2 Control and Security
A FortiGate must place IP cameras into a camera VLAN automatically when they are connected to any managed FortiSwitch port, based on device attributes. Which feature should be used?
- AAn LLDP-MED network policy that advertises the camera VLAN to every device on every port
- BA DHCP snooping profile that leases addresses from the camera subnet to matching MAC vendors
- CAn 802.1X security policy with a guest VLAN set to the camera VLAN for any device without a supplicant
- DA NAC policy matching the device type that assigns the camera VLAN, with ports in NAC mode Correct answer
Answer and explanation: FortiGate NAC policies match devices by attributes such as type, vendor or user group and move the matched port to the assigned VLAN; ports set to NAC mode start in the onboarding VLAN. LLDP-MED network policy is used by phones and similar endpoints, DHCP snooping does not change VLANs, and a guest VLAN catches every device without a supplicant rather than cameras only.
Question 9 of 10, Monitoring and Troubleshooting. Choose 2.
Which outputs help an administrator confirm on a FortiGate that a managed FortiSwitch has learned a particular host's MAC address and on which port? (Choose two.)
- Aexecute switch-controller get-sync-status for the managed switch
- Bdiagnose switch-controller switch-info mac-table on the FortiGate Correct answer
- Cget system arp on the FortiGate for hosts in other routed subnets
- DThe FortiSwitch Clients or device inventory view in the FortiGate GUI Correct answer
- Ediagnose debug application fnbamd for the switch authentication
Answer and explanation: The switch-info mac-table diagnostic retrieves the MAC table from managed switches, and the GUI client/device views show where each host was learned. The FortiGate ARP table does not show switch ports and does not include hosts in other subnets, fnbamd debugging traces authentication, and get-sync-status reports configuration synchronization.
Question 10 of 10, Monitoring and Troubleshooting
Which FortiSwitch CLI command shows the LLDP neighbours discovered on each port?
- Aget switch lldp neighbors-summary Correct answer
- Bget system interface physical
- Cget switch stp instance
- Ddiagnose switch trunk list
Answer and explanation: get switch lldp neighbors-summary lists the neighbour learned through LLDP on each port. The STP instance command shows spanning tree state, trunk list shows LAG membership, and get system interface physical shows interface status on FortiOS rather than LLDP neighbours.