Home / Data Analyst practice test / Analyzing Queries / Question

Databricks Data Analyst Associate · free practice question

A data analyst clicks on a query in Query History and notices that the Query Profile panel shows 'Query profile is not available' for that execution. What is…

Exam-style question on Analyzing Queries from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Analyzing Queries

A data analyst clicks on a query in Query History and notices that the Query Profile panel shows 'Query profile is not available' for that execution. What is the MOST likely reason for this message?

  1. AThe query ran for less than five seconds, and Databricks generates a Query Profile once a query passes a minimum duration threshold, which avoids profiling overhead on short-running operations
  2. BThe query finished successfully within the normal time range, and a Query Profile is retained for queries that produced an error or exceeded a configurable slow-query threshold on the warehouse
  3. CThe analyst lacks CAN MANAGE permission on the SQL warehouse that ran the query, and Query Profiles are shown to workspace administrators and to users holding warehouse-level CAN MANAGE access
  4. DThe query was written in Python (PySpark) rather than SQL, and the Query Profile captures statements submitted through the SQL editor in SQL syntax, leaving out notebook-based Python executions
  5. EThe query result was served from the query cache instead of being executed on the SQL warehouse, and a query answered from the cache produces no execution metrics from which to build a profile
Answer & explanation

Correct answer: E

WHY E: The documentation states that a Query Profile is not available for queries that run from the query cache. To bypass the cache and get a fresh profile, the analyst makes a trivial change to the query, such as altering or removing the LIMIT clause.

WHY NOT A: There is no documented minimum duration for generating a Query Profile; short queries produce profiles when they are actually executed.

WHY NOT C: Viewing a profile requires being the query owner or having CAN MONITOR (not CAN MANAGE) on the warehouse, and a missing permission is not what this message indicates.

WHY NOT D: Query Profiles are also accessible from notebooks attached to SQL warehouses or serverless compute, not just from the SQL editor.

WHY NOT B: Query Profiles are generated for successfully completed queries; the cache, not the success or failure status, is what suppresses the profile.

Take the full Data Analyst practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Analyst Associate practice test. Take it and get a section-by-section score.

Start the free test →