Exercise 3: Assigning 192.168.10.255 to a Server on a /24 Network — Possible Solution
====================================================================

What went wrong:

Per the chapter's own worked example for a /24 network, "broadcast
address: 192.168.1.255" -- on a 192.168.10.0/24 network specifically,
the broadcast address is 192.168.10.255, using the exact same logic
(the broadcast address is the address with every host bit set to 1,
which for a /24 network means the fourth octet is 255). The
administrator assigned the network's own broadcast address directly to
a server, which is exactly the mistake the chapter's own warn-box
names: "assigning 192.168.1.0 or 192.168.1.255 directly to a device on
a /24 network... [is] reserved -- the network address identifies the
subnet itself, and the broadcast address is used to reach every device
on the subnet at once. Assigning either to a single device breaks
things in ways that can be genuinely confusing to diagnose later."

Why this causes connectivity problems:

The broadcast address exists specifically so that a single packet sent
to it gets delivered to every device on the subnet simultaneously --
it's a special, shared destination, not a normal, individually
addressable device. Assigning it to one specific server creates a
direct conflict between two completely different meanings for the same
address: the network infrastructure (routers, switches, other devices)
still treats 192.168.10.255 as "send this to everyone on the subnet,"
while the newly configured server expects to receive traffic addressed
specifically and only to itself at that address. Traffic meant only for
the server may get flooded to every device on the subnet instead, and
traffic that other devices intend as a genuine broadcast may get
misinterpreted as being aimed specifically at this one server -- the
address is doing two incompatible jobs at once, which is exactly the
kind of confusing, hard-to-diagnose behavior the chapter's own
warn-box predicts.

The fix:

The server should be assigned any address within the network's actual
usable host range instead -- per the chapter's own /24 example, that
range is 192.168.10.1 through 192.168.10.254, deliberately excluding
both the network address (192.168.10.0) and the broadcast address
(192.168.10.255).

WHY THIS WORKS AS AN ANSWER
------------------------------
This identifies specifically which reserved address (the broadcast
address) was misassigned, explains the actual mechanism of the
resulting conflict (one address serving two incompatible roles) rather
than just citing the rule, and names the correct usable range from the
chapter's own worked example.