Sure Pass Exam NSE5_FSW_AD-7.6 PDF

According to theFortiSwitchOS 7.6 Administration Guideand theFortiLink 7.6 Study Guide, the Spanning Tree Protocol (STP) is automatically enabled on managed FortiSwitches to ensure a loop-free Layer 2 topology within the FortiLink fabric. When multiple physical paths exist between switches (as shown in the redundant connections between the Core and Access tiers), STP must block one of the paths to prevent a broadcast storm.

The behavior described in the exhibit—whereport3 on Access-1enters aDiscarding state—is a result of the STP election process. In a standard STP environment, switches elect aRoot Bridgebased on the lowestBridge Priority(or lowest MAC address as a tie-breaker). Once a root is established, other switches identify the " best " path to that root (the Root Port) and block all other redundant paths.

The provided exhibit shows that Access-1 has two paths to the core: one to Core-1 and one to Core-2. The fact that the path to Core-2 is discarded suggests that the STP topology was recalculated when Core-2 was enabled. In the context of Fortinet technical exams for this specific scenario,Option C (Core-2 has the lowest bridge priority)is the standard answer identifying that Core-2 ' s priority settings influenced the STP tree such that Access-1 ' s link to it was determined to be the redundant (alternate) path.

If the switches were configured withMCLAG (Multi-Chassis Link Aggregation), both physical links would be treated as a single logical trunk, and neither would be in a discarding state. However, without MCLAG, the system relies on bridge priorities to prune the loop.BPDU Guard (Option A)is incorrect because it would administratively shut down the port rather than placing it in an STP " Discarding " state.Option Bis incorrect as the switch would not appear in the managed topology if unauthorized.

According to theFortiSwitchOS 7.6 Administration Guideand theFortiSwitch 7.6 Study Guide, Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) is an enhancement to standard LLDP that provides advanced discovery and configuration for endpoints li1ke IP phones. While the current configuration in the exhibit correctly handlesNetwork Policy TLVsto advertise QoS2and VLAN settings to the phones, it is missing the specific component required for data collection.34

To coll5ect detail6ed information such as themanufacturer, software version, hardware version, and serial or asset numbers, you mustEnable LLDP-MED inventory management TLVs (Option C). The documentation specifies that when the inventory-management TLV is active, the switch can retrieve these extensive device characteristics from the connected Media Endpoints. This information is then visible to the administrator through the FortiGate or FortiSwitch monitoring tools, providing a complete hardware inventory of the voice network.

Regarding the other options:Option Ais unnecessary because a single LLDP profile can support multiple TLV types simultaneously by adding them to the med-tlvs string.Option Bis already partially implemented in the exhibit ' s network policy but does not contribute to device detection or data collection.Option Dis used for automatic trunking between FortiSwitches and is unrelated to endpoint device information. Therefore, the addition of the inventory-management TLV is the specific requirement to fulfill the goal of collecting detailed IP phone data.

FortiGate ' s multi-tenancy feature, specifically Virtual Domains (VDOMs), is the most appropriate tool for segmenting network operations and the administration of managed FortiSwitch devices on FortiGate. Here ' s why:

VDOMs as Virtual Firewalls:VDOMs function as independent virtual firewalls within a single FortiGate device. Each VDOM can have its own:

Security policies

Interfaces (Including FortiLink interfaces for FortiSwitch management)

Routing table

Administrative access

Segmenting Network Operations:By assigning different FortiSwitch devices (or groups of ports) to separate VDOMs, you effectively partition your network. Network administrators can manage specific FortiSwitches through their assigned VDOMs, maintaining operational isolation.

Enhanced Administration:VDOMs offer granular administrative control. Different administrators can be assigned to specific VDOMs, limiting their management scope and reducing the risk of accidental configuration changes.

Why Other Options Are Less Suitable:

B. Multi-chassis link aggregation trunk:This focuses on link redundancy and bandwidth aggregation, not network segmentation.

C. FortiGate clustering protocol:This is aimed at high availability and scalability of the firewall functions themselves, not the management of switches.

D. FortiLink split interface:This allows dividing a FortiLink interface on the FortiGate for managing multiple FortiSwitches, but it doesn ' t provide the true segmentation and administrative isolation that VDOMs offer.

According to the FortiOS 7.6 Study Guide and the FortiSwitch 7.6 FortiLink Guide , when establishing a FortiLink connection between a standalone FortiGate unit and a single managed FortiSwitch unit, Fortinet supports two valid FortiLink interface architectures:

Single Physical Port (Option A): In basic or entry-level deployments, FortiLink can be enabled directly on a dedicated individual physical interface of the FortiGate (such as a hardware port designated for FortiLink or any unassigned internal Ethernet port). Under this deployment mode, a single physical Ethernet or fiber cable connects the FortiGate physical port directly to the FortiSwitch discovery port.

Link Aggregation Group (LAG) (Option D): Fortinet best-practice architecture recommends configuring the FortiLink interface as an 802.3ad aggregate interface (LAG). Even when connecting a single FortiGate to a single FortiSwitch, a LAG interface can bundle multiple physical links together to provide link redundancy, increased aggregate bandwidth, and seamless scalability for future link additions without disrupting the management tunnel.

Regarding the incorrect options:

Option B (Port channel): " Port channel " is vendor-specific terminology primarily used in Cisco IOS/NX-OS platforms. In Fortinet documentation and GUI/CLI commands, 802.3ad multi-link bundles are strictly defined and configured as 802.3ad aggregate or LAG interfaces.

Option C (Switchport mode trunk): " Switchport mode trunk " is also Cisco syntax. Within Fortinet FortiOS and FortiSwitchOS environments, trunking and tagging behavior is defined by setting the Native VLAN and adding secondary subnets into the Allowed VLANs list on a physical or aggregate interface, rather than using Cisco switchport command modes.