Challenge 1: Does Rapid-Fail Protection Trigger at 6 Crashes in 4
Minutes? — Solution Walkthrough

The answer: Yes, Rapid-Fail Protection triggers, and the Application
Pool is taken offline.

Why:

The default thresholds are rapidFailProtectionMaxCrashes="5" and
rapidFailProtectionInterval="00:05:00" (5 minutes) -- meaning IIS
trips the circuit breaker once a pool's worker process crashes MORE
than 5 times within any 5-minute window. In this scenario, the pool
crashed 6 times within a 4-minute window -- both conditions are
satisfied: 6 crashes exceeds the max-crashes threshold of 5, and the
4-minute window in which they happened is within (shorter than) the
5-minute interval being measured. Since both the crash count and the
timing condition are met, IIS takes the entire Application Pool
offline, returning 503 Service Unavailable to every request against
it, rather than continuing to restart a repeatedly-crashing worker
process.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the reader can apply both real default
numbers (5 crashes, 5-minute window) together to a concrete scenario,
rather than just remembering that Rapid-Fail Protection exists in the
abstract -- correctly recognizing that 6 crashes in a SHORTER window
than the threshold clearly satisfies the trigger condition.