Transport for Computer Networkss
The transport layer provides process-to-process communication between hosts, using port numbers to separate applications. UDP offers a thin, connectionless service, while TCP adds reliable, ordered delivery with handshakes, acknowledgements, retransmission, flow control and congestion control. This layer determines how fast and how reliably an application's data arrives.
Stage: Transport Layer · Part of the Computer Networks roadmap · Last reviewed 19 November 2026
What to learn in Transport
- Compare UDP and TCP and choose one for video calls versus file transfer
- Walk through the TCP three-way handshake and the connection teardown
- Explain how sequence numbers and acknowledgements detect loss and reordering
- Describe how the sliding window implements flow control
- Explain slow start and congestion avoidance and how the congestion window changes
Transport interview questions
What is the difference between flow control and congestion control in TCP?
Flow control protects the receiver from being overwhelmed, using the advertised receive window. Congestion control protects the network, with the sender limiting its congestion window based on signs of loss or delay. The sender's rate is bounded by the smaller of the two windows.
Why does DNS usually use UDP?
A DNS query and answer are small, so a single UDP exchange avoids the handshake delay and per-connection state of TCP. The resolver retries if no reply arrives. DNS falls back to TCP when responses are too large, and for zone transfers.
Where Transport fits in the Computer Networks roadmap
Transport belongs to the Transport Layer stage (intermediate level). Reliable delivery.
Back to the full Computer Networks roadmap