What practice supports safe bulk updates of addresses?

What practice supports safe bulk updates of addresses?

• A. One-by-one updates with no reporting
• B. Batch updates with chunked processing
• C. Random updates
• D. Per-record identity confusion

Answer: (B)

Processing bulk updates in batches is essential for safe updates. By updating records in controlled chunks, you keep the load on the database predictable, reducing the risk of timeouts, locks, and contention that can affect other operations. Each batch can be executed within its own transactional boundary, so if something goes wrong, you can roll back just that batch without undoing successful changes from earlier batches. This approach also makes progress visible, supports auditing, and allows retrying only the failed records without reprocessing everything.

Updating records one by one without reporting creates blind spots and is inefficient at scale; it’s hard to monitor, hard to recover from errors, and can take much longer. Random updates lack any predictable order, increasing the chance of conflicts or missing updates. Per-record identity confusion isn’t a valid technique and would undermine data integrity by mixing up identifiers.