Challenge 2: Seven Fundamentals Chapters, and Why IIS Needed About as
Much of Them as Apache Did — Solution Walkthrough

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

1. Chapter 2 (Architecture Models) -- introduced Application Pools and
   their w3wp.exe worker process conceptually, including recycling,
   without configuring either in real depth.

2. Chapter 3 (Configuration Philosophy) -- introduced the GUI/XML
   model (applicationHost.config machine-wide, web.config
   per-directory) without covering real inheritance behavior across
   them.

3. Chapter 4 (Virtual Hosts) -- covered Sites and bindings only at a
   basic level.

4. Chapter 7 (TLS/HTTPS Termination) -- covered the Windows
   Certificate Store and HTTPS bindings generically, with no SNI
   depth specific to IIS.

5. Chapter 9 (Performance Basics) -- named Dynamic/Static Content
   Compression and Output Caching briefly and comparatively, with no
   real tuning or troubleshooting tooling.

(Chapters 6 and 8 are the other two: Ch.6 named ARR as IIS's own
add-on reverse-proxy capability without configuring it, and Ch.8
named IP/Domain Restrictions and Basic/Windows Authentication without
real directive depth.)

Why IIS needed about as much of Fundamentals as Apache did:

Per this chapter's own reasoning, IIS has its own genuine
per-directory configuration-override mechanism -- web.config -- the
same underlying idea as Apache's .htaccess, and structurally closer
to Apache's philosophy than to Nginx's single centralized config file.
That real architectural similarity to Apache (rather than to Nginx)
is exactly why IIS's own footprint across Fundamentals' comparative
chapters ended up close to Apache's seven, rather than Nginx's three.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the reader has actually read this chapter's
own "What Web Servers Fundamentals Already Covered" section, and can
connect IIS's wider footprint in that earlier course to the same
underlying architectural reason (a real per-directory override
mechanism) that Apache In Depth's own Chapter 1 gave for Apache's own
wider footprint -- a genuine parallel between the two sibling courses,
not a coincidence.