Prevent Unintentional S3 File Deletion
Short answer
B Enable S3 Versioning for the S3 bucket to retain previous object versions and allow recovery from accidental deletions.
Question
Key Takeaways
The question tests data lifecycle management and accidental deletion prevention; the common trap is choosing complex replication or archiving when simple versioning suffices.
Amazon S3 Versioning is the correct solution to prevent unintentional file deletion with the least operational overhead. It automatically retains multiple versions of objects, allowing recovery without manual backups.
Common mistake: Candidates often choose replication (C) because it provides redundancy, but it adds significant cost and complexity compared to versioning, which is specifically designed for this use case.
Expert Analysis
Why the Answer Is Correct
S3 Versioning (Option B) is the most effective way to protect against unintentional deletions with minimal operational overhead. When enabled, S3 keeps a history of all object versions; if a file is deleted, it is marked as a delete marker rather than being permanently removed, allowing easy restoration. This directly addresses the requirement to prevent permanent loss from accidental actions.
Why the Other Options Are Wrong
Manually backing up (A) requires significant operational effort and does not prevent deletion in real-time. Replication (C) copies data to another bucket/region but does not inherently protect against deletions unless Cross-Region Replication with Delete Marker Replication is explicitly configured, adding unnecessary complexity. Glacier (D) is for long-term archival and does not provide immediate protection against active bucket deletions.
Community Comment Notes
Community consensus strongly supports Option B. As user sdas1 noted, "S3 Versioning keeps multiple versions of an object... ensures that no data is lost permanently due to accidental deletions." While one user mentioned cost concerns regarding logging, versioning remains the standard best practice for this specific scenario in the exam context.
Official Reference
https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked to prevent accidental deletion with 'least operational overhead', always consider S3 Versioning before more complex solutions like replication or external backup systems.
Frequently Asked Questions
Why not use S3 Replication to prevent deletion?
Does enabling versioning increase costs significantly?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 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 4
-
sdas1 👍 3S3 Versioning keeps multiple versions of an object in the same bucket. When you enable versioning, every time an object is overwritten or deleted, a new version of that object is created, and the previous version is retained. This ensures that no data is lost permanently due to accidental deletions or overwrites.
-
0c2d840 👍 1B seems to be the correct answer. But the side effect is, versioning of log files will be expensive as every change to the file will versioned.
-
Bmaster 👍 3B is good..
-
HunkyBunky 👍 2 Answered BB - is right answer
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →