Exam AZ-300 topic 5 question 5 discussion

This link might shed some light on EVENTS versus MESSAGES: https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services?toc=/azure/service-bus-messaging/toc.json&bc=/azure/service-bus-messaging/breadcrumb/toc.json An excerpt here: 1. Event Grid - Use to React to Status Changes 2. Event Hubs - Use for Telemetry and distributed data streaming 3. Service Bus - Use for Order Processing and Financial Transactions Seems like Service Bus for the answer.

ANS: C https://docs.microsoft.com/en-us/azure/event-grid/overview

given answer is correct https://azure.microsoft.com/en-in/blog/events-data-points-and-messages-choosing-the-right-azure-messaging-service-for-your-data/ While Azure Event Grid and Azure Event Hubs have a razor-sharp focus on the collection and distribution of events at great scale, and with great velocity, an Azure Service Bus namespace is a host for queues holding jobs of critical business value. It allows for the creation of routes for messages that need to travel between applications and application modules. It is a solid platform for workflow and transaction handling and has robust facilities for dealing with many application fault conditions. A sale recorded in a point-of-sale solution is both a financial record and an inventory tracking record, and not a mere event. It’s recorded in a ledger, which will eventually be merged into a centralized accounting system, often via several integration bridges, and the information must not be lost on the way

Shopping Cart: Service Bus (ordering related) "When handling high-value messages that cannot be lost or duplicated, use Azure Service Bus" "advanced messaging features like FIFO, batching/sessions, transactions, dead-lettering, temporal control, routing and filtering, and duplicate detection" https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services?toc=/azure/service-bus-messaging/toc.json&bc=/azure/service-bus-messaging/breadcrumb/toc.json Inventory Distribution: Event Grid (integration with workflows -e.g. Azure logic Apps, blob storage queues) https://docs.microsoft.com/en-us/azure/event-grid/overview Restaurant Telemetry: Event Hub - "Azure Event Hubs is a big data pipeline. It facilitates the capture, retention, and replay of telemetry and event stream data." https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services?toc=/azure/service-bus-messaging/toc.json&bc=/azure/service-bus-messaging/breadcrumb/toc.json

It'c C for sure. Data sent to Blob, blob triggers event in Event Grid and finally Logic Apps reacts to the event and process the data.

EventGrid is the right ans https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services an e-commerce site can use Service Bus to process the order, Event Hubs to capture site telemetry, and Event Grid to respond to events like an item was shipped.

Answer: C (Event Grid) The type of information being shared are *updates* or inventory changes. If this can be interpreted as event, then Event Grid is more appropriate. Another clue is that the information is being stored in Blob which implies the actual event will have only reference to data. For Service Bus, we would expect the actual message to include the data itself

Possible solutions are Event Grid and Service Bus. Of these 2 Service Bus is the most appropriate for the inventory. My justification is below: * Event grid deals with events- change in the state of azure services. Doesn't concern itself with what triggered the event, what is in the event and what is to be done with it. * Service bus deals with messages- raw data produced by a service to be stored or used elsewhere- and state.

A is correct. Read section about " common messaging scenarios" : https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview

Surely it's EventGrid? It says that that inventory information is stored on blob storage. Blob storage changes can be subscribed to by the EventGrid as evidenced here: https://docs.microsoft.com/en-us/azure/event-grid/blob-event-quickstart-portal. Finally, EventGrid has connectors to Logic Apps so everything fits together.

A is correct, refer to the POS scenario in the below link and same can be applied here with Logic Apps. https://www.codemag.com/article/1112041/Introducing-Queues-and-Topics-in-Azure-Service-Bus

Answer" C As we can create Event Grid. Event Subscription and Topic.

Can anyone explain why a service bus would be preferable over a logic app?

Shouldn't be D ( Event HUB ) Event HUB can send data to Storage Ref: https://www.serverless360.com/blog/azure-event-hubs-vs-service-bus