A retailer tracks inventory in real time and sends events to Azure Event Grid. You need a subscription filter that can adapt dynamically to seasonal shifts in product demand. Which type of Event Grid filter should you use?

The correct answer is an advanced filter because it allows for complex filtering logic based on the event's data payload. By including a "season" field in the event data, an advanced filter can dynamically evaluate this field along with other criteria (e.g., product category, inventory level) using Boolean conditions. This enables the filter to adapt to changing seasonal demand without requiring manual updates to the filter itself. A prefix filter on the event type is too simplistic; it only checks the beginning of the event type string and cannot evaluate data within the event. A label-based subscription filter is not a standard Event Grid filter type. While you could implement a similar concept using advanced filters on custom data fields, "label-based" isn't a direct Event Grid feature. A static subject filter is too rigid; it would require the subject to always contain "/seasonal/inventory," which doesn't allow for dynamic adaptation based on the actual season or product demand changes.