A customer is evaluating the Platform Events solution and would like help in comparing/contrasting it with Outbound Messaging for real-time/near-real time needs. They expect 3,000 customers to view messages in Salesforce.
Which three considerations should be evaluated and highlighted when deciding between the solutions? (Choose three.)
When deciding between Platform Events and Outbound Messaging for real-time or near-real-time needs, three key considerations should be evaluated. First, the number of concurrent subscribers to Platform Events is capped at 2,000, and Outbound Messaging configurations can send only up to 100 notifications in a single message to a SOAP endpoint. Second, both solutions offer declarative means for asynchronous near-real-time needs but are not best suited for real-time integrations. Finally, while both solutions are highly scalable, only Platform Events come with event delivery and event publishing limits that must be considered.
I would consider A, B, & E to be the correct answers. C is not correct; outbound messages are queued and retried multiple times D is not correct; platform event recovery is not handled by Salesforce; it's up to the remote system to use replay IDs to retrieve messages are within the recovery window (24 hours or 72 hours, depending on event type).
C is incorrect because order of execution is not guaranteed in both cases https://developer.salesforce.com/docs/atlas.en-us.214.0.platform_events.meta/platform_events/platform_event_limits.htm https://help.salesforce.com/s/articleView?id=sf.workflow_om_considerations.htm&type=5
ABE looks correct
https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_event_limits.htm
ADE is the answer
B is also incorrect because Platform Events are suited to real-time integrations https://www.salesforceben.com/salesforce-platform-events/
C is incorrect because Outbound Messages may be delivered more than once and out of order. https://help.salesforce.com/s/articleView?id=sf.workflow_om_considerations.htm&type=5
A- Platform Event: Maximum number of concurrent CometD clients (subscribers) per platform event channel or across all platform event channels = 2000 Outbound Message: A single SOAP message can include up to 100 notifications. D- Platform Event: A subscriber can retrieve events at any time and isn’t restricted to listening to events at the time they’re sent. https://developer.salesforce.com/docs/atlas.en-us.214.0.platform_events.meta/platform_events/platform_events_api_considerations.htm Outboud Message: Messages are queued until they are sent, to preserve message reliability. E Platform Event: Maximum number of event notifications published per hour = 100000