Challenge 3: Why No Dedicated Reverse-Proxy/ARR Chapter — Solution
Walkthrough

The reasoning:

Apache In Depth and Nginx In Depth each devote a real chapter to
reverse proxying and load balancing because mod_proxy and proxy_pass
are core, built-in capabilities of those two servers -- functionality
every real Apache or Nginx installation already has available, no
extra install required. IIS's situation is genuinely different: its
reverse-proxy capability, Application Request Routing (ARR), is a
separate, optional add-on module that a large share of real IIS
installations never install at all, because IIS's primary real-world
job is hosting ASP.NET/.NET applications directly, not proxying
traffic to something else.

Why this matters for the course's own scope:

Giving ARR a full chapter here, matching the shape of its Apache and
Nginx siblings, would misrepresent how central reverse proxying
actually is to a typical IIS deployment -- it would imply IIS
users need this the way Apache and Nginx users genuinely do. Instead,
this course spends its chapters on what IIS itself does natively and
centrally: Application Pools, the configuration model, the module
pipeline, and IIS-native URL Rewrite (which works fine without ARR at
all, since Rewrite alone doesn't require proxying anything).

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the reader understands a course's chapter
list is a deliberate reflection of what's actually central to a given
technology, not a checklist forced to match a sibling course's shape
just for consistency -- IIS genuinely doesn't need a proxy chapter the
way Apache and Nginx do, and this chapter says so honestly rather than
including one anyway for symmetry.