Correct Answer: Publish events using the device's unique ID as the Partition Key when sending to the Event Hub.
When you send events to Azure Event Hubs with a Partition Key, Event Hubs hashes the key to determine which partition the event belongs to. Using the device's unique ID as the Part...
Correct Answer
Publish events using the device's unique ID as the Partition Key when sending to the Event Hub.
Why This Answer Is Correct
When you send events to Azure Event Hubs with a Partition Key, Event Hubs hashes the key to determine which partition the event belongs to. Using the device's unique ID as the Partition Key guarantees that all events from that device land in the same partition in strict chronological order, which enables sequential processing by downstream consumers.
This question evaluates your knowledge of Azure Event Hubs — a core concept tested in Microsoft Certified: Azure Developer Associate (AZ-204). Understanding Azure Event Hubs is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
You are ingesting telemetry from 1 million IoT devices using Azure Event Hubs. You need to ensure that all telemetry from the same device is always processed by the same consumer in order. How should you configure Event Hubs?
Your IoT solution uses Event Hubs to ingest device telemetry. A downstream processing service needs to re-read all telemetry from the past 3 days to replay a failed batch analytics job. Which Event Hubs feature supports this?