MENU
Universal Containers (UC) processes orders in Salesforce in a custom object, Order__c. 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?
Suggested Answer: A
Get Premium DEX-450 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
19 comments · newest first
JU
Justine
11 months ago
Flow with an invocable method sounds interesting, but is it efficient?
KA
Kara
11 months ago
Isn't using an @future method risky with governor limits?
SU
Sunny
11 months ago
Wait, can Batchable really handle this? Seems like overkill.
MA
Marilynn
11 months ago
Totally agree, Queueable is perfect for this!
AN
Annita
11 months ago
I think option A is the best choice for handling the trigger.
TA
Tambra
12 months ago
I have a hunch that using an @future method could work, but I remember there are limits on callouts that might complicate things.
LE
Lettie
12 months ago
Flow with an invocable method sounds interesting, but I can't recall if it supports REST callouts directly.
RE
Reid
1 year ago
I think we practiced a similar question where we had to send data to an external system. I feel like Batchable might be overkill for just one order at a time.
MA
Madalyn
1 year ago
I remember we discussed using Queueable Apex for handling asynchronous processes, but I'm not sure if it's the best fit here.
AS
Ashlyn
1 year ago
I'm a little confused by the requirement to process the orders one at a time. Wouldn't a Batchable class be better since it can handle larger volumes of orders? I'll need to think through the tradeoffs between the different options, but I'm leaning towards B or C.
BE
Bernardine
1 year ago
Okay, I think I've got a good handle on this. The key is that the orders need to be processed one at a time, so a Queueable class called from a trigger seems like the best approach. That way I can process each order individually and handle any errors or retries without impacting the rest of the system.
KA
Kasandra
1 year ago
Hmm, I'm a bit unsure about this one. I'm not super familiar with the Batchable and Queueable classes, so I'll need to review the documentation on those. I'm also wondering if a Flow might be a simpler solution since it can handle the callout directly.
PO
Portia
1 year ago
This looks like a pretty straightforward integration problem. I think I'll go with option B - a Batchable class called from a scheduled job. That way I can process the orders in batches and handle any errors or retries more easily.
NO
Noah
1 year ago
I think a Flow with a callout from an invocable method might be a more efficient solution for this scenario.
AN
Annalee
1 year ago
I believe a Batchable class called from a scheduled job could also work for this integration.
OL
Ollie
1 year ago
I agree with Brigette, using a Queueable class will help in processing orders one at a time.
AN
An
1 year ago
I think the answer is B. Callout from a Batchable class called from a scheduled job. It seems like the best way to handle a large volume of orders and integrate with the ERP system.
LO
Louvenia
1 year ago
I agree, using a Batchable class for callouts in a scheduled job is a good choice for handling large volumes.
BR
Brigette
1 year ago
I think the developer should implement a callout from a Queueable class called from a trigger.