A copper-roof workshop runs a long-lived worker that must checkpoint Cosmos change-feed progress so a restart does not replay the entire history. Which approach should the developer use?
Select an answer to reveal the explanation.
Short Explanation
Treat leases like bookmarks in a shared library book. The change feed processor plus a lease container remembers where you stopped so restarts do not reread the whole catalog. That is at-least-once checkpointing—not a Functions-only rule.
Full Explanation
The change feed processor model uses a lease container to coordinate and checkpoint progress across workers, providing automatic resume behavior with at-least-once delivery semantics. Azure Functions Cosmos triggers are a different host path covered elsewhere. Local files and full-container polls do not provide the official lease-based checkpoint design.