Examkin

Soru

Zorluk: ZorConnection-Oriented vs Connectionless Protocols

A network administrator is designing the communication architecture for an automated logistics facility. The design requires one stream for low-latency, unacknowledged telemetry updates from mobile sensors where occasional dropped packets are acceptable, and a second stream for critical database synchronization where missing data must be retransmitted. Which of the following transport layer characteristics correctly distinguish the connectionless protocol chosen for sensor telemetry from the connection-oriented protocol chosen for database synchronization? (SELECT TWO)

  1. A
    The sensor telemetry protocol initiates session state via a three-way handshake before transmitting payload data, whereas the database synchronization protocol sends datagrams without prior signaling.
  2. The sensor telemetry protocol operates with minimal header overhead of 8 bytes and delegates error recovery to higher-layer applications, whereas the database synchronization protocol uses a minimum 20-byte header containing reliability control fields.Cevap
  3. The database synchronization protocol utilizes sequence numbers and acknowledgment tracking to support sliding-window flow control and ordered segment reassembly.Cevap
  4. D
    The sensor telemetry protocol operates directly at the Network Layer (Layer 3) to reduce processing overhead, while the database synchronization protocol operates at the Transport Layer (Layer 4).
  5. E
    The database synchronization protocol is restricted to well-known ports (1–1023), while the sensor telemetry protocol operates exclusively within dynamic/ephemeral port ranges (49152–65535).

Cevap

The correct selections state that the connectionless telemetry protocol operates with an 8-byte header overhead while delegating error recovery, and that the connection-oriented database protocol utilizes sequence numbers and acknowledgment tracking for flow control and ordered delivery.
The options describing the 8-byte header size with application-level error recovery and the option describing sequence/acknowledgment numbers for sliding-window flow control correctly detail the technical differences between UDP and TCP. UDP minimizes latency and overhead with an 8-byte header, while TCP uses at least 20 bytes of header data to track sequence numbers, ACKs, and window size for reliable delivery.

Adım Adım Çözüm

1
Identify the protocol types required for each traffic flow based on the scenario requirements.
Sensor telemetry requires a connectionless protocol (UDP) prioritizing low latency over reliability. Database synchronization requires a connection-oriented protocol (TCP) guaranteeing reliable, ordered delivery.
UDP provides lightweight datagram transmission without connection overhead, whereas TCP guarantees packet delivery via connection management.
2
Analyze header structure and overhead differences between UDP and TCP.
UDP uses a fixed 8-byte header containing Source Port, Destination Port, Length, and Checksum. TCP uses a minimum 20-byte header containing sequence/acknowledgment numbers, window sizing, and flags.
The extra header fields in TCP are necessary to maintain state and perform reliability mechanisms.
3
Evaluate flow control and delivery mechanisms for TCP vs. UDP.
TCP uses sequence numbers, ACK fields, and sliding windows to manage data reassembly and traffic rates. UDP provides no native sequencing or flow control.
Connection-oriented protocols build stateful control structures into the transport header to handle lost or out-of-order segments.

Anahtar Kavram

Connection-oriented protocols (TCP) establish stateful sessions using sequence numbers, ACKs, and flow control with a minimum 20-byte header, whereas connectionless protocols (UDP) send unacknowledged datagrams with minimal 8-byte header overhead.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Connection-Oriented vs Connectionless Protocols

Bu konudan daha fazla soru