Difficulty: Easy
Correct Answer: Automatic retransmission of a corrupted or lost frame by the link itself
Explanation:
Introduction:
Ethernet's original IEEE 802.3 design focused on a simple, fast link-layer method for sending frames on a shared medium. Understanding exactly what classic Ethernet does—and does not—do helps separate link-layer responsibilities from those of upper layers like TCP/IP. This question asks which specific capability is not supplied by basic Ethernet (without VLAN extensions or higher-layer recovery).
Given Data / Assumptions:
Concept / Approach:
At Layer 2, Ethernet offers addressing (MAC), framing, and an integrity check (FCS). Historical shared-media networks used CSMA/CD for media access control. If a frame is corrupted or lost, Ethernet does not automatically retransmit it by itself; the receiver simply discards a bad frame (FCS failure). Reliable delivery—automatic retransmission, ordering, flow/congestion control—belongs to higher layers (e.g., TCP) or to special link types that implement ARQ (not standard Ethernet).
Step-by-Step Solution:
Verification / Alternative check:
Packet captures show that receivers drop frames with bad FCS; no Ethernet "NACK" exists in standard 802.3. Recovery—if any—arises from upper-layer protocols (e.g., TCP sequence/ACK).
Why Other Options Are Wrong:
Common Pitfalls:
Assuming link-layer reliability exists because Wi-Fi uses ARQ; conflating switched full-duplex (no collisions) with guaranteed delivery; confusing VLANs (802.1Q) with basic 802.3.
Final Answer:
Automatic retransmission of a corrupted or lost frame by the link itself.
Discussion & Comments