Question 160
A team wants to modify a business entity through a view but discovers a complex multi-table projection is not directly updateable. A stored procedure catches an error yet commits partially completed inventory deductions and returns success to the caller. What is the most appropriate plan for this situation?
Explanation
Correct Answer
First, complex views can lose straightforward update semantics and need explicit mapping of writes. Second, transactional failure handling must preserve atomicity and communicate that the operation did not complete.
Incorrect Answers
Review whether controlled procedures or a suitable INSTEAD OF trigger provide a supported update interface; Move external side effects to a reliable asynchronous integration path and keep the trigger transaction short: transactional failure handling must preserve atomicity and communicate that the operation did not complete.
Make the calculation's assumptions explicit and validate session-sensitive behavior in repeatable integration tests; use TRY/CATCH with transaction rollback and consistent failure signaling so partial business changes are not reported as committed: complex views can lose straightforward update semantics and need explicit mapping of writes.
Review whether controlled procedures or a suitable INSTEAD OF trigger provide a supported update interface.



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