Directly from a Cisco article.
What are two reasons that cause late collisions to increment on an Ethernet interface? (Choose two)
A. when the sending device waits 15 seconds before sending the frame again
B. when the cable length limits are exceeded
C. when one side of the connection is configured for half-duplex
D. when Carrier Sense Multiple Access/Collision Detection is used
E. when a collision occurs after the 32nd byte of a frame has been transmitted
Answer: B, C
A late collision is defined as any collision that occurs after the first 512 bits (or 64th byte) of the frame have Been transmitted. The usual possible causes are full-duplex/half-duplex mismatch, exceeded Ethernet cable length limits, or defective hardware such as incorrect cabling, non-compliant number of hubs in the network, or
a bad NIC. Late collisions should never occur in a properly designed Ethernet network. They usually occur when Ethernet cables are too long or when there are too many repeaters in the network.
Reference: https://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1904.html
Given Answer B & E are correct!
*******
A late collision is defined as any collision that occurs after the first 512 bits (or 64th byte) of the frame have Been transmitted. The usual possible causes are full-duplex/half-duplex mismatch, exceeded Ethernet cable length limits, or defective hardware such as incorrect cabling, non-compliant number of hubs in the network, or
a bad NIC. Late collisions should never occur in a properly designed Ethernet network. They usually occur when Ethernet cables are too long or when there are too many repeaters in the network.
Correct is B and E.
B . If you use Half -Dublex it cause collusion. It doesnt matter both side is half-dublex. If it is full dublex than no collusion.
E. This is clear. If cable is long than limit, it cause late collision.
Why not A? Because CSMA/CD is not cause. It is for to stop collusion. It is the reason..
Late Collision is a collision on an Ethernet network that is detected late in the transmission of the packet. Late collisions can result from defective Ethernet transceivers, from having too many repeaters between stations, or from exceeding Ethernet specifications for maximum node-to-node distances
the right answer is B_E
B is not a correct answer because at CSMA/CD mode, end points cannot send and receive frames at the same time. Therefore end points(NIC) have to be in half-duplex mode. B is not a cause of late collision. But A can detect collision but also not the cause of late collision. All in all there is issue in the description of the question itself.
But B (when one side of the connection is configured for half-duplex) leaves open if the other side of the connection is configured as half-duplex as well so this doesn´t necessarily mean a duplex missmacth or am I wrong here?
But on the other hand, as Wikipedia states:
"As a correctly set up CSMA/CD (Carrier-sense multiple access with collision detection) network link should not have late collisions, the usual possible causes are full-duplex/half-duplex mismatch, exceeded Ethernet cable length limits, or defective hardware such as incorrect cabling, non-compliant number of hubs in the network, or a bad NIC."
So I guess A can not be the right answer.
https://en.wikipedia.org/wiki/Carrier-sense_multiple_access_with_collision_detection#Late_collision
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.
John248
Highly Voted 4 years, 11 months agodendio
3 years, 5 months agoZUMY
Highly Voted 4 years, 2 months agobymrdas
Most Recent 1 year agoNmk173
1 year, 7 months agovuhidus
2 years, 11 months agowhojabagooya
3 years agolohaN73
3 years agoilluded03jolted
3 years, 1 month agolock12333
3 years, 1 month agoHodicek
3 years, 7 months agoShaz313
3 years, 11 months agoadmin1982
4 years, 5 months agoLakshmi_200_301
4 years, 6 months agojowill
4 years, 6 months agosiva_13
4 years, 6 months agodaslux4
4 years, 7 months agoboghota
4 years, 7 months agoboghota
4 years, 7 months ago