TCP (Transmission Control Protocol) is an open Internet protocol that ensures reliable, ordered delivery of data by breaking messages into packets, tracking each one, reassembling them in order at the destination, and requesting retransmission of any packets that get lost.
TCP stands for Transmission Control Protocol, and it's the Internet's quality-control system. The CED defines a protocol as an agreed-upon set of rules that specify the behavior of a system (EK CSN-1.B.3), and TCP's specific job is making sure data actually arrives, complete and in the right order. When you send a message over the Internet, it gets chopped into packets, and each packet carries metadata for routing and reassembly (EK CSN-1.C.2). Here's the problem TCP solves. Packets may arrive in order, out of order, or not at all (EK CSN-1.C.3). TCP numbers the packets, reassembles them in the correct sequence at the destination, and if a packet never shows up, it asks the sender to transmit it again.
Think of TCP as certified mail with tracking numbers. Every package is labeled, the receiver checks them off a list, and anything missing gets re-sent. The CED names IP, TCP, and UDP as the common protocols used on the Internet (EK CSN-1.C.4), and TCP is the one you reach for when getting every single bit matters, like loading a webpage or downloading a file. Like all Internet protocols, TCP is open and nonproprietary (EK CSN-1.B.4), which is exactly why any device can join the Internet and immediately speak the same language as everything else.
TCP lives in Unit 4 (Computer Systems and Networks), Topic 4.1 (The Internet), and it directly supports learning objective 4.1.C, which asks you to explain how data are sent through the Internet via packets. It also feeds into 4.1.B (explaining how the Internet works), since TCP is a textbook example of the open, standardized protocols that make the Internet scalable. The exam logic goes like this. First you learn that data travels as packets, then you learn packets can arrive scrambled or go missing, and then TCP is the answer to 'so how does anything work?' If you can explain that chain, you've got the core of Topic 4.1. TCP also shows up implicitly whenever the exam tests fault tolerance and reliability, because TCP is the protocol-level mechanism that makes unreliable packet delivery usable.
Keep studying AP® Computer Science Principles Unit 4
UDP (Unit 4)
UDP is TCP's faster, looser sibling. It sends packets without tracking delivery or requesting retransmission, which makes it quicker but unreliable. The exam loves asking you to pick which protocol fits a scenario, so remember TCP for accuracy, UDP for speed.
Routing (Unit 4)
Routing decides which path each packet takes across the network, and that routing is dynamic, so packets from one message can take different routes. That's exactly why packets arrive out of order, and exactly why TCP's reassembly job exists. Routing creates the chaos; TCP cleans it up.
HTTP (Unit 4)
HTTP is the protocol of the World Wide Web, and it runs on top of TCP. When you load a webpage, HTTP defines the request, while TCP underneath guarantees every packet of that page actually arrives. This layering is the cleanest example of how the Web uses the Internet (EK CSN-1.D.3).
Computer network (Unit 4)
A computer network is a group of interconnected computing devices that send and receive data (EK CSN-1.A.3). Protocols like TCP are what let billions of different devices on the Internet, which is a network of networks, communicate without anyone coordinating in advance.
TCP is multiple-choice territory in AP CSP, and the questions are predictable. The most common stem asks which protocol ensures reliable transmission by breaking data into packets, tracking delivery, and requesting retransmission of lost packets. The answer is TCP. A second favorite asks what happens when packets arrive out of order, and the answer involves reassembly using packet metadata, which is TCP's job. The third pattern is TCP versus UDP comparison questions, where you identify that TCP guarantees delivery and order while UDP trades reliability for speed. You won't write code about TCP, and no released FRQ has required it verbatim, but you do need to use it correctly when explaining how the Internet moves data. One trap to avoid is mixing up which protocol does what, since IP handles addressing and routing while TCP handles reliability.
Both TCP and UDP send data as packets over the Internet, but they make opposite trade-offs. TCP tracks every packet, reassembles them in order, and re-requests anything lost, so it's reliable but slower. UDP just fires packets off without checking whether they arrived, so it's fast but lossy. That's why file downloads and webpages use TCP (you need every byte) while live video calls often use UDP (a dropped frame is better than a frozen, lagging call). If an exam question says 'reliable' or 'retransmission,' the answer is TCP. If it says 'speed over accuracy,' think UDP.
TCP (Transmission Control Protocol) guarantees reliable, ordered delivery of data over the Internet by tracking packets and requesting retransmission of any that are lost.
Packets can arrive in order, out of order, or not at all, and TCP is the protocol that fixes this by numbering packets and reassembling them correctly at the destination.
TCP is reliable but slower, while UDP is fast but doesn't guarantee delivery, and the exam frequently asks you to tell them apart.
The CED names IP, TCP, and UDP as the common Internet protocols, with IP handling addressing and routing while TCP handles reliability.
TCP is an open, nonproprietary protocol, which is part of why any new device can connect to the Internet and communicate immediately.
HTTP, the protocol of the World Wide Web, relies on TCP underneath it to make sure webpages arrive complete.
TCP (Transmission Control Protocol) is an Internet protocol that ensures reliable, ordered delivery of data. It breaks data into packets, tracks each one, reassembles them in the correct order, and requests retransmission of lost packets. It's tested in Topic 4.1 under learning objective 4.1.C.
TCP guarantees every packet arrives and gets reassembled in order, making it reliable but slower. UDP sends packets without tracking delivery, making it faster but unreliable. Webpages and downloads use TCP; live streaming and video calls often use UDP.
Sort of, but not the way you might think. Packets can still travel different routes and arrive at the destination out of order. TCP guarantees the data is reassembled in the correct order using packet metadata, and that's the distinction MCQs test.
No. They're separate protocols that work together (you'll often see 'TCP/IP'). IP handles addressing and routing packets to the right destination, while TCP handles reliability, ordering, and retransmission. The CED lists them as distinct common protocols in EK CSN-1.C.4.
You only need the conceptual level. Know that TCP ensures reliable, ordered delivery, that it requests retransmission of lost packets, and how it contrasts with UDP and IP. There's no TCP code or technical handshake detail on the exam.
Connect this key term to the AP exam workflow: review the course, practice questions, and check related study tools.
Review units, study guides, and course resources.
Check this vocabulary in multiple-choice context.
Apply key concepts in written AP responses.
Estimate the exam score you are working toward.
Review the highest-yield facts before practice.
Put the full course together before test day.