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?
- Inspect both the outer service tag and the preserved inner customer VID
- Compare the sequence of 802.1Q tags observed at both switch ends
- Inspect the tag-control information and decode its VID independently of PCP
- 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”.
Question 31
At the factory, FortiSwitch port16 uses native VLAN 70, allowed VLANs 77, 83, 95, and discard-mode none. A tagged frame with VLAN ID 77 arrives. What is the correct ingress decision?
- Accept the frame into VLAN 77 without changing its VLAN classification
- Discard the frame for failing the allowed-VLAN check
- Forward it into VLAN 103 because that is the untagged egress list
- Remove the 802.1Q header and assign VLAN 70
Explanation
Correct Answer
A:For the received tagged VLAN on port16, the ingress filter compares a tagged frame against both the native VLAN and the explicit allowed list. Here VLAN 77 matches a permitted value, so its VLAN identity is retained.
Incorrect Answers
B:For the received tagged VLAN on port16, 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 70 and allowed IDs are 77, 83, 95; those exact values, not tag validity alone, control the decision.
C:The untagged VLAN list governs how eligible traffic exits a port, rather than allowing ingress traffic to select VLAN 103. It cannot override the tag classification on this arrival.
D:For the received tagged VLAN on port16, native VLAN assignment occurs when an arriving frame is untagged. This frame already carries VLAN 77; ingress filtering does not recast a tagged packet as native merely because of this port setting.
Question 32
A FortiSwitch in the distribution floor forwards an internally tagged VLAN 42 frame toward port23. That egress port has native VLAN 42, allowed VLANs 49, 55, 67, and untagged VLANs 75. What goes onto the wire?
- Drop the frame at egress due to VLAN membership
- Forward the frame carrying VLAN tag 42
- Send the frame without an 802.1Q tag
- Rewrite the frame to use VLAN 141
Explanation
Correct Answer
C:VLAN 42 matches the native VLAN; that classification removes the header before the frame exits. Native egress handling strips the tag even though the switching pipeline classified the frame with that VLAN ID.
Incorrect Answers
A:VLAN 42 is outside the configured native, untagged and allowed egress memberships; the port cannot transmit it.
B:VLAN 42 belongs to the allowed VLAN list but is not native or configured for untagged egress, so the 802.1Q header remains.
D:For the outgoing Ethernet frame at port23, 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 42 into VLAN 141.
Question 33
On port30 serving the media studio, discard-mode is all-tagged and an untagged Ethernet frame reaches the interface. Assume its VLAN would otherwise be allowed. What does discard-mode do?
- Allow this frame type to proceed to ordinary VLAN processing
- Always discard the frame before VLAN membership checking
- Replace the source MAC address with the FortiSwitch management address
- Place the frame in a new private VLAN automatically
Explanation
Correct Answer
A:The all-tagged setting does not exclude this frame type. Under the indicated discard-mode on port30, its packet-type filter is checked separately from native and allowed-VLAN classification.
Incorrect Answers
B:Under the indicated discard-mode on port30, 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 port30, 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 port30.
D:Under the indicated discard-mode on port30, private VLAN associations are configured explicitly, not triggered by the ingress discard-mode value all-tagged.
Question 34
An administrator configuring the retail site has set port37 native VLAN to 120 and allowed VLANs to 127, 133, 145. The port receives an untagged frame. What is its VLAN status immediately after the ingress checks?
- Classify it into native VLAN 120
- Send it out port37 immediately without MAC learning
- Require a DHCP lease before performing VLAN classification
- Replace its VLAN with 219 to preserve isolation
Explanation
Correct Answer
A:The absence of a tag makes the native VLAN 120 apply automatically; the allowed list does not control this untagged admission.
Incorrect Answers
B:Before selecting a forwarding port after ingress on port37, 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 port37, 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 port37, VLAN 219 is not configured on this port and FortiSwitch does not assign an unrelated VLAN at this ingress stage.
Question 35
A production incident in the factory reveals the need to stop untagged uplink traffic from being classified into a different VLAN by the peer. Which targeted FortiSwitch setting or method should the team use?
- Correct inconsistent native VLAN expectations at both ends
- Configure an explicit native VLAN for untagged input
- Apply VLAN stacking with an outer service tag
- Read the 12-bit VLAN identifier in an 802.1Q tag
Explanation
Correct Answer
A:The switch behavior that matters is: both ends must agree on native VLAN handling when untagged frames are exchanged. This distinction is material to the factory, where the stated goal is to stop untagged uplink traffic from being classified into a different VLAN by the peer.
Incorrect Answers
B:Compared with the requested “Correct inconsistent native VLAN expectations at both ends” at the factory, this would classify untagged ingress frames into the intended local VLAN rather than VLAN carried by a tag instead: untagged Ethernet frames are internally associated with the ingress port's native VLAN. At the factory, the operational proof would instead be to compare effective native VLAN settings at both ends and capture an untagged frame, whereas “Configure an explicit native VLAN for untagged input” is validated by a different test: inject an untagged test frame and inspect its learned VLAN membership.
C:Compared with the requested “Correct inconsistent native VLAN expectations at both ends” at the factory, 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 factory, the operational proof would instead be to compare effective native VLAN settings at both ends and capture an untagged frame, 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.
D:For the factory, “Read the 12-bit VLAN identifier in an 802.1Q tag” is a different type of control from “Correct inconsistent native VLAN expectations at both ends”: the 802.1Q tag contains a twelve-bit VID field that identifies the VLAN. Unlike the requested feature, that setting addresses the need to identify the forwarding VLAN separately from any priority bits in a tagged Ethernet frame, not the objective to stop untagged uplink traffic from being classified into a different VLAN by the peer.
Question 36
An operations log records this activity at the distribution floor: apply VLAN stacking with an outer service tag. Which result is specifically attributable to that action?
- Tagged trunk forwarding preserves each non-native VLAN identity across the shared link
- A PVLAN community can communicate internally and reach the primary promiscuous gateway
- Discard-mode all-tagged filters tagged arrivals at ingress rather than rewriting them
- QinQ carries an additional service tag outside the customer VLAN tag
Explanation
Correct Answer
D:At this network boundary, the configured operation is meant to transport customer VLAN identifiers without treating all customer networks as one provider VLAN. The most relevant validation is to inspect both the outer service tag and the preserved inner customer VID for the equipment at the distribution floor.
Incorrect Answers
A:This outcome would be relevant to “Use 802.1Q tagged trunk membership between switches” at the distribution floor, not the task “Apply VLAN stacking with an outer service tag”; the other task is to carry multiple independently isolated VLANs over one physical uplink. The action “Apply VLAN stacking with an outer service tag” targets a different result: QinQ carries an additional service tag outside the customer VLAN tag; the proposed alternative would instead be checked by compare the sequence of 802.1Q tags observed at both switch ends.
B:That behavior applies when engineers “Use a community private VLAN for a shared tenant group”; the different operation “Apply VLAN stacking with an outer service tag” is intended to transport customer VLAN identifiers without treating all customer networks as one provider VLAN. That different feature is verified by test one in-community path and an inter-community path to verify the boundary; for “Apply VLAN stacking with an outer service tag” on a local switch administering branch clients, the relevant evidence is to inspect both the outer service tag and the preserved inner customer VID.
C:That behavior applies when engineers “Drop tagged input using all-tagged discard mode”; the different operation “Apply VLAN stacking with an outer service tag” is intended to transport customer VLAN identifiers without treating all customer networks as one provider VLAN. That different feature is verified by send tagged and untagged test traffic and inspect which type the interface admits; for “Apply VLAN stacking with an outer service tag” on a local switch administering branch clients, the relevant evidence is to inspect both the outer service tag and the preserved inner customer VID.
Question 37
At the campus, FortiSwitch port19 uses native VLAN 310, allowed VLANs 317, 323, 335, and discard-mode none. A tagged frame with VLAN ID 355 arrives. What is the correct ingress decision?
- Forward it into VLAN 343 because that is the untagged egress list
- Discard the frame because VLAN membership does not permit it
- Remove the 802.1Q header and assign VLAN 310
- Accept the frame because its tag is an arbitrary valid 802.1Q ID
Explanation
Correct Answer
B:For the received tagged VLAN on port19, the ingress filter compares a tagged frame against both the native VLAN and the explicit allowed list. Here VLAN 355 matches neither set, so the switch rejects it before normal VLAN forwarding.
Incorrect Answers
A:The untagged VLAN list governs how eligible traffic exits a port, rather than allowing ingress traffic to select VLAN 343. It cannot override the tag classification on this arrival.
C:For the received tagged VLAN on port19, native VLAN assignment occurs when an arriving frame is untagged. This frame already carries VLAN 355; ingress filtering does not recast a tagged packet as native merely because of this port setting.
D:For the received tagged VLAN on port19, 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 310 and allowed IDs are 317, 323, 335; those exact values, not tag validity alone, control the decision.
Question 38
A FortiSwitch in the remote depot forwards an internally tagged VLAN 319 frame toward port26. That egress port has native VLAN 312, allowed VLANs 319, 325, 337, and untagged VLANs 345. What goes onto the wire?
- Send the frame without an 802.1Q tag
- Forward the frame carrying VLAN tag 319
- Drop the frame at egress due to VLAN membership
- Rewrite the frame to use VLAN 411
Explanation
Correct Answer
B:VLAN 319 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 319 matches an explicitly untagged egress VLAN; that classification removes the header before the frame exits.
C:VLAN 319 is outside the configured native, untagged and allowed egress memberships; the port cannot transmit it.
D:For the outgoing Ethernet frame at port26, 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 319 into VLAN 411.
Question 39
On port33 serving the branch office, 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?
- Always admit the frame regardless of tag format
- Place the frame in a new private VLAN automatically
- Reject this frame before normal forwarding
- 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 port33, its packet-type filter is checked separately from native and allowed-VLAN classification.
Incorrect Answers
A:Under the indicated discard-mode on port33, 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 port33, the arriving frame type determines whether the filter applies.
B:Under the indicated discard-mode on port33, 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 port33.
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?
- Send it out port1 immediately without MAC learning
- Keep VLAN 10 for forwarding
- Replace its VLAN with 109 to preserve isolation
- 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.