Prevent Unintentional S3 File Deletion
A company stores logs in an Amazon S3 bucket. When a data engineer attempts to access several log files, the data engineer discovers that some files have been unintentionally deleted. The data engineer needs a solution that will prevent unintentional file deletion in the future. Which solution will meet this requirement with the LEAST operational overhead?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
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.
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.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
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
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?
Replication copies data but doesn't inherently block deletes unless specifically configured for delete markers, adding complexity and cost compared to simple versioning.
Does enabling versioning increase costs significantly?
Yes, storage costs increase as all versions are stored, but it is the most efficient operational method for preventing data loss from accidental deletions.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →