DRAG DROP –
You are implementing an order processing system. A point of sale application publishes orders to topics in an Azure Service Bus queue. The Label property for the topic includes the following data:
The system has the following requirements for subscriptions:
You need to implement filtering and maximize throughput while evaluating filters.
Which filter types should you implement? To answer, drag the appropriate filter types to the correct subscriptions. Each filter type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Correct Answer:
![]()
FutureOrders: CorrelationFilter –
(with the not existing value of any filed to avoid getting any message)
(with the not existing value of any filed to avoid getting any message)
HighPriortyOrders: SQLFilter
(as we need to get all high priority AND international orders, but for Correlation filter: A match exists when an arriving message’s value for a property is equal to the value specified in the correlation filter and we need not equal)
(as we need to get all high priority AND international orders, but for Correlation filter: A match exists when an arriving message’s value for a property is equal to the value specified in the correlation filter and we need not equal)
InternationalOrders: SQLFilter –
Country NOT USA requires an SQL Filter
HighQuantityOrders: SQLFilter –
Need to use relational operators so an SQL Filter is needed.
AllOrders: No Filter –
SQL Filter: SQL Filters – A SqlFilter holds a SQL-like conditional expression that is evaluated in the broker against the arriving messages’ user-defined properties and system properties. All system properties must be prefixed with sys. in the conditional expression. The SQL-language subset for filter conditions tests for the existence of properties (EXISTS), as well as for null-values (IS NULL), logical NOT/AND/OR, relational operators, simple numeric arithmetic, and simple text pattern matching with LIKE.
Correlation Filters – A CorrelationFilter holds a set of conditions that are matched against one or more of an arriving message’s user and system properties. A common use is to match against the CorrelationId property, but the application can also choose to match against ContentType, Label, MessageId, ReplyTo,
ReplyToSessionId, SessionId, To, and any user-defined properties. A match exists when an arriving message’s value for a property is equal to the value specified in the correlation filter. For string expressions, the comparison is case-sensitive. When specifying multiple match properties, the filter combines them as a logical
AND condition, meaning for the filter to match, all conditions must match.
Boolean filters – The TrueFilter and FalseFilter either cause all arriving messages (true) or none of the arriving messages (false) to be selected for the subscription.