A whimbrel-flat device’s readings must stay in order per device on Event Hubs. How should related events be kept on one ordered stream?
Select an answer to reveal the explanation.
Short Explanation
Same device, same key, same partition. Use the device id as the partition key so readings stay ordered—don’t hand-pick partition IDs as the happy path.
Full Explanation
A partition key hashes related events onto one partition so order is preserved for that key (for example per device). Official guidance discourages sending directly to a partition ID as the primary pattern. Disabling partitions or switching wholesale to Service Bus sessions is not the Event Hubs ordering answer here.