Question 890
An Azure SQL application suddenly has higher latency after its transaction volume triples and resource metrics show sustained compute saturation. What should the SQL developer do next?
Explanation
Correct Answer
Capacity planning should follow CPU, IO and workload measurements rather than an untested tier upgrade.
Incorrect Answers
Load-test representative concurrency and distinguish resource saturation from transaction blocking before choosing a fix: load-test representative concurrency and distinguish resource saturation from transaction blocking before choosing a fix: single-user latency does not predict contention or service capacity under production load; Compare the measured demand with the database service tier and scale or optimize according to the actual bottleneck.
Fix connection pooling and idle session handling and tune limits only after measuring concurrent capacity: fix connection pooling and idle session handling and tune limits only after measuring concurrent capacity: unbounded client sessions can consume resources without improving transaction throughput; Compare the measured demand with the database service tier and scale or optimize according to the actual bottleneck.
Inspect temporary storage usage and query operators, then optimize sort/worktable demand and supported tempdb configuration: inspect temporary storage usage and query operators, then optimize sort/worktable demand and supported tempdb configuration: tempdb pressure can reflect workload design rather than an external network problem; Compare the measured demand with the database service tier and scale or optimize according to the actual bottleneck.



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