200-150 · Question #105
Which field in an Ethernet II frame performs the same function as the DSAP field in an 802.3 Ethernet frame?
The correct answer is B. EtherType. Both the DSAP field in 802.3 LLC and the EtherType field in Ethernet II identify the upper-layer protocol that should receive the frame payload. EtherType is the Ethernet II equivalent of DSAP.
Question
Which field in an Ethernet II frame performs the same function as the DSAP field in an 802.3 Ethernet frame?
Options
- AStart of frame
- BEtherType
- CFrame check sequence
- DSubnetwork Access Protocol
- ELogical Link Control
How the community answered
(25 responses)- B92% (23)
- D4% (1)
- E4% (1)
Why each option
Both the DSAP field in 802.3 LLC and the EtherType field in Ethernet II identify the upper-layer protocol that should receive the frame payload. EtherType is the Ethernet II equivalent of DSAP.
The Start of Frame delimiter (SFD) signals the beginning of the frame to receiving hardware - it plays no role in identifying the upper-layer protocol.
The EtherType field in an Ethernet II frame is a 2-byte field that identifies the Layer 3 protocol encapsulated in the frame payload (for example, 0x0800 for IPv4 and 0x0806 for ARP). This is functionally equivalent to the DSAP field in the 802.3 LLC header, which also identifies the destination upper-layer service or protocol that should process the incoming data.
The Frame Check Sequence (FCS) is a 4-byte CRC trailer used for error detection, not for protocol type identification.
SNAP (Subnetwork Access Protocol) is an extension header used within 802.3 LLC frames to allow EtherType-style protocol identification, but it is not itself the counterpart to DSAP.
LLC (Logical Link Control) is the sublayer and header structure that contains DSAP and SSAP fields in 802.3 - it is the broader container, not the functional equivalent of DSAP.
Concept tested: EtherType vs DSAP protocol identification fields
Source: https://www.cisco.com/c/en/us/support/docs/lan-switching/ethernet/17465-1.html
Topics
Community Discussion
No community discussion yet for this question.