Correct Answer: Use Event Hubs message retention to keep events for 3 days and reset the consumer offset
Event Hubs retains events for a configurable retention period (1–90 days on Standard/Premium tiers). Each consumer group independently tracks its own offset (checkpoint). To replay...
Correct Answer
Use Event Hubs message retention to keep events for 3 days and reset the consumer offset
Why This Answer Is Correct
Event Hubs retains events for a configurable retention period (1–90 days on Standard/Premium tiers). Each consumer group independently tracks its own offset (checkpoint). To replay, you reset the consumer group's offset to the desired point in time and re-read events. This is native to Event Hubs without needing Capture.
This question evaluates your knowledge of Azure Event Hubs — a core concept tested in Microsoft Certified: Azure IoT Developer Specialty (AZ-220). 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 designing an IoT ingestion pipeline using Azure Event Hubs to process real-time telemetry from 50,000 devices. Downstream services need to process events in the order they were sent by each device. How should you ensure that all telemetry events from a specific device are sent to and processed in sequence from the same partition?
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?