Challenge 1: Rewrite vs. Redirect -- Solution Walkthrough

A Rewrite action is handled entirely inside IIS: the module changes
which physical resource or handler actually serves the request, but
the client never finds out -- the URL shown in the browser's address
bar stays exactly what the visitor originally typed or clicked, and
the whole thing happens in a single HTTP round trip, with the client
receiving one response containing the actual content.

A Redirect action is genuinely different at the HTTP level: IIS
sends back a 301 (permanent) or 302 (temporary) response pointing at
a new URL, and the browser -- not IIS -- is the one that then makes
a second, separate request to that new URL. The client's address bar
updates to the new URL, and two full round trips occur: the original
request that received the redirect response, and the follow-up
request the browser made because of it.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the reader understands these aren't just
two configuration options for "changing where a request goes" but
two fundamentally different HTTP behaviors -- one entirely
server-side and invisible to the client, one requiring the client's
own follow-up request and a visible URL change.