You deployed a stateful ASP.NET Core web app (PolicyApp) to an App Service that reacts to Azure Event Grid events. Requirements: all authentication events (sign-ins and sign-outs) must be handled by PolicyApp, and sign-outs must be processed as quickly as possible. What should you implement?

Creating separate Event Grid topics and subscriptions for sign-in and sign-out events is the most effective solution. This approach ensures that sign-out events, which require rapid processing, have their own dedicated channel, preventing them from being queued behind less urgent sign-in events. This isolation guarantees minimal latency for critical sign-out operations. Using a single subscription for all authentication events (first option) would mean sign-out events could be delayed by sign-in event processing. Creating separate handlers (second option) doesn't address the queuing issue within Event Grid itself; events would still arrive at a single subscription. While filtering with subjectBeginsWith (fourth option) can differentiate events, it still relies on a single subscription, meaning all events are routed to the same endpoint and processed sequentially, potentially delaying sign-outs.