Which two conditions cause late collisions to be counted on an Ethernet interface? (Choose two.)

Late collisions occur when a collision is detected after the first 64 bytes (or 512 bits) of a frame have been transmitted. This typically indicates a problem with the network segment. One common cause is a duplex mismatch, where one end of the link is configured for half-duplex and the other for full-duplex. The half-duplex device will perform CSMA/CD, while the full-duplex device transmits without listening, leading to collisions that are detected late by the half-duplex device. Another cause is excessive cable length. Ethernet standards define maximum cable lengths to ensure that collision signals can propagate across the entire segment and be detected by all nodes within the collision window. If the cable is too long, a station may finish transmitting a significant portion of its frame before the collision signal from a distant station reaches it, resulting in a late collision. CSMA/CD is the mechanism that detects collisions, but it doesn't directly cause late collisions. The sender waiting 15 seconds before retransmitting is not a standard Ethernet behavior related to collision handling.