MENU
Northern Trail Outfitters has had an increase in requests from other business units to integrate opportunity information with other systems from Salesforce. The developers have started writing asynchronous @future callouts directly into the target systems. The CIO is concerned about the viability of this approach scaling for future growth and has requested a solution recommendation.
What should be done to mitigate the concerns that the CIO has?
Suggested Answer: B
Get Premium ARC-101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
35 comments · newest first
BE
Bea
11 months ago
Wait, are we sure any of these will actually solve the problem?
CA
Cathrine
11 months ago
D could really help with scalability, I’m all for it!
XE
Xenia
12 months ago
C seems a bit complicated, not sure it’s necessary.
CA
Casie
12 months ago
I think B is the way to go, less redundancy is key!
EL
Elliott
1 year ago
A sounds solid for reducing network traffic.
XU
Xuan
1 year ago
I have a vague recollection of custom metadata being useful for managing integration endpoints, but I’m not confident if that’s the best approach here.
SH
Shaun
1 year ago
I practiced a similar question about refactoring Apex methods, and I feel like Enhanced External Services could streamline the integration process effectively.
SO
Solange
1 year ago
I'm not entirely sure, but I think using an ETL tool for batch processing might be a safer option to manage data loads without overwhelming the system.
TO
Toshia
1 year ago
I remember discussing the importance of scalability in integration solutions, and I think an Enterprise Service Bus could really help with that.
LA
Lavonne
1 year ago
I think option C is the way to go. Refactoring the existing code to use a more modern integration approach like Enhanced External Services seems like it would address the CIO's concerns about scalability and maintainability. Plus, it's probably the fastest to implement out of the options presented.
EU
Eugene
1 year ago
Option D sounds like the most robust solution, but it also seems like the most complex and time-consuming. I'm not sure if that's the best approach for this particular scenario, especially if the CIO is looking for a more scalable solution quickly.
WI
William
1 year ago
Hmm, I'm a bit confused by the different options here. I'm not sure if an ETL tool is the right solution, and I'm not very familiar with Enhanced External Services. I'll need to do some more research on those before deciding.
IV
Ivan
1 year ago
This seems like a pretty straightforward integration problem. I think option B looks like the best approach to streamline the code and make it more maintainable.
AL
Alline
1 year ago
Ah, the age-old debate: batch vs real-time integration. I say we settle this with a game of Salesforce Trailhead trivia. Loser has to implement the chosen solution!
PE
Peggie
1 year ago
I'm voting for C, but I'm also curious if the developers have considered using Heroku Connect. Might be a good way to sync the data without all the custom Apex code.
LU
Lucy
1 year ago
That could also be a good option to consider for long-term scalability.
AR
Argelia
1 year ago
D) Implement an Enterprise Service Bus for service orchestration, mediation, routing and decouple dependencies across systems.
SH
Shoshana
1 year ago
I'm voting for C too. It seems like a more modern and scalable solution.
CH
Cherri
1 year ago
C) Refactor the existing future methods to use Enhanced External Services, import Open API 2.0 schemas and update flows to use services instead of Apex.
AL
Albert
1 year ago
A is a classic 'band-aid' approach. Nightly batch loads? That's so 2010s. We need a more modern, real-time integration solution here.
TY
Tyisha
1 year ago
D) Implement an Enterprise Service Bus for service orchestration, mediation, routing and decouple dependencies across systems.
ES
Essie
1 year ago
C) Refactor the existing future methods to use Enhanced External Services, import Open API 2.0 schemas and update flows to use services instead of Apex.
VA
Valentin
1 year ago
B) Develop a comprehensive catalog of Apex classes to eliminate the need for redundant code and use custom metadata to hold the endpoint information for each integration.
TI
Timothy
2 years ago
B seems promising, a catalog of Apex classes and custom metadata could help streamline the integrations. But I'm worried it might not address the scalability concerns the CIO has.
SY
Sylvia
2 years ago
I'm leaning towards D. An Enterprise Service Bus could really help decouple the systems and provide better orchestration and routing. Seems like the most robust long-term solution.
CH
Chantell
1 year ago
C) Refactor the existing future methods to use Enhanced External Services, import Open API 2.0 schemas and update flows to use services instead of Apex.
CA
Cathrine
1 year ago
A) Implement an ETL tool and perform nightly batch data loads to reduce network traffic using last modified dates on the opportunity object to extract the right records.
JA
Jacquelyne
1 year ago
D) Implement an Enterprise Service Bus for service orchestration, mediation, routing and decouple dependencies across systems.
PA
Pamella
2 years ago
C looks like the best option to me. Refactoring the future methods to use Enhanced External Services and Open API 2.0 schemas seems like a more scalable and maintainable solution.
EL
Elouise
1 year ago
It's important to consider long-term scalability when integrating systems, so C seems like the most viable option.
AN
Angella
1 year ago
I agree, using Enhanced External Services and Open API 2.0 schemas would definitely help with scalability and maintenance.
YV
Yvonne
2 years ago
C looks like the best option to me. Refactoring the future methods to use Enhanced External Services and Open API 2.0 schemas seems like a more scalable and maintainable solution.
LE
Leah
2 years ago
I'm not sure about option C. I think option D might be a better choice to implement an Enterprise Service Bus for better service orchestration.
LA
Lacresha
2 years ago
I agree with Coral. Option C seems like the most efficient way to address the CIO's concerns about scalability.
CO
Coral
2 years ago
I think option C sounds like a good solution. Using Enhanced External Services and Open API 2.0 schemas can help improve scalability.