A developer created a new trigger that inserts a Task when a new Lead is created. After deploying to production, an outside integration is periodically reporting errors.
Which change should the developer make to ensure the integration is not affected with minimal impact to business logic?
To ensure the integration is not affected with minimal impact to business logic, the developer should use the Database method with allOrNone set to False. This approach allows partial success in bulk operations, meaning that if some records fail, the successful ones will still be processed, thus preventing the entire transaction from rolling back. This ensures that the integration does not encounter errors due to the failure of some operations, maintaining smoother workflow and data consistency.
Correct answer B
yes. You can surely suppress the error using try catch, but the insertion of other record within the same transaction will be canceled as well. Since try catch is "AllOrNone".
Answer: B A Try/Catch block after the insert statement has no sense. It could be wrapping the insert.
i was wrong with my first response, i think B is better.
B is te answer
yes, i confirm the correct answer is C
Try Catch Block after the insert statement doesn't make sense at all. It should be around the insert statement. So to me correct answer is B.
The correct ans is C
Didn't get proper explanation why try and catch need to be used after Insert. It also know about the issue but never resolve the problem
All of these answers are bad. "C" is best because with "use the Database method with allOrNone set to False" would still produce an error to the integration.
Correct answer B
B is the answer