Examkin

Question

Difficulty: HardConnection-Oriented vs Connectionless Protocols

A senior network architect is documenting transport layer protocol selection guidelines for an enterprise infrastructure upgrade. Match each application communication requirement on the left with the corresponding Transport Layer protocol operational mechanism on the right.

  • Real-time telemetry streaming over low-bandwidth links where dropped frames are discarded rather than retransmitted to avoid latency spikes.Unacknowledged connectionless datagram delivery utilizing fixed 8-byte protocol headers without transmission state tracking.
  • Remote database synchronization across a lossy WAN requiring verified packet sequencing and dynamic rate adaptation based on receiver buffer capacity.Connection-oriented transport leveraging dynamic sliding window mechanisms and explicit cumulative sequence acknowledgments.
  • Stateful network firewall filtering tracking active session states via sequence numbers and explicit segment acknowledgment markers.Stateful connection establishment relying on a three-way handshake sequence (SYN, SYN-ACK, ACK) and connection state table tracking.
  • Low-overhead transactional client-server query/response where transmission failure detection is delegated to application-layer timers.Best-effort connectionless transport offloading session state maintenance, framing integrity, and recovery logic to upper OSI layers.

Answer

Each scenario maps to its underlying transport mechanism: low-latency streaming maps to 8-byte connectionless headers; database sync maps to dynamic sliding window connection-oriented transport; stateful firewall tracking maps to three-way handshake session creation; and transactional query/response maps to connectionless transport with application-managed reliability.
Transport layer protocol selection depends on application tolerance for latency versus data integrity. Connection-oriented protocols (TCP) establish state via a three-way handshake, maintain sequence numbers, guarantee delivery, and perform sliding-window flow control. Connectionless protocols (UDP) operate statelessly with fixed 8-byte headers, delivering datagrams with minimal overhead while delegating error recovery to application layers.

Step-by-Step Solution

1
Analyze latency and overhead requirements for real-time telemetry streaming.
Identified requirement for UDP due to its unacknowledged connectionless datagram architecture and lightweight 8-byte header.
Retransmission and handshake delays introduced by connection-oriented protocols degrade real-time metrics.
2
Analyze database synchronization requirements over lossy WAN links.
Identified TCP as mandatory due to mandatory packet ordering, reliable delivery, and window-based flow control.
Data integrity and receiver buffer protection require cumulative acknowledgments and sliding window flow control.
3
Determine how stateful firewalls track connection-oriented sessions.
Matched firewall session state tracking to TCP's three-way handshake mechanism.
Firewalls validate connection status by inspecting control flags (SYN, SYN-ACK, ACK) during session creation.
4
Evaluate lightweight query/response transactions with application-layer retry mechanisms.
Matched to connectionless best-effort transport delegating recovery to higher OSI layers.
When higher-layer protocols handle retransmissions, transport-layer connection management adds unnecessary overhead.

Key Concept

Connection-Oriented (TCP) vs. Connectionless (UDP) Protocol Operational Characteristics
Rate this question

Topics

Connection-Oriented vs Connectionless Protocols

More questions from this topic