Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet NSE5_FSW_AD-7.6 Exam - Topic 2 Question 4 Discussion

Actual exam question for Fortinet's NSE5_FSW_AD-7.6 exam
Question #: 4
Topic #: 2
[All NSE5_FSW_AD-7.6 Questions]

Refer to the exhibits

Traffic arriving on port2 on FortiSwitch is tagged with VLAN ID 10 and destined for PC1 connected on port1. PC1 expects to receive traffic untagged from port1 on FortiSwitch. Which two configurations can you perform on FortiSwitch to ensure PC1 receives untagged traffic on port1? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

According to theFortiSwitchOS 7.6 Administration Guideand theFortiSwitch 7.6 Study Guide, the way a FortiSwitch handles VLAN tags on egress (outgoing) traffic is governed by the port'sNative VLANand itsUntagged VLAN list. When traffic for VLAN 10 arrives at port2 (the uplink) and is forwarded to port1, the switch must determine whether to strip the 802.1Q tag before transmission.

Untagged VLAN List (Option B):The documentation explicitly states that the 'untagged VLAN list' specifies VLANs for which the port will transmit frameswithout the VLAN tag. By adding VLAN ID 10 to the untagged VLANs on port1, any traffic belonging to VLAN 10 will have its tag stripped at the egress point, ensuring PC1 receives a standard untagged frame.

Configuration Logic (Option C):In FortiSwitch management, moving a VLAN from the 'Allowed' list (which typically implies tagged delivery) to the 'Untagged' list on a specific interface forces the switch to perform the tag-stripping action. This effectively converts the port from a trunked behavior for that VLAN to an 'access' or untagged behavior.

Regarding the incorrect options:Option A (MAC-based assignment)is used primarily foringress classification. While it can assign a device to a VLAN when it sends trafficintothe switch, the documentation notes that by default, egress packets for MAC-based VLANs still include the tag unless the untagged list is configured.Option D(Private VLANs) is a security feature for isolating traffic between ports within the same VLAN and does not address the physical tagging requirements of the endpoint.


Contribute your Thoughts:

0/2000 characters
Edison
3 days ago
Private VLAN on VLAN 10? That sounds complicated for this scenario.
upvoted 0 times
...
Dudley
9 days ago
Totally agree with B, that’s the simplest fix!
upvoted 0 times
...
Lashon
14 days ago
Wait, why would you need to add PC1's MAC? Seems unnecessary.
upvoted 0 times
...
Brock
19 days ago
I think C could work too, but not sure about A.
upvoted 0 times
...
Winfred
24 days ago
Option B is definitely the way to go!
upvoted 0 times
...
Devora
29 days ago
I don't recall anything about Private VLANs from our study sessions, so I think option D is definitely not the right choice here.
upvoted 0 times
...
Kayleigh
1 month ago
I feel like option C could also be a possibility, but I need to double-check if removing VLAN 10 from allowed VLANs is the right approach.
upvoted 0 times
...
Deonna
1 month ago
I'm not entirely sure about option A. I remember something about MAC addresses, but I don't think adding PC1's MAC to VLAN 10 is necessary for untagged traffic.
upvoted 0 times
...
Yun
1 month ago
I think option B sounds right since it mentions adding VLAN ID 10 to untagged VLANs on port1. That seems like what we practiced.
upvoted 0 times
...

Save Cancel