S3 Glacier Vault Lock for WORM Compliance
Short answer
C S3 Glacier Vault Lock enforces a write-once, read-many model to ensure archived documents remain immutable for compliance.
Question
Key Takeaways
The exam tests knowledge of specific AWS storage controls; the common trap is confusing general access policies or versioning with actual WORM enforcement mechanisms.
This question tests the identification of Amazon S3 features that enforce Write-Once, Read-Many (WORM) compliance. S3 Glacier Vault Lock is the correct solution for ensuring data immutability.
Common mistake: Learners often select S3 Versioning, assuming it prevents deletion, but versioning allows new versions to be created and old ones deleted unless combined with other strict policies.
Expert Analysis
Why the Answer Is Correct
S3 Glacier Vault Lock provides a WORM (Write Once, Read Many) model by allowing you to set a vault lock policy that cannot be changed once deployed. This ensures that archived documents cannot be modified or deleted for a specified retention period, satisfying legal and compliance obligations.
Why the Other Options Are Wrong
S3 Versioning maintains multiple copies of an object but does not inherently prevent deletion or modification of existing versions. S3 bucket policies control access permissions but do not enforce immutability on their own. MFA Delete adds a security layer for deletions but does not provide the write-once guarantee required for compliance archives.
Community Comment Notes
The community consensus strongly supports C. Users like Supercell and Kilobay1 note that Glacier Vault Lock specifically enforces the WORM model for regulatory compliance. While one user suggested bucket policy, it lacks the immutable locking feature provided by Vault Lock.
Exam Strategy
When asked about 'immutable' or 'compliance' storage, look for services designed for long-term archiving like Glacier with Lock features. Distinguish between access control (policies) and data integrity/enforcement (Vault Lock).
Frequently Asked Questions
Why isn't S3 Versioning sufficient for WORM?
Can I use S3 Object Lock instead?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
Supercell 👍 3 Answered CBy using S3 Glacier Vault Lock, the company can ensure that its archived documents are stored in a write-once, read-many (WORM) model, meeting legal and compliance obligations that require data immutability and retention for a specified period or indefinitely.
-
Kilobay1 👍 2 Answered CS3 Glacier Vault Lock provides the ability to lock your Glacier vaults to enforce WORM protection. Once a vault is locked with a retention policy, data cannot be modified or deleted for the specified retention period, ensuring compliance with regulatory requirements for write-once, read-many storage. This feature is specifically designed to meet compliance and regulatory requirements for immutable data storage.
-
Karpovsky2222 👍 2The right answer is S3 bucket policy
-
alokdixit2006 👍 1 Answered CS3 Glacier Vault Lock allows you to enforce compliance controls on your archived data in Glacier, ensuring data is stored in a "write once, read many" (WORM) manner, meaning it cannot be modified or deleted within a predefined period
-
ShaiTay 👍 1 Answered CC. S3 Glacier Vault Lock
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →