Examkin

Question

Difficulty: Very hardConnection-Oriented vs Connectionless Protocols

An organization deploys thousands of remote edge devices that transmit brief, 64-byte heartbeat status updates every second across a high-latency, limited-bandwidth satellite network. The network administrator observes that stateful firewall session tables at the central hub are constantly saturating due to session tracking overhead, while high link latency causes excessive control packet accumulation. To resolve these operational constraints without upgrading hardware, the administrator plans to adjust the application transport layer architecture. Which of the following transport protocol selections and technical justifications best resolves both issues?

  1. Implement a connectionless protocol (UDP), because it eliminates stateful session maintenance on firewalls while reducing per-packet overhead by omitting sequence numbers, flow control, and acknowledgment header fields.Answer
  2. B
    Implement a connection-oriented protocol (TCP), because its dynamic sliding window mechanism automatically scales firewall session timeouts down to match the heartbeat frequency.
  3. C
    Implement a connection-oriented protocol (TCP), because TCP operates at Layer 3 of the OSI model to encapsulate session state tables directly into IP routing headers.
  4. D
    Implement a connectionless protocol (UDP), because binding the application to a registered port below 1024 automatically disables stateful tracking on network firewalls.

Answer

Implement a connectionless protocol (UDP), because it eliminates stateful session maintenance on firewalls while reducing per-packet overhead by omitting sequence numbers, flow control, and acknowledgment header fields.
The option advocating for a connectionless protocol (UDP) is correct because UDP operates without connection state establishment (no SYN/ACK handshake or connection state tables), preventing firewall table exhaustion. Furthermore, UDP's minimal 8-byte header overhead compared to TCP's 20-byte base header maximizes payload efficiency for small 64-byte heartbeats across bandwidth-constrained links.

Step-by-Step Solution

1
Analyze the operational constraints presented in the scenario.
Identified two primary issues: firewall session table exhaustion due to state tracking of thousands of devices, and bandwidth/latency inefficiency caused by transport control overhead.
The transport protocol choice must address both session state overhead and header size constraints.
2
Evaluate the architectural characteristics of connection-oriented vs. connectionless protocols.
Connection-oriented protocols (TCP) require state tracking (SYN/ACK handshakes, sequence numbers, session cleanup), maintaining open states on stateful firewalls and using a minimum 20-byte header. Connectionless protocols (UDP) are stateless and use a lightweight 8-byte header without handshake or teardown overhead.
Stateless transmission prevents firewall session table saturation and conserves satellite bandwidth on frequent 64-byte heartbeat transmissions.
3
Match the requirement with the correct transport choice and technical justification.
UDP satisfies all requirements by being connectionless and lightweight.
UDP avoids session maintenance and reduces header overhead from 20+ bytes to 8 bytes.

Key Concept

Connection-Oriented vs Connectionless Transport Protocols
Rate this question

Topics

Connection-Oriented vs Connectionless Protocols

More questions from this topic