DRAG DROP
You are developing an Azure solution to collect inventory data from thousands of stores located around the world. Each
store location will send the inventory data hourly to an Azure Blob storage account for processing.
The solution must meet the following requirements:
Begin processing when data is saved to Azure Blob storage.
Filter data based on store location information.
Trigger an Azure Logic App to process the data for output to Azure Cosmos DB.
Enable high availability and geographic distribution.
Allow 24-hours for retries.
Implement an exponential back off data processing.
You need to configure the solution.
What should you implement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Select and Place:
Explanation:
Box 1: Azure Event Grid
Blob storage events are pushed using Azure Event Grid to subscribers such as Azure Functions, Azure Logic Apps, or even
to your own http listener. Event Grid provides reliable event delivery to your applications through rich retry policies and dead-
lettering.
Box 2: Azure Logic App
Event Grid uses event subscriptions to route event messages to subscribers. This image illustrates the relationship between
event publishers, event subscriptions, and event handlers.
Box 3: Azure Service Bus
The Event Grid service doesn't store events. Instead, events are stored in the Event Handlers, including ServiceBus,
EventHubs, Storage Queue, WebHook endpoint, or many other supported Azure Services.
Reference: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-event-overview https://docs.microsoft.com/en-
us/java/api/overview/azure/messaging-eventgrid-readme
Should be this:
Event Source: Azure Blob Storage
Event Receiver: Azure Event Grid
Event Handler: Azure Logic App
Event Source: Azure Blob Storage.
The inventory data from each store location is sent to an Azure Blob storage account. This is where the data originates, making it the event source.
Event Receiver: Azure Event Grid.
Azure Event Grid is a service that routes events based on event sources to event handlers. In this case, it would be used to trigger the processing of data when it's saved to Azure Blob Storage (based on Blob Storage events), making it the event receiver.
Event Handler: Azure Logic App.
The requirement is to trigger an Azure Logic App to process the data for output to Azure Cosmos DB. This makes the Azure Logic App the event handler, as it's the service that responds to the event.