Exercise 2: Why a Socket-Activated Connection Looks Identical to the Client — Possible Solution
====================================================================

Explanation:

Per the chapter's own description of what socket activation actually
does, systemd itself "opens and listens on the network socket... on
behalf of a service, before that service is even running." This means
the socket the client is connecting to is ALREADY open and accepting
connections at the operating-system level, regardless of whether the
real application process behind it happens to be running yet or not.

When a client attempts a connection, the chapter is explicit that
"any connection attempt is queued by the kernel/systemd" -- the
connection itself succeeds at the socket level immediately, exactly
as it would against an already-running service's own listening
socket. Only AFTER that initial connection is accepted does systemd
check whether the real service process is running, and start it if
it isn't, handing it the already-open socket (via the well-known file
descriptor this chapter describes) to actually begin processing the
now-queued connection.

From the client's own point of view, none of this internal
bookkeeping is visible -- the connection attempt succeeded, exactly
as it would have against a service that was already running the whole
time. The client has no way to directly observe whether the process
behind the socket had to be started just now or was already sitting
there warm -- the socket-level connection experience is identical
either way, which is precisely why the chapter states this is
"completely invisible" from the client's perspective.

WHY THIS WORKS AS AN ANSWER
------------------------------
This traces the exact mechanism (the socket itself is already open
and accepting connections regardless of the service's own running
state, with the service only started afterward) rather than just
asserting the experience is identical, directly grounding the
explanation in the chapter's own description of the queuing and
handoff process.