BookatlasTwo-Day MuleSoft → Salesforce Bootcamp
1 / 18 · Module 2 — Building a Real Mule Flow · filtered: cheatsheet⊞ allnext →

2.23Five likely interview questions

Q: What happens to the Mule payload after a Salesforce operation?

The operation generally produces a new payload containing its result, so I preserve earlier data in variables when I'll need it downstream.


Q: Why use Transform Message before Salesforce?

The incoming API contract normally shouldn't be identical to the Salesforce object model. DataWeave maps the external representation into the structure expected by the Salesforce Connector.


Q: Why use Salesforce Connector instead of HTTP Request directly against Salesforce REST API?

The connector abstracts authentication, Salesforce operations, object metadata and many API details. I'd use raw HTTP only when I specifically needed functionality or behavior not appropriately exposed through the connector.


Q: Create or upsert?

For integration-controlled entities that have a stable external identifier, I'd normally prefer upsert because it naturally supports retries and reduces duplicate creation.


Q: Why store something in vars?

Variables let me preserve application state across processors even as those processors replace or transform the current payload.