BookatlasTwo-Day MuleSoft → Salesforce Bootcamp
70 / 80 · Module 17 — Interview System-Design Scenarios · filtered: interview← prev⊞ allnext →

17.33Interview answer

“For a seconds-level Salesforce change requirement I'd prefer an event-driven mechanism such as Change Data Capture rather than aggressive polling. I'd design the consumer for duplicate delivery and replay, make the downstream update idempotent, and carry source sequence/version information if stale events can overwrite newer state. I'd also monitor event lag because eventual consistency becomes part of the business SLA.”

Excellent.