App1 uploads a cumulative transaction log named File1.txt to a block blob in container app1data once per hour; File1.txt contains only the current day's transactions. You must be able to restore the most recent uploaded version of File1.txt from any previous day for up to 30 days after it was overwritten, while minimizing storage usage. What feature should you enable?

Blob versioning is the correct choice because it automatically saves the previous state of a blob each time it's overwritten or deleted, allowing you to restore any past version. This directly addresses the requirement to restore the most recent uploaded version from any previous day for up to 30 days. Container soft delete protects entire containers from accidental deletion, not individual blob versions. Blob snapshots create point-in-time read-only copies, but they are manual or require automation, and managing many snapshots for daily versions can be less efficient than versioning. Blob soft delete protects deleted blobs for a specified retention period, but it doesn't automatically save previous versions when a blob is overwritten, only when it's explicitly deleted.