Query performance tuning in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Tableau's Query Performance

Which of the following best explains why using Extracts instead of Live Connections can improve query performance in Tableau?

A Live Connections cache data automatically, so extracts are slower.

B Extracts always use more server resources, which speeds up queries.

C Extracts require more network bandwidth, improving query speed.

D Extracts store a snapshot of data locally, reducing the need to query the original database repeatedly.

💡 Hint

Think about where the data is stored and how often Tableau needs to ask the database for information.

Extracts create a local snapshot of the data, so Tableau does not need to send queries to the database each time. This reduces load and speeds up performance.

❓ dax_lod_result

intermediate

Calculating Average Sales per Region with LOD Expressions

Given a Tableau data source with sales data by region and date, which LOD expression correctly calculates the average sales per region regardless of filters?

Tableau

{ FIXED [Region] : AVG([Sales]) }

A { INCLUDE [Region] : SUM([Sales]) }

B { FIXED [Region] : AVG([Sales]) }

C { EXCLUDE [Region] : AVG([Sales]) }

D { FIXED [Date] : AVG([Sales]) }

💡 Hint

Consider which LOD type fixes the calculation at the region level, ignoring filters.

The FIXED LOD expression calculates the average sales per region regardless of other filters, which is what is asked.

❓ visualization

advanced

Optimizing Dashboard Performance

You have a Tableau dashboard with multiple complex visualizations. Which design choice will most improve dashboard load time?

A Use fewer quick filters and replace them with parameter controls.

B Add more detailed tooltips to each visualization.

C Increase the number of worksheets on the dashboard.

D Use live connections for all data sources.

💡 Hint

Think about how filters affect query execution and dashboard rendering.

Quick filters generate additional queries and slow down dashboards. Parameters are static and do not trigger extra queries, improving performance.

🔧 Formula Fix

advanced

Identifying Query Bottlenecks in Tableau

A Tableau dashboard is slow because of a complex join between two large tables. Which approach will most likely improve query performance?

A Create an extract of the joined data to reduce query complexity.

B Add more calculated fields to the dashboard to optimize joins.

C Use live connection and increase the number of quick filters.

D Remove all filters to speed up the dashboard.

💡 Hint

Think about how extracts and joins affect query execution time.

Extracting the joined data reduces the need for complex live queries, improving performance.

🎯 Scenario

expert

Designing a High-Performance Tableau Report for Large Data

You need to build a Tableau report that queries a very large dataset with millions of rows. Which combination of strategies will best optimize query performance?

A Use live connections, avoid extracts, and rely on dashboard actions for filtering.

B Use extracts with full detail data, add many quick filters, and avoid LOD expressions.

C Use extracts with aggregated data, limit quick filters, and optimize calculations with LOD expressions.

D Use live connections, add many quick filters, and create complex calculated fields on the fly.

💡 Hint

Think about reducing data volume, minimizing queries, and efficient calculations.

Aggregated extracts reduce data size, fewer quick filters reduce query load, and LOD expressions optimize calculations, all improving performance.