When integrating high-security back-office systems like an Enterprise Billing System (EBS) and a Document Management System (DMS) with Salesforce, the primary concern for an Integration Architect is maintaining the integrity of the organization's existing security perimeter. In an enterprise landscape with over 10 million customers, these systems are typically governed by strict regulatory and compliance standards (such as PCI-DSS or GDPR) that dictate who can view financial records.
The consultant must consider Enterprise security needs for access to these systems rather than simply attempting to synchronize credentials. This involves evaluating an Identity Federation strategy using protocols like SAML 2.0 or OpenID Connect. Instead of maintaining a separate silo of authentication details within Salesforce (which creates a security risk and administrative overhead), Salesforce should act as a Service Provider (SP) that trusts a central Identity Provider (IdP).1234 Furthermore, the "seamle5ss access" requirement implies that once a support agent is authenticated into Salesforce, their identity should be propagated to the EBS and DMS to authorize the specific 6view of a7 customer's bill. This is often achieved through Single Sign-On (SSO) and Token-Based Authentication8. By prioritizing the enterprise security framewo9rk, the architect ensures that access is auditable, centralized, and compliant with corporate policies, while providing th10e "360-degree" view required by support agents without forcing them to log in to multiple disconnected systems. Migrating such massive systems (Option A) into Salesforce is technically and financially unfeasible for most enterprises due to data volume and specialized processing logic.

For a unified service experience between Salesforce Service Cloud and B2C Commerce (formerly Demandware), Salesforce provides a purpose-built, cross-cloud solution known as the Salesforce B2C Commerce to Service Cloud Connector.
This connector is part of the Salesforce B2C Solution Architecture and is designed to provide "out-of-the-box" synchronization of data between the two platforms. By implementing this connector, service agents gain several high-value capabilities within the Service Console:
Customer Profile Sync: Ensures that customer data (name, address, etc.) is consistent across both systems.
Order History View: Allows agents to see real-time order data from the Commerce system directly within the Case record page.
Order on Behalf Of: Enables agents to place orders for customers without leaving Salesforce.
While you could build a custom integration using the Commerce REST API (Option B) or MuleSoft (Option C), these would require significant development, testing, and maintenance effort. The Salesforce B2C Connector is the recommended "path of least resistance" because it leverages Salesforce's own pre-built logic for cross-cloud interoperability, reducing technical debt and time-to-value. For an architect, choosing the standard1 connector ensures better supportability and future-proofing 2as Salesforce continues to enhance its multi-cloud features.

To design a robust and scalable integration architecture, a Salesforce architect must first define the technical scope and "plumbing" of the data flow.
The most critical details for solving integration architecture needs include:
Source and Target Systems: Identifying which systems are involved determines the available APIs (REST, SOAP, etc.) and the necessary security protocols.
Directionality: Knowing whether the integration is unidirectional (Salesforce to System X) or bidirectional is vital for managing record mastering and avoiding "infinite loops" in data synchronization.
Data Volume & Transformation Complexity: High volumes may require asynchronous batch processing via the Bulk API, while complex transformations (e.g., mapping custom external IDs to Salesforce Account Numbers) may necessitate a middleware layer like MuleSoft to act as the "central nervous system".
Option A focuses on UI/UX and licensing, which are general program concerns rather than architectural integration requirements. Option C deals with project management and governance, which are important for execution but do not inform the choice between a Request-Reply or Fire-and-Forget pattern. By focusing on systems, data direction, and transformation complexity, the architect can select the correct pattern and tools that satisfy business requirements while staying within platform limits.

When proposing Platform Events as an integration mechanism, an architect must ensure that the security model is correctly configured to allow for the publication and subscription of events. Unlike standard objects, Platform Events have specific permission requirements for the "Integration User" or any system entity interacting with the event bus.
For an external system to subscribe to a Platform Event stream (via CometD or the Pub/Sub API), the user account used to authenticate the connection must have the "Read" permission on the specific Platform Event entity. Similarly, if the external system needs to publish events back into Salesforce, the user must have "Create" permissions. These permissions are typically managed through a Profile or a Permission Set assigned to the Integration User.
Regarding the other options, Option A is incorrect because Platform Events are designed for asynchronous communication. They are inherently decoupled; the external system does not need the same uptime as Salesforce. High-volume platform events are stored in the event bus for 72 hours, allowing an external system to "catch up" using a Replay ID once it comes back online. Option C is also incorrect because Platform Events follow a Publish/Subscribe pattern. Salesforce "broadcasts" the event to the bus without needing to know which specific external systems are listening. This decoupling is a primary advantage of event-driven architecture, as it allows for a "one-to-many" distribution model where multiple systems can consume the same message without additional configuration within Salesforce. Thus, ensuring the correct object-level permissions (Read/Create) is the most critical technical consideration for the architect to guarantee successful message delivery.

When designing high-volume integrations, the Salesforce Platform Integration Architect must distinguish between standard REST resources and "Composite" resources to optimize API consumption. The Salesforce REST API provides several composite resources to group multiple operations into a single call, thereby reducing the overhead of multiple HTTP requests and helping to stay within daily API limits.
According to Salesforce documentation on Composite Resources, the sObject Tree resource (/services/data/vXX.X/composite/tree/) is specifically designed to handle multiple records in a single request. While it is primarily marketed for creating complex hierarchies (parent-child relationships), it has a unique limit that allows for up to 200 records to be processed in a single call. These records can even be unrelated records of the same type. This is a significant advantage over the standard Batch and Composite resources.
The Composite resource and the Batch resource both have a much lower limit of 25 subrequests per call. While each subrequest in a Batch call could technically be a collection operation, the question specifically asks for the resource that natively supports the "200 records" threshold preferred for bulk-style updates within the REST framework. By utilizing the sObject Tree resource, the architect can bundle 200 record updates into a single transaction, effectively reducing API consumption by a factor of 200 compared to individual REST calls. This aligns with the requirement to avoid major architectural changes (like switching to the Bulk API 2.0) while solving the immediate problem of exceeding daily governor limits. In the context of the Integration Architect exam, understanding these specific payload limits is crucial for selecting the most efficient "Request-Reply" or "Data Synchronization" pattern.