Identify Poorly Performing Queries in the Databricks Intelligence Platform, Such as Query Insights, Query Profiler Log, Etc. DATA-ANALYST-ASSOCIATE Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   Which of the following is a common sign of a poorly performing query?

   • AHigh cache hit ratio
   • BLow CPU utilization
   • CSmall number of tasks
   • DExcessive shuffles
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   When reading the Query Profiler log, what does a 'stage' represent?

   • AThe final result of the query
   • BA collection of tasks that can be executed in parallel
   • CA single operation on a single row
   • DThe entire query execution plan
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A data analyst is troubleshooting a query that is slow in production. Query Insights shows the query has a high total execution time. To find the root cause, the analyst opens the Query Profiler log and sees that a specific stage has a very long duration. What is the most effective next step to pinpoint the issue within that stage?

   • ARe-run the query on a larger cluster to see if the stage duration improves.
   • BLook at the task-level metrics within that stage in the Query Profiler log to see if a few tasks are outliers.
   • CReview the audit log to see who ran the query and when.
   • DCheck the Query Insights page for other queries that ran at the same time to see if there was contention.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   What type of information is captured in the Query Profiler log?

   • AThe results of the query
   • BThe user credentials of everyone who ran queries
   • CThe SQL text of all queries run in the workspace
   • DDetailed execution statistics such as stages, tasks, and operators
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A data analyst is reviewing a query in Query Insights that is taking much longer than expected. The metrics show that 'Execution Time' is low, but 'Wait Time' is very high. What does this combination of metrics most likely indicate?

   • AThe query is performing an excessive number of shuffles, causing network congestion.
   • BThe query is spending most of its time waiting for resources, such as cluster capacity or I/O, rather than actively computing.
   • CThe query is CPU-bound and needs more cores to run faster.
   • DThe query has a data skew problem that is causing some tasks to run much longer than others.
   Reveal Solution Discussion Select an answer first