A senior network engineer is analyzing edge-case operational characteristics of transport-layer protocols during abnormal network state events. Match each connection-oriented or connectionless protocol scenario on the left with its corresponding transport-layer mechanism or operational consequence on the right.
- TCP sequence number space wrap-around on a high-throughput 10 Gbps linkRequires Protection Against Wrapped Sequence Numbers (PAWS) using timestamps to validate segment ordering
- UDP socket buffer saturation during an unthrottled traffic burstSilently discards arriving datagrams at the host buffer without sending transport-layer flow control feedback
- TCP selective acknowledgment (SACK) operation during isolated segment lossRetransmits only missing data gaps while buffering out-of-order blocks already received
- UDP session availability monitoring across an idle, stateful firewallDepends entirely on application-layer heartbeat timers because no transport session state is maintained
Cevap
TCP sequence number wrap-around matches PAWS timestamp validation; UDP socket saturation matches silent datagram discarding without flow control; TCP SACK operation matches retransmitting only missing gaps while buffering out-of-order segments; UDP session monitoring matches reliance on application-layer heartbeats.
TCP maintains explicit connection state, sequence numbers, and dynamic windowing. Under high data rates, sequence numbers wrap around, requiring PAWS (TCP Timestamps) for validation. TCP SACK optimizes recovery by specifying exact missing byte ranges. Conversely, UDP is stateless: socket overflow results in silent drops without transport-layer backpressure, and maintaining active firewall translation rules requires application-level heartbeats.
Adım Adım Çözüm
Anahtar Kavram
Connection-Oriented (TCP) state, sequencing, and windowing management versus Connectionless (UDP) stateless datagram processing
Tahmini Süre:3m 0s