An integration architect has built a solution using REST API, updating Account, Contact, and other related information. The data volumes have…

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.