Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam ARC-101 Topic 8 Question 26 Discussion

Actual exam question for Salesforce's ARC-101 exam
Question #: 26
Topic #: 8
[All ARC-101 Questions]

A conglomerate is designing a Lightning Web Component (LWC) to display transactions aggregated from different sources. Their current system landscape is as follows:

1. Transactions are created at any time through their various on-premise and cloud-based systems.

2. All necessary transactions are replicated to a custom Transaction object in Salesforce. It is updated periodically so it only has a subset of the necessary transactions between updates.

3. Middleware supports publish-subscribe interactions and provides RESTful Enterprise APIs that can retrieve transactions from on-premise and cloud-based systems.

The company wants to address a usability concern regarding incomplete data displayed on the LWC component. What should the Integration Architect specify so the LWC will be able to display all the required transactions?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Sage
1 months ago
Hey, at least the question didn't ask us to use a Batch Apex job to fetch the transactions. That would have been a real head-scratcher!
upvoted 0 times
...
Tanja
1 months ago
Wait, there's a 'Continuation class'? I thought we were talking about Salesforce, not some old-school Java enterprise app!
upvoted 0 times
Camellia
16 days ago
A: Yeah, the Continuation class is used to call Enterprise APIs in Salesforce.
upvoted 0 times
...
...
Brice
1 months ago
I'm surprised option A) even made it as a choice. Using the Continuation class just sounds like a recipe for callback hell. C) is definitely the way to go.
upvoted 0 times
Bobbye
4 days ago
C) Call the Enterprise APIs directly from the LWC's JavaScript code and redisplay the LWC on receipt of the API response.
upvoted 0 times
...
Joaquin
7 days ago
I'm surprised option A) even made it as a choice. Using the Continuation class just sounds like a recipe for callback hell.
upvoted 0 times
...
Sabine
16 days ago
A) Use the Continuation class to call the Enterprise APIs and then process the response in a callback method.
upvoted 0 times
...
...
Nicholle
2 months ago
D) is an interesting idea, but it might add unnecessary complexity with the Platform Event and middleware. I think C) is the cleanest solution to the problem.
upvoted 0 times
Gladis
17 days ago
I think B) could also work well if we want real-time updates without additional complexity.
upvoted 0 times
...
Rana
27 days ago
But wouldn't using the Continuation class in A) provide a more robust solution?
upvoted 0 times
...
Nydia
1 months ago
I agree, C) seems like the most straightforward approach.
upvoted 0 times
...
...
Deeanna
2 months ago
I'm not sure about option B. Relying on the Lightning Data Service might not be sufficient if the custom object is not updated frequently enough. We need a more proactive approach to fetch the data.
upvoted 0 times
Nohemi
19 days ago
D) Publish a Platform Event, have the middleware subscribe and update the custom object on receipt of Platform Event.
upvoted 0 times
...
Cyndy
28 days ago
C) Call the Enterprise APIs directly from the LWC's JavaScript code and redisplay the LWC on receipt of the API response.
upvoted 0 times
...
Adelaide
1 months ago
A) Use the Continuation class to call the Enterprise APIs and then process the response in a callback method.
upvoted 0 times
...
...
Felicitas
2 months ago
C) looks like the most straightforward approach to me. Calling the APIs directly from the LWC component and updating the UI accordingly seems like the best way to ensure we display all the required transactions.
upvoted 0 times
Tonette
17 days ago
D) Publish a Platform Event, have the middleware subscribe and update the custom object on receipt of Platform Event.
upvoted 0 times
...
Corrinne
29 days ago
B) Let the Lightning Data Service with a wire adapter display new values when the custom object records change.
upvoted 0 times
...
Marsha
1 months ago
A) Use the Continuation class to call the Enterprise APIs and then process the response in a callback method.
upvoted 0 times
...
Bobbye
1 months ago
C) looks like the most straightforward approach to me. Calling the APIs directly from the LWC component and updating the UI accordingly seems like the best way to ensure we display all the required transactions.
upvoted 0 times
...
Arlean
1 months ago
A) Use the Continuation class to call the Enterprise APIs and then process the response in a callback method.
upvoted 0 times
...
Nickole
1 months ago
C) looks like the most straightforward approach to me. Calling the APIs directly from the LWC component and updating the UI accordingly seems like the best way to ensure we display all the required transactions.
upvoted 0 times
...
Yuki
2 months ago
A) Use the Continuation class to call the Enterprise APIs and then process the response in a callback method.
upvoted 0 times
...
Armando
2 months ago
C) looks like the most straightforward approach to me. Calling the APIs directly from the LWC component and updating the UI accordingly seems like the best way to ensure we display all the required transactions.
upvoted 0 times
...
...
Iluminada
2 months ago
I see both points, but I think option B could also work well. Letting the Lightning Data Service with a wire adapter display new values when custom object records change can provide a seamless user experience.
upvoted 0 times
...
Beata
3 months ago
I disagree, I believe option D is the way to go. Publishing a Platform Event and having the middleware update the custom object will ensure real-time updates and accurate data on the LWC.
upvoted 0 times
...
Vilma
3 months ago
I think option A is the best choice because using the Continuation class will allow us to call the Enterprise APIs asynchronously and process the response efficiently.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77