An xeric-ridge archive job and a live-alerting job must both read the same Event Hub without sharing a cursor. What should the developer create?
Select an answer to reveal the explanation.
Short Explanation
Independent jobs need independent cursors. Spin up two consumer groups (you already have $Default) so archive and alerting each track their own progress.
Full Explanation
Consumer groups give each reading application its own offsets on the hub; one active reader epoch applies per partition per group. Sharing a single public offset, collapsing into one email fan-out, or mirroring into competing Storage queues does not provide independent Event Hubs read views.