Exam AWS Certified SysOps Administrator - Associate topic 1 question 212 discussion

B. Compliance mode is required for this situation. Comparison and reference below: https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-overview.html In governance mode, users can't overwrite or delete an object version or alter its lock settings unless they have special permissions. With governance mode, you protect objects against being deleted by most users, but you can still grant some users permission to alter the retention settings or delete the object if necessary. You can also use governance mode to test retention-period settings before creating a compliance-mode retention period. In compliance mode, a protected object version can't be overwritten or deleted by any user, including the root user in your AWS account. When an object is locked in compliance mode, its retention mode can't be changed, and its retention period can't be shortened. Compliance mode helps ensure that an object version can't be overwritten or deleted for the duration of the retention period.

Answer is B, governance mode allows some users to delete/modify the data

Nobody on customer side including root can delete objects before they expire (unless maybe if you delete the entire account). I do know there is a "force" option for deleting buckets with existing objects. Would be interesting to see if that would do it. I"m sure Amazon can always delete files if they have to (and customer insisted they do it).

B The S3 Object Lock feature in compliance mode can be used to enforce a retention period for objects in the bucket. This ensures that the backups are protected from deletion for at least 3 months after they are created, which meets the requirement. The retention period can be set at the bucket level, or at the object level.