Universal Containers (UC) needs to move millions of records from an external enterprise resource planning (ERP) system into Salesforce. What should a data architect recommend to be done while using the Bulk API in serial mode instead of parallel mode?
A.
Placing 20 batches on the queue for upset jobs.
B.
Inserting 1 million orders distributed across a variety of accounts with potential lock exceptions.
C.
Leveraging a controlled feed load with 10 batches per job.
D.
Inserting 1 million orders distributed across a variety of accounts with lock exceptions eliminated and managed.
D.
Inserting 1 million orders distributed across a variety of accounts with lock exceptions eliminated and managed.
Explanation
The Bulk API serial mode processes records sequentially rather than concurrently, specifically to manage and minimize record-locking issues. In scenarios involving multiple records associated with the same accounts or related objects, lock contention can severely degrade performance. Option D explicitly handles the complexity by distributing records and eliminating lock exceptions effectively through sequential processing. Option B doesn't manage locks explicitly, potentially causing issues, while options A and C don't specifically address locking issues. Serial mode is specifically recommended for high-lock scenarios, ensuring performance stability during large migrations or data loads.