Implementing Messaging Solution with Azure Storage Queue and .Net API for Azure Service Application | AZ-204 Exam Solution
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 Storage Queue from the mobile application.
Create an Azure Function App that uses an Azure Storage Queue trigger.
Does the solution meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.B.
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 provided solution meets the stated requirements. Here's why:
The solution proposes using an Azure Storage Queue to receive messages from a mobile application, which is a valid option for implementing a messaging solution in Azure. Using a queue helps to decouple the processing of messages from the mobile application, which can continue to send messages without being blocked by processing delays.
The .Net API can be used to add messages to the Azure Storage Queue from the mobile application. This can be done using a REST API or a client library, such as the Azure.Storage.Queues NuGet package. The message can include any data that needs to be processed by the service application.
To process messages from the queue, the solution proposes using an Azure Function App with an Azure Storage Queue trigger. This is a cost-effective approach, as Azure Functions are billed based on the number of executions and the amount of resources used. By using a trigger, the function is automatically executed when a new message is added to the queue.
The FIFO ordering of messages is maintained by the Azure Storage Queue service itself, which guarantees that the oldest message in the queue is processed first. This is suitable for scenarios where the order of processing is important.
Finally, the requirement to limit the size of the queue to 80 GB is also met by using Azure Storage Queue, as the maximum size of a single queue is 500 TB. This ensures that the application can continue to receive messages without running out of storage space.
Therefore, the solution meets all the stated requirements, and the answer is A. Yes.
