Exam AZ-305 topic 4 question 65 discussion

There are 15 variations of this question, each offerings different answers. In all 15 questions, there is always only one out of two answers: either its Azure Queue Storage or its Azure Service Bus. I havent seen a question where both of them are a possibility.

Azure Queue Storage is the correct answer

C is correct Azure Queue Storage or Azure Service Bus

Azure Queue Storage is designed for large-scale, asynchronous messaging between application components. It allows you to store large numbers of messages that can be accessed from anywhere via authenticated calls using HTTP or HTTPS. It supports decoupling different components of a transaction, enabling them to communicate asynchronously by placing messages in a queue. This makes it suitable for handling various transaction components like customer orders, billing, payment, inventory, and shipping, where each component can process messages at its own pace.

The answer is technically correct, but in the real world, it depends. I would not advise splitting your transaction in multiple messages. Better to use a Blob in that case.

The appropriate service for this requirement is Azure Queue Storage. Azure Queue Storage is a service for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls using HTTP or HTTPS. It offers asynchronous message queueing for communication between application components, whether they are running in the cloud, on the desktop, on-premises, or on mobile devices. So, the answer is: C. Azure Queue Storage

Azure Queue Storage is a messaging service that allows decoupling of components in an application by providing a reliable way to pass messages between them asynchronously. It can handle messages in a first-in-first-out (FIFO) order and can scale to handle millions of messages per second. By using Azure Queue Storage, each component of the transaction process can push messages to the queue with relevant transaction information in XML format, which can be retrieved by the receiving component. This allows for loose coupling between the components, as they do not need to know about each other to communicate. Azure Notification Hubs and Azure Service Fabric are not messaging services but rather services for pushing notifications and deploying microservices, respectively. Azure Data Lake is a storage service for big data processing and analytics and does not provide messaging capabilities.

Same as Question 83. https://www.examtopics.com/discussions/microsoft/view/99750-exam-az-305-topic-4-question-83-discussion

C is the answer. https://learn.microsoft.com/en-us/azure/storage/queues/storage-queues-introduction Azure Queue Storage is a service for storing large numbers of messages. You access messages from anywhere in the world via authenticated calls using HTTP or HTTPS. A queue message can be up to 64 KB in size. A queue may contain millions of messages, up to the total capacity limit of a storage account. Queues are commonly used to create a backlog of work to process asynchronously.

ASB. this is repeated question

Correct Answer: C

C. Azure Queue Storage

C. Azure Queue Storage

C. Azure Queue Storage

In absence of ASB in the choose, next solution to be look at is Azure Storage Queue. In my opinion though, ASB is more durable than a Storage queue.

I'm going to have to go with C on this one.

Asynchronous messaging options. There are different types of messages and the entities that participate in a messaging infrastructure. Based on the requirements of each message type, Microsoft recommends Azure messaging services. The options include Azure Service Bus, Event Grid, and Event Hubs. Azure Service Bus queues are well suited for transferring commands from producers to consumers. Data is transferred between different applications and services using messages. A message is a container decorated with metadata, and contains data. The data can be any kind of information, including structured data encoded with the common formats such as the following ones: JSON, XML, Apache Avro, Plain Text. Reference: https://docs.microsoft.com/en-us/azure/architecture/guide/technology-choices/messaging https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview