A loon-lake checkout retries a send after a timeout and must not fulfill the order twice. What should the developer enable on the Service Bus entity?
Select an answer to reveal the explanation.
Short Explanation
Timeouts love double sends. Flip on duplicate detection, keep MessageId stable, and Service Bus drops the twin inside the detection window.
Full Explanation
Service Bus duplicate detection suppresses messages with the same MessageId within the configured history window, protecting against sender retries. Cosmos ETags and Event Hubs TUs are unrelated. Receive-and-delete affects receive loss risk, not sender-side duplicate suppression.