A developer needs to store files in an Amazon S3 bucket for a company's application. Each S3 object can have multiple versions. The objects must be permanently removed 1 year after object creation…

Question

Options

• ACreate an S3 Lifecycle rule on the S3 bucket. Configure the rule to expire current versions of
• BCreate an event notification for all object creation events in the S3 bucket. Configure the event
• CCreate an event notification for all object removal events in the S3 bucket. Configure the event
• DCreate an S3 Lifecycle rule on the S3 bucket. Configure the rule to delete expired object delete

• A
  77% (24)
• B
  3% (1)
• C
  6% (2)
• D
  13% (4)

Explanation

Option A is correct because S3 Lifecycle rules are the native, purpose-built mechanism for automating object expiration - you configure the rule to expire current object versions 365 days after creation, and S3 handles permanent deletion automatically without any custom code or external services.

Options B and C are wrong because event notifications are reactive triggers (they fire when something already happens) - they don't enforce retention by themselves; you'd need additional infrastructure like Lambda to act on the notification, making this far more complex than necessary.

Option D is wrong because deleting expired object delete markers is a housekeeping task for cleaning up leftover metadata after versioned objects have already been deleted - it does not expire or remove live object versions.

Memory tip: Think "Lifecycle = scheduled automation, Events = reactive triggers." Whenever an exam question asks about automatically expiring or deleting objects after a time period, reach for a Lifecycle rule - it's S3's built-in scheduler for object management.

No community discussion yet for this question.