Fortinet NSE5_FSW_AD-7.6 (Fortinet NSE 5 - FortiSwitch 7.6 Administrator) Practice Test 1

Question 1

At the warehouse, FortiSwitch port1 uses native VLAN 22, allowed VLANs 29, 35, 47, and discard-mode none. A tagged frame with VLAN ID 47 arrives. What is the correct ingress decision?

  1. Accept the frame into VLAN 47 without changing its VLAN classification
  2. Discard the frame for failing the allowed-VLAN check
  3. Forward it into VLAN 55 because that is the untagged egress list
  4. Remove the 802.1Q header and assign VLAN 22

Explanation

Correct Answer

A:

For the received tagged VLAN on port1, the ingress filter compares a tagged frame against both the native VLAN and the explicit allowed list. Here VLAN 47 matches a permitted value, so its VLAN identity is retained.

Incorrect Answers

B:

For the received tagged VLAN on port1, a tagged ingress frame is allowed only when its VLAN ID equals the native VLAN or appears among allowed VLANs. For the received tagged VLAN on port1, the configured native value is 22 and allowed IDs are 29, 35, 47; those exact values, not tag validity alone, control the decision.

C:

For the received tagged VLAN on port1, the untagged VLAN list governs how eligible traffic exits a port, rather than allowing ingress traffic to select VLAN 55. It cannot override the tag classification on this arrival.

D:

For the received tagged VLAN on port1, native VLAN assignment occurs when an arriving frame is untagged. This frame already carries VLAN 47; ingress filtering does not recast a tagged packet as native merely because of this port setting.

Question 2

A FortiSwitch in the headquarters forwards an internally tagged VLAN 57 frame toward port8. That egress port has native VLAN 24, allowed VLANs 31, 37, 49, and untagged VLANs 57. What goes onto the wire?

  1. Forward the frame carrying VLAN tag 57
  2. Drop the frame at egress due to VLAN membership
  3. Rewrite the frame to use VLAN 123
  4. Send the frame without an 802.1Q tag

Explanation

Correct Answer

D:

VLAN 57 matches an explicitly untagged egress VLAN; that classification removes the header before the frame exits.

Incorrect Answers

A:

VLAN 57 belongs to the allowed VLAN list but is not native or configured for untagged egress, so the 802.1Q header remains.

B:

VLAN 57 is outside the configured native, untagged and allowed egress memberships; the port cannot transmit it.

C:

For the outgoing Ethernet frame at port8, the FortiSwitch native, allowed and untagged settings decide whether a frame can leave and whether its existing tag is stripped. They do not arbitrarily translate VLAN 57 into VLAN 123.

Question 3

On port15 serving the hospital wing, discard-mode is none and an untagged Ethernet frame reaches the interface. Assume its VLAN would otherwise be allowed. What does discard-mode do?

  1. Always discard the frame before VLAN membership checking
  2. Place the frame in a new private VLAN automatically
  3. Replace the source MAC address with the FortiSwitch management address
  4. Allow this frame type to proceed to ordinary VLAN processing

Explanation

Correct Answer

D:

The none setting does not exclude this frame type. Under the indicated discard-mode on port15, its packet-type filter is checked separately from native and allowed-VLAN classification.

Incorrect Answers

A:

Discard-mode none is selective: all-tagged rejects tagged input, all-untagged rejects untagged input, and none rejects neither type. Under the indicated discard-mode on port15, the arriving frame type determines whether the filter applies.

B:

Private VLAN associations are configured explicitly, not triggered by the ingress discard-mode value none. A private-VLAN mapping is a separate switch configuration and cannot be inferred from an ingress frame-type filter.

C:

Discard-mode never rewrites source MAC addressing; it limits which tagged or untagged frame types may enter port15.

Question 4

An administrator configuring the training center has set port22 native VLAN to 130 and allowed VLANs to 137, 143, 155. The port receives a VLAN 143-tagged frame. What is its VLAN status immediately after the ingress checks?

  1. Send it out port22 immediately without MAC learning
  2. Keep VLAN 143 for forwarding
  3. Require a DHCP lease before performing VLAN classification
  4. Replace its VLAN with 229 to preserve isolation

Explanation

Correct Answer

B:

Before selecting a forwarding port after ingress on port22, the received tag 143 identifies the traffic and appears on the native or allowed list, so the frame retains that VLAN.

Incorrect Answers

A:

Before selecting a forwarding port after ingress on port22, the VLAN admission decision precedes ordinary MAC-table lookup and egress selection; admitting a frame does not mean immediate reflection out its ingress port.

C:

Before selecting a forwarding port after ingress on port22, frame tagging and VLAN membership operate at Layer 2 and do not require a DHCP address. DHCP snooping is a distinct optional protection.

D:

Before selecting a forwarding port after ingress on port22, VLAN 229 is not configured on this port and FortiSwitch does not assign an unrelated VLAN at this ingress stage.

Question 5

Two PCs in the lab share one FortiSwitch but use VLAN 132 and VLAN 145 respectively. Both ports have learned MAC addresses. They need IP connectivity without moving hosts into one VLAN. Which design handles the inter-VLAN traffic?

  1. Add both MAC addresses as static MAC entries
  2. Provide Layer 3 routing through SVIs or an appropriate FortiGate interface
  3. Enable LLDP-MED on both host ports
  4. Increase the STP bridge priority on one switch

Explanation

Correct Answer

B:

A Layer 2 MAC forwarding table is scoped to VLAN membership. Packets crossing from VLAN 132 to VLAN 145 require a routed gateway with interfaces for the relevant networks and suitable policies/routes.

Incorrect Answers

A:

A static MAC entry fixes where a destination is reached inside its VLAN. It does not route IP packets between separate broadcast domains.

C:

LLDP-MED advertises endpoint information such as voice-network policy; it does not create a routed path between VLAN 132 and 145.

D:

STP selects loop-free Layer 2 paths. Changing its bridge priority cannot supply the Layer 3 gateway required between the two VLANs.

Question 6

At the staging rack, port17 is a host-facing access port and port18 carries VLANs 214, 221 and 227 toward another FortiSwitch. The neighbor expects the non-native VLANs with 802.1Q tags. Which setting makes that possible?

  1. Move all hosts into the FortiSwitch management VLAN
  2. Make every uplink VLAN an untagged VLAN
  3. Configure the link as a promiscuous private-VLAN host port
  4. Permit VLANs 221 and 227 as tagged allowed VLANs on the uplink

Explanation

Correct Answer

D:

The inter-switch link must carry each non-native VLAN with its own 802.1Q identifier so frames remain segregated across the link. Set VLAN 214 as native only if that matches the peer.

Incorrect Answers

A:

The control-plane management VLAN is not a substitute for carrying production VLAN IDs across an uplink. Doing so also undermines traffic segmentation.

B:

Transmitting several different VLANs without their tags removes the identification the far-end trunk relies on. Untagged membership is appropriate only where the peer expects that egress handling.

C:

Promiscuous PVLAN ports handle private-VLAN access to shared services, not general 802.1Q trunk membership for VLANs 221 and 227.

Question 7

At the research building, FortiSwitch port4 uses native VLAN 40, allowed VLANs 47, 53, 65, and discard-mode none. A tagged frame with VLAN ID 73 arrives. What is the correct ingress decision?

  1. Discard the frame because VLAN membership does not permit it
  2. Remove the 802.1Q header and assign VLAN 40
  3. Accept the frame because its tag is an arbitrary valid 802.1Q ID
  4. Forward it into VLAN 73 because that is the untagged egress list

Explanation

Correct Answer

A:

For the received tagged VLAN on port4, the ingress filter compares a tagged frame against both the native VLAN and the explicit allowed list. Here VLAN 73 matches neither set, so the switch rejects it before normal VLAN forwarding.

Incorrect Answers

B:

For the received tagged VLAN on port4, native VLAN assignment occurs when an arriving frame is untagged. This frame already carries VLAN 73; ingress filtering does not recast a tagged packet as native merely because of this port setting.

C:

For the received tagged VLAN on port4, a tagged ingress frame is allowed only when its VLAN ID equals the native VLAN or appears among allowed VLANs. The configured native value is 40 and allowed IDs are 47, 53, 65; those exact values, not tag validity alone, control the decision.

D:

The untagged VLAN list governs how eligible traffic exits a port, rather than allowing ingress traffic to select VLAN 73. It cannot override the tag classification on this arrival.

Question 8

A FortiSwitch in the airport office forwards an internally tagged VLAN 109 frame toward port11. That egress port has native VLAN 102, allowed VLANs 109, 115, 127, and untagged VLANs 135. What goes onto the wire?

  1. Drop the frame at egress due to VLAN membership
  2. Send the frame without an 802.1Q tag
  3. Rewrite the frame to use VLAN 201
  4. Forward the frame carrying VLAN tag 109

Explanation

Correct Answer

D:

VLAN 109 belongs to the allowed VLAN list but is not native or configured for untagged egress, so the 802.1Q header remains.

Incorrect Answers

A:

VLAN 109 is outside the configured native, untagged and allowed egress memberships; the port cannot transmit it.

B:

VLAN 109 matches an explicitly untagged egress VLAN; that classification removes the header before the frame exits.

C:

For the outgoing Ethernet frame at port11, the FortiSwitch native, allowed and untagged settings decide whether a frame can leave and whether its existing tag is stripped. They do not arbitrarily translate VLAN 109 into VLAN 201.

Question 9

On port18 serving the operations center, discard-mode is all-untagged and an untagged Ethernet frame reaches the interface. Assume its VLAN would otherwise be allowed. What does discard-mode do?

  1. Reject this frame before normal forwarding
  2. Always admit the frame regardless of tag format
  3. Replace the source MAC address with the FortiSwitch management address
  4. Place the frame in a new private VLAN automatically

Explanation

Correct Answer

A:

The all-untagged setting excludes the arriving frame type. Under the indicated discard-mode on port18, its packet-type filter is checked separately from native and allowed-VLAN classification.

Incorrect Answers

B:

Under the indicated discard-mode on port18, discard-mode all-untagged is selective: all-tagged rejects tagged input, all-untagged rejects untagged input, and none rejects neither type. Under the indicated discard-mode on port18, the arriving frame type determines whether the filter applies.

C:

Discard-mode never rewrites source MAC addressing; it limits which tagged or untagged frame types may enter port18.

D:

Under the indicated discard-mode on port18, private VLAN associations are configured explicitly, not triggered by the ingress discard-mode value all-untagged.

Question 10

An administrator configuring the warehouse has set port25 native VLAN to 130 and allowed VLANs to 137, 143, 155. The port receives a VLAN 143-tagged frame. What is its VLAN status immediately after the ingress checks?

  1. Send it out port25 immediately without MAC learning
  2. Require a DHCP lease before performing VLAN classification
  3. Keep VLAN 143 for forwarding
  4. Replace its VLAN with 229 to preserve isolation

Explanation

Correct Answer

C:

Before selecting a forwarding port after ingress on port25, the received tag 143 identifies the traffic and appears on the native or allowed list, so the frame retains that VLAN.

Incorrect Answers

A:

Before selecting a forwarding port after ingress on port25, the VLAN admission decision precedes ordinary MAC-table lookup and egress selection; admitting a frame does not mean immediate reflection out its ingress port.

B:

Before selecting a forwarding port after ingress on port25, frame tagging and VLAN membership operate at Layer 2 and do not require a DHCP address. DHCP snooping is a distinct optional protection.

D:

Before selecting a forwarding port after ingress on port25, VLAN 229 is not configured on this port and FortiSwitch does not assign an unrelated VLAN at this ingress stage.

Fortinet NSE 5 - FortiSwitch 7.6 Administrator (NSE5_FSW_AD-7.6) Practice Tests