A network administrator is categorizing application protocols and network workloads based on their transport layer requirements. Match each operational scenario on the left with the corresponding transport protocol characteristic on the right.
- HTTPS web traffic requiring guaranteed, ordered packet delivery and TLS encryption session trackingConnection-oriented protocol utilizing a three-way handshake and sequence numbers for flow control
- VoIP audio stream where minimal packet delay is critical and lost packets should not be retransmittedConnectionless protocol with minimal header overhead prioritizing real-time low-latency transmission
- TFTP firmware download utilizing lightweight headers and application-controlled reliabilityConnectionless protocol operating without transport-level session state or sequence acknowledgment
- BGP router peer session exchanging routing table updates over a persistent linkConnection-oriented protocol providing reliable, byte-stream delivery for session stability
Answer
HTTPS matches connection-oriented transport with a three-way handshake and sequence numbers; VoIP matches connectionless transport with low-latency overhead; TFTP matches connectionless transport without transport-level session state; and BGP matches connection-oriented reliable byte-stream delivery.
The pairings correctly match application requirements to their underlying Layer 4 protocol mechanisms. TCP provides reliable, ordered, session-based transport for HTTPS and BGP, whereas UDP provides low-overhead, unacknowledged datagram transport for VoIP and TFTP.
Step-by-Step Solution
Key Concept
Connection-Oriented (TCP) vs Connectionless (UDP) Transport Protocol Operational Characteristics