Discuss Salesforce ARC-101 Exam Topic 7 Question 15

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

Suggested Answer: A, C, D

Get Premium ARC-101 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

28 comments · newest first

Corrie 12 months ago

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

Una 12 months ago

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

Zita 12 months ago

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

Joni 1 year ago

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

Jutta 1 year ago

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

Rusty 1 year 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.

Leota 1 year 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.

Bettye 1 year 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.

Gilma 1 year 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.

Luis 1 year ago

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

Mica 1 year ago

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

Corazon 1 year ago

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

Shawna 1 year ago

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

Annette 1 year 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.

Tracey 1 year 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.

Eugene 1 year ago

↳ replying to Tracey

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

Lizbeth 1 year ago

↳ replying to Tracey

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

Dottie 1 year ago

↳ replying to Tracey

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

Gretchen 1 year ago

↳ replying to Tracey

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

Cammy 1 year ago

↳ replying to Tracey

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

Leila 1 year ago

↳ replying to Tracey

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

Dean 2 years 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.

Tammi 1 year ago

↳ replying to Dean

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

Tammi 1 year ago

↳ replying to Dean

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

Gladys 2 years 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.

Tracey 2 years ago

I'm not sure about option A, I think option B might be a better choice.

Ashton 2 years ago

I agree with Vanna, option A seems like a feasible solution.

Vanna 2 years ago

I think option A sounds like a good recommendation.

Salesforce ARC-101 Exam - Topic 7 Question 15 Discussion