
Unit II Checkpoint: Follow the Data
Where you are: Unit II — How the Digital World Works · Checkpoint · About 12 minutes. This checkpoint draws on Chapters 3 to 6 of Dr. Al-Doori's Cyber Security Essentials and Lessons 2.1 to 2.4.
Unit II gave you a working picture of how data moves: across the Internet in packets, through mail servers, into your browser and over Wi-Fi. This checkpoint asks you to follow the data in three everyday situations. For each one, read the scenario, choose your answer, and then compare your reasoning with the model answer. All names and addresses are invented.
Scenario 1: Who could read this message?
Sofia writes an ordinary email in her phone's mail app to her friend Ben, who uses a different email provider. Neither of them uses any special encryption. Her app connects to her provider over an encrypted connection, and the message arrives in Ben's inbox a few seconds later.
Apart from Sofia and Ben, who could read the content of this message?
Model answer
c is right. Email is relayed: Sofia's app hands the message to her provider's mail server, which passes it to Ben's provider's server using SMTP, where it is stored until Ben's app collects it. Each server reads enough of the message to route it, and both providers hold readable copies of ordinary email. As Dr. Al-Doori puts it, your email passes through servers you don't control.
a is not right: the encrypted connection protects the message on its way between the app and the provider, but it is not end-to-end encryption. b is not right: email is handled by mail providers, not by the phone company. d is not right: the encrypted connection from Sofia's app is exactly what protects her from people on the same Wi-Fi network.
The practical lesson: treat ordinary email like a postcard handled by several sorting offices. Don't send passwords, ID documents or bank details by email.
Scenario 2: Real or look-alike?
Your university's real domain is tallowfield.test. A message asks you to reset your student account and gives three addresses. You copy them down rather than tapping them. All domains ending in .test or .example in this scenario are reserved for training and cannot be real public websites.
- A.
accounts.tallowfield.test/reset - B.
tallowfield.test.account-reset.test/student - C.
tallowfield-edu.example/accounts/reset
Which of these addresses can only belong to your university?
Model answer
b is right. Read each host name backwards from the first single slash to find the registered domain:
- A ends in
tallowfield.test. "accounts." is a label only the university can create. Real. - B ends in
account-reset.test. "tallowfield.test" is just a label on the left, chosen by whoever owns account-reset.test. Look-alike. - C is
tallowfield-edu.example, a different domain with a hyphen and a different ending. Look-alike.
a is not right: containing the university's name anywhere in the address proves nothing. c is not right: B's real domain is account-reset.test. d is not right: both B and C are look-alikes, and A is genuine.
Even so, the safest move is not to use any link from the message. Go to the university portal through your bookmark or by typing the address you already know. If the reset request is genuine, you'll see it there.
Scenario 3: Two networks, one name
At a public library, your laptop shows two Wi-Fi networks, both called Library_Guest. One shows full signal; the other is weaker. You want to sign in to your university account to submit an assignment.
What is the main risk, and what is the best thing to do?
Model answer
a is right. Your device identifies a network mainly by its name, and anyone can broadcast any name. Two networks with the same name could both be the library's, or one could be an impostor. Signal strength only tells you which access point is closer, not who owns it. Confirm the official network name with the staff or on the library's own signage. For sensitive sign-ins on a network you can't confirm, mobile data is a sensible alternative.
b is not right: same-name networks are sometimes legitimate, but you can't tell from the list, so "no risk" is not a safe assumption. c is not right: an impostor's device may be closer than the library's access point, so a stronger signal can point to the fake. d is not right: the risk is uncertainty about this particular network, not Wi-Fi in general; checking with the venue solves it.
Unit V (Lessons 5.9 and 5.10) returns to fake hotspots and how to secure networks you run yourself.
Before you move on
If any model answer surprised you, revisit the matching lesson: 2.2 for how email travels, 2.3 for reading a web address, and 2.4 for how devices choose networks. Unit III now turns to the people on the other end of the data, and how they try to manipulate you.
