Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce ARC-101 Exam - Topic 8 Question 53 Discussion

Posted by Kristofer on Dec 06, 2024 at 09:52 AM

A company needs to be able to send data from Salesforce to a home grown system behind a corporate firewall. The data needs to be pushed only one way and doesn't need to be sent in real time. The average volume is 2 million records per day.

What should an integration architect consider when choosing the right option in building the integration between the external system and Salesforce?

Suggested Answer: B, D, E

Get Premium ARC-101 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
34 comments · newest first
DO
Dottie 11 months ago
I think using BULK API is the best option for this volume.
HU
Huey 11 months ago
REST API calls might hit limits, so better be cautious.
BU
Bulah 12 months ago
Wait, can Salesforce even handle that many records at once?
MA
Margart 12 months ago
I agree, BULK API is definitely the way to go here!
BI
Billye 1 year ago
A third party tool sounds like overkill for just pushing data.
CA
Carline 1 year ago
If I recall correctly, making a REST API call from Salesforce to the external system might not be the best option due to the volume.
RE
Regenia 1 year ago
I'm not entirely sure, but I feel like the BULK API could be the right choice for handling large data volumes efficiently.
CA
Caitlin 1 year ago
I think we practiced a similar question where we discussed using a third-party tool for staging records. It might be necessary here too.
DA
Danica 1 year ago
I remember that with such a high volume, we might hit limits on concurrent requests with the REST API, so that could be a concern.
LA
Larae 1 year ago
This is a good one. I like how it's testing our understanding of Salesforce integration patterns. I think I'd start by considering the BULK API, as that seems like the best fit for the high-volume, one-way data transfer requirement.
ED
Edda 1 year ago
Okay, got it. The key here is to avoid hitting any API limits on either side. I reckon a third-party integration tool might be the way to go, as that could help stage the data off-platform and manage the high volume.
SH
Shawnda 1 year ago
Hmm, I'm a bit unsure about this one. The requirement to push data one-way behind a corporate firewall adds an extra layer of complexity. I'll need to think carefully about the security and connectivity implications.
TO
Tommy 1 year ago
This seems like a pretty straightforward integration problem, but the high volume of records is definitely something to consider. I think I'd start by looking at the Salesforce BULK API as an option to handle the data transfer efficiently.
CH
Chaya 2 years ago
I wonder if they're going to hire a team of supercomputers to handle all that data. Maybe we should just use a fleet of carrier pigeons instead.
LA
Lawrence 1 year ago
↳ replying to Chaya
C) Due to high volume of records, the external system will need to use a BULK API Rest endpoint to connect to salesforce.
CH
Christiane 1 year ago
↳ replying to Chaya
B) Maybe we should just use a fleet of carrier pigeons instead.
HA
Hassie 1 year ago
↳ replying to Chaya
A) Due to high volume of records, number of concurrent requests can hit the limit for the REST API call to external system.
CA
Catrice 2 years ago
With 2 million records a day, the external system better have a firewall the size of the Great Wall of China!
CE
Celia 1 year ago
↳ replying to Catrice
B) Due to high volume of records, a third party integration tool is required to stage records off platform.
CE
Celia 1 year ago
↳ replying to Catrice
A) Due to high volume of records, number of concurrent requests can hit the limit for the REST API call to external system.
CE
Celia 2 years ago
↳ replying to Catrice
C) Due to high volume of records, the external system will need to use a BULK API Rest endpoint to connect to salesforce.
FR
Freeman 2 years ago
Option D? Really? Salesforce making the API calls? That's like asking a hamster to pull a freight train.
CO
Cordelia 1 year ago
↳ replying to Freeman
Option D? Really? Salesforce making the API calls? That's like asking a hamster to pull a freight train.
LO
Loise 1 year ago
↳ replying to Freeman
C) Due to high volume of records, the external system will need to use a BULK API Rest endpoint to connect to salesforce.
BI
Billi 2 years ago
↳ replying to Freeman
B) Due to high volume of records, a third party integration tool is required to stage records off platform.
JU
Juliann 2 years ago
↳ replying to Freeman
A) Due to high volume of records, number of concurrent requests can hit the limit for the REST API call to external system.
MA
Mable 2 years ago
I'm not sure, but I know one thing - I'm not the one who has to deal with 2 million records a day! That's a lot of data.
ME
Mel 2 years ago
I'm not sure, but I think option B could also work if we need to stage records off platform to manage the high volume of data.
LE
Leslee 2 years ago
Hmm, I would have gone with C. The BULK API is perfect for high-volume data transfers.
LA
Laticia 1 year ago
↳ replying to Leslee
User 2: Yeah, the BULK API Rest endpoint is designed for exactly that purpose.
RO
Ronna 1 year ago
↳ replying to Leslee
User 1: I agree, C seems like the best option for handling high volume of records.
CR
Cristal 2 years ago
Definitely option B. A third-party integration tool is the way to go for handling that kind of volume.
DA
Dana 2 years ago
I agree with Gilberto, option C seems like the most suitable option for this scenario. It will prevent hitting the limit for the REST API call.
GI
Gilberto 2 years ago
I think option C is the best choice because the BULK API Rest endpoint is designed for handling large volumes of data efficiently.
0/2000 characters

Save Cancel