Databricks-DA-Assoc Creating Dashboards and Visualizations Practice Question
Exhibit
Refer to the exhibit.
[ { "id": 1, "type": "bar", "y_axis": "sales", "x_axis": "date" }, { "id": 2, "type": "line", "y_axis": "revenue", "x_axis": "date" } ]Refer to the exhibit. An analyst notices that widget 2 is displaying incorrect trends. Based on the configuration provided, what is the most likely cause?
⚠ Common exam trap
Candidates often look for complex syntax errors in the SQL code rather than checking whether the underlying aggregation levels match the visualization axes.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The query for widget 2 does not aggregate data to match the X-axis.
The configuration shows that both widgets share the same X-axis ('date'), but they are visualizing different metrics ('sales' vs 'revenue'). If the data is aggregated at different levels or filtered differently, the trends might appear conflicting. Identifying mismatches between data sources and visualization axes is a common troubleshooting step for analysts, ensuring that the dashboard accurately reflects the underlying business logic and prevents misleading interpretations of the reported data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The widget type is set to 'line' instead of 'bar'.
Why it's wrong here
Choosing 'line' versus 'bar' is a stylistic choice and does not inherently make a trend 'incorrect'. While some trends are better shown with one type than the other, the type setting alone does not cause a calculation or data display error in the underlying values of the trend line.
- ✗
The X-axis for widget 2 is not properly aligned to the date range.
Why it's wrong here
The exhibit explicitly shows that widget 2 is configured with the 'date' X-axis. Unless there is a data quality issue in the source table, the X-axis configuration itself is valid. If the trend is wrong, the issue likely lies within the query logic or the aggregation method.
- ✓
The query for widget 2 does not aggregate data to match the X-axis.
Why this is correct
If the query does not group by the 'date' column, the visualization may attempt to plot raw, un-aggregated data points, leading to a jagged or incorrect trend line. For a time-based chart, the SQL query must include an appropriate 'GROUP BY' clause to ensure the visualization displays the correct trend.
- ✗
The 'revenue' column is incompatible with the 'line' chart type.
Why it's wrong here
Revenue is a numerical value, which is perfectly compatible with line charts. Line charts are actually the preferred visualization for revenue trends over time. There is no technical incompatibility between a numerical metric and a line chart that would lead to an incorrect trend display in this context.
About these practice questions
One of 291 original Databricks-DA-Assoc practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DA-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DA-Assoc exam.