BookatlasTwo-Day MuleSoft → Salesforce Bootcamp
168 / 279 · Module 10 — Synchronous vs Asynchronous Integrations · filtered: code← prev⊞ allnext →

10.61Interview scenario

Events sometimes arrive twice.

Answer:

“I'd consider duplicate delivery normal and design the consumer to be idempotent using a stable event or business key. If ordering matters I'd also track version or sequence because idempotency alone doesn't prevent stale events from overwriting newer state.”

That's a particularly strong answer.