A query that succeeded last week now runs far longer, and the team wants to compare the two executions. Which feature supports this?
Select an answer to reveal the explanation.
Short Explanation
You need query history, the record of what actually ran and how it went. Comparing today's execution to last week's is exactly the job it exists for.
Full Explanation
The query history feature retains prior executions with their details, which is what makes a before-and-after comparison possible: the same statement, two runs, and the differences between them. The storage billing report is incorrect because it aggregates cost and cannot attribute a slowdown to a particular execution. The data manager is incorrect because registration timestamps say when a table was catalogued, not how a query behaved. The access control screens are incorrect because they define entitlement; they are not an execution record. For the exam, route troubleshooting of query behaviour to query history rather than to billing or governance screens.