Salesforce Certified Platform Integration Architect free question 7 / 10 · Domain 4: Design Integration Solutions
A remote system must create an account, a contact, and an opportunity in one all-or-nothing transaction, with custom validation on the Salesforce side before commit. Which component does the Remote Call-In table describe for these requirements?
- A platform event, given that publishing the event runs the custom validation and then commits the three records together
- An Apex web service or Apex REST service, given that it gives full transactional support and custom logic, but needs code
- The standard SOAP API, given that one call can span a transaction across multiple API calls and applies custom logic natively
- Bulk API 2.0, given that it processes the three object types together in one transaction and rolls back the whole job on an error
Show the answer and explanation
Answer: B
Why this is correct
The Apex web services and Apex REST services rows are rated suboptimal, with the note that they are typically used where additional requirements must be met. Those are full transactional support, for example creating an account, contact, and opportunity in one transaction, and custom logic applied on the Salesforce side before committing.
Why the other options are wrong
"The standard SOAP API, given that one call can span a transaction across multiple API calls and applies custom logic natively" … The page says it isn’t possible to span a transaction across multiple API calls. The standard API also has no custom pre-commit logic.
"Bulk API 2.0, given that it processes the three object types together in one transaction and rolls back the whole job on an error" … Bulk API 2.0 is for large asynchronous data operations. It is for large asynchronous data operations, so a single transaction across the three object types is not what it provides.
"A platform event, given that publishing the event runs the custom validation and then commits the three records together" … The page notes that pre-insert transaction logic at the consumer does not apply to platform events, so this is not a fit for the requirement.
Key points
Choose a custom Apex service only when a standard API cannot meet the transactional or logic requirement. Otherwise it is more code to own.