SHARING-AND-VISIBILITY-DESIGNER practice question 18 of 30

Which two options can help mitigate the risks of import failures associated with large-volume bulk data loads? Choose 2 answers.

Full set: 212 questions
Answer options
A: Minimize user group hierarchy.
B: Defer​​Sharing​​Calculation. Correct answer
C: Increase batch size.
D: Group records by ParentID within a batch. ​ Correct answer
Correct Answer:
B. Defer​​Sharing​​Calculation.; D. Group records by ParentID within a batch. ​
Explanation

Large bulk loads can be stalled by record-level sharing recalculations and database-row locking.
B. Deferring Sharing Calculation suspends recalculations during the load, preventing CPU spikes and time-outs.
D. Grouping rows that share the same ParentId keeps related records in the same batch, greatly reducing locking collisions and “UNABLETOLOCKROW” errors, which are the most common source of bulk-load failures.

Why Incorrect

A. User-role hierarchy depth affects sharing, not bulk API processing; reducing it does not mitigate load failures.
C. Increasing batch size raises, rather than lowers, the likelihood of lock contention and failed batches.

References

1. Bulk API Developer Guide v57.0, “Performance and Locking Considerations”, pp. 24-26 – recommends grouping by ParentId.

2. Salesforce Help: “Suspend/Resume Sharing Calculations”, Record-Level Access Performance, para. 2 – describes deferring sharing before large data operations.

Scroll to Top