Databricks Certified Data Analyst Associate free question 2 / 10 · Domain 2: Managing Data
A data science team queries the table sales.orders every day from notebooks that run Python, while the BI team uses saved queries in the SQL editor. On the table's Insights tab, only the BI team's queries appear under Frequent queries. Why?
- Notebook queries are listed after they are saved into a SQL file.
- Notebook reads are counted under Frequent notebooks instead of as queries.
- The queries on the Insights tab are limited to those run in Databricks SQL.
- Python queries are hidden unless the notebook owner shares them publicly.
Show the answer and explanation
Answer: C
Why this is correct
A note on the table insights page says that the queries listed on the Insights tab are limited to queries performed using Databricks SQL, and the limitations section adds that the frequent queries metric only captures saved queries in the SQL editor. The BI team's saved queries meet both conditions. The data science team's Python in notebooks does not, so their daily reads are not listed under Frequent queries, even though they use the table more often than the BI team.
Why the other options are wrong
"Notebook queries are listed after they are saved into a SQL file." … The page states where listed queries come from: queries on the Insights tab are limited to those performed using Databricks SQL, and the frequent queries metric captures saved queries in the SQL editor. A SQL file is neither.
"Python queries are hidden unless the notebook owner shares them publicly." … Query permissions matter for the viewer: you need CAN VIEW on a query to see it, and you will not see queries you lack permission to view. That rule hides saved Databricks SQL queries from some viewers; it does not explain why notebook Python never appears.
"Notebook reads are counted under Frequent notebooks instead of as queries." … Frequent notebooks is a separate section of the tab, so notebooks can show up there. That section does not change the rule for the Frequent queries list, which is defined by where the query was run, not by a choice between two lists.
Reading the tab correctly
Viewing frequent queries and user data needs SELECT on the table, USE SCHEMA and USE CATALOG on its parents, and CAN VIEW on the Databricks SQL queries themselves. An empty or short query list therefore says little about how much a table is used from notebooks; the other sections of the tab give a broader picture.