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

Question 40

An administrator configuring the factory has set port1 native VLAN to 10 and allowed VLANs to 17, 23, 35. The port receives a VLAN 10-tagged frame. What is its VLAN status immediately after the ingress checks?

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

Explanation

Correct Answer

B:

The received tag 10 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 port1, 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:

VLAN 109 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 port1, frame tagging and VLAN membership operate at Layer 2 and do not require a DHCP address. DHCP snooping is a distinct optional protection.

Question 41

An auditor wants operational evidence for the switch action “Prune unnecessary VLANs from an inter-switch link” at the campus. Which check is relevant?

  1. Inspect the effective tagged VLAN membership on an ISL before and after pruning
  2. Inspect both the outer service tag and the preserved inner customer VID
  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

A:

This approach fits because VLAN pruning limits trunk VLAN transport based on which downstream memberships require it. Directly measuring that result demonstrates whether the step to avoid carrying VLAN traffic over a stack segment with no users of that VLAN succeeded on a standalone FortiSwitch appliance.

Incorrect Answers

B:

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 “Prune unnecessary VLANs from an inter-switch link” at the campus. Checking “Prune unnecessary VLANs from an inter-switch link” at the campus requires evidence of its own mechanism: VLAN pruning limits trunk VLAN transport based on which downstream memberships require it; that is not the outcome measured by “Apply VLAN stacking with an outer service tag”.

C:

The proposed check concerns “Read the 12-bit VLAN identifier in an 802.1Q tag” rather than “Prune unnecessary VLANs from an inter-switch link”: the 802.1Q tag contains a twelve-bit VID field that identifies the VLAN. For “Prune unnecessary VLANs from an inter-switch link” on a standalone FortiSwitch appliance, a better test would be to inspect the effective tagged VLAN membership on an ISL before and after pruning, which targets avoid carrying VLAN traffic over a stack segment with no users of that VLAN rather than the alternative diagnostic “Read the 12-bit VLAN identifier in an 802.1Q tag”.

D:

This check is suited to “Configure an explicit native VLAN for untagged input” when trying to classify untagged ingress frames into the intended local VLAN rather than VLAN carried by a tag, not to verify “Prune unnecessary VLANs from an inter-switch link” at the campus. Checking “Prune unnecessary VLANs from an inter-switch link” at the campus requires evidence of its own mechanism: VLAN pruning limits trunk VLAN transport based on which downstream memberships require it; that is not the outcome measured by “Configure an explicit native VLAN for untagged input”.

Question 42

The operational requirement for a newly commissioned floor switch at the remote depot is to map selected Layer 2 payload protocols to different VLANs at a defined ingress point. Which FortiSwitch choice directly targets it?

  1. Apply VLAN stacking with an outer service tag
  2. Add a required VLAN to the allowed list on a trunk
  3. Classify VLAN membership from Ethernet protocol type
  4. Read the 3-bit PCP field in an 802.1Q tag
  5. Prune unnecessary VLANs from an inter-switch link

Explanation

Correct Answer

C:

The critical distinction is that protocol-based VLAN classification selects the segment from frame protocol information. The operator can test this claim by the specific check: inspect EtherType in a sample packet and compare its assigned VLAN.

Incorrect Answers

A:

Compared with the requested “Classify VLAN membership from Ethernet protocol type” at the remote depot, this would transport customer VLAN identifiers without treating all customer networks as one provider VLAN instead: QinQ carries an additional service tag outside the customer VLAN tag. At the remote depot, the operational proof would instead be to inspect EtherType in a sample packet and compare its assigned VLAN, whereas “Apply VLAN stacking with an outer service tag” is validated by a different test: inspect both the outer service tag and the preserved inner customer VID.

B:

Compared with the requested “Classify VLAN membership from Ethernet protocol type” at the remote depot, this would carry a particular non-native VLAN across an 802.1Q switch-to-switch link instead: a tagged ingress frame is accepted when its VLAN ID is on the allowed or native VLAN list. At the remote depot, the operational proof would instead be to inspect EtherType in a sample packet and compare its assigned VLAN, whereas “Add a required VLAN to the allowed list on a trunk” is validated by a different test: compare the tag in a test packet with the configured allowed VLAN list.

D:

For the remote depot, “Read the 3-bit PCP field in an 802.1Q tag” is a different type of control from “Classify VLAN membership from Ethernet protocol type”: priority Code Point occupies three bits and can represent service classes without changing the VID. Unlike the requested feature, that setting addresses the need to separate a traffic-priority marking from the VLAN identification on a trunk, not the objective to map selected Layer 2 payload protocols to different VLANs at a defined ingress point.

E:

Compared with the requested “Classify VLAN membership from Ethernet protocol type” at the remote depot, 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 remote depot, the operational proof would instead be to inspect EtherType in a sample packet and compare its assigned VLAN, 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 43

At the data hall, FortiSwitch port22 uses native VLAN 130, allowed VLANs 137, 143, 155, and discard-mode none. A tagged frame with VLAN ID 143 arrives. What is the correct ingress decision?

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

Explanation

Correct Answer

B:

For the received tagged VLAN on port22, the ingress filter compares a tagged frame against both the native VLAN and the explicit allowed list. Here VLAN 143 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 163. It cannot override the tag classification on this arrival.

C:

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

D:

For the received tagged VLAN on port22, 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 130 and allowed IDs are 137, 143, 155; those exact values, not tag validity alone, control the decision.

Question 44

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

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

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

For the outgoing Ethernet frame at port29, 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 115 into VLAN 201.

B:

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

C:

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

Question 45

On port36 serving the conference venue, discard-mode is all-tagged and a frame with an 802.1Q tag reaches the interface. Assume its VLAN would otherwise be allowed. What does discard-mode do?

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

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

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

B:

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

D:

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

Question 46

An administrator configuring the campus has set port4 native VLAN to 50 and allowed VLANs to 57, 63, 75. The port receives a VLAN 57-tagged frame. What is its VLAN status immediately after the ingress checks?

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

Explanation

Correct Answer

C:

The received tag 57 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 port4, frame tagging and VLAN membership operate at Layer 2 and do not require a DHCP address. DHCP snooping is a distinct optional protection.

B:

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

D:

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

Question 47

A change record for two distribution switches states “Assign a source MAC to a configured VLAN policy.” Which description correctly explains what this will accomplish?

  1. Protocol-based VLAN classification selects the segment from frame protocol information
  2. MAC-based VLAN assignment maps a matching source hardware address to its configured network
  3. Tagged trunk forwarding preserves each non-native VLAN identity across the shared link
  4. Discard-mode all-tagged filters tagged arrivals at ingress rather than rewriting them

Explanation

Correct Answer

B:

The switch behavior that matters is: the configured operation is meant to keep a registered endpoint in a designated VLAN despite an access-port move. The most relevant validation is to match the learned MAC with its configured VLAN and resulting port forwarding state for the equipment at the data hall.

Incorrect Answers

A:

That behavior applies when engineers “Classify VLAN membership from Ethernet protocol type”; the different operation “Assign a source MAC to a configured VLAN policy” is intended to keep a registered endpoint in a designated VLAN despite an access-port move. That different feature is verified by inspect EtherType in a sample packet and compare its assigned VLAN; for “Assign a source MAC to a configured VLAN policy” on two distribution switches, the relevant evidence is to match the learned MAC with its configured VLAN and resulting port forwarding state.

C:

That behavior applies when engineers “Use 802.1Q tagged trunk membership between switches”; the different operation “Assign a source MAC to a configured VLAN policy” is intended to keep a registered endpoint in a designated VLAN despite an access-port move. That different feature is verified by compare the sequence of 802.1Q tags observed at both switch ends; for “Assign a source MAC to a configured VLAN policy” on two distribution switches, the relevant evidence is to match the learned MAC with its configured VLAN and resulting port forwarding state.

D:

This outcome would be relevant to “Drop tagged input using all-tagged discard mode” at the data hall, not the task “Assign a source MAC to a configured VLAN policy”; the other task is to forbid 802.1Q-tagged input on a port reserved for ordinary untagged hosts. The action “Assign a source MAC to a configured VLAN policy” targets a different result: MAC-based VLAN assignment maps a matching source hardware address to its configured network; the proposed alternative would instead be checked by send tagged and untagged test traffic and inspect which type the interface admits.

Question 48

An auditor wants operational evidence for the switch action “Use a community private VLAN for a shared tenant group” at the development floor. Which check is relevant?

  1. Send tagged and untagged test traffic and inspect which type the interface admits
  2. Compare the sequence of 802.1Q tags observed at both switch ends
  3. Inspect EtherType in a sample packet and compare its assigned VLAN
  4. Test one in-community path and an inter-community path to verify the boundary

Explanation

Correct Answer

D:

At this network boundary, a PVLAN community can communicate internally and reach the primary promiscuous gateway. Directly measuring that result demonstrates whether the step to permit peers in one server community to communicate while excluding other communities succeeded on a staging FortiSwitch.

Incorrect Answers

A:

The proposed check concerns “Drop tagged input using all-tagged discard mode” rather than “Use a community private VLAN for a shared tenant group”: discard-mode all-tagged filters tagged arrivals at ingress rather than rewriting them. For “Use a community private VLAN for a shared tenant group” on a staging FortiSwitch, a better test would be to test one in-community path and an inter-community path to verify the boundary, which targets permit peers in one server community to communicate while excluding other communities rather than the alternative diagnostic “Drop tagged input using all-tagged discard mode”.

B:

This check is suited to “Use 802.1Q tagged trunk membership between switches” when trying to carry multiple independently isolated VLANs over one physical uplink, not to verify “Use a community private VLAN for a shared tenant group” at the development floor. Checking “Use a community private VLAN for a shared tenant group” at the development floor requires evidence of its own mechanism: a PVLAN community can communicate internally and reach the primary promiscuous gateway; that is not the outcome measured by “Use 802.1Q tagged trunk membership between switches”.

C:

This check is suited to “Classify VLAN membership from Ethernet protocol type” when trying to map selected Layer 2 payload protocols to different VLANs at a defined ingress point, not to verify “Use a community private VLAN for a shared tenant group” at the development floor. Checking “Use a community private VLAN for a shared tenant group” at the development floor requires evidence of its own mechanism: a PVLAN community can communicate internally and reach the primary promiscuous gateway; that is not the outcome measured by “Classify VLAN membership from Ethernet protocol type”.

Question 49

The accepted design for the conference venue requires the ability to distinguish priority of traffic at Ethernet VLAN-tag level. Which switch feature is the closest fit?

  1. Classify frames using 802.1p PCP
  2. Remark DSCP for a marked class
  3. Use LLDP-MED device capability advertisement
  4. Configure ingress CoS classification
  5. Set an LLDP-MED location policy

Explanation

Correct Answer

A:

In this deployment, the 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues. This distinction is material to the conference venue, where the stated goal is to distinguish priority of traffic at Ethernet VLAN-tag level.

Incorrect Answers

B:

Compared with the requested “Classify frames using 802.1p PCP” at the conference venue, this would normalize packet priority markings across a trust boundary instead: remarking changes packet QoS bits for subsequent network devices rather than installing a route. At the conference venue, the operational proof would instead be to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports, whereas “Remark DSCP for a marked class” is validated by a different test: capture ingress and egress IP headers and compare their DSCP fields.

C:

Compared with the requested “Classify frames using 802.1p PCP” at the conference venue, this would allow a network administrator to determine whether a neighbor supports media-endpoint extensions instead: LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing. At the conference venue, the operational proof would instead be to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports, whereas “Use LLDP-MED device capability advertisement” is validated by a different test: query the LLDP-MED neighbor detail for capabilities and device class.

D:

For the conference venue, “Configure ingress CoS classification” is a different type of control from “Classify frames using 802.1p PCP”: classification rules can map recognized 802.1p or DSCP values to internal priority treatment. Unlike the requested feature, that setting addresses the need to assign frames to a service class as they arrive at an access port, not the objective to distinguish priority of traffic at Ethernet VLAN-tag level.

E:

Compared with the requested “Classify frames using 802.1p PCP” at the conference venue, this would provide location-identification metadata for supported media endpoints instead: an LLDP-MED location TLV supplies location information; it does not route packets to emergency services. At the conference venue, the operational proof would instead be to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports, whereas “Set an LLDP-MED location policy” is validated by a different test: inspect the location TLV being advertised and verify endpoint acceptance.

Question 50

An operations log records this activity at the campus: classify frames using 802.1p PCP. Which result is specifically attributable to that action?

  1. DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment
  2. The switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication
  3. A policer meters selected frames and can drop or mark traffic that violates its profile
  4. The 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues

Explanation

Correct Answer

D:

For the stated requirement, the configured operation is meant to distinguish priority of traffic at Ethernet VLAN-tag level. The most relevant validation is to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports for the equipment at the campus.

Incorrect Answers

A:

That behavior applies when engineers “Classify IP traffic by DSCP”; the different operation “Classify frames using 802.1p PCP” is intended to distinguish priority of traffic at Ethernet VLAN-tag level. That different feature is verified by capture a marked IP packet and compare its DSCP with the switch QoS profile; for “Classify frames using 802.1p PCP” on a central switching stack, the relevant evidence is to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports.

B:

That behavior applies when engineers “Advertise an LLDP-MED voice network policy”; the different operation “Classify frames using 802.1p PCP” is intended to distinguish priority of traffic at Ethernet VLAN-tag level. That different feature is verified by read the LLDP-MED network-policy TLV reported by the attached phone; for “Classify frames using 802.1p PCP” on a central switching stack, the relevant evidence is to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports.

C:

This outcome would be relevant to “Police a traffic class with an ACL policer” at the campus, not the task “Classify frames using 802.1p PCP”; the other task is to constrain an identified flow that exceeds the permitted rate. The action “Classify frames using 802.1p PCP” targets a different result: the 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues; the proposed alternative would instead be checked by read policer statistics and compare conforming versus exceeding packet counters.

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