300-415 · Question #99
Which TCP Optimization feature is used by WAN Edge to prevent unnecessary retransmissions and large initial TCP window sizes to maximize throughput and achieve a better quality?
The correct answer is D. SACK. SACK (Selective Acknowledgment) is the TCP Optimization feature that prevents unnecessary retransmissions by allowing the receiver to acknowledge non-contiguous received segments, so only truly missing segments are retransmitted.
Question
Options
- ASEQ
- BSYN
- CRTT
- DSACK
How the community answered
(30 responses)- A3% (1)
- B3% (1)
- C7% (2)
- D87% (26)
Why each option
SACK (Selective Acknowledgment) is the TCP Optimization feature that prevents unnecessary retransmissions by allowing the receiver to acknowledge non-contiguous received segments, so only truly missing segments are retransmitted.
SEQ refers to TCP sequence numbers used for ordering segments - it is a fundamental TCP field, not a specific optimization feature for preventing retransmissions.
SYN is the TCP flag used during the three-way handshake to initiate connections - while TCP Optimization intercepts SYN packets to proxy connections, SYN itself is not the feature that prevents retransmissions.
RTT (Round-Trip Time) is a measurement metric used by TCP to calculate retransmission timers, but it is not an optimization feature that actively prevents unnecessary retransmissions.
SACK (Selective Acknowledgment) extends standard TCP acknowledgment to allow a receiver to report multiple non-contiguous blocks of received data. This prevents the sender from blindly retransmitting all data after a lost packet and also allows better control of initial window sizes. Cisco SD-WAN's TCP Optimization uses SACK to maximize throughput and improve quality by minimizing redundant retransmissions across WAN links.
Concept tested: Cisco SD-WAN TCP Optimization SACK retransmission prevention
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/qos/ios-xe-17/qos-book-xe/m-appqoe-tcp-opt.html
Topics
Community Discussion
No community discussion yet for this question.