CERTIFIED-DATA-ANALYST-ASSOCIATE · Question #83
CERTIFIED-DATA-ANALYST-ASSOCIATE Question #83: Real Exam Question with Answer & Explanation
The correct answer is C: Save the SQL statement as a Query. Saving as a Query (C) is the right approach because queries are designed to store reusable SQL statements that can be visualized as counters, tables, or charts - making them the building block for dashboards. A Dashboard (A) is a collection of visualizations, not a place to store
Question
A data analyst has opened up the SQL Editor page and written a new SQL statement. The data analyst now wants to save that statement to easily refer back to it later to add it to a dashboard. The results of the SQL statement must be able to be displayed as a counter, table, or a data visualization. Which approach should the data analyst use to accomplish this task?
Options
- ASave the SQL statement as a Dashboard
- BSave the SQL statement within a Notebook
- CSave the SQL statement as a Query
- DSave the SQL statement in the Query History page
Explanation
Saving as a Query (C) is the right approach because queries are designed to store reusable SQL statements that can be visualized as counters, tables, or charts - making them the building block for dashboards. A Dashboard (A) is a collection of visualizations, not a place to store raw SQL; you'd build a dashboard from queries, not save SQL directly into one. A Notebook (B) is for exploratory analysis combining text, code, and results, but it's not the standard mechanism for saving reusable, dashboard-ready SQL. Query History (D) is a read-only log of previously executed statements - you can view past queries there, but it's not a save destination.
Memory tip: Think of it as a pipeline - write a Query, build a Dashboard from it. History is just a log, Notebooks are for exploration.
Community Discussion
No community discussion yet for this question.