You need to design a real-time stream solution that uses Azure Functions to process data uploaded to Azure Blob Storage.
The solution must meet the following requirements:
Support up to 1 million blobs.
✑ Scaling must occur automatically.
✑ Costs must be minimized.
What should you recommend?
To design a real-time stream solution using Azure Functions that can support up to 1 million blobs, automatically scale, and minimize costs, it is best to deploy the Azure Function in a Consumption plan and use an Event Grid trigger. The Consumption plan provides dynamic scaling based on the workload, ensuring cost efficiency by charging only for the execution time of the functions. The Event Grid trigger is more suited for handling a high volume of events, like processing up to 1 million blobs, and provides near real-time processing by triggering functions directly from events, ensuring scalability and reliability.
The solution is B - Deploy the Azure Function in a Consumption plan and use an Event Grid trigger. 1M blobs will cripple the ability of blob trigger to provide the events. The EventGrid trigger is instantaneous, so it depends on your needs.
you're right In addition, storage logs are created on a "best effort" basis. There's no guarantee that all events are captured. Under some conditions, logs may be missed. If you require faster or more reliable blob processing, consider creating a queue message when you create the blob. Then use a queue trigger instead of a blob trigger to process the blob. Another option is to use Event Grid; see the tutorial Automate resizing uploaded images using Event Grid. https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=csharp
Because it's a real time processing, it has to be appservice plan THE CORRECT ANSWER IS D
I would say it is B as because of thee High number of blobs that can land it has to be definitely an Event Grid Trigger (See https://docs.microsoft.com/es-es/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=csharp#alternatives). Also, due to cost minimized, it should be a consumption plan. Even being a consumption plan the trigger delay will be minimum and fit to the conditions. However if you have a service plan you have to had the resources needed allocated even if you are using them or not.
I would say it is B as because of thee High number of blobs that can land it has to be definitely an Event Grid Trigger (See https://docs.microsoft.com/es-es/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=csharp#alternatives). Also, due to cost minimized, it should be a consumption plan. Even being a consumption plan the trigger delay will be minimum and fit to the conditions. However if you have a service plan you have to had the resources needed allocated even if you are using them or not.
Because it's a real time processing, it has to be appservice plan THE CORRECT ANSWER IS D
I would say it is B as because of thee High number of blobs that can land it has to be definitely an Event Grid Trigger (See https://docs.microsoft.com/es-es/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=csharp#alternatives). Also, due to cost minimized, it should be a consumption plan. Even being a consumption plan the trigger delay will be minimum and fit to the conditions. However if you have a service plan you have to had the resources needed allocated even if you are using them or not.
I would say it is B as because of thee High number of blobs that can land it has to be definitely an Event Grid Trigger (See https://docs.microsoft.com/es-es/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=csharp#alternatives). Also, due to cost minimized, it should be a consumption plan. Even being a consumption plan the trigger delay will be minimum and fit to the conditions. However if you have a service plan you have to had the resources needed allocated even if you are using them or not.
https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=csharp#alternatives
High-scale: High scale can be loosely defined as containers that have more than 100,000 blobs in them or storage accounts that have more than 100 blob updates per second.
B. Deploy the Azure Function in a Consumption plan and use an Event Grid trigger.
The requirement is leading to the answer below as it was focusing to minimize cost. B. Deploy the Azure Function in a Consumption plan and use an Event Grid trigger. Reference: https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale
It doesn't say you have to minimize latency.
real-time = minimize latency