Question 350
An application treats SQL deadlock victim error as a permanent invalid request and silently discards a legitimate business transaction. Which recommendation best resolves this issue?
Explanation
Correct Answer
A deadlock victim may succeed on retry, but duplicate side effects must be prevented.
Incorrect Answers
Shorten the blocking transaction and move interactive waiting outside its lock-holding interval: locks retained through human interaction unnecessarily serialize otherwise independent requests.
Investigate deadlock graphs and implement targeted transaction, indexing and retry improvements instead of merely raising timeouts: investigate deadlock graphs and implement targeted transaction, indexing and retry improvements instead of merely raising timeouts: longer timeouts do not remove cyclic lock dependencies or guarantee a deadlock victim will succeed.
Standardize the table access order and review indexes and transaction scope to reduce cyclic lock dependencies: standardize the table access order and review indexes and transaction scope to reduce cyclic lock dependencies: deadlocks arise when sessions acquire resources in incompatible cycles; consistent ordering reduces the pattern.



Developing AI-Enabled Database Solutions (DP-800) Practice Tests