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 Exam ARC-101 Topic 5 Question 21 Discussion

Actual exam question for Salesforce's ARC-101 exam
Question #: 21
Topic #: 5
[All ARC-101 Questions]

A company has an external system that processes and tracks orders. Sales reps manage their leads and opportunity pipeline in Salesforce. In the current state, the two systems are disconnected and processing orders requires a lot of manual entry on sales rep part. This creates delays in processing orders and incomplete data due to manual entry.

As a part of modernization efforts the company decided to integrate Salesforce and the order management system. The following technical requirements were identified:

1. Orders need to be created in real time from salesforce

2. Minimal customization*, and code should be written due to a tight timeline and lack of developer resources

3. Sales reps need to be able to see order history and be able to see most up to date information on current order status.

4. Managers need to be able to run reports in Salesforce to see daily and monthly order volumes and fulfillment timelines.

5. The legacy system is hosted on premise and is currently connected to the Enterprise Service Bus (ESB). The ESB is flexible enough to provide any methods and connection types needed by salesforce team.

6. There are 1000 sales reps. Each user processes/creates on average 15 orders per shift. Most of the orders contain 20-30 line items.

How should an integration architect integrate the two systems based on the technical requirements and system constraints?

Show Suggested Answer Hide Answer
Suggested Answer: A, C, D

Contribute your Thoughts:

Long
13 hours ago
Hmm, Option D with the Salesforce Big Object and SOAP API seems a bit overkill for this scenario. I'd prefer a more lightweight solution like Option B or C.
upvoted 0 times
...
Audra
6 days ago
I'm leaning towards Option C. Using the standard object and REST API is a tried-and-true approach, and the ETL process will help ensure data integrity between the two systems.
upvoted 0 times
...
Ruth
7 days ago
I'm not sure, but I think option C could also work since it involves using Salesforce standard object, REST API, and ETL. It might be worth considering as well.
upvoted 0 times
...
James
8 days ago
Option B seems like the most comprehensive solution that meets all the requirements. Creating a custom REST API to integrate with the legacy system is a great way to minimize customization and leverage Salesforce's built-in features.
upvoted 0 times
...
Isabelle
8 days ago
I agree with Jean. Option B seems like the most practical solution given the technical requirements and system constraints.
upvoted 0 times
...
Jean
10 days ago
I think option B is the best choice because it allows for minimal customization and code, which is important due to the tight timeline and lack of developer resources.
upvoted 0 times
...
Isreal
13 days ago
I'm not sure, but I think option C using Salesforce standard object, REST API and ETL could also work well for this integration.
upvoted 0 times
...
Jacklyn
20 days ago
I agree with Shannon. Option B using custom object, custom REST API and ETL seems like the most efficient solution.
upvoted 0 times
...
Shannon
22 days ago
I think option B is the best choice because we need minimal customization and code due to tight timeline.
upvoted 0 times
...

Save Cancel