Challenge 1: Why No Apache/Nginx Comparison Here — Solution
Walkthrough

Why the comparison is absent:

Web Servers Fundamentals already covered the comparative question in
full -- architecture, configuration philosophy, virtual hosting, TLS,
and performance, all side by side across Apache, Nginx, and IIS,
closing with a dedicated capstone decision framework for choosing
between them. That question has already been answered by the time
someone reaches this course.

What this course assumes instead:

Per this chapter's own framing, this course assumes the reader has
either already decided IIS fits their job -- very often because the
application itself is a Windows/.NET one -- using Web Servers
Fundamentals' own framework, or already knows they specifically want
to go deep on IIS. Repeating the Apache/Nginx comparison here would
duplicate material that already exists elsewhere on the site, rather
than adding anything new -- this course's entire purpose is to go
further into IIS specifically, in the areas (Application Pools,
configuration inheritance, the module pipeline, authentication) that
were deliberately kept shallow there.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the relationship between these two courses
is understood correctly -- Web Servers Fundamentals owns the
comparative question, IIS In Depth owns the single-server deep dive --
matching the same pattern already established by Apache In Depth and
Nginx In Depth's own scope chapters.