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 are developing an Azure Service application that processes queue data when it receives a message from a mobile application.
Messages may not be sent to the service consistently.
You have the following requirements: -> Queue size must not grow larger than 80 gigabytes (GB)
-> Use first-in-first-out (FIFO) ordering of messages.
-> Minimize Azure costs.
You need to implement the messaging solution.
Solution: Use the .Net API to add a message to an Azure Storage Queue from the mobile application.
Create an Azure VM that is triggered from Azure Storage Queue events.
Does the solution meet the goal?
Click on the arrows to vote for the correct answer
A. B.B.
Don't use a VM, instead create an Azure Function App that uses an Azure Service Bus Queue trigger.
https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-storage-queue-triggered-functionThe proposed solution suggests using the .NET API to add a message to an Azure Storage Queue from the mobile application and creating an Azure VM that is triggered from Azure Storage Queue events to process the messages.
This solution does meet the requirement of using Azure Storage Queue as a message queue. The first-in-first-out (FIFO) requirement is also met since Azure Storage Queue supports FIFO ordering of messages by default.
However, the solution does not address the requirement to limit the queue size to 80 GB. It is possible that the queue could grow larger than 80 GB if the rate of incoming messages exceeds the rate at which messages are processed. Therefore, this solution does not fully meet the stated goal.
Regarding cost, it is unclear how the proposed solution will minimize Azure costs. While using Azure Storage Queue is a cost-effective way to implement a message queue, creating an Azure VM can add additional cost. It would depend on the size and type of VM selected, as well as the amount of data processed.
In conclusion, the proposed solution meets some of the requirements but does not fully meet all of them. Therefore, the answer is B. No.