Refer to the exhibit. After the switch configuration, the ping test fails between PC A and PC B. Based on the output for switch 1, which error must be corrected?
can't anybody see that Native Vlan Tagging is enabled on both the switches, so native vlan traffic will go tagged on the trunk port. But allowed vlans on the trunk port is 50-100 whereas the both PC-A and PC-B belongs to vlan A so their traffic won't be allowed on the trunk port. So the correct answer should be B.
There is VLAN Mismatch. Remember there is no any intervlan routing on the two sitches thus minimising the chance of communication.
Answer is D
https://www.youtube.com/watch?v=klqpX6U-_JY
ChatGPT says,
Based on the output for switch 1, the error that must be corrected in order for the ping test to be successful between PC A and PC B is option D, "There is a native VLAN mismatch."
Explanation:
The output of the show interfaces trunk command on Switch 1 shows that the trunk link between Switch 1 and Switch 2 is configured with a native VLAN of 10 on Switch 1 and a native VLAN of 20 on Switch 2. This is a native VLAN mismatch, which can cause issues with VLAN traffic crossing the trunk link.
In this scenario, PC A is in VLAN 10 and PC B is in VLAN 20. When the switch receives traffic from PC A, it tags the traffic with VLAN 10, but when the traffic crosses the trunk link to Switch 2, the traffic is sent on the native VLAN 20, which Switch 2 is expecting to receive traffic on. As a result, the traffic from PC A is dropped and the ping test fails.
To correct this error, the native VLAN on the trunk link between Switch 1 and Switch 2 should be the same on both switches. Either the native VLAN should be changed to 10 on both switches or it should be changed to 20 on both switches.
can't anybody see that Native Vlan Tagging is enabled on both the switches, so native vlan traffic will go tagged on the trunk port. But allowed vlans on the trunk port is 50-100 whereas the both PC-A and PC-B belongs to vlan A so their traffic won't be allowed on the trunk port. So the correct answer should be B.
can't anybody see that Native Vlan Tagging is enabled on both the switches, so native vlan traffic will go tagged on the trunk port. But allowed vlans on the trunk port is 50-100 whereas the both PC-A and PC-B belongs to vlan 99 so their traffic will be allowed on the trunk port. So the correct answer should be D.
can't anybody see that Native Vlan Tagging is enabled on both the switches, so native vlan traffic will go tagged on the trunk port. But allowed vlans on the trunk port is 50-100 whereas the both PC-A and PC-B belongs to vlan A so their traffic won't be allowed on the trunk port. So the correct answer should be B.
The real problem is that: Sw2 has Vlan 99 as native vlan, this way send untagged traffic. If we put another vlan as native, there is not problem for pinging...
can't anybody see that Native Vlan Tagging is enabled on both the switches, so native vlan traffic will go tagged on the trunk port. But allowed vlans on the trunk port is 50-100 whereas the both PC-A and PC-B belongs to vlan A so their traffic won't be allowed on the trunk port. So the correct answer should be B.
Packet from PC A to PC B will reach its destination but return packet will not be encapsulated (native vlan 99) in Switch 2, and will be interpreted as vlan 1 in switch 1, thus it will not be forwarded to PC A.
Correct answer is A. In this case, ping will only fail if the PC is on native VLAN. But in VLAN 99, the ping will be successful. Tested on Cisco Packet Tracer.
can't anybody see that Native Vlan Tagging is enabled on both the switches, so native vlan traffic will go tagged on the trunk port. But allowed vlans on the trunk port is 50-100 whereas the both PC-A and PC-B belongs to vlan A so their traffic won't be allowed on the trunk port. So the correct answer should be B.
i think the answer is A because you would configure the link between a pc and switch as an access port, and links between switches as trunks. the only thing im thinking is if the VLANs are different, then the switch will not forward the frame to the correct vlan.
can't anybody see that Native Vlan Tagging is enabled on both the switches, so native vlan traffic will go tagged on the trunk port. But allowed vlans on the trunk port is 50-100 whereas the both PC-A and PC-B belongs to vlan A so their traffic won't be allowed on the trunk port. So the correct answer should be B.
Native vlan traffic will still go through from one switch to another despite Native Vlan mismatch. It will just create a larger broadcast domain between the 2 switches. However, in this question for the "tagged" vlan traffic there is a disruption- the 2 PCs will not be able to communicate.
When an untagged frame enters a switch port, the native VLAN is tagged on the frame. So if Switch 1 were to send a frame to Switch 2, it would be sent untagged, and Switch 2 would tag it as VLAN 99. If Switch 2 were to send the frame, Switch 1 would tag it as VLAN 1.
can't anybody see that Native Vlan Tagging is enabled on both the switches, so native vlan traffic will go tagged on the trunk port. But allowed vlans on the trunk port is 50-100 whereas the both PC-A and PC-B belongs to vlan A so their traffic won't be allowed on the trunk port. So the correct answer should be B.
True, cause native vlans should also match in order for untagged traffic to get automatically tagged with it, If there are different native VLANs, then packet mismatch will happen, thus no ping
This section is not available anymore. Please use the main Exam Page.200-301 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Kane4555
Highly Voted 2 years, 10 months agodipanjana1990
2 years, 3 months agofreezeladmsflmaldfs
1 year, 4 months ago[Removed]
Most Recent 7 months, 3 weeks agoFALARASTA
1 year, 6 months agoelixirwell
1 year, 7 months agodipanjana1990
2 years, 3 months agoDixieNormus
2 years, 2 months agoMauro_Babarram
2 years, 4 months agoZUMY
2 years, 5 months agodipanjana1990
2 years, 3 months agorictorres333
2 years, 6 months agodipanjana1990
2 years, 3 months agoNalle72
2 years, 7 months agoPoBratsky
2 years, 11 months agodipanjana1990
2 years, 3 months agoPoBratsky
2 years, 11 months agodave1992
2 years, 11 months agoonikafei
2 years, 9 months agodipanjana1990
2 years, 3 months agoMicah7
3 years, 5 months agooooMooo
3 years, 6 months agosim5710
3 years, 7 months agoNerdyNerdy
3 years, 7 months agodipanjana1990
2 years, 3 months agoSUKABLED
3 years, 9 months agoamrith501
3 years, 10 months ago