AWS Certified SysOps Administrator Practice Exam

What is a consequence of enabling S3 versioning on a bucket?

1. You cannot delete objects in the bucket

2. Costs may increase due to multiple versions being stored

3. Data archiving becomes mandatory

4. Access controls must be revisited

The correct answer is: Costs may increase due to multiple versions being stored

Enabling S3 versioning on a bucket allows you to maintain multiple versions of an object whenever it is modified or deleted. Each version of the object is stored as a separate entity within the same bucket, which can significantly impact storage costs. This is because every version of an object, including those created through updates and deletion actions, occupies storage space. Consequently, as more versions accumulate over time, the total cost associated with storage will increase due to the additional storage requirements for these multiple versions. While it may be true that you can still delete objects in a versioned bucket, doing so might not erase all versions, leading to potential confusion and the storage of many obsolete versions. Therefore, while the idea of revisiting access controls and the potential implications of mandatory data archiving could be relevant in a broader context, these do not directly illustrate the financial consequence. Thus, the clear and immediate consequence of enabling versioning is the potential increase in costs associated with storing multiple versions of objects.