Question 14 - Salesforce ARC-101 Real Exam Questions [Jan 2026 Update]

Q: 14

A company wants to standardize exception tracking, handling, and analytics. Given the following actions: 1. Build a company wide logging service hosted on a middleware platform 2. Create case object records for exceptions based thresholds 3. Change all their Apex Loggers to publish Application Exceptions as custom Platform Events. Which two specifications should the integration architect include in the logging service architecture? Choose 2 answers

Options

Correct Answer:

B, D

Explanation

The proposed architecture involves an external logging service that interacts with Salesforce. This requires two distinct integration points.

First, the service must receive exception data from Salesforce. The requirement specifies that exceptions are published as custom Platform Events. The correct mechanism for an external client to subscribe to and receive Platform Events is by using the Salesforce Streaming API (which encompasses CometD and the Pub/Sub API).

Second, after the middleware service processes an event and determines a case is needed, it must create a Case record in Salesforce. The standard, robust, and governable method for an external system to create data in Salesforce is through a direct API call, such as REST or SOAP.

References

1. Salesforce Streaming API for Platform Events (Answer D): Platform Events Developer Guide

"Subscribe to Platform Event Notifications". This guide states

"External apps subscribe to events using CometD... The subscription process is similar to how you subscribe to PushTopic or generic streaming events." This confirms the Streaming API is the correct mechanism for an external service.

2. Salesforce APIs for Record Creation (Answer B): Salesforce Integration Guide

"Salesforce APIs". This document outlines the primary APIs for integration. It specifies

"Use REST API... to create

read

update

and delete records." This establishes the REST/SOAP API as the standard for an external service to create a Case record.

3. Change Data Capture vs. Platform Events (Reasoning for A): Change Data Capture Developer Guide

"What Is Change Data Capture?". The guide defines it as a tool to "receive near-real-time changes of Salesforce records." This clearly distinguishes its purpose from subscribing to custom Platform Events.

4. Automatic Case Creation Rules (Reasoning for C): Salesforce Help

"Email-to-Case". This documentation describes the feature as a way to "automatically create cases and auto-populate case fields when customers send messages to the email addresses you specify." This identifies it as a channel-specific feature

not a primary integration API for a middleware service.

Premium Access Includes

FLASH OFFER

avail 10% DISCOUNT on YOUR PURCHASE