A team suggests deleting query history to improve platform performance. What is wrong with this?
Select an answer to reveal the explanation.
Short Explanation
Query history isn't what's slowing your queries. Clearing it throws away the record you need the next time something breaks, and the actual bottleneck is still there in the morning.
Full Explanation
The correct answer is the option stating that deleting query history removes the troubleshooting and audit record without addressing any actual performance bottleneck. Query performance is determined by engine sizing, data layout, statement design and concurrency. Retained execution records are not a bottleneck, so discarding them buys nothing while destroying the evidence used to diagnose problems and answer audit questions. The option claiming query history cannot be deleted under any circumstances is incorrect because the objection is not that removal is impossible; it is that it is the wrong lever. The option claiming deletion forces every engine to restart before queries can resume is incorrect because there is no such restart dependency. The option claiming it causes registered tables to lose their catalog entries is incorrect because catalog registration is independent of execution history. For the exam, treat the history as diagnostic and audit evidence, and look for performance causes in engines, data layout and the statements themselves.