Enable Change Feed for Blob Storage Point-in-Time Restore
Short answer
A Enable the change feed on the storage account to begin capturing and recording changes for point-in-time restore.
Question
Key Takeaways
Point-in-time restore relies on the blob change feed to track modifications over time; without it, the storage account cannot revert to a previous state.
To configure an Azure Blob Storage account for point-in-time restore, you must enable the change feed to capture modifications. This page confirms that enabling the change feed is the required step when versioning and soft delete are already active.
Common mistake: Choosing to create a snapshot (Option C) is a common mistake because snapshots capture a single blob's state manually, whereas point-in-time restore uses the change feed to automatically revert entire containers or accounts to a previous state.
Expert Analysis
Why the Answer Is Correct
Point-in-time restore for Azure Blob Storage allows you to restore data to its state at a previous point in time. To support this feature, the storage account must have blob versioning, soft delete, and the change feed enabled. Since versioning and soft delete are already enabled in the scenario, enabling the change feed (Option A) is the necessary step to begin capturing and recording changes, which makes point-in-time restore possible.Why the Other Options Are Wrong
Option B is incorrect because object replication asynchronously copies blobs between storage accounts and does not facilitate point-in-time restore. Option C is incorrect because creating a snapshot captures a single blob's state at a specific moment, but point-in-time restore operates at the container or account level using the change feed, not individual snapshots. Option D is incorrect because an immutability policy protects data from deletion or modification for a retention period, which actually prevents restore operations that need to overwrite or delete current data.Community Comment Notes
Several users correctly identified that enabling the change feed is required, with one noting the Microsoft documentation explicitly lists it as a prerequisite. Another user incorrectly suggested creating a snapshot, misunderstanding that point-in-time restore relies on the change feed rather than manual snapshots.Official Reference
https://learn.microsoft.com/en-us/azure/storage/blobs/point-in-time-restore-overview
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked about Azure Blob Storage point-in-time restore prerequisites, remember the three mandatory features: blob versioning, soft delete, and the change feed. If any of these are missing in the scenario, enabling the absent feature is the correct action.
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
KeithSh 👍 3Looks like the answer is correct. https://learn.microsoft.com/en-us/azure/storage/blobs/point-in-time-restore-manage?tabs=portal#enable-and-configure-point-in-time-restore
-
mahomes15 👍 1Given the need for point-in-time restore and the capabilities of the options: Correct Answer: C. Create a snapshot of the blob in the hot tier. Reasoning: Creating a snapshot allows you to capture the current state of the blob and restore it later, which meets the requirement of restoring to a previous day for testing.
-
Vichu_1607 👍 1 Answered AA. Enable the change feed on the storage account to begin capturing and recording changes.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.