S3 versioning in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when you delete an object in a versioned S3 bucket?

You have enabled versioning on an S3 bucket. You delete an object named photo.jpg. What is the state of the object after deletion?

A A delete marker is added, hiding the latest version but previous versions remain accessible.

B The object is archived to Glacier automatically.

C The object is copied to a backup bucket before deletion.

D The object is permanently removed and cannot be recovered.

💡 Hint

Think about how versioning protects data from permanent deletion.

When versioning is enabled, deleting an object adds a delete marker. This hides the current version but keeps all previous versions intact and recoverable.

❓ Architecture

intermediate

How to configure S3 versioning for data protection in a multi-region setup?

You want to protect your data in an S3 bucket with versioning and replicate all versions to another region. Which AWS feature must you enable alongside versioning?

A Enable S3 Transfer Acceleration to speed up replication.

B Use Lifecycle policies to move versions to Glacier.

C Enable Cross-Region Replication (CRR) with versioning enabled on both buckets.

D Enable S3 Event Notifications to trigger Lambda for copying objects.

💡 Hint

Replication of versions requires a specific S3 feature that works with versioning.

Cross-Region Replication (CRR) replicates all versions of objects automatically between buckets in different regions when versioning is enabled on both.

❓ security

advanced

What is the effect of disabling versioning on an existing versioned S3 bucket?

You have a versioned S3 bucket with many object versions. You disable versioning on this bucket. What happens to the existing versions and new uploads?

A All existing versions are deleted immediately, and new uploads create versions.

B Existing versions remain, but new uploads overwrite objects without creating versions.

C Versioning is paused; new uploads create delete markers instead of versions.

D Existing versions are archived, and new uploads are rejected until versioning is re-enabled.

💡 Hint

Consider what disabling versioning means for existing data and future uploads.

Disabling versioning stops new versions from being created, but all existing versions remain intact and accessible.

✅ Best Practice

advanced

How to minimize storage costs while using S3 versioning for critical data?

You use S3 versioning to protect critical data but want to reduce storage costs over time. Which approach is best?

A Apply Lifecycle rules to transition non-current versions to cheaper storage classes like Glacier.

B Manually delete old versions every month to save space.

C Disable versioning and rely on backups instead.

D Use S3 Transfer Acceleration to reduce storage costs.

💡 Hint

Think about automated ways to manage old versions cost-effectively.

Lifecycle rules can automatically move older versions to cheaper storage classes, reducing costs while keeping data protected.

🧠 Conceptual

expert

What is the total number of object versions after these operations in a versioned S3 bucket?

In a versioned S3 bucket, you perform these steps on an object named report.pdf:

1. Upload report.pdf (version 1)
2. Upload a new report.pdf (version 2)
3. Delete report.pdf
4. Upload report.pdf again (version 3)

How many versions (including delete markers) exist for report.pdf now?

A 2 versions

B 3 versions

C 5 versions

D 4 versions

💡 Hint

Remember that deleting adds a delete marker version.

There are 3 uploads (versions 1, 2, and 3) plus 1 delete marker from the delete operation, totaling 4 versions.