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

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.

Question 11

The operational requirement for an access switch in routine maintenance at the retail site is to classify untagged ingress frames into the intended local VLAN rather than VLAN carried by a tag. Which FortiSwitch choice directly targets it?

  1. Drop untagged input using all-untagged discard mode
  2. Configure an explicit native VLAN for untagged input
  3. Use a community private VLAN for a shared tenant group
  4. Correct inconsistent native VLAN expectations at both ends

Explanation

Correct Answer

B:

The switch behavior that matters is: untagged Ethernet frames are internally associated with the ingress port's native VLAN. This distinction is material to the retail site, where the stated goal is to classify untagged ingress frames into the intended local VLAN rather than VLAN carried by a tag.

Incorrect Answers

A:

Compared with the requested “Configure an explicit native VLAN for untagged input” at the retail site, this would require attached infrastructure to send tagged frames only instead: discard-mode all-untagged filters frames lacking an 802.1Q tag before ordinary VLAN processing. At the retail site, the operational proof would instead be to inject an untagged test frame and inspect its learned VLAN membership, whereas “Drop untagged input using all-untagged discard mode” is validated by a different test: send an untagged test packet and verify the ingress filter rejects it.

C:

For the retail site, “Use a community private VLAN for a shared tenant group” is a different type of control from “Configure an explicit native VLAN for untagged input”: a PVLAN community can communicate internally and reach the primary promiscuous gateway. Unlike the requested feature, that setting addresses the need to permit peers in one server community to communicate while excluding other communities, not the objective to classify untagged ingress frames into the intended local VLAN rather than VLAN carried by a tag.

D:

Compared with the requested “Configure an explicit native VLAN for untagged input” at the retail site, this would stop untagged uplink traffic from being classified into a different VLAN by the peer instead: both ends must agree on native VLAN handling when untagged frames are exchanged. At the retail site, the operational proof would instead be to inject an untagged test frame and inspect its learned VLAN membership, whereas “Correct inconsistent native VLAN expectations at both ends” is validated by a different test: compare effective native VLAN settings at both ends and capture an untagged frame.

Question 12

A switch change for the airport office consists of this step: add a required VLAN to the allowed list on a trunk. Which behavior reflects the purpose of that change?

  1. Both ends must agree on native VLAN handling when untagged frames are exchanged
  2. A PVLAN community can communicate internally and reach the primary promiscuous gateway
  3. QinQ carries an additional service tag outside the customer VLAN tag
  4. A tagged ingress frame is accepted when its VLAN ID is on the allowed or native VLAN list
  5. The 802.1Q tag contains a twelve-bit VID field that identifies the VLAN

Explanation

Correct Answer

D:

At this network boundary, the configured operation is meant to carry a particular non-native VLAN across an 802.1Q switch-to-switch link. The most relevant validation is to compare the tag in a test packet with the configured allowed VLAN list for the equipment at the airport office.

Incorrect Answers

A:

That behavior applies when engineers “Correct inconsistent native VLAN expectations at both ends”; the different operation “Add a required VLAN to the allowed list on a trunk” is intended to carry a particular non-native VLAN across an 802.1Q switch-to-switch link. That different feature is verified by compare effective native VLAN settings at both ends and capture an untagged frame; for “Add a required VLAN to the allowed list on a trunk” on a managed campus switch, the relevant evidence is to compare the tag in a test packet with the configured allowed VLAN list.

B:

This outcome would be relevant to “Use a community private VLAN for a shared tenant group” at the airport office, not the task “Add a required VLAN to the allowed list on a trunk”; the other task is to permit peers in one server community to communicate while excluding other communities. The action “Add a required VLAN to the allowed list on a trunk” targets a different result: a tagged ingress frame is accepted when its VLAN ID is on the allowed or native VLAN list; the proposed alternative would instead be checked by test one in-community path and an inter-community path to verify the boundary.

C:

That behavior applies when engineers “Apply VLAN stacking with an outer service tag”; the different operation “Add a required VLAN to the allowed list on a trunk” is intended to carry a particular non-native VLAN across an 802.1Q switch-to-switch link. That different feature is verified by inspect both the outer service tag and the preserved inner customer VID; for “Add a required VLAN to the allowed list on a trunk” on a managed campus switch, the relevant evidence is to compare the tag in a test packet with the configured allowed VLAN list.

E:

That behavior applies when engineers “Read the 12-bit VLAN identifier in an 802.1Q tag”; the different operation “Add a required VLAN to the allowed list on a trunk” is intended to carry a particular non-native VLAN across an 802.1Q switch-to-switch link. That different feature is verified by inspect the tag-control information and decode its VID independently of PCP; for “Add a required VLAN to the allowed list on a trunk” on a managed campus switch, the relevant evidence is to compare the tag in a test packet with the configured allowed VLAN list.

Question 13

At the training center, FortiSwitch port7 uses native VLAN 120, allowed VLANs 127, 133, 145, and discard-mode none. A tagged frame with VLAN ID 120 arrives. What is the correct ingress decision?

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

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

For the received tagged VLAN on port7, 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 120 and allowed IDs are 127, 133, 145; those exact values, not tag validity alone, control the decision.

B:

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

D:

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

Question 14

A FortiSwitch in the lab forwards an internally tagged VLAN 155 frame toward port14. That egress port has native VLAN 122, allowed VLANs 129, 135, 147, and untagged VLANs 155. 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 221
  4. Forward the frame carrying VLAN tag 155

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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

C:

For the outgoing Ethernet frame at port14, 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 155 into VLAN 221.

D:

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

Question 15

On port21 serving the media studio, discard-mode is all-untagged and a frame with an 802.1Q tag 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. Allow this frame type to proceed to ordinary VLAN processing
  3. Place the frame in a new private VLAN automatically
  4. Replace the source MAC address with the FortiSwitch management address

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

Under the indicated discard-mode on port21, 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 port21, the arriving frame type determines whether the filter applies.

C:

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

D:

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

Question 16

An administrator configuring the retail site has set port28 native VLAN to 310 and allowed VLANs to 317, 323, 335. The port receives a VLAN 355-tagged frame. What is its VLAN status immediately after the ingress checks?

  1. Require a DHCP lease before performing VLAN classification
  2. Replace its VLAN with 409 to preserve isolation
  3. Reject the VLAN 355 frame
  4. Send it out port28 immediately without MAC learning

Explanation

Correct Answer

C:

Tagged traffic for VLAN 355 is absent from both native and allowed VLAN memberships, so ingress rejects it. A disallowed tag cannot reach the later MAC lookup and egress-port decision.

Incorrect Answers

A:

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

B:

VLAN 409 is not configured on this port and FortiSwitch does not assign an unrelated VLAN at this ingress stage.

D:

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

Question 17

An auditor wants operational evidence for the switch action “Use an untagged VLAN list on an egress port” at the factory. Which check is relevant?

  1. Test one in-community path and an inter-community path to verify the boundary
  2. Compare effective native VLAN settings at both ends and capture an untagged frame
  3. Inspect the tag-control information and decode its VID independently of PCP
  4. Capture egress Ethernet headers and verify the selected VLAN leaves without a tag

Explanation

Correct Answer

D:

This approach fits because an egress frame for an explicitly untagged VLAN is transmitted after its tag is stripped. Directly measuring that result demonstrates whether the step to transmit a selected non-native VLAN without a tag to a device that does not parse 802.1Q succeeded on a FortiSwitch connected to the security edge.

Incorrect Answers

A:

The proposed check concerns “Use a community private VLAN for a shared tenant group” rather than “Use an untagged VLAN list on an egress port”: a PVLAN community can communicate internally and reach the primary promiscuous gateway. For “Use an untagged VLAN list on an egress port” on a FortiSwitch connected to the security edge, a better test would be to capture egress Ethernet headers and verify the selected VLAN leaves without a tag, which targets transmit a selected non-native VLAN without a tag to a device that does not parse 802.1Q rather than the alternative diagnostic “Use a community private VLAN for a shared tenant group”.

B:

This check is suited to “Correct inconsistent native VLAN expectations at both ends” when trying to stop untagged uplink traffic from being classified into a different VLAN by the peer, not to verify “Use an untagged VLAN list on an egress port” at the factory. Checking “Use an untagged VLAN list on an egress port” at the factory requires evidence of its own mechanism: an egress frame for an explicitly untagged VLAN is transmitted after its tag is stripped; that is not the outcome measured by “Correct inconsistent native VLAN expectations at both ends”.

C:

This check is suited to “Read the 12-bit VLAN identifier in an 802.1Q tag” when trying to identify the forwarding VLAN separately from any priority bits in a tagged Ethernet frame, not to verify “Use an untagged VLAN list on an egress port” at the factory. Checking “Use an untagged VLAN list on an egress port” at the factory requires evidence of its own mechanism: an egress frame for an explicitly untagged VLAN is transmitted after its tag is stripped; that is not the outcome measured by “Read the 12-bit VLAN identifier in an 802.1Q tag”.

Question 18

The accepted design for the distribution floor requires the ability to forbid 802.1Q-tagged input on a port reserved for ordinary untagged hosts. Which switch feature is the closest fit?

  1. Read the 3-bit PCP field in an 802.1Q tag
  2. Add a required VLAN to the allowed list on a trunk
  3. Prune unnecessary VLANs from an inter-switch link
  4. Drop tagged input using all-tagged discard mode

Explanation

Correct Answer

D:

The critical distinction is that discard-mode all-tagged filters tagged arrivals at ingress rather than rewriting them. The operator can test this claim by the specific check: send tagged and untagged test traffic and inspect which type the interface admits.

Incorrect Answers

A:

Compared with the requested “Drop tagged input using all-tagged discard mode” at the distribution floor, this would separate a traffic-priority marking from the VLAN identification on a trunk instead: priority Code Point occupies three bits and can represent service classes without changing the VID. At the distribution floor, the operational proof would instead be to send tagged and untagged test traffic and inspect which type the interface admits, whereas “Read the 3-bit PCP field in an 802.1Q tag” is validated by a different test: decode the PCP bits and verify the VLAN ID is still the value in the VID field.

B:

For the distribution floor, “Add a required VLAN to the allowed list on a trunk” is a different type of control from “Drop tagged input using all-tagged discard mode”: a tagged ingress frame is accepted when its VLAN ID is on the allowed or native VLAN list. Unlike the requested feature, that setting addresses the need to carry a particular non-native VLAN across an 802.1Q switch-to-switch link, not the objective to forbid 802.1Q-tagged input on a port reserved for ordinary untagged hosts.

C:

Compared with the requested “Drop tagged input using all-tagged discard mode” at the distribution floor, this would avoid carrying VLAN traffic over a stack segment with no users of that VLAN instead: VLAN pruning limits trunk VLAN transport based on which downstream memberships require it. At the distribution floor, the operational proof would instead be to send tagged and untagged test traffic and inspect which type the interface admits, whereas “Prune unnecessary VLANs from an inter-switch link” is validated by a different test: inspect the effective tagged VLAN membership on an ISL before and after pruning.

Question 19

At the warehouse, FortiSwitch port10 uses native VLAN 22, allowed VLANs 29, 35, 47, and discard-mode none. A tagged frame with VLAN ID 67 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 22
  3. Accept the frame because its tag is an arbitrary valid 802.1Q ID
  4. Forward it into VLAN 55 because that is the untagged egress list

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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

C:

For the received tagged VLAN on port10, 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 port10, the configured native value is 22 and allowed IDs are 29, 35, 47; those exact values, not tag validity alone, control the decision.

D:

For the received tagged VLAN on port10, 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.

Question 20

A FortiSwitch in the headquarters forwards an internally tagged VLAN 87 frame toward port17. That egress port has native VLAN 62, allowed VLANs 69, 75, 87, and untagged VLANs 95. What goes onto the wire?

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

Explanation

Correct Answer

C:

VLAN 87 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 87 matches an explicitly untagged egress VLAN; that classification removes the header before the frame exits.

B:

For the outgoing Ethernet frame at port17, 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 87 into VLAN 161.

D:

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

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