Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Network protocols are the invisible rules that make the internet work—they determine how devices find each other, how data travels reliably across the globe, and how your information stays secure. On the AP exam, you're being tested on your understanding of layered architecture, reliability vs. speed tradeoffs, and how abstraction enables complex systems to function. These protocols demonstrate core computer science principles like error handling, addressing, and the client-server model.
Don't just memorize what each protocol does—know why it exists and what problem it solves. When you understand that TCP sacrifices speed for reliability while UDP does the opposite, you're thinking like a computer scientist. That comparative reasoning is exactly what FRQs reward, so focus on the underlying mechanisms and tradeoffs, not just definitions.
These protocols form the backbone of all internet communication. They handle the fundamental challenges of getting data from point A to point B—addressing, routing, and ensuring data arrives correctly.
Compare: TCP vs. UDP—both are transport-layer protocols that work on top of IP, but TCP prioritizes reliability (guaranteed delivery, ordering) while UDP prioritizes speed (no handshake, no error correction). If an FRQ asks when you'd choose one over the other, think: "Does this application need every packet, or does it need them fast?"
These protocols power your everyday browsing experience. They define how web browsers request content from servers and how that content gets delivered—with or without encryption.
Compare: HTTP vs. HTTPS—identical request-response functionality, but HTTPS wraps everything in encryption. The "S" stands for secure, and it's now the default standard. Know that HTTPS doesn't change what HTTP does—it adds a security layer on top.
Before any communication happens, devices need to find each other. DNS solves the problem of humans preferring words while computers need numbers.
www.example.com into numerical addresses computers useCompare: DNS functions like a phone book for the internet—you look up a name, you get a number. This is a perfect example of abstraction: users never need to know IP addresses because DNS handles the translation automatically.
Email requires multiple protocols working together—one for sending, others for receiving. The key distinction is between pushing mail out (SMTP) and pulling mail in (POP3/IMAP).
Compare: POP3 vs. IMAP—both retrieve email, but POP3 downloads and deletes (single device, offline focus) while IMAP syncs and stores (multiple devices, always connected). FRQ tip: if asked about accessing email from multiple devices, IMAP is your answer.
When you need to move files between systems, specialized protocols handle the job. FTP predates the web and remains useful for bulk file transfers.
Compare: FTP vs. HTTP—both can transfer files, but FTP is optimized for it with features like resume-interrupted-downloads and directory browsing. HTTP is better for web content delivery; FTP is better for bulk file management.
| Concept | Best Examples |
|---|---|
| Reliable data delivery | TCP (guarantees order and arrival) |
| Fast, low-latency transmission | UDP (no handshake, no guarantees) |
| Device addressing and routing | IP (IPv4, IPv6 addresses) |
| Web content transfer | HTTP, HTTPS |
| Encryption and security | HTTPS (SSL/TLS), SMTP authentication |
| Name-to-address translation | DNS |
| Sending email | SMTP |
| Receiving email (single device) | POP3 |
| Receiving email (multi-device sync) | IMAP |
| Bulk file transfer | FTP |
Which two protocols operate at the transport layer, and what tradeoff distinguishes them from each other?
A video call application needs to prioritize minimal delay over perfect accuracy. Which protocol should it use, and why would TCP be a poor choice?
Compare and contrast POP3 and IMAP: what problem does each solve, and which would you recommend for someone who uses both a phone and laptop for email?
Explain how DNS demonstrates the principle of abstraction. What would internet use look like without it?
An FRQ asks you to describe how a secure online purchase works. Which protocols are involved when you type a URL, connect to a store, and submit payment information? Trace the path from domain name to encrypted transaction.