A developer enables versioning on an S3 bucket where each object can have multiple versions. Objects must be permanently removed one year after creation. What should the developer configure next to meet this retention policy?

The correct answer is to create an S3 Lifecycle rule that expires current object versions and permanently deletes noncurrent versions one year after object creation. This directly addresses the requirement for permanent removal of all versions (current and noncurrent) after one year. S3 Lifecycle rules are the native and most efficient way to manage object retention and deletion policies in S3. The option to create an event notification for object creation that triggers a Lambda function is less efficient and more complex than using S3 Lifecycle rules for this specific task. Lambda functions would incur additional cost and management overhead. The option to create an event notification for object removal is incorrect because the goal is to initiate removal, not react to it. The option to create an S3 Lifecycle rule that deletes expired object delete markers and permanently deletes noncurrent versions is incomplete; it doesn't account for the permanent deletion of the current version after one year.