TCP vs UDP: How to Choose the Right Protocol on A+
TCP is for reliable, ordered sessions. UDP is for lightweight, low-latency exchanges. This guide shows how A+ questions usually signal the right choice.
Quick answer
Use TCP when the scenario needs sequencing, acknowledgments, retransmission, or reliable ordered delivery. Use UDP when the scenario is a short request/response or low-latency exchange where the application can tolerate loss or retry on its own.
Start with reliability versus overhead
If a remote administration session drops keystrokes or reorders data, the session breaks. That is a TCP cue because the application needs reliable, ordered delivery.
If a DNS query fails, the client can ask again. That is a UDP cue because the exchange is brief and the application can retry without maintaining a full transport session.
For A+ Core 1 networking questions, the task is rarely deep protocol design. The task is recognizing which transport behavior matches the service or symptom in the scenario.
- TCP: connection-oriented, sequenced, acknowledged, retransmitted.
- UDP: connectionless, lower overhead, common for DNS and NTP.
- Do not reduce the answer to "UDP is faster." Match the protocol to the application need.
- File transfer and remote administration usually point toward TCP.
TCP and UDP compared
TCP
Best for
Reliable sessions where missing or out-of-order data is a problem.
Exam cue
Sequencing, acknowledgments, retransmission, file transfer, remote access.
Common mistake
Choosing UDP just because the word speed appears.
UDP
Best for
Short exchanges and low-latency traffic that can tolerate retry or loss.
Exam cue
DNS, NTP, streaming media packets, brief request/response.
Common mistake
Assuming UDP is always the better answer for performance.
DNS over UDP
Best for
Normal quick name lookups.
Exam cue
Client asks for a hostname lookup and can retry if needed.
Common mistake
Choosing TCP for every DNS scenario without a reliability cue.
TCP service ports
Best for
Services that need reliable session delivery.
Exam cue
HTTP/HTTPS, SSH, RDP, FTP, SMTP, IMAP, POP3.
Common mistake
Memorizing ports without understanding why the service needs sessions.
Scenario cues to look for
A user opens a remote shell and keystrokes must arrive in order.
Answer: TCP
Remote interactive sessions need ordered reliable delivery.
Why not the distractor: UDP would not provide built-in sequencing or retransmission.
A workstation sends a quick DNS lookup and can retry if the packet is lost.
Answer: UDP
The exchange is short and the application can retry.
Why not the distractor: TCP overhead is not needed for the normal lookup cue.
A file transfer must not silently lose chunks of data.
Answer: TCP
Reliable delivery and retransmission are the key cues.
Why not the distractor: UDP being lower overhead does not make it correct when data integrity matters.
Common exam mistakes
Using "speed" as the only rule.
Ask whether the application needs reliable ordered delivery or can tolerate retry/loss.
Memorizing service ports without transport behavior.
Tie common ports back to why the service uses TCP or UDP.
Assuming UDP means unreliable application.
UDP has no built-in reliability, but the application can still add retry logic.
Quick practice questions
Answer each question to reveal the explanation. The full app adds tracked results and weak-area review.
Q1.Which transport protocol provides sequencing, acknowledgments, and retransmission?
Q2.Which protocol is commonly used for normal DNS name lookups?
Q3.A scenario says occasional packet loss is acceptable but low latency matters. Which protocol is usually the better fit?
Ready to test your knowledge?
Try the free CompTIA A+ practice test, or use the app for tracked weak-area review.