A county publishes a meter-data retention schedule: keep objects online for three years, then move them to Glacier storage classes, then expire them. How should the architect enforce that policy automatically in S3?
Select an answer to reveal the explanation.
Short Explanation
Retention schedules should run on autopilot. S3 Lifecycle rules age meter data from hot storage to Glacier and then expire it—no calendar reminders. Transfer Acceleration speeds uploads; it does not enforce how long you keep files.
Full Explanation
S3 Lifecycle configuration encodes retention by transitioning objects between storage classes and expiring them after defined periods. Manual anniversary moves and monitoring-only alarms do not reliably enforce policy. Transfer Acceleration optimizes transfer performance and is unrelated to retention enforcement.