Exercise 3: An Early Move Out of the Cool Tier — Possible Solution
====================================================================

The Cool tier's real minimum recommended retention period is 30 days.
The early deletion penalty applies whenever a blob is deleted,
overwritten, OR moved to a DIFFERENT tier before that minimum period
has elapsed -- this includes moving to a warmer tier, not just
deleting the blob or moving it to an even colder one.

In this scenario, the blob is moved from Cool to Hot after only 12
days -- 18 days short of the real 30-day minimum. Because this is a
move to a different tier before the minimum retention period has
transpired, it counts as an early move under Azure's own real billing
rules.

ANSWER: Yes, this does trigger a real, documented cost consequence.
Moving the blob out of the Cool tier after only 12 days (18 days
before the real 30-day minimum) triggers a prorated early deletion
charge, billed as though the blob had continued being stored in the
Cool tier for the remaining 18 days it didn't actually spend there --
even though the blob wasn't deleted, only moved to a warmer tier.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly recognizes that the early deletion penalty is
triggered by moving to ANY different tier before the minimum
retention period, not only by deletion or moving to a colder tier --
a real, easy-to-miss detail, since "moving to Hot" intuitively sounds
like the opposite of the kind of action that would trigger an early
DELETION charge.