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 questionsLarge 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.
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.
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.
Keep practicing
Take the free SHARING-AND-VISIBILITY-DESIGNER practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other SHARING-AND-VISIBILITY-DESIGNER practice questions
- Question 1Universal Containers is a fast-growing company that sells containers globally. It has tho…
- Question 2Universal Containers uses 75,000 distributors that have close to 1 million total users. D…
- Question 3Universal Containers would like to create a custom team solution that can be used on a cu…
- Question 4Universal Containers has a private sharing model on Accounts. Apex Managed Sharing is req…
- Question 5Universal Containers keeps product brochures in Salesforce as files. Sarah shares a publi…
- Question 6What is the best practice for testing sharing and visibility changes?
