CERTIFIED-DATA-ANALYST-ASSOCIATE · Question #15
CERTIFIED-DATA-ANALYST-ASSOCIATE Question #15: Real Exam Question with Answer & Explanation
The correct answer is A: Go to the Query History tab and click on the text of the query. The slideout shows if the results. Option A is correct because Databricks SQL's Query History tab is the designated place to inspect query execution details. When you click on a specific query's text, a slideout panel appears that includes metadata about how the query was executed - including whether the results w
Question
How can a data analyst determine if query results were pulled from the cache?
Options
- AGo to the Query History tab and click on the text of the query. The slideout shows if the results
- BGo to the Alerts tab and check the Cache Status alert.
- CGo to the Queries tab and click on Cache Status. The status will be green if the results from the
- DGo to the SQL Warehouse (formerly SQL Endpoints) tab and click on Cache. The Cache file will
- EGo to the Data tab and click Last Query. The details of the query will show if the results came
Explanation
Option A is correct because Databricks SQL's Query History tab is the designated place to inspect query execution details. When you click on a specific query's text, a slideout panel appears that includes metadata about how the query was executed - including whether the results were served from cache rather than computed fresh.
The distractors describe features or tabs that either don't exist in Databricks SQL or don't serve this function: there is no "Cache Status" alert in an Alerts tab (B), no "Cache Status" button under a Queries tab (C), no cache file viewable from the SQL Warehouse tab (D), and the Data tab does not surface query execution metadata like cache status (E) - these are all invented or misplaced interfaces.
Memory tip: Think "History = How it happened." The Query History tab tells you the history of how results were retrieved - including whether the cache did the heavy lifting. If you want to know what happened with a query, Query History is always your first stop.
Community Discussion
No community discussion yet for this question.