Free Access to Salesforce.Integration-Architect.v2026-08-26.q122 with Valid Practice Test (Page 2)

Question 1

A conglomerate is designing a Lightning Web Component (LWC) to display transactions aggregated from different sources. Their current system landscape is as follows:
1. Transactions are created at any time through their various on-premise and cloud-based systems.
2. All necessary transactions are replicated to a custom Transaction object in Salesforce. It is updated periodically so it only has a subset of the necessary transactions between updates.
3. Middleware supports publish-subscribe interactions and provides RESTful Enterprise APIs that can retrieve transactions from on-premise and cloud-based systems.
The company wants to address a usability concern regarding incomplete data displayed on the LWC component. What should the Integration Architect specify so the LWC will be able to display all the required transactions?

A.Use the Continuation class to call the Enterprise APIs and then process the response in a callback method.
B.Publish a Platform Event, have the middleware subscribe and update the custom object on receipt of Platform Event.
C.Let the Lightning Data Service with an ©wire adapter display new values when the custom object records change.
D.Call the Enterprise APIs directly from the LWC's JavaScript code and redisplay the LWC on receipt of the API response.

Question 2

A company needs to be able to send data from Salesforce to a home grown system behind a corporate firewall. The data needs to be pushed only one way and doesn't need to be sent in real time. The average volume is 2 million records per day.
What should an integration architect consider when choosing the right option in building the integration between the external system and Salesforce?

A.Due to high volume of records, a third party integration tool is required to stage records off platform.
B.Due to high volume of records, number of concurrent requests can hit the limit for the REST API call to external system.
C.Due to high volume of records, the external system will need to use a BULK API Rest endpoint to connect to salesforce.
D.Due to high volume of records, salesforce will need to make a REST API call to external system.

Question 3

Service agents at Northern Trail Outfitters use Salesforce to manage cases and B2C Commerce for ordering.
Which integration solution should an architect recommend in order for the service agents to see order history from a business-to-consumer (B2C) Commerce system?

A.Salesforce B2C Commerce to Service Cloud Connector
B.REST API offered by Commerce Platforms
C.MuleSoft Anypoint Platform

Question 4

Northern Trail Outfitters (NTO) uses a custom mobile app to interact with its customers. One of the features of the app is Salesforce Chatter Feeds. NTO wants to automatically post a Chatter item to Twitter whenever the post includes the #thanksNTO hashtag.
Which API should an integration architect use to meet this requirement?

A.REST API
B.Streaming API to generate PushTopic
C.Connect REST API

Correct Answer: C

When designing integrations that specifically involve Chatter, social collaboration, or Experience Cloud sites, the Connect REST API (formerly known as the Chatter REST API) is the architecturally recommended choice. While the standard REST API is optimized for CRUD operations on data records, the Connect REST API is specifically designed to handle the complex, nested structures of social feeds, including posts, comments, hashtags, and mentions.
The Connect REST API provides a specialized resource for feed elements that simplifies the process of identifying specific social markers like hashtags. In this use case, the mobile app or a middleware service can subscribe to or query the feed. The Connect REST API returns structured data where hashtags are identified as distinct message segments, making it trivial for an application logic to detect the #thanksNTO tag and trigger a subsequent call to the Twitter API.
From an architectural standpoint, using the Connect REST API offers several advantages over the standard REST API or Streaming API for this requirement:
* Efficiency: Connect REST API responses are structured specifically for presentation in mobile applications, providing only the relevant social metadata and localized content needed for the feed.
* Feature Richness: It provides native support for social actions such as liking, sharing, and following, which are often required alongside feed monitoring.
* Scalability: It is designed to handle the high-volume, real-time nature of social interactions within Experience Cloud and mobile ecosystems.
While the Streaming API (Option B) can notify an application of record changes, it does not provide the rich, formatted social context that the Connect REST API delivers. The standard REST API (Option A) could technically access FeedItem records, but it would require significant custom parsing logic to identify hashtags within the raw body text, whereas the Connect REST API handles this segmenting natively. Therefore, for building custom mobile experiences that interact with Chatter data, the Connect REST API is the superior solution.

Question 5

A call center manager uses a custom dashboard to track Case related metrics. The manager wants a component to display the number of closed Cases in real time.
What type of event should be used to meet this requirement?

A.Push Topic Event
B.Change Data Capture Event
C.Platform Event
D.Generic Event

Question 1

Question 2

Question 3

Question 4

Question 5

Download PDF File