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:

Tiara
24 days ago
Ah, the joys of legacy systems and tight timelines. At least the ESB is flexible enough to handle this - otherwise, we'd be in real trouble!
upvoted 0 times
...
Cyndy
25 days ago
I'm just hoping they don't ask about the number of line items per order on the exam. That's the real test of an integration architect's sanity!
upvoted 0 times
...
Merlyn
1 months ago
Option A with the OData connector looks interesting, but I'm not sure if it'll provide the level of customization and control needed to meet all the requirements. Gotta be careful with pre-built connectors sometimes.
upvoted 0 times
Brunilda
23 days ago
C: Option C with standard object, REST API and ETL could also work well without the need for extensive customization.
upvoted 0 times
...
Stefanie
26 days ago
B: Yeah, I agree. Using custom solutions can give us more control over the integration process.
upvoted 0 times
...
Minna
29 days ago
A: I think option B with custom object, custom REST API and ETL might be a better choice for more customization.
upvoted 0 times
...
...
Long
2 months 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
Billy
3 days ago
I agree, Option D does seem like overkill for this integration.
upvoted 0 times
...
Salome
4 days ago
I think we should go with Option B or C for a more lightweight solution that meets our technical requirements.
upvoted 0 times
...
Soledad
6 days ago
Yeah, I think Option B or C would be a better fit considering the tight timeline and lack of developer resources.
upvoted 0 times
...
Pamela
6 days ago
Yeah, keeping it lightweight with Option B or C would definitely be the way to go.
upvoted 0 times
...
Marcos
7 days ago
I agree, Option D does seem like overkill. Option B or C would probably be more efficient.
upvoted 0 times
...
Peggie
10 days ago
Using a custom object, custom REST API, and ETL could be a good fit for this scenario.
upvoted 0 times
...
Effie
11 days ago
I think Option B or C would be more efficient and easier to implement.
upvoted 0 times
...
Devon
19 days ago
I agree, Option D does seem like a heavy solution for this integration.
upvoted 0 times
...
...
Audra
2 months 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
2 months 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
2 months 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
Lakeesha
1 months ago
I agree, using a custom REST API will allow for real-time order creation and seamless integration between Salesforce and the order management system.
upvoted 0 times
...
Dick
1 months 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
2 months ago
I agree with Jean. Option B seems like the most practical solution given the technical requirements and system constraints.
upvoted 0 times
...
Jean
2 months 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
2 months 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
2 months 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
2 months 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