Exercise 1: Reading a Link-Local Address — Possible Solution
====================================================================

WHAT THE PATTERN IS
------------------------------
Per this chapter, an address in the 169.254.0.0/16 range (a "link-local"
or APIPA address) is one the operating system self-assigns when it
cannot reach a DHCP server to be given a real one. The absence of a
default gateway alongside it is consistent with this - a self-assigned
address has no gateway to configure, because it was never actually
handed out by anything on the real network.

WHAT IT MEANS
------------------------------
Per this chapter, "DHCP failed, full stop." The machine has no real
address, no gateway, and no way to reach anything outside its own local
segment. The specific cause could be a disconnected cable, a
misconfigured switch port, a DHCP server outage, or a wireless
authentication failure - but whatever it is, the fault is squarely at
the local-connectivity rung.

WHY TESTING DNS OR PING AT THIS POINT IS A WASTE OF TIME
------------------------------
Per this chapter's own ladder logic (established in Chapter 2), you
work the ladder bottom-up and stop at the first failing rung. A
169.254.x.x address with no gateway already IS that first failure -
local connectivity itself is broken, so DNS resolution and reaching the
app are simply not possible yet regardless of whether those specific
services are healthy. Testing them would only reproduce the same
failure one rung too early to be useful.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names the address range and what it signifies (a DHCP
failure, self-assigned fallback address), and connects it back to the
ladder's own bottom-up, stop-at-first-failure principle to explain why
testing further up would be wasted effort rather than just asserting
that it would be.