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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce ARC-101 Exam - Topic 5 Question 21 Discussion

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 salesforce2. Minimal customization*, and code should be written due to a tight timeline and lack of developer resources3. 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?
A) Use Salesforce external object and OData connector. and C) Use Salesforce standard object, REST API and ETL. and D) Use Salesforce big object, SOAP API and Dataloader.
B) Use Salesforce custom object, custom REST API and ETL.

Salesforce ARC-101 Exam - 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

by Wynell at Jul 24, 2023, 04:29 AM

Limited Time Offer

25%

Off

Get Premium ARC-101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Aretha
6 months ago
Totally agree, integrating with the ESB makes sense for flexibility!
upvoted 0 times
...
Malcom
7 months ago
Wait, are they really expecting minimal customization with all those requirements?
upvoted 0 times
...
Zana
7 months ago
Real-time order creation is a must, but how will they handle the legacy system?
upvoted 0 times
...
Aleshia
7 months ago
I think a custom REST API might be overkill for this.
upvoted 0 times
...
Candida
7 months ago
Sounds like using the OData connector could streamline things!
upvoted 0 times
...
Howard
8 months ago
I recall a practice question where we used big objects for large datasets, but I’m not sure if that applies here with the need for real-time order creation.
upvoted 0 times
...
Johanna
8 months ago
I feel like the standard object option might be the safest bet since it could reduce complexity, but I’m not entirely confident about the ETL part.
upvoted 0 times
...
Desmond
8 months ago
I think using a custom REST API could work, but I’m worried about the tight timeline and the need for minimal customization.
upvoted 0 times
...
Mitzie
8 months ago
I remember we discussed using external objects for real-time data access, but I'm not sure if OData is the best choice here.
upvoted 0 times
...
Irma
8 months ago
I'm pretty sure the first, second, and third windows refer to different wavelength ranges used for optical fiber transmission. I think the question is asking us to identify which of the answer choices correctly describes these windows.
upvoted 0 times
...
Herman
8 months ago
The key here is identifying the critical business units and systems. I'd say this is definitely the business impact analysis phase.
upvoted 0 times
...
Matt
8 months ago
This looks like a tricky XSLT question. I'll need to carefully review the schema and the XSLT stylesheet to understand the expected output.
upvoted 0 times
...
Ellen
8 months ago
Okay, I think I've got a good handle on this. The Workflow Monitor allows you to view your workflows, see status information for the process instances, and perform control operations. I'll select those options and hope I've got it right.
upvoted 0 times
...
Tiara
1 year 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
1 year 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
Cheryl
11 months ago
D) Yeah, using big objects and SOAP API might be overkill for this integration.
upvoted 0 times
...
Hana
11 months ago
C) I agree, using standard objects and REST API seems like a straightforward approach.
upvoted 0 times
...
Casie
11 months ago
B) That sounds like a good option, minimal customization is key.
upvoted 0 times
...
Leatha
12 months ago
A) Use Salesforce external object and OData connector.
upvoted 0 times
...
...
Merlyn
1 year 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
1 year 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
1 year ago
B: Yeah, I agree. Using custom solutions can give us more control over the integration process.
upvoted 0 times
...
Minna
1 year 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
1 year 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
Stephanie
12 months ago
Yeah, that sounds like a more lightweight solution that would still meet the technical requirements.
upvoted 0 times
...
Nichelle
12 months ago
Using Salesforce custom object, custom REST API and ETL would probably be more efficient.
upvoted 0 times
...
Michael
12 months ago
I think Option B or C would be a better fit considering the tight timeline and lack of developer resources.
upvoted 0 times
...
Billy
12 months ago
I agree, Option D does seem like overkill for this integration.
upvoted 0 times
...
Salome
12 months 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
1 year 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
1 year ago
Yeah, keeping it lightweight with Option B or C would definitely be the way to go.
upvoted 0 times
...
Marcos
1 year ago
I agree, Option D does seem like overkill. Option B or C would probably be more efficient.
upvoted 0 times
...
Peggie
1 year ago
Using a custom object, custom REST API, and ETL could be a good fit for this scenario.
upvoted 0 times
...
Effie
1 year ago
I think Option B or C would be more efficient and easier to implement.
upvoted 0 times
...
Devon
1 year ago
I agree, Option D does seem like a heavy solution for this integration.
upvoted 0 times
...
...
Audra
1 year 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
1 year 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
1 year 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 year 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 year 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
1 year ago
I agree with Jean. Option B seems like the most practical solution given the technical requirements and system constraints.
upvoted 0 times
...
Jean
1 year 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
1 year 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
1 year 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
1 year 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