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

Bea

3 months ago

Wait, are we sure any of these will actually solve the problem?

upvoted 0 times

...

Cathrine

3 months ago

D could really help with scalability, I’m all for it!

upvoted 0 times

...

Xenia

3 months ago

C seems a bit complicated, not sure it’s necessary.

upvoted 0 times

...

Casie

4 months ago

I think B is the way to go, less redundancy is key!

upvoted 0 times

...

Elliott

4 months ago

A sounds solid for reducing network traffic.

upvoted 0 times

...

Xuan

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

upvoted 0 times

...

Shaun

4 months ago

I practiced a similar question about refactoring Apex methods, and I feel like Enhanced External Services could streamline the integration process effectively.

upvoted 0 times

...

Solange

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

upvoted 0 times

...

Toshia

5 months ago

I remember discussing the importance of scalability in integration solutions, and I think an Enterprise Service Bus could really help with that.

upvoted 0 times

...

Lavonne

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

upvoted 0 times

...

Eugene

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

upvoted 0 times

...

William

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

upvoted 0 times

...

Ivan

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

upvoted 0 times

...

Alline

9 months 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

9 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

Lucy

8 months ago

That could also be a good option to consider for long-term scalability.

upvoted 0 times

...

Argelia

9 months ago

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

upvoted 0 times

...

Shoshana

9 months ago

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

upvoted 0 times

...

Cherri

9 months 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

10 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

9 months ago

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

upvoted 0 times

...

Essie

9 months 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

9 months 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

10 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

10 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 months 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

9 months 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

9 months ago

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

upvoted 0 times

...

Pamella

10 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

9 months ago

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

upvoted 0 times

...

Angella

9 months ago

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

upvoted 0 times

...

Yvonne

10 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

...