What should the developer implement to accomplish this?

Universal Containers (UC) processes orders in Salesforce in a custom object, ord=xr <. They also allow sales reps to upload CSV files with thousands of orders at a time.

A developer is tasked with integrating orders placed in Salesforce with UC’s enterprise resource planning (ERP) system.

After the status for an order__ c is first set to ‘Placed’, the order information must be sent to a REST endpoint in the ERP system that can process one order at a time.

What should the developer implement to accomplish this?
A . Callout from an Qfuture method called from a trigger
B . Callout from a Batchable class called from a scheduled job
C . Flow with a callout from an invocable method
D . Callout from a Queueable class called from a trigger

View Answer

Answer: D

Explanation:

To integrate Order__c records with the ERP system after their status is set to ‘Placed’, and considering that orders may be uploaded in bulk, the developer should: Option D: Callout from a Queueable class called from a trigger

Trigger: Implement an after-update trigger on Order__c to detect when the status changes to ‘Placed’.

Queueable Apex: Use Queueable Apex to handle asynchronous processing and callouts. Queueable classes support callouts by implementing the Database.AllowsCallouts interface. Benefits:

Handles Bulk Data: Queueable Apex can process records in batches and can be chained for processing large volumes.

Supports Callouts: Unlike future methods, Queueable Apex allows for more complex data types and

supports callouts with fewer limitations.

Reference: "To make a Web service callout to an external service or API, you must use asynchronous Apex, such as future methods, Queueable Apex, or batch Apex."

"Queueable Apex is an asynchronous Apex feature that is a superset of future methods with some extra features."

― Apex Developer Guide: Queueable Apex Why Other Options Are Incorrect:

Option A: Callout from an @future method called from a trigger

@future methods have limitations, such as accepting only primitive types as parameters and a limit of 50 calls per transaction, which can be exceeded when processing thousands of records.

Reference: "Methods with the future annotation must be static methods and can only return a void type. The specified parameters must be primitive data types, arrays of primitive data types, or collections of primitive data types."

― Apex Developer Guide: Future Methods

Option B: Callout from a Batchable class called from a scheduled job

Batch Apex is not immediately triggered by record changes and may not meet the requirement of processing the order after the status changes.

Scheduling adds delay and complexity unnecessary for this use case.

Option C: Flow with a callout from an invocable method

Flows invoked from triggers (record-triggered flows) cannot perform callouts unless they are configured to run asynchronously, and managing bulk operations with flows can be less efficient.