Salesforce ARC-101 Exam - Topic 7 Question 15 Discussion

Actual exam question for Salesforce's ARC-101 exam

Question #: 15
Topic #: 7

An enterprise architect has requested the Salesforce Integration architect to review the following (see diagram & description) and provide recommendations after carefully considering all constraints of the enterprise systems and Salesforce platform limits.

* About 3,000 phone sales agents use a Salesforce Lightning UI concurrently to check eligibility of a customer for a qualifying offer.

* There are multiple eligibility systems that provides this service and are hosted externally. However, their current response times could take up to 90 seconds to process and return (there are discussions to reduce the response times in future, but no commitments are made).

* These eligibility systems can be accessed through APIs orchestrated via ESB (MuleSoft).

* All requests from Salesforce will have to traverse through customer's API Gateway layer and the API Gateway imposes a constraint of timing out requests after 9 seconds.

Which three recommendations should be made?

Choose 3 answers

AESB (Mule) with cache/state management to return a requestID (or) response if available from external system.

BRecommend synchronous Apex call-outs from Lightning UI to External Systems via Mule and implement polling on API gateway timeout.

CUse Continuation callouts to make the eligibility check request from Salesforce from Lightning UI at page load.

DWhen responses are received by Mule, create a Platform Event in Salesforce via Remote-Call-In and use the empAPI in the lightning UI to serve 3,000 concurrent users.

EImplement a 'Check Update' button that passes a requestID received from ESB (user action needed).

Show Suggested Answer

Suggested Answer: A, C, D

by Willow at Feb 26, 2023, 08:15 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Corrie

4 months ago

E is a good fallback, but it requires user action which could slow things down.

upvoted 0 times

...

Una

4 months ago

Wait, can we really handle 3,000 users with D? Sounds ambitious!

upvoted 0 times

...

Zita

4 months ago

B seems risky, synchronous calls could lead to more timeouts.

upvoted 0 times

...

Joni

4 months ago

Totally agree with A! It’s all about efficiency.

upvoted 0 times

...

Jutta

4 months ago

A is a solid choice, caching can really help with response times.

upvoted 0 times

...

Rusty

5 months ago

Option D sounds interesting, especially with using Platform Events to handle concurrent users, but I wonder if it could complicate the architecture too much.

upvoted 0 times

...

Leota

5 months ago

I think option C with Continuation callouts could be a good way to manage the user experience during the page load, but I’m not confident if it’s the best fit here.

upvoted 0 times

...

Bettye

5 months ago

I'm not entirely sure about the synchronous Apex call-outs in option B; it feels risky given the timeout constraints. We might need to explore alternatives.

upvoted 0 times

...

Gilma

5 months ago

I remember we discussed the importance of caching in our last study session, so option A seems like a solid choice to handle the long response times.

upvoted 0 times

...

Luis

5 months ago

Hmm, this seems like a tricky one. I'll need to think through the details carefully to figure out the likely cause.

upvoted 0 times

...

Mica

5 months ago

I'm pretty sure the correct sequence is UOM Class, UOM, UOM Conversions, but I'll double-check the notes to be sure.

upvoted 0 times

...

Corazon

5 months ago

I remember we discussed principles-based ethics in class, and I think it was about encouraging values rather than just following rules.

upvoted 0 times

...

Shawna

9 months ago

I heard the external system team is considering a new feature: the 'Deliberately Slow' API. Just to keep things interesting, you know?

upvoted 0 times

...

Annette

10 months ago

I'm going with A, C, and E. Anything that involves 3,000 concurrent users and 90-second response times is going to be a headache, so we need to get creative with caching and user interactions.

upvoted 0 times

...

Tracey

10 months ago

I'm not sure about D, but the other options look good. At least the exam question isn't asking us to suggest hiring more developers to manually process the requests.

upvoted 0 times

Eugene

9 months ago

Let's go with A, B, and E then. They should address the issue without adding unnecessary complexity.

upvoted 0 times

...

Lizbeth

9 months ago

I agree, D does seem a bit complicated. A, B, and E are more straightforward solutions.

upvoted 0 times

...

Dottie

9 months ago

I think A, B, and E are the best options. They seem like they would help improve the response times.

upvoted 0 times

...

Gretchen

9 months ago

User 3: Yeah, D might be too much for this scenario.

upvoted 0 times

...

Cammy

9 months ago

User 2: I agree, D does seem a bit complicated.

upvoted 0 times

...

Leila

9 months ago

User 1: I think A, B, and E are good options.

upvoted 0 times

...

Dean

10 months ago

B is not a good recommendation since making 3,000 concurrent callouts to external systems could overwhelm the API Gateway. D seems overly complex for this use case.

upvoted 0 times

Tammi

9 months ago

E) Implement a 'Check Update' button that passes a requestID received from ESB (user action needed).

upvoted 0 times

...

Tammi

10 months ago

A) ESB (Mule) with cache/state management to return a requestID (or) Tammi if available from external system.

upvoted 0 times

...

Gladys

10 months ago

A, C, and E seem like the most reasonable options to address the constraints and requirements. Using the ESB with caching and continuation callouts should help avoid the API Gateway timeout issue.

upvoted 0 times

...