Examkin

Question

Difficulty: HardConnection-Oriented vs Connectionless Protocols

Match each network application scenario to the specific transport protocol characteristic that satisfies its operational requirements.

  • High-frequency live video streaming requiring minimal jitter and tolerance for missing frames.Connectionless transport utilizing 8-byte headers to prioritize low latency over error correction.
  • Automated database transaction mirroring requiring strict packet ordering and guaranteed delivery.Connection-oriented transport utilizing a three-way handshake and dynamic windowing for reliable byte-stream transfer.
  • Network Time Protocol (NTP) updates requiring small datagram size without session maintenance overhead.Connectionless transport operating statelessly without connection establishment or teardown overhead.
  • Secure Shell (SSH) administrative sessions requiring persistent state tracking and packet retransmission.Connection-oriented transport employing sequence numbers and retransmission timers for error-free session tracking.

Answer

Each scenario maps to its appropriate transport characteristics based on requirements for connection state, header overhead, latency tolerance, and delivery guarantees: Live streaming maps to connectionless low-latency 8-byte headers; Database transaction mirroring maps to connection-oriented three-way handshake with dynamic windowing; NTP time sync maps to connectionless stateless operation; SSH management maps to connection-oriented sequence numbering and retransmission timers.
Each application requirement matches its fundamental Transport Layer protocol: latency-sensitive live streaming and lightweight NTP transactions use UDP connectionless transport (minimal overhead, no handshake), whereas mission-critical database mirroring and SSH administration sessions use TCP connection-oriented transport (three-way handshake, sequence numbers, retransmissions, and flow control).

Step-by-Step Solution

1
Analyze the requirements for live video streaming.
Real-time streaming requires low latency and jitter tolerance, making connectionless UDP with minimal 8-byte headers the ideal match.
Retransmitting delayed video frames is useless for live playback because delayed frames arrive out of order and cause playback freezing.
2
Analyze database transaction mirroring requirements.
Database synchronization requires absolute data completeness, matching connection-oriented TCP with flow control and handshakes.
Missing or out-of-order bytes corrupt database tables, requiring connection state and acknowledgment verification.
3
Analyze Network Time Protocol (NTP) updates.
NTP exchanges lightweight time checks, matching stateless connectionless transport without handshake overhead.
Establishing a TCP session for a single small timestamp packet wastes network bandwidth and processing cycles.
4
Analyze Secure Shell (SSH) administrative sessions.
SSH requires reliable delivery of command input, matching connection-oriented TCP sequence numbering and retransmissions.
Unacknowledged or dropped keystrokes in a remote terminal can execute corrupted commands, necessitating error correction.

Key Concept

Selecting between connection-oriented (TCP) and connectionless (UDP) transport protocols based on application requirements for reliability, overhead, ordering, and latency.
Rate this question

Topics

Connection-Oriented vs Connectionless Protocols

More questions from this topic