Hi @murillocg ,
I wanted to respond quickly before I have to run out the door so there is more context here (maybe an interesting read), but our best practice would be to always set DMQ Eligible to true so the Consumer can make the call of whether they want to use a DMQ or not. As you found with JCSMP this isn’t the case in our older APIs for backwards compatibility reasons, however DMQ Eligible is now set to true by default in our new Java, Python and Go Messaging APIs. It is also set to true in our newer connectors like Boomi, MuleSoft and in our Spring Cloud Stream Binder.
Hope that helps!