INTEGRATION-ARCHITECTURE-DESIGNER practice question 23 of 25
A company wants to standardize exception tracking, handling, and analytics. Given the following actions: 1. Build a company wide logging service…
Full set: 106 questionsDomain Design an Integration Solution
The proposed architecture involves two distinct integration actions performed by the middleware logging service. First, the service must receive the exception data from Salesforce. The scenario specifies that exceptions are published as custom Platform Events. The standard, event-driven mechanism for an external client to subscribe to and receive Platform Events is by using the Salesforce Streaming API (which uses the CometD protocol). Second, after receiving an event and determining that a threshold has been met, the service must create a Case record in Salesforce. The most robust and direct method for an external system to create data in Salesforce is to make a callout using one of the standard data APIs, such as the REST, SOAP, or Bulk API.
A. Change Data Capture (CDC) is used for streaming changes to existing Salesforce records (sObjects), not for subscribing to custom Platform Events, which is the mechanism specified in the requirements.
C. While technically possible to trigger Case creation via a mechanism like Email-to-Case, this is an indirect and less reliable pattern for system-to-system integration compared to a direct API call.
1. Platform Events Developer Guide, "Subscribe to Platform Events": This guide details how clients subscribe to platform event notifications. It states, "External apps subscribe to platform events using CometD... Salesforce provides the Streaming API, which is an implementation of CometD that enables receiving event notifications." This directly supports option D.
2. REST API Developer Guide, "sObject Basic Information, Create a Record": This documentation outlines the standard procedure for creating a new record in Salesforce via the REST API using a POST request to the appropriate sObject resource URI (e.g., /services/data/vXX.X/sobjects/Case/). This supports option B as the standard method for the middleware to create the Case.
3. Salesforce Architects, "Event-Driven Architecture": The principles of event-driven architecture on Salesforce advocate for using Platform Events for publishing business process notifications. External systems (subscribers) listen for these events and can then use callback APIs (like REST/SOAP) to update Salesforce or perform other actions. This reference supports the combined pattern of D and B.
4. Change Data Capture Developer Guide, "Introduction": "With Change Data Capture, you can receive near-real-time changes of Salesforce records... Change Data Capture publishes change events, which represent changes to Salesforce records." This clarifies that CDC is for record changes, making option A incorrect for a Platform Event scenario.
Keep practicing
Take the free INTEGRATION-ARCHITECTURE-DESIGNER practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other INTEGRATION-ARCHITECTURE-DESIGNER practice questions
- Question 1Northern Trail Outfitters has a requirement to encrypt few of widely used standard fields…
- Question 2An Integration Developer is developing an HR synchronization app for a client. The app sy…
- Question 3Northern Trail Outfitters submits orders to the manufacturing system web-service. Recentl…
- Question 4Customer is evaluating Platform Events solution and would like help in comparing/contrast…
- Question 5Universal Containers (UC) is a large printing company that sells advertisement banners. T…
- Question 6A large consumer goods manufacturer operating in multiple countries is planning to implem…
