You store globally distributed data in multiple Azure Blob Storage containers, enabled blob versioning and soft delete, and need the ability to restore blob data to a previous day for testing. How should you configure the storage account to support point-in-time restore?

Enabling the change feed on the storage account is the correct approach for point-in-time restore. The change feed provides a durable, ordered, read-only log of all changes that occur to blobs in your storage account. This log allows you to reconstruct the state of a blob or container at any point in time, which is essential for point-in-time restore scenarios. Object replication copies blobs to a destination account, primarily for disaster recovery or data locality, not for point-in-time restore within the same account. Creating a snapshot of a blob captures its state at a specific moment, but managing numerous snapshots for a daily restore across many containers would be cumbersome and inefficient compared to the change feed. Configuring an immutability policy prevents accidental deletion or modification for a specified period, which is a data retention strategy, not a mechanism for restoring to a previous state.