Exam Integration-Architect Topic 5 Question 19 Discussion

For a team with limited development resources and a low-code requirement, Lightning Flow (Flow Builder) is the primary declarative engine for modern integrations.
In this scenario, creating a Platform Event via a record-triggered flow provides a highly scalable, near real- time "Fire-and-Forget" signal to the middleware. This is considered low-code because it can be built entirely using point-and-click tools within Salesforce. Once the Order is created, the flow publishes the event to the bus. The middleware, acting as a subscriber, receives the event and orchestrates the REST call to the ERP.
Option C (Outbound Messaging) is also a low-code tool, but it natively sends messages in SOAP format.
Since the ERP requires a REST endpoint, using Outbound Messaging would necessitate additional transformation logic in the middleware, making it a less efficient architectural choice than using a Flow to trigger an event or an External Service. Option B (Change Data Capture) is a powerful tool but often requires more advanced "pro-code" configuration on the subscriber/middleware side to handle Replay IDs and Bayeux protocols, which might exceed the "limited resources" constraint of the Salesforce team.