A newt-pond shipping subscription should receive only messages where region equals west. What should the developer configure on the subscription?
Select an answer to reveal the explanation.
Short Explanation
Do not make shipping read every OrderPlaced just to ignore east. Put a SQL or correlation filter on that subscription so only region = west lands there.
Full Explanation
A newt-pond shipping subscription should not read every OrderPlaced only to discard non-west traffic. Configure a Service Bus subscription filter—SQL or correlation—so only messages with region = west are copied to that subscription. Filtering at the broker reduces noise, cost, and accidental cross-region processing while other subscriptions can apply different predicates.
An Event Grid event-type filter on the Service Bus namespace fails because Event Grid filters apply to Event Grid subscriptions, not as the native filter model on Service Bus topic subscriptions. A Cosmos DB partition key equal to west on the topic fails conceptually: Cosmos partitioning does not configure Service Bus subscription matching. AKS network policies that drop east region packets at the node fail because network drops are not message property filters and would be a brittle, wrong-layer control.
Exam caveat: default filters may accept all messages—an empty or overly broad rule can silently deliver everything until you tighten the SQL/correlation expression. Operational check: publish west and east sample messages, apply the region filter, and confirm only west messages appear on the shipping subscription.