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 solution to collect point-of-sale (POS) device data from 2,000 stores located throughout the world.
A single device can produce 2 megabytes (MB) of data every 24 hours.
Each store location has one to five devices that send data.
You must store the device data in Azure Blob storage.
Device data must be correlated based on a device identifier.
Additional stores are expected to open in the future.
You need to implement a solution to receive the device data.
Solution: Provision an Azure Notification Hub.
Register all devices with the hub.
Does the solution meet the goal?
Click on the arrows to vote for the correct answer
A. B.B.
Instead use an Azure Service Bus, which is used order processing and financial transactions.
https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-servicesThe proposed solution of provisioning an Azure Notification Hub and registering all devices with the hub does not meet the goal of storing device data in Azure Blob storage and correlating it based on a device identifier.
Azure Notification Hub is a scalable mobile push notification engine that enables sending push notifications to mobile devices, and it is not suitable for receiving and storing large amounts of device data.
To meet the goal of storing device data in Azure Blob storage, a more appropriate solution would be to use Azure Event Hubs, which is a highly scalable data streaming platform and event ingestion service. Event Hubs can receive millions of events per second and can store data for up to seven days, making it ideal for collecting and storing data from thousands of devices.
To implement the solution using Azure Event Hubs, each POS device can send data to an Event Hub instance that is configured with a device-specific partition key. This allows all the data from a specific device to be stored together in the same partition, making it easy to correlate the data based on the device identifier.
In addition to using Event Hubs, a data ingestion pipeline can be created to store the data in Azure Blob storage or any other data store, such as Azure Data Lake Storage or Azure SQL Database, for long-term storage and analysis. This pipeline can be implemented using Azure Stream Analytics or Azure Functions, which can process the data in real-time and store it in the appropriate data store.
In conclusion, the proposed solution of provisioning an Azure Notification Hub and registering all devices with the hub is not suitable for storing device data in Azure Blob storage and correlating it based on a device identifier. Instead, Azure Event Hubs should be used in combination with a data ingestion pipeline to meet the requirements.