Exercise 2: The Overlooked Second Eviction Reason — Possible Solution
====================================================================

Azure Spot VMs can be evicted for two real, genuinely distinct
reasons, not just one. The team's own expectation -- "we'll only lose
the VM if Azure runs out of capacity" -- only accounts for the first
real reason, capacity-based eviction.

The second, genuinely Azure-specific reason is price-based eviction:
if the real current Spot market price for that VM size rises above
the maximum price the team themselves configured, the VM is evicted
regardless of whether capacity is actually available. The scenario
describes the team setting their own maximum price WELL BELOW the
current market rate -- meaning even a modest real price increase
could push the actual Spot price above their own configured ceiling,
triggering an eviction that has nothing to do with Azure's own
available capacity at all.

ANSWER: The overlooked reason is price-based eviction. Because the
team set their own maximum price well below the current market rate,
a real, even moderate rise in the Spot price could exceed their own
ceiling and evict the VM -- independent of whether Azure has spare
capacity -- which they may not have planned for if they were only
expecting capacity-driven evictions.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly identifies that setting a low maximum price actually
INCREASES real exposure to price-based eviction specifically (a
counterintuitive but real consequence of how the mechanism works),
rather than just naming "price-based eviction" as a fact without
connecting it to why the team's own specific configuration choice
made this risk more, not less, likely.