Which two ways should a developer working on a data loading integration that operates between different Salesforce environments insert multiple related records in one call or transaction? Choose 2 answers
The correct selection is A, C. REST sObject Tree is designed for nested parent-child creation, while REST Composite can chain subrequests and reference IDs returned by earlier subrequests. Both reduce round trips and can create related records in one request structure; Bulk API and Streaming API serve different workload patterns. From a build perspective, the implementation should be source-driven, reviewable, automatable, and modular. Engineering controls such as version control, package boundaries, static analysis, coding standards, and isolated development environments reduce defects early and make changes easier to understand, test, and promote. The remaining options are weaker because they address symptoms after code is written instead of improving the build process through automation, modularity, and explicit development standards. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (A. REST API SObject Tree Request; C. REST API Composite Request). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.
Study Guide reference: Building --- Salesforce DX; package development; coding standards; static analysis; source control; secure development.