Option A is correct because using ESB (Mule) with cache/state management can help to handle the long- running requests from Salesforce and return a request ID or a response if available from the external systems. This way, Salesforce does not have to wait for the externalsystems to respond and can avoid the API gateway timeout1 Option C is correct because using Continuation callouts can make the eligibility check request from Salesforce from Lightning UI at page load without blocking the UI thread. Continuation callouts are asynchronous and can handle long-running requestsup to 60 seconds23 Option E is correct because implementing a 'Check Update' button that passes a requestID received from ESB can allow the user to manually check the status of the eligibility check request. This can be useful when theresponse is not available within the Continuation timeout limit or when the user wants to refresh the data4 Option B is incorrect because recommending synchronous Apex callouts from Lightning UI to External Systems via Mule and implementing polling on APIgateway timeout can cause performance issues and user frustration. Synchronous Apex callouts block the UI thread and can only handle requests up to 120 seconds. Polling on API gateway timeout can increasethe network traffic and consume the callout limits25 Option D is incorrect because creating a Platform Event in Salesforce via Remote-Call-In and using the empAPI in the lightning UI to serve 3,000 concurrent users can introduce complexity and scalability issues.
Platform Events are meant for event-driven architecture and not for request-response scenarios. Remote-Call- In requires an additional license and configuration. empAPI has a limit of 1,000 concurrent subscribers per channel678 References: 1: MuleSoft Documentation 2: Salesforce Documentation 4: Salesforce Trailhead 3: Salesforce Developers Blog 5: Salesforce Documentation 6: Salesforce Documentation 7: Salesforce Documentation 8:
Salesforce Documentation