Salesforce Exam ARC-101 Topic 4 Question 54 Discussion

Actual exam question for Salesforce's ARC-101 exam

Question #: 54
Topic #: 4

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?

AImplement 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.

BDevelop 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.

CRefactor the existing future methods to use Enhanced External Services, import Open API 2.0 schemas and update flows to use services instead of Apex.

DImplement an Enterprise Service Bus for service orchestration, mediation, routing and decouple dependencies across systems.

Show Suggested Answer

Suggested Answer: B

by Quiana at Jan 09, 2025, 07:56 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Alline

29 days 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!

upvoted 0 times

...

Peggie

1 months 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.

upvoted 0 times

Argelia

8 days ago

D) Implement an Enterprise Service Bus for service orchestration, mediation, routing and decouple dependencies across systems.

upvoted 0 times

...

Shoshana

12 days ago

I'm voting for C too. It seems like a more modern and scalable solution.

upvoted 0 times

...

Cherri

15 days 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.

upvoted 0 times

...

Albert

1 months 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.

upvoted 0 times

Tyisha

5 days ago

D) Implement an Enterprise Service Bus for service orchestration, mediation, routing and decouple dependencies across systems.

upvoted 0 times

...

Essie

10 days 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.

upvoted 0 times

...

Valentin

14 days 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.

upvoted 0 times

...

Timothy

1 months 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.

upvoted 0 times

...

Sylvia

1 months 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.

upvoted 0 times

Chantell

9 days 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.

upvoted 0 times

...

Cathrine

15 days 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.

upvoted 0 times

...

Jacquelyne

16 days ago

D) Implement an Enterprise Service Bus for service orchestration, mediation, routing and decouple dependencies across systems.

upvoted 0 times

...

Pamella

2 months 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.

upvoted 0 times

Elouise

19 days ago

It's important to consider long-term scalability when integrating systems, so C seems like the most viable option.

upvoted 0 times

...

Angella

23 days ago

I agree, using Enhanced External Services and Open API 2.0 schemas would definitely help with scalability and maintenance.

upvoted 0 times

...

Yvonne

1 months 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.

upvoted 0 times

...