INTEGRATION-ARCHITECTURE-DESIGNER practice question 4 of 25

Customer is evaluating Platform Events solution and would like help in comparing/contrasting it with Outbound Message for a real-time / near-real time needs. They expect 3,000 consumers of messages from Salesforce. Which three considerations should be evaluated and highlighted when deciding between the solutions? Choose 3 answers

Full set: 106 questions

Domain Design an Integration Solution

Answer options
A: Both Platform Events and Outbound Message offer declarative means for asynchronous near-real time needs. They aren't best suited for real- time integrations. Correct answer
B: In both Platform Events and Outbound Messages, the event messages are retried by and delivered in sequence, and only once. Salesforce ensures there is no duplicate message delivery.
C: Message sequence is possible in Outbound Message but not guaranteed with Platform Events. Both offer very high reliability. Fault handling and recovery are fully handled by Salesforce. Correct answer
D: Number of concurrent subscribers to Platform Events is capped at 2,000. An Outbound Message configuration can pass only 100 notifications in a single messages to a SOAP end point. Correct answer
E: Both Platform Events and Outbound Message are highly scalable. However, unlike Outbound Message, only Platform Events have Event Delivery and Event Publishing limits to be considered.
Correct Answer:
A. Both Platform Events and Outbound Message offer declarative means for asynchronous near-real time needs. They aren't best suited for real- time integrations.; C. Message sequence is possible in Outbound Message but not guaranteed with Platform Events. Both offer very high reliability. Fault handling and recovery are fully handled by Salesforce.; D. Number of concurrent subscribers to Platform Events is capped at 2,000. An Outbound Message configuration can pass only 100 notifications in a single messages to a SOAP end point.
Explanation

When comparing Platform Events and Outbound Messages for a near-real-time integration with 3,000 consumers, several key architectural considerations arise.
1. Pattern Fit (A): Both solutions are fundamentally asynchronous and can be configured declaratively, making them suitable for near-real-time "fire-and-forget" scenarios where an immediate response is not required within the same transaction. This is a correct high-level characterization.
2. Scale & Limits (D): The requirement for 3,000 consumers is a critical factor. Platform Events have a documented limit of 2,000 concurrent CometD subscribers per org. This hard limit makes Platform Events (using this subscription method) unsuitable for the stated requirement. Outbound Messages also have a limit of 100 notifications per message, which impacts endpoint design.
3. Reliability & Ordering (C): Both mechanisms are highly reliable. Outbound Messages retry for 24 hours, and Platform Events are durable on the event bus for 72 hours. However, their ordering guarantees differ. Outbound Messages are sent sequentially, but network conditions can affect arrival order. Platform Events do not guarantee processing order for subscribers.

Why Incorrect

B: This is incorrect because neither solution guarantees "only once" delivery. Both provide "at-least-once" delivery, meaning the consuming system must be designed to handle potential duplicates. E: This is incorrect because it falsely claims that only Platform Events have limits. Outbound Messages are also subject to limits, such as the number of messages sent per hour/day and the number of notifications per message.

References

1. Platform Event Allocations & Limits: Salesforce Developer Documentation

"Platform Event Allocations". This document explicitly states

"Maximum number of concurrent CometD clients (subscribers) across all channels... 2

000". This directly supports the reasoning in option D.

2. Outbound Message Details: Salesforce Help

"Outbound Messaging". This documentation notes

"A single SOAP message can include up to 100 notifications." It also describes the retry mechanism

confirming its reliability but also the at-least-once delivery nature. This supports options C and D and refutes B.

3. Integration Patterns Overview: Salesforce Architects

"Integration Patterns and Practices" guide. The "Remote Process Invocation—Fire and Forget" pattern section describes the use of asynchronous mechanisms like Outbound Messaging and Platform Events for near-real-time use cases

supporting the characterization in option A. It also clarifies that while events are published in order

subscriber processing order is not guaranteed

supporting option C.

4. Platform Event Basics: Salesforce Developer Documentation

"Platform Events Developer Guide"

Chapter: "Subscribe to Platform Events". This guide details the subscription mechanisms and the at-least-once delivery guarantee

stating

"The event bus doesn’t guarantee that it delivers a message only once... Your app must be able to handle duplicate messages." This directly refutes the "only once" claim in option B.

Scroll to Top