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 Service Bus. Configure a topic to receive the device data by using a correlation filter.
Does the solution meet the goal?
A. Yes
B. No
One more thing to say about Event Hub is:
Number of partitions per event hub : 32
According to: https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-quotas
So, I don’t think that Event Hub could help in this scenario.
Partition Keys is not directly related to number of Partitions
B is the correct answer
Solution: Provision an Azure Event Hub. Configure the machine identifier as the partition key and enable capture.
B is answer
If “Event Hub” were the solution you would end up with 10.000 patitions keys aprox. Does it make sense?
If the device Identifier is the partition key and based on the question:
– ” Each store location has one to five devices that send data.” and “…device data from 2,000 stores “. That could lead to 5*2000 = 10.000 devices ids.
So, I’m not so sure that Even Hub will be the right soliution.
I would opt more for Service Bus with a correlation filter. Tha’s my guess.