Change feed
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed
Change feed support is well-suited for scenarios that process data based on objects that have changed. For example, applications can:
- Update a secondary index, synchronize with a cache, search-engine, or any other content-management scenarios.
Change Feed, https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed?tabs=azure-portal, ... change feed is well suited for ... sychronizing with a cache
The feature in Azure Blob Storage that enables you to sync a Blob Storage account to an external cache is called "Azure Blob Storage on Edge." Azure Blob Storage on Edge extends the capabilities of Azure Blob Storage by providing a distributed caching solution that enables you to replicate blobs from a centralized Blob Storage account to edge locations closer to your applications or end-users.
'Azure Blob Storage on Edge' uses Azure Blob Storage's "change feed" functionality to detect changes to blobs in the centralized Blob Storage account and replicate those changes to the edge cache.
23rd mars 2023,
response from CHATGPT:
The correct answer is not listed in the options provided.
Azure Blob Storage does not have a built-in feature that enables you to sync a Blob Storage account to an external cache. However, you can use a caching solution such as Azure Blob Cache or Redis Cache to achieve this functionality.
Agree with Azure Blob Cache or Redis Cache.
Just as an FYI, ChatGPT (inside of Bing Chat) could be hallucinating.
When asked "Can't the Change Feed feature in Azure Blob storage enable the synch to an external cache?" the response is .."Yes, the Change Feed feature in Azure Blob storage can enable the synchronization to an external cache" with a reference to this link to Change feed (https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed?tabs=azure-portal), that has nothing mentioned about synching Blob storage to an external cache.
Change feed support is well-suited for scenarios that process data based on objects that have changed. For example, applications can:
Update a secondary index, synchronize with a cache, search-engine, or any other content-management scenarios.
Extract business analytics insights and metrics, based on changes that occur to your objects, either in a streaming manner or batched mode.
Store, audit, and analyze changes to your objects, over any period of time, for security, compliance or intelligence for enterprise data management.
Build solutions to backup, mirror, or replicate object state in your account for disaster management or compliance.
Build connected application pipelines that react to change events or schedule executions based on created or changed object.
The correct answer is A. the Hot access tier.
The Hot access tier in Azure Blob Storage is designed for frequently accessed data that requires low latency and high throughput. One of the features of the Hot access tier is the ability to enable geo-replication, which allows you to sync a Blob Storage account to an external cache. This can improve the performance of read-heavy workloads by reducing the latency of data access.
Change feed, snapshots, and versioning are other features of Azure Blob Storage, but they do not provide the ability to sync a Blob Storage account to an external cache. Change feed provides a way to receive notifications when new or updated blobs are added to a container, snapshots allow you to create point-in-time backups of your data, and versioning allows you to keep multiple versions of a blob.
Regenerate response
The Azure Blob Storage feature that enables you to sync a Blob Storage account to an external cache is Azure File Sync.
Snapshots, versioning, change feed and hot access tier are other features but are not related to syncing a Blob Storage account to an external cache.
Snapshots are read-only copies of a blob that you can use to back up and restore data.
Versioning maintains multiple versions of an object in a container.
Change feed is a feature that allows you to track changes to blobs in a container.
Hot access tier allows you to store frequently accessed data at a lower storage cost.
to add on
The purpose of the change feed is to provide transaction logs of all the changes that occur to the blobs and the blob metadata in your storage account. The change feed provides ordered, guaranteed, durable, immutable, read-only log of these changes. Client applications can read these logs at any time, either in streaming or in batch mode. The change feed enables you to build efficient and scalable solutions that process change events that occur in your Blob Storage account at a low cost.
https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed?tabs=azure-portal
This section is not available anymore. Please use the main Exam Page.DP-900 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
jellybiscuit
Highly Voted 2 years, 8 months agomsapi7
Highly Voted 2 years, 7 months agoYomzie
Most Recent 1 year, 2 months agojxs221
1 year, 2 months agowenny0501
2 years, 1 month agosrgopalkr
1 year, 9 months agosrgopalkr
1 year, 9 months agotangerine141
2 years, 1 month agoAzurre
2 years, 1 month agotangerine141
2 years, 1 month agoStuurwiel1
2 years, 3 months agoreza88
2 years, 6 months agoJA2018
2 years, 7 months agoJA2018
2 years, 6 months agoKermedi2018
2 years, 7 months agoKermedi2018
2 years, 7 months agocjemaiorano
2 years, 7 months ago