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

Question 71

A new Salesforce program requires data updates between internal systems and Salesforce. Which relevant detail should an integration architect seek to solve for integration architecture needs?

A.Core functional and non-functional requirements for User Experience design, Encryption needs, Community and license choices
B.Integration skills, SME availability, and Program Governance details
C.Timing aspects, real-time/near real-time (synchronous or asynchronous), batch and update frequency

Question 72

An integration developer is developing an HR synchronization app for a client. The app synchronizes Salesforce record data changes with an HR system that's external to Salesforce. What should the integration architect recommend to ensure notifications are stored for up to 3 days if data replication fails?

A.Change Data Capture
B.Outbound Message
C.Callouts

Question 73

A large enterprise customer has decided to implement Salesforce as their CRM. The current system landscape includes the following:
1. An Enterprise Resource Planning (ERP) solution that is responsible for Customer Invoicing and Order fulfillment.
2. A Marketing solution they use for email campaigns.
The enterprise customer needs their sales and service associates to use Salesforce to view and log their interactions with customers and prospects in Salesforce.
Which system should be the System of record for their customers and prospects?

A.ERP with all prospect data from Marketing and Salesforce.
B.Marketing with all customer data from Salesforce and ERP.
C.Salesforce with relevant Marketing and ERP information.
D.New Custom Database forCustomers and Prospects.

Correct Answer: C

Explanation
Option C is correct because Salesforce should be the system of record for their customers and prospects, as it is the CRM solution that the sales and service associates use to view and log their interactions with them. Salesforce can also integrate with the Marketing and ERP solutions to display relevant information from those systems, such as campaign history, invoices, and orders12 Option A is incorrect because ERP is not a suitable system of record for customers and prospects, as it is mainly focused on invoicing and order fulfillment. ERP may not have all the data that the sales and service associates need to interact with them, such as contact details, preferences, activities, and opportunities. ERP may also have different data models and definitions than Salesforce and Marketing, which can cause data quality and consistency issues3 Option B is incorrect because Marketing is not a suitable system of record for customers and prospects, as it is mainly focused on email campaigns. Marketing may not have all the data that the sales and service associates need to interact with them, such as account information, service cases, contracts, and quotes. Marketing may also have different data models and definitions than Salesforce and ERP, which can cause data quality and consistency issues.
Option D is incorrect because creating a new custom database for customers and prospects is not a feasible or efficient solution, as it would require additional development, maintenance, and integration costs. It would also create another layer of complexity and potential data duplication in the system landscape. Salesforce already provides a robust and flexible platform for managing customer and prospect data, which can be easily customized and integrated with other systems.
References: 1: Salesforce CRM - The Definitive Guide 2: Salesforce Integration Cloud - Connect Any App, Data, or Device 3: What Is ERP? | Oracle : Salesforce vs ERP: What's the Difference? : Marketing Cloud - Digital Marketing Platform : Salesforce vs Marketing Cloud: What's the Difference? : Salesforce Platform - Build Apps Fast : Why You Shouldn't Build Your Own CRM System

Question 74

Universal Containers (UC) is currently managing acustom monolithic webservice that runs on an on-premise server.
This monolithic web service is responsible for Point-to-Point (P2P) integrations between:
1. Salesforce and a legacy billing application
2. Salesforce and a cloud-based Enterprise Resource Planning application
3. Salesforce and a data lake.
UC has found that the tight interdependencies between systems is causing integrations to fail.
What should an architect recommend to decouple the systems and improve performance of the integrations?

A.Re-write and optimize the current web service to be more efficient.
B.Leverage modular design by breaking up the web service into smaller pieces for a microservice architecture.
C.Use the Salesforce Bulk API when integrating back into Salesforce.
D.Move thecustom monolithic web service from on-premise to a cloud provider.

Question 75

A customer is evaluating the Platform Events solution and would like help in comparing/contrasting it with Outbound Messaging for real-time/near-real time needs. They expect 3,000 customers to view messages in Salesforce. What should be evaluated and highlighted when deciding between the solutions?12

A.In both Platform Events and Outbound Messaging, the event messages are retried by and delivered in sequence, and 3only once. Sales4force ensures there is no duplicate message delivery.
B.Message sequence is possible in Outbound Messaging, but not guaranteed with Platform Events. Both offer very high reliability. Fault handling and recovery are fully handled by Salesforce.
C.Both Platform Events and Outbound Messaging are highly scalable. However, unlike Outbound Messaging, only Platform Events have Event Delivery and Event Publishing limits to be considered.

Correct Answer: C

When comparing Platform Events and Outbound Messaging for a near-real-time architecture, a Salesforce Platform Integration Architect must evaluate fundamental differences in their delivery models and governance. While both provide declarative, asynchronous "Fire-and-Forget" capabilities, their technical constraints differ significantly, particularly regarding scalability and platform limits.
The key architectural highlight in this scenario is that Platform Events operate on a specialized event bus with specific Event Publishing and Event Delivery limits. Unlike Outbound Messaging, which is governed by more general daily outbound call limits (often tied to user licenses), Platform Events have a dedicated allocation for the number of events that can be published per hour and delivered in a 24-hour period to external clients via the Pub/Sub API or CometD. For example, the number of concurrent subscribers to a Platform Event channel is typically capped at 2,000 for standard configurations. Since the customer expects
3,000 customers to view these messages, this limit is a critical evaluation point; the architecture would need to account for this gap, perhaps by using middleware to fan out messages to the larger audience.
In contrast, Outbound Messaging does not have an "Event Delivery" limit in the same sense. It is a point-to- point SOAP-based push mechanism where Salesforce manages retries for up to 24 hours if the receiving endpoint is unavailable. However, it is less flexible for multi-consumer scenarios because it requires a separate configuration for every unique destination.
Regarding the other options: Option A is incorrect because neither system strictly guarantees "exactly-once" delivery without the possibility of duplicates; in fact, Outbound Messaging may deliver a message more than once if it doesn't receive a timely acknowledgment. Option B is incorrect because Platform Events do not have built-in "fault recovery" handled by Salesforce in the same way as Outbound Messaging's automatic retry queue; with Platform Events, it is the subscriber's responsibility to use a Replay ID to retrieve missed events within the 72-hour retention window. Therefore, highlighting the unique delivery and publishing limits is the most vital step for the architect.

Question 71

Question 72

Question 73

Question 74

Question 75

Download PDF File