The correct options are Change feed, Soft delete, and Versioning.

Soft delete protects blobs and blob versions from accidental deletion by retaining deleted data for a configurable retention period so administrators can restore deleted items within that window.

Versioning keeps prior versions of a blob when it is overwritten so you can revert to an earlier state and recover data that was changed or replaced.

Change feed provides an ordered, durable log of all blob create, update, and delete events so you can identify which objects changed and when and then use versions and deleted items to reconstruct storage to a past point in time.

Immutability policies are designed for compliance and retention by preventing modification or deletion of data but they do not provide the operational point in time restore workflow needed to recover overwritten blobs.

Object replication copies blobs between storage accounts for disaster recovery or data distribution but it does not maintain historical versions or a change log that lets you restore all objects to a prior point in time.

Snapshots are per-blob read only copies and can be used for manual recovery in some scenarios but they are not part of the automated point in time restore capability and are largely superseded by versioning for this purpose.

Full AWS Practitioner Certification Question