Note: This question is part of a series of questions that present the same scenario.
Each question in the series contains a unique solution that might meet the stated goals.
Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it.
As a result, these questions will not appear in the review screen.
You develop a software as a service (SaaS) offering to manage photographs.
Users upload photos to a web service which then stores the photos in Azure Storage Blob storage.
The storage account type is General-purpose V2
When photos are uploaded, they must be processed to produce and save a mobile-friendly version of the image.
The process to produce a mobile-friendly version of the image must start in less than one minute.
You need to design the process that starts the photo processing.
Solution: Move photo processing to an Azure Function triggered from the blob upload.
Does the solution meet the goal?
Click on the arrows to vote for the correct answer
A. B.A.
Azure Storage events allow applications to react to events.
Common Blob storage event scenarios include image or video processing, search indexing, or any file- oriented workflow.
Events are pushed using Azure Event Grid to subscribers such as Azure Functions, Azure Logic Apps, or even to your own http listener.
Note: Only storage accounts of kind StorageV2 (general purpose v2) and BlobStorage support event integration.
Storage (general purpose v1) does not support integration with Event Grid.
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-event-overviewYes, the solution meets the goal.
The proposed solution suggests using an Azure Function triggered by the blob upload to initiate the photo processing. This approach is valid because Azure Functions can be configured to automatically execute a code snippet in response to events, such as the creation of a new blob in Azure Storage.
By using an Azure Function, the photo processing can start within a minute of the blob upload, as required by the goal. Azure Functions can be configured to start executing code very quickly, even within a few milliseconds of the triggering event.
Furthermore, using an Azure Function for the photo processing allows for greater scalability and flexibility. The Azure Function can be configured to scale automatically to meet the processing demands of the uploaded photos, without requiring any manual intervention. Additionally, Azure Functions can be written in a variety of programming languages, allowing for flexibility in the implementation of the photo processing logic.
Overall, using an Azure Function triggered from the blob upload is a valid and efficient solution for achieving the goal of starting the photo processing within a minute.