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

17.17Interview answer

“I'd treat this as orchestration in a Process API. Assuming Salesforce, Billing and Loyalty all need only the customer ID and are independent, I'd call them concurrently with Scatter-Gather and aggregate the results with DataWeave. I'd define per-route timeout and failure semantics explicitly—for example Loyalty might be optional while Salesforce is mandatory—and propagate the same correlation ID across all three calls.”

Strong.