A yellowthroat-bog Event Hubs processor restarts and re-reads yesterday's telemetry. What must the consumer do so resume continues from the last processed offset?
Select an answer to reveal the explanation.
Short Explanation
Event Hubs is a log — it does not babysit your cursor. Checkpoint the offset (Blob checkpoint store with the processor client is the usual path) so a restart picks up where you left off, not yesterday.
Full Explanation
Consumers are responsible for persisting progress. With EventProcessorClient and related SDKs, offsets are typically checkpointed to a Blob checkpoint store so processing resumes after a restart. Event Hubs does not push offsets to webhooks like Event Grid. Deleting partitions or moving to Logic Apps does not replace checkpointing.