SF-PD2 Performance Practice Question
A developer is building a high-performance REST API integration. Which of the following is the most important practice for ensuring the integration handles high throughput?
⚠ Common exam trap
Test-takers frequently choose standard single-record REST endpoints instead of batch-oriented resources when asked about high-throughput integrations.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Utilize the Composite API to batch multiple operations.
High throughput requires minimizing the cost per request. By using bulk-enabled API endpoints, such as the Bulk API or Composite resources, a developer can process multiple records in a single request. This reduces the overhead of authentication, network latency, and server-side processing, allowing the integration to scale efficiently and stay well within the organization's API request limits, which is vital for high-volume data synchronization scenarios.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use individual REST API calls for every record update.
Why it's wrong here
Individual REST calls for every record are extremely inefficient and will quickly exhaust the daily API request limit. Each call incurs significant overhead, making this approach non-scalable for high-throughput integrations where thousands of records need to be synced in a timely manner without impacting other system operations.
- ✓
Utilize the Composite API to batch multiple operations.
Why this is correct
The Composite API allows developers to combine multiple SObject operations into a single request. This drastically reduces the number of API calls needed to sync large datasets, minimizing the impact on API limits and reducing the network latency associated with multiple round-trips to the Salesforce server.
- ✗
Disable all triggers during the integration process.
Why it's wrong here
Disabling triggers is a dangerous practice that bypasses critical business logic, validations, and data integrity checks. It is not a sustainable performance strategy and could lead to corrupted data or inconsistent states in the org, which are far more costly to fix than the performance overhead of triggers.
- ✗
Increase the API timeout duration to five minutes.
Why it's wrong here
Extending timeouts does not improve throughput; it only hides latency issues. If an API call is taking five minutes, the underlying logic is inefficient. Increasing the timeout will likely cause threads to be held open longer, potentially leading to resource contention and further slowing down the system overall.
About these practice questions
This SF-PD2 question is part of Courseiva's 226-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-PD2 practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-PD2 exam.