Challenge 2: Seven Fundamentals Chapters, and Why Apache Needed More
of Them Than Nginx Did — Solution Walkthrough

Five (of the seven) worth naming, and what each left shallow:

1. Chapter 2 (Architecture Models) — introduced the three MPMs
   (prefork, worker, event) conceptually, without tuning any of them
   for a real workload.

2. Chapter 3 (Configuration Philosophy) — introduced the
   directory-context model and .htaccess as Apache's own philosophy,
   without covering the directive precedence/merge-order rules that
   make it actually predictable in practice.

3. Chapter 4 (Virtual Hosts) — covered Apache virtual hosts only at a
   basic name-based level, with no SNI or IP-based depth.

4. Chapter 6 (Reverse Proxying & Load Balancing Fundamentals) —
   introduced mod_proxy and a single ProxyPass line, without
   mod_proxy_balancer or any real load-balancing algorithm.

5. Chapter 9 (Performance Basics) — covered compression and
   keep-alive briefly and comparatively, with no real tuning or log
   analysis.

(Chapters 7 and 8 are the other two: Ch.7 covered TLS termination
generically across all three servers rather than Apache's own mod_ssl
directives, and Ch.8 covered access control/hardening only at a
survey level.)

Why Apache needed more of these chapters than Nginx did:

Apache's per-directory configuration model (.htaccess, directory
contexts) and its multiple MPM choices are genuinely different enough
from Nginx's single centralized config file and one event-driven
architecture that almost every comparative chapter in Fundamentals
had real, Apache-specific material to introduce — not just a passing
mention — which is exactly why Apache In Depth's own scope chapter
lists seven prior chapters instead of Nginx In Depth's three.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the reader has actually read and can recall
this chapter's own "What Web Servers Fundamentals Already Covered"
section, and understands the specific, honest reason Apache's own
footprint in that earlier course is wider than Nginx's — a real
architectural difference, not an arbitrary inconsistency between the
two sibling courses.