Question 860
Service calls time out while CPU remains low and many sessions wait on locks. Initial testing shows: Wait chains clear and transaction latency stabilizes. Which limitation should the team still consider?
Explanation
Correct Answer
Killing a transaction can create lengthy rollback and data-side effects. DMVs can expose blocking sessions, wait types and transaction states.
Incorrect Answers
That residual-risk statement assumes an invalid guarantee: Blocking is about lock ownership and transaction lifetime; inspect DMVs/wait chains before changes.
This limitation misstates what the feature provides: Use request/transaction DMVs and waiting-resource evidence; termination may trigger lengthy rollback.
This is not the governing limitation because Execution-plan analysis can complement lock investigation but does not substitute for live wait and blocker evidence. That assertion removes or misidentifies the relevant residual risk and does not follow from the feature semantics.