In which scenario is ACK piggybacking most effective?

• A. When there is data to send in the opposite direction
• B. When there is no outbound data for a long time
• C. When the connection is in TIME_WAIT
• D. When using TLS

Answer: (A)

ACK piggybacking happens when the receiver’s acknowledgment is sent together with a data segment it is sending back to the other side, instead of as a separate ACK packet. The best situation for this is when there is data to send in the opposite direction. In that case, the ACK rides along with that data, reducing the number of packets and the header overhead, and often improving overall throughput. If there is no outbound data for a long time, the receiver ends up sending pure ACKs, which adds extra packets and latency. The TIME_WAIT state is about handling connection termination and ensuring delayed segments don’t cause issues after close; it doesn’t create a favorable condition for piggybacking. TLS sits above TCP and doesn’t affect this TCP behavior, since piggybacking is a TCP mechanism regardless of encryption.