Notifications
Clear all
Topic starter
17/05/2022 2:37 pm
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 Carner Sense Multiple Access/Collision Detection is used
- E . when a collision occurs after the 32nd byte of a frame has been transmitted
Suggested Answer: BC
Explanation:
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, noncompliant 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: Click here
Explanation:
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, noncompliant 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: Click here