networks exam 1

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/22

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

23 Terms

1
New cards

Protocol

A set of rules that devices follow. A set of processes to follow INVOLVES MORE THAN 1 PERSON, IT CANNOT BE YOURSELF

2
New cards

Internet structure

The internet is a network of networks. When you send data, it hops through many routers and networks to reach the destination — not directly.

3
New cards

End system (host)

A device that connects to the internet and uses network apps, like your phone, laptop, or a web server.

4
New cards

Application layer

Where apps like web browsers and email live — it’s what the user interacts with.

5
New cards

Transport layer

Handles reliable delivery of messages between apps (like making sure your message arrives complete and in order).

6
New cards

Network layer

Decides the best path for your data to travel across networks — it deals with IP addresses.

7
New cards

Link layer

Deals with communication between devices on the same network, like your PC and your router.

8
New cards

Physical layer

All the hardware stuff — wires, Wi-Fi signals, anything that physically moves bits.

9
New cards

Encapsulation

As data goes down the layers, each layer adds its own header to the message. When it’s received, the layers remove the headers in reverse order.

10
New cards

Packet sniffer

A tool that captures and lets you see network traffic. Useful for debugging, but can be misused to steal passwords or spy on users.

11
New cards

HTTP

The protocol used by web browsers to request and receive web pages.

12
New cards

SMTP

The protocol used to send emails between servers.

13
New cards

HTTP request structure

Includes method (GET/POST), URL, headers, and maybe a body. It’s a way to ask a server for something.

14
New cards

Caching (in HTTP and DNS)

Temporary storage of recent data so future requests are faster. Browsers, DNS servers, and even your OS use it.

15
New cards

HTTP vs SMTP

HTTP pulls data (client asks, server sends), while SMTP pushes it (client sends data to server). Also, SMTP stores messages; HTTP doesn’t.

16
New cards

Socket

A combo of IP address and port number that lets apps send/receive data. Think of it as the app’s "address" on the internet.

17
New cards

DNS (Domain Name System)

Translates easy-to-remember names (like google.com) into IP addresses. Without it, you’d have to remember numbers.

18
New cards

19
New cards

Steps of DNS query (e.g. to visit www.utrgv.edu)

Browser checks cache → Asks OS → Asks DNS resolver → May ask root server → TLD server → Authoritative server → Gets IP → Connects.

20
New cards

Client

A device/app that makes requests (like your browser).

21
New cards

Server

A device/app that responds to requests (like a website's backend).

22
New cards

Client-server model

Client initiates connection, server waits for requests. Server usually has more resources and is always online.

23
New cards

P2P (Peer-to-peer)

Devices talk directly to each other and share resources (like BitTorrent). No need for a central server, more scalable.