Challenge 3: The One Command to Run Before Restarting — Solution
Walkthrough

The command:

apachectl configtest (or equivalently, apachectl -t)

What it would likely have told them:

configtest validates the entire configuration's syntax without
actually reloading or restarting the running server -- it's a
read-only check, safe to run at any time. Given that a full restart
immediately took the entire site down with no traffic served at all,
this strongly suggests the config the team just edited contains a
genuine syntax error. Had they run configtest first, Apache would
almost certainly have reported something like "AH00526: Syntax error
on line N" -- naming the exact line the problem is on -- and, because
configtest doesn't actually apply anything, the previously-running,
still-working Apache process would have kept serving traffic
completely undisturbed while the error was found and fixed. Only once
configtest reports the config is valid should a real restart or
reload ever be applied.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the reader has internalized the specific,
concrete workflow this chapter recommends -- configtest before every
reload, not just "check the config carefully" as vague advice -- and
understands that skipping it is exactly how a small typo becomes a
full outage instead of a five-second non-event.