Implementing Messaging Solution for Azure Service Application
Question
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 Service Bus Queue from the mobile application.
Create an Azure Windows VM that is triggered from Azure Service Bus Queue.
Does the solution meet the goal?
Answers
Explanations
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 does not fully meet the requirements as stated. While using the .Net API to add a message to an Azure Service Bus Queue from the mobile application is a valid approach for sending messages, the solution does not address the requirement for FIFO ordering of messages, nor does it prevent the queue size from growing larger than 80 GB.
Creating an Azure Windows VM that is triggered from the Azure Service Bus Queue could potentially allow for FIFO ordering of messages, but it also introduces additional costs and complexity. Additionally, this approach does not necessarily address the requirement to prevent the queue size from growing larger than 80 GB.
To fully meet the requirements, a more comprehensive solution may include implementing message batching to reduce the number of requests to the queue, setting up auto-scaling to dynamically adjust the number of instances processing the queue based on the queue size and message rate, and using Azure Queue Storage to automatically handle the scaling and FIFO ordering of messages while also enforcing the queue size limit.
Therefore, the answer to the question is B. No, the proposed solution does not fully meet the stated goals.
