A network engineer is optimizing a high-frequency sensor telemetry service that transmits small status updates every 50 milliseconds across a lossy wireless WAN link. The application prioritizes ultra-low latency over absolute delivery, as outdated telemetry is immediately rendered obsolete by the next transmission. Diagnostic captures reveal that the legacy implementation experiences severe delay spikes caused by SYN/ACK negotiation, cumulative acknowledgment processing, and retransmission buffer queuing during temporary signal drops. Which transport layer design change should the engineer implement to eliminate these latency spikes while meeting application requirements?
- Transition the service from TCP to UDP to eliminate connection setup handshakes and sliding window flow control overhead.Answer
- BMaintain TCP as the transport protocol but increase the TCP window size to guarantee packet delivery without queuing delay.
- CEncapsulate telemetry data directly into Data Link Layer frames to enforce connection-oriented delivery using switch MAC table sockets.
- DReassign the TCP application traffic to UDP port 123 to force the underlying TCP stack to operate in connectionless mode.
Answer
Transition the service from TCP to UDP to eliminate connection setup handshakes and sliding window flow control overhead.
The requirement calls for minimal latency and tolerance of missing updates in a real-time telemetry application. Switching to a connectionless protocol like UDP eliminates connection establishment overhead, sequence numbers, acknowledgment tracking, and retransmission delays, resolving the latency spikes caused by TCP's Head-of-Line blocking.
Step-by-Step Solution
Key Concept
Connection-Oriented (TCP) vs. Connectionless (UDP) Protocol Selection