A Service Bus topic must route only “public-health” intents to the clinic assistant worker. Which feature implements that rule?
Select an answer to reveal the explanation.
Short Explanation
SQL filters are the clinic desk’s routing stamp—“public-health” intents get their own subscription rule so housing noise never wakes the clinic assistant.
Full Explanation
A Service Bus topic that must route only “public-health” intents to the clinic assistant worker should use a subscription SQL filter (or equivalent rule) on message application properties. The clinic subscription’s rule matches intent (or category) values such as public-health; other intents bypass that subscription. Filtering at the broker keeps housing or inspections traffic from waking clinic workers and preserves clean scale and DLQ ownership per subscription.
Delivering every topic message to the clinic worker and filtering only inside unstructured free text with no rule fails efficiency and reliability: workers spend lock time on irrelevant intents, and free-text heuristics misclassify. Deleting the topic and forcing public-health intents onto an unrelated storage queue with no filters abandons pub/sub fan-out and loses topic-level routing design. Using Event Grid subject filters exclusively even though the path is a Service Bus topic subscription answers the wrong product: Event Grid filters do not configure Service Bus subscription rules.
Exam caveat: SQL filters operate on user/system properties—producers must set the intent property consistently; filtering on body text is not what SQL filters are for. Rule changes should be tested with both matching and non-matching properties. Operational check: publish messages with intent=public-health and intent=housing; confirm only public-health appears on the clinic subscription; inspect rule metrics and DLQ for unexpected mismatches.