A company wants to protect data stored in Amazon S3 from accidental deletion.

Comprehensive and Detailed Explanation From AWS Cloud Documentation:

Enabling S3 Versioning is the customer action that protects Amazon S3 objects from many accidental deletions and overwrites. Versioning keeps multiple variants of an object in the same bucket. When a user deletes a versioned object without specifying a version ID, Amazon S3 normally adds a delete marker instead of permanently removing all prior versions, allowing an earlier version to be recovered. It also preserves prior versions when an object is overwritten. Because the customer chooses the bucket configuration and enables versioning, option D is correct under the shared responsibility model. AWS is responsible for operating and patching the underlying S3 service, maintaining the physical storage infrastructure, and providing the designed durability of the service, so options A, B, and C are not customer tasks. Versioning should still be combined with appropriate IAM permissions, lifecycle rules, backups or replication where required, and possibly S3 Object Lock or MFA Delete for stronger protection. The central exam point is that AWS operates S3, while the customer configures data-protection features for the customer’s buckets and objects.