Exercise 1: A Lifecycle Policy for 7-Year Compliance Records — Possible Solution
====================================================================

The data described has two distinct real phases: an initial period
(the first 90 days) where it might genuinely still be accessed, and a
long remaining period (90 days through 7 years) where it must legally
be kept but is almost never actually read.

A real, reasonable lifecycle policy:

  Days 0-90:    S3 Standard (or Standard-IA, if it's rarely read even
                in this window) -- fast, immediate access while it's
                still plausibly needed.

  Day 90:       Transition to S3 Glacier Flexible Retrieval (or
                Glacier Deep Archive, if retrieval speed genuinely
                doesn't matter) -- the compliance requirement is
                "must be retrievable," not "must be retrievable
                instantly," and this tier is dramatically cheaper for
                data that's essentially never read.

  Year 7:       Expire (delete) the objects entirely -- once the
                legal retention period has passed, there's no
                remaining reason to keep paying to store them.

ANSWER: Standard (or Standard-IA) for the first 90 days, transitioning
to a Glacier tier (Flexible Retrieval or Deep Archive, depending on
how tolerant the compliance need is of a multi-hour retrieval delay)
from day 90 onward, with automatic expiration at the 7-year mark.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly reads the two real, distinct requirements in the
scenario -- a genuine access window followed by a long, rarely-touched
retention period, with a hard legal expiration -- and maps each phase
to the specific storage class in the chapter's own table best suited
to it, rather than defaulting to one class for the whole 7 years.