A library consortium must keep contested digital records immutable for a court-mandated retention period, including protection against privileged deletion. Which S3 control best meets a WORM-style legal hold requirement?
Select an answer to reveal the explanation.
Short Explanation
Think bank safe, not sticky note: Object Lock in Compliance mode is WORM for S3—nobody, not even root-style privilege, casually deletes during retention. Versioning helps history; it is not the same as locked immutability. Public-read is the opposite of a legal hold.
Full Explanation
S3 Object Lock, especially Compliance mode, enforces write-once-read-many retention so objects cannot be overwritten or deleted by any user during the retention period. Versioning alone and Intelligent-Tiering do not provide WORM legal-hold guarantees. Making the bucket public increases exposure rather than protecting contested records.