Challenge 3: "Apache Is Obsolete Now That Nginx Exists" — Solution Walkthrough

What's true in the claim:

Nginx was genuinely built to solve a concurrency problem that older
versions of Apache — particularly the Prefork MPM — handled poorly,
and for a long time this gave Nginx a real, meaningful edge in
high-concurrency scenarios. That history is accurate.

What's an oversimplification:

Modern Apache, running its Event MPM, closes most of that original gap
by offloading idle keep-alive connections without tying up a full
worker thread for each one — the same category of efficiency gain
Nginx's own architecture was built around from the start. Per this
chapter's own warning box, treating this as "Nginx's architecture is
simply better" ignores that the concurrency-model differentiator has
substantially narrowed. The real, lasting differences between the two
servers today are more about configuration philosophy and ecosystem
fit (module flexibility vs. a centralized, high-performance-first
config model) than a fixed performance gap.

A short, accurate response:

"That's true historically — Nginx really was built to beat Apache's
old concurrency model — but Apache's modern Event MPM has closed a lot
of that gap. Today the more useful question isn't 'which is faster,'
it's which configuration style and ecosystem actually fits what you're
building."

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise asks for a direct, own-words rebuttal built from this
chapter's own warning box — correctly separating "true historically"
from "still true as a blanket statement today" is the exact nuance the
warning box exists to preserve, rather than letting the chapter's own
comparison be flattened into a simple "winner and loser."