AZ-204 practice question 28 of 35

You are developing an Azure Service application that processes queue data when it receives a message from a mobile application. Messages may not be…

Domain Develop Azure compute solutions

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?

Answer options

A: Yes

B: No Correct answer

Correct Answer:

B. No

Explanation

The proposed solution does not meet all the specified requirements. While Azure Storage Queues can handle a size of 80 GB and are a cost-effective option, they do not guarantee First-In, First-Out (FIFO) message ordering. The official documentation states that message order is not guaranteed. For strict FIFO ordering, Azure Service Bus Queues with messaging sessions are the appropriate service. Since the solution fails to meet the mandatory FIFO requirement, it is incorrect.

Why Incorrect

A. Yes: This is incorrect because the solution uses Azure Storage Queues, which do not provide the guaranteed FIFO ordering mandated by the requirements.

References

1. Microsoft Docs. (2023). Compare Azure Queues and Service Bus queues. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted.

Reference Point: In the "Feature comparison" table, under the "Ordering" row, it explicitly states "Not supported" for Storage Queues, clarifying that messages can be retrieved out of order. For Service Bus Queues, it states "First-In, First-Out (FIFO)" is guaranteed when using messaging sessions.

2. Microsoft Docs. (2023). Message sessions. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/service-bus-messaging/message-sessions.

Reference Point: The first paragraph states, "Microsoft Azure Service Bus sessions enable joint and ordered handling of unbounded sequences of related messages. Sessions can be used in first in, first out (FIFO) and request-response patterns."

3. Microsoft Docs. (2023). Scalability and performance targets for standard storage accounts. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/storage/common/scalability-and-performance-targets-for-storage-accounts.

Reference Point: The table "Scale targets for standard storage accounts" shows the "Total storage account capacity" is 5 PiB, which is far greater than the 80 GB requirement. This confirms the size requirement is met by Storage Queues.

Keep practicing

Take the free AZ-204 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test