Implementing Azure Service Bus Queue with FIFO Ordering for Message Processing
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 Function App that uses an Azure Service Bus Queue trigger.
Does the solution meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.A.
You can create a function that is triggered when messages are submitted to an Azure Storage queue.
https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-storage-queue-triggered-functionThe given solution does partially meet the stated requirements, but it does not completely meet all of the requirements.
Firstly, the solution does ensure that messages are added to an Azure Service Bus Queue in a FIFO order, which meets the requirement of using first-in-first-out (FIFO) ordering of messages.
However, the solution does not address the requirement of ensuring that the queue size does not grow larger than 80 GB. It is possible that messages may continue to be added to the queue, causing it to grow beyond the specified limit. Additionally, the solution does not specify how to handle messages that exceed the maximum queue size limit.
In addition, the solution proposes using an Azure Function App that uses an Azure Service Bus Queue trigger, but it does not provide any further details on how the function will process the messages or how it will minimize Azure costs.
Therefore, the solution does not completely meet all of the stated requirements, and the answer is B. No.
To fully meet the requirements, additional steps would need to be taken such as implementing a mechanism to monitor the queue size and take appropriate actions when the size exceeds the specified limit, such as deleting the oldest messages or sending an alert. Additionally, strategies to optimize the Azure costs associated with using the service bus and function app would need to be considered, such as using auto-scaling, adjusting message retention periods, and optimizing code for performance.
