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

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.

Question 21

On port24 serving the hospital wing, 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. Always admit the frame regardless of tag format
  2. Place the frame in a new private VLAN automatically
  3. Reject this frame before normal forwarding
  4. Replace the source MAC address with the FortiSwitch management address

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

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

B:

Under the indicated discard-mode on port24, 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 port24.

Question 22

An administrator configuring the factory has set port31 native VLAN to 120 and allowed VLANs to 127, 133, 145. The port receives a VLAN 145-tagged frame. What is its VLAN status immediately after the ingress checks?

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

Explanation

Correct Answer

B:

The received tag 145 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 port31, 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 port31, 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 port31, VLAN 219 is not configured on this port and FortiSwitch does not assign an unrelated VLAN at this ingress stage.

Question 23

For the warehouse, an administrator applies the action “Drop untagged input using all-untagged discard mode.” Which effect should appear when it operates as intended?

  1. MAC-based VLAN assignment maps a matching source hardware address to its configured network
  2. An egress frame for an explicitly untagged VLAN is transmitted after its tag is stripped
  3. Discard-mode all-untagged filters frames lacking an 802.1Q tag before ordinary VLAN processing
  4. Discard-mode all-tagged filters tagged arrivals at ingress rather than rewriting them
  5. Tagged trunk forwarding preserves each non-native VLAN identity across the shared link

Explanation

Correct Answer

C:

The switch behavior that matters is: the configured operation is meant to require attached infrastructure to send tagged frames only. The most relevant validation is to send an untagged test packet and verify the ingress filter rejects it for the equipment at the warehouse.

Incorrect Answers

A:

That behavior applies when engineers “Assign a source MAC to a configured VLAN policy”; the different operation “Drop untagged input using all-untagged discard mode” is intended to require attached infrastructure to send tagged frames only. That different feature is verified by match the learned MAC with its configured VLAN and resulting port forwarding state; for “Drop untagged input using all-untagged discard mode” on a switch serving a high-density endpoint area, the relevant evidence is to send an untagged test packet and verify the ingress filter rejects it.

B:

That behavior applies when engineers “Use an untagged VLAN list on an egress port”; the different operation “Drop untagged input using all-untagged discard mode” is intended to require attached infrastructure to send tagged frames only. That different feature is verified by capture egress Ethernet headers and verify the selected VLAN leaves without a tag; for “Drop untagged input using all-untagged discard mode” on a switch serving a high-density endpoint area, the relevant evidence is to send an untagged test packet and verify the ingress filter rejects it.

D:

That behavior applies when engineers “Drop tagged input using all-tagged discard mode”; the different operation “Drop untagged input using all-untagged discard mode” is intended to require attached infrastructure to send tagged frames only. That different feature is verified by send tagged and untagged test traffic and inspect which type the interface admits; for “Drop untagged input using all-untagged discard mode” on a switch serving a high-density endpoint area, the relevant evidence is to send an untagged test packet and verify the ingress filter rejects it.

E:

This outcome would be relevant to “Use 802.1Q tagged trunk membership between switches” at the warehouse, not the task “Drop untagged input using all-untagged discard mode”; the other task is to carry multiple independently isolated VLANs over one physical uplink. The action “Drop untagged input using all-untagged discard mode” targets a different result: discard-mode all-untagged filters frames lacking an 802.1Q tag before ordinary VLAN processing; the proposed alternative would instead be checked by compare the sequence of 802.1Q tags observed at both switch ends.

Question 24

An auditor wants operational evidence for the switch action “Read the 12-bit VLAN identifier in an 802.1Q tag” at the remote depot. Which check is relevant?

  1. Inspect EtherType in a sample packet and compare its assigned VLAN
  2. Capture a broadcast on same-VLAN and other-VLAN access ports
  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

C:

At this network boundary, the 802.1Q tag contains a twelve-bit VID field that identifies the VLAN. Directly measuring that result demonstrates whether the step to identify the forwarding VLAN separately from any priority bits in a tagged Ethernet frame succeeded on a managed switch running FortiSwitchOS 7.6.

Incorrect Answers

A:

The proposed check concerns “Classify VLAN membership from Ethernet protocol type” rather than “Read the 12-bit VLAN identifier in an 802.1Q tag”: protocol-based VLAN classification selects the segment from frame protocol information. For “Read the 12-bit VLAN identifier in an 802.1Q tag” on a managed switch running FortiSwitchOS 7.6, a better test would be to inspect the tag-control information and decode its VID independently of PCP, which targets identify the forwarding VLAN separately from any priority bits in a tagged Ethernet frame rather than the alternative diagnostic “Classify VLAN membership from Ethernet protocol type”.

B:

This check is suited to “Segment clients into distinct VLAN broadcast domains” when trying to prevent a local broadcast from reaching hosts in an unrelated workgroup, not to verify “Read the 12-bit VLAN identifier in an 802.1Q tag” at the remote depot. Checking “Read the 12-bit VLAN identifier in an 802.1Q tag” at the remote depot requires evidence of its own mechanism: the 802.1Q tag contains a twelve-bit VID field that identifies the VLAN; that is not the outcome measured by “Segment clients into distinct VLAN broadcast domains”.

D:

This check is suited to “Use an untagged VLAN list on an egress port” when trying to transmit a selected non-native VLAN without a tag to a device that does not parse 802.1Q, not to verify “Read the 12-bit VLAN identifier in an 802.1Q tag” at the remote depot. Checking “Read the 12-bit VLAN identifier in an 802.1Q tag” at the remote depot requires evidence of its own mechanism: the 802.1Q tag contains a twelve-bit VID field that identifies the VLAN; that is not the outcome measured by “Use an untagged VLAN list on an egress port”.

Question 25

At the retail site, FortiSwitch port13 uses native VLAN 140, allowed VLANs 147, 153, 165, and discard-mode none. A tagged frame with VLAN ID 153 arrives. What is the correct ingress decision?

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

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

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

B:

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

D:

For the received tagged VLAN on port13, 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 140 and allowed IDs are 147, 153, 165; those exact values, not tag validity alone, control the decision.

Question 26

A FortiSwitch in the airport office forwards an internally tagged VLAN 247 frame toward port20. That egress port has native VLAN 202, allowed VLANs 209, 215, 227, and untagged VLANs 235. What goes onto the wire?

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

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

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

B:

For the outgoing Ethernet frame at port20, 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 247 into VLAN 301.

C:

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

Question 27

A production incident in the distribution floor reveals the need to separate a traffic-priority marking from the VLAN identification on a trunk. Which targeted FortiSwitch setting or method should the team use?

  1. Use 802.1Q tagged trunk membership between switches
  2. Classify VLAN membership from Ethernet protocol type
  3. Read the 3-bit PCP field in an 802.1Q tag
  4. Use an untagged VLAN list on an egress port
  5. Segment clients into distinct VLAN broadcast domains

Explanation

Correct Answer

C:

The deciding detail is that priority Code Point occupies three bits and can represent service classes without changing the VID. This distinction is material to the distribution floor, where the stated goal is to separate a traffic-priority marking from the VLAN identification on a trunk.

Incorrect Answers

A:

Compared with the requested “Read the 3-bit PCP field in an 802.1Q tag” at the distribution floor, this would carry multiple independently isolated VLANs over one physical uplink instead: tagged trunk forwarding preserves each non-native VLAN identity across the shared link. At the distribution floor, the operational proof would instead be to decode the PCP bits and verify the VLAN ID is still the value in the VID field, whereas “Use 802.1Q tagged trunk membership between switches” is validated by a different test: compare the sequence of 802.1Q tags observed at both switch ends.

B:

Compared with the requested “Read the 3-bit PCP field in an 802.1Q tag” at the distribution floor, this would map selected Layer 2 payload protocols to different VLANs at a defined ingress point instead: protocol-based VLAN classification selects the segment from frame protocol information. At the distribution floor, the operational proof would instead be to decode the PCP bits and verify the VLAN ID is still the value in the VID field, whereas “Classify VLAN membership from Ethernet protocol type” is validated by a different test: inspect EtherType in a sample packet and compare its assigned VLAN.

D:

For the distribution floor, “Use an untagged VLAN list on an egress port” is a different type of control from “Read the 3-bit PCP field in an 802.1Q tag”: an egress frame for an explicitly untagged VLAN is transmitted after its tag is stripped. Unlike the requested feature, that setting addresses the need to transmit a selected non-native VLAN without a tag to a device that does not parse 802.1Q, not the objective to separate a traffic-priority marking from the VLAN identification on a trunk.

E:

Compared with the requested “Read the 3-bit PCP field in an 802.1Q tag” at the distribution floor, this would prevent a local broadcast from reaching hosts in an unrelated workgroup instead: layer 2 VLAN membership restricts ordinary broadcast flooding to the given VLAN. At the distribution floor, the operational proof would instead be to decode the PCP bits and verify the VLAN ID is still the value in the VID field, whereas “Segment clients into distinct VLAN broadcast domains” is validated by a different test: capture a broadcast on same-VLAN and other-VLAN access ports.

Question 28

An administrator configuring the warehouse has set port34 native VLAN to 22 and allowed VLANs to 29, 35, 47. The port receives an untagged frame. What is its VLAN status immediately after the ingress checks?

  1. Classify it into native VLAN 22
  2. Require a DHCP lease before performing VLAN classification
  3. Replace its VLAN with 121 to preserve isolation
  4. Send it out port34 immediately without MAC learning

Explanation

Correct Answer

A:

The absence of a tag makes the native VLAN 22 apply automatically; the allowed list does not control this untagged admission.

Incorrect Answers

B:

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

C:

VLAN 121 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 port34, 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 29

For the retail site, an administrator applies the action “Segment clients into distinct VLAN broadcast domains.” Which effect should appear when it operates as intended?

  1. A PVLAN community can communicate internally and reach the primary promiscuous gateway
  2. Discard-mode all-tagged filters tagged arrivals at ingress rather than rewriting them
  3. Both ends must agree on native VLAN handling when untagged frames are exchanged
  4. Layer 2 VLAN membership restricts ordinary broadcast flooding to the given VLAN

Explanation

Correct Answer

D:

This approach fits because the configured operation is meant to prevent a local broadcast from reaching hosts in an unrelated workgroup. The most relevant validation is to capture a broadcast on same-VLAN and other-VLAN access ports for the equipment at the retail site.

Incorrect Answers

A:

That behavior applies when engineers “Use a community private VLAN for a shared tenant group”; the different operation “Segment clients into distinct VLAN broadcast domains” is intended to prevent a local broadcast from reaching hosts in an unrelated workgroup. That different feature is verified by test one in-community path and an inter-community path to verify the boundary; for “Segment clients into distinct VLAN broadcast domains” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to capture a broadcast on same-VLAN and other-VLAN access ports.

B:

That behavior applies when engineers “Drop tagged input using all-tagged discard mode”; the different operation “Segment clients into distinct VLAN broadcast domains” is intended to prevent a local broadcast from reaching hosts in an unrelated workgroup. That different feature is verified by send tagged and untagged test traffic and inspect which type the interface admits; for “Segment clients into distinct VLAN broadcast domains” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to capture a broadcast on same-VLAN and other-VLAN access ports.

C:

This outcome would be relevant to “Correct inconsistent native VLAN expectations at both ends” at the retail site, not the task “Segment clients into distinct VLAN broadcast domains”; the other task is to stop untagged uplink traffic from being classified into a different VLAN by the peer. The action “Segment clients into distinct VLAN broadcast domains” targets a different result: layer 2 VLAN membership restricts ordinary broadcast flooding to the given VLAN; the proposed alternative would instead be checked by compare effective native VLAN settings at both ends and capture an untagged frame.

Question 30

After implementing “Use 802.1Q tagged trunk membership between switches,” the site engineer needs to assess its actual effect on a switch serving a high-density endpoint area. Which test is the best match?

  1. Inspect both the outer service tag and the preserved inner customer VID
  2. Compare the sequence of 802.1Q tags observed at both switch ends
  3. Inspect the tag-control information and decode its VID independently of PCP
  4. Inject an untagged test frame and inspect its learned VLAN membership

Explanation

Correct Answer

B:

The critical distinction is that tagged trunk forwarding preserves each non-native VLAN identity across the shared link. Directly measuring that result demonstrates whether the step to carry multiple independently isolated VLANs over one physical uplink succeeded on a switch serving a high-density endpoint area.

Incorrect Answers

A:

This check is suited to “Apply VLAN stacking with an outer service tag” when trying to transport customer VLAN identifiers without treating all customer networks as one provider VLAN, not to verify “Use 802.1Q tagged trunk membership between switches” at the airport office. Checking “Use 802.1Q tagged trunk membership between switches” at the airport office requires evidence of its own mechanism: tagged trunk forwarding preserves each non-native VLAN identity across the shared link; that is not the outcome measured by “Apply VLAN stacking with an outer service tag”.

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 802.1Q tagged trunk membership between switches” at the airport office. Checking “Use 802.1Q tagged trunk membership between switches” at the airport office requires evidence of its own mechanism: tagged trunk forwarding preserves each non-native VLAN identity across the shared link; that is not the outcome measured by “Read the 12-bit VLAN identifier in an 802.1Q tag”.

D:

The proposed check concerns “Configure an explicit native VLAN for untagged input” rather than “Use 802.1Q tagged trunk membership between switches”: untagged Ethernet frames are internally associated with the ingress port's native VLAN. For “Use 802.1Q tagged trunk membership between switches” on a switch serving a high-density endpoint area, a better test would be to compare the sequence of 802.1Q tags observed at both switch ends, which targets carry multiple independently isolated VLANs over one physical uplink rather than the alternative diagnostic “Configure an explicit native VLAN for untagged input”.

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