Question 360
A developer wants to synchronize an incoming batch into a master table without duplicate key races. Which implementation step most directly addresses this requirement?
Explanation
Correct Answer
Upsert patterns must account for concurrency, unique constraints and platform-specific MERGE limitations. Use a tested transactional upsert with proper uniqueness and locking rather than blind MERGE assumptions. Parallel imports do not create duplicates or silently lose updates.
Incorrect Answers
That change leaves the underlying defect unresolved: Isolation, uniqueness and deployment-specific MERGE behavior must be tested under concurrency.
The proposed implementation creates the wrong boundary because Validate source keys and conflict rules before transactional update/insert processing.
This step would not produce the required behavior: Uniqueness prevents duplicate rows, not lost updates; apply version checks and contention tests. This alternative omits a necessary contract or control and leaves the tested failure path open.