SF-PD2 Process Automation, Logic, and Integration Practice Question
A business process requires that when a high-value Opportunity is closed, an external ERP system is notified via an event-driven architecture. Which solution provides the most decoupled and scalable integration pattern?
⚠ Common exam trap
Candidates often suggest synchronous Apex or triggers for external integration, failing to recognize that these tightly couple the systems and can cause performance issues if the external system is slow.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Publish a Platform Event to an event bus for the ERP system to consume.
Platform Events are the ideal choice for this architecture. They allow the Salesforce environment to publish an event message that is completely decoupled from the subscriber. This provides high scalability, as the ERP system can subscribe to the events at its own pace without impacting the transaction performance of the originating Salesforce process, ensuring that the business requirements are met with maximum system resilience.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use an Apex trigger to perform an HTTP callout directly to the ERP system.
Why it's wrong here
Direct callouts from triggers block the transaction until a response is received, which is risky for scalability and performance. If the ERP system is slow or unreachable, the entire Salesforce transaction will fail or time out, creating a tight coupling that violates best practices for event-driven system design.
- ✗
Configure an Outbound Message via Workflow Rule to send the data to the ERP.
Why it's wrong here
Outbound messages are a legacy feature with limited flexibility compared to modern event-driven patterns. They are tied to the synchronous nature of legacy workflow rules and do not provide the robust, highly scalable, and asynchronous event bus capabilities that modern, enterprise-level integration architectures demand for high-value business processes.
- ✓
Publish a Platform Event to an event bus for the ERP system to consume.
Why this is correct
Platform Events facilitate an asynchronous, decoupled architecture where Salesforce publishes changes to the event bus. This approach ensures that the primary transaction completes quickly while the ERP system consumes events independently. This pattern is highly scalable and fault-tolerant, perfectly aligning with modern enterprise integration requirements for reliable system communication.
- ✗
Implement a scheduled batch job to query for closed opportunities and export them.
Why it's wrong here
Scheduled batch jobs introduce significant latency, as updates are not processed in real-time. This approach defeats the requirement for prompt notification and relies on polling rather than an event-driven paradigm. Real-time integrations are far more effective for high-value business processes that require immediate downstream system awareness and action.
About these practice questions
This SF-PD2 question is part of Courseiva's 226-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-PD2 practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-PD2 exam.