Exam AZ-204 topic 3 question 16 discussion

FutureOrder, not based on the property -> Correlation Filter. AllOrders, it's clear.. no filter. The rest is based on one or more properties --> SQL filter I agree with @stylebc

How do you justify No Filter for All Orders when you need to take action? Each newly created topic subscription has an initial default subscription rule. If you don't explicitly specify a filter condition for the rule, the applied filter is the true filter that enables all messages to be selected into the subscription. The default rule has no associated annotation action https://docs.microsoft.com/en-us/azure/service-bus-messaging/topic-filters

FutureOrders should be SQLFilter as you can check with the condition on AuditedAt user's property or EnqueuedTimeUtc system property but that is required a greater than condition but correlation filter condition needs to be matched. 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. https://docs.microsoft.com/en-us/azure/service-bus-messaging/topic-filters

HighPriorityOrders: CorrelationFilter You can apply to multiple system or user-defined properties and when multiple properties then filter combined them with AND logical operator. https://docs.microsoft.com/en-us/azure/service-bus-messaging/topic-filters 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 the following properties: ContentType Label MessageId ReplyTo ReplyToSessionId SessionId To 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.

no sense at all , you want future filters and do nothing? , you want all the orders and you apply filter?

Why a filter for all orders?

I somewhat agree with this answer after going through lot of resources. The only thing that bothers me is answer for the first and last question. When you create a subscription by default a SQL filter is added which is 1=1 i.e. always evaluates to true. So my source of confusion is how "No Filter" is treated. I have two interpretations either "No Filter" is we don't add any filter or the other is absence of a filter. Mostly I believe it is treated as absence of a filter in which case the this answer looks correct.

How do you justify Correlation Filter for HighPriorityOrders, when it involves Region <> US ? I think it should be SQL filter as well.

How do you remember all 375 questions?