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.

Practice

1. What is the primary purpose of using Tableau's Performance Recorder?

easy

A. To schedule data refreshes

B. To identify slow queries and dashboard actions for optimization

C. To export data to Excel

D. To create new visualizations automatically

Solution

1. Step 1: Understand Performance Recorder's role

   Performance Recorder tracks how long queries and dashboard actions take to run.

2. Step 2: Identify its main use

   This helps users find slow parts to improve dashboard speed.

3. Final Answer:

   To identify slow queries and dashboard actions for optimization -> Option B

4. Quick Check:

   Performance Recorder = Identify slow parts [OK]

Hint: Performance Recorder finds slow dashboard parts fast [OK]

Common Mistakes:

• Thinking it creates visualizations
• Confusing it with data export tools
• Assuming it schedules refreshes

2. Which of the following is the correct way to enable Performance Recorder in Tableau?

easy

A. Use the Data menu to activate Performance Recorder

B. Right-click on a worksheet and select 'Enable Performance Recorder'

C. Click on Dashboard > Performance Settings > Enable

D. Go to Help > Settings and Performance > Start Performance Recording

Solution

1. Step 1: Locate Performance Recorder in Tableau menus

   Performance Recorder is started from the Help menu under Settings and Performance.

2. Step 2: Confirm correct menu path

   The correct path is Help > Settings and Performance > Start Performance Recording.

3. Final Answer:

   Go to Help > Settings and Performance > Start Performance Recording -> Option D

4. Quick Check:

   Performance Recorder start = Help menu [OK]

Hint: Performance Recorder starts from Help menu [OK]

Common Mistakes:

• Looking under Data or Dashboard menus
• Right-clicking worksheet expecting option
• Assuming a separate settings panel

3. Consider a Tableau dashboard with many filters applied on live data. Which change is most likely to improve query performance?

medium

A. Replace live connection with an extract

B. Add more filters to narrow data further

C. Use complex calculated fields for filtering

D. Increase the number of worksheets in the dashboard

Solution

1. Step 1: Understand impact of live connections

   Live connections query the database every time, which can be slow with many filters.

2. Step 2: Use extracts to improve speed

   Extracts store data locally and speed up queries by reducing database load.

3. Final Answer:

   Replace live connection with an extract -> Option A

4. Quick Check:

   Extracts speed queries better than live connections [OK]

Hint: Use extracts to speed up slow live queries [OK]

Common Mistakes:

• Adding more filters increases query time
• Complex calculations slow performance
• More worksheets increase load, not reduce

4. You notice your Tableau dashboard is slow. You see this calculation: IF [Sales] > 1000 THEN [Profit] ELSE 0 END. What is a likely fix to improve performance?

medium

A. Replace the calculation with a simple filter on Sales > 1000

B. Add more nested IF statements

C. Use a string function instead of IF

D. Remove all filters from the dashboard

Solution

1. Step 1: Analyze calculation impact

   Calculations inside dashboards can slow queries, especially row-by-row IF statements.

2. Step 2: Simplify by filtering data first

   Filtering data before calculations reduces rows processed and speeds performance.

3. Final Answer:

   Replace the calculation with a simple filter on Sales > 1000 -> Option A

4. Quick Check:

   Filtering before calculation improves speed [OK]

Hint: Filter data before calculations to boost speed [OK]

Common Mistakes:

• Adding more IFs increases complexity
• Using string functions unrelated to numeric filters
• Removing filters can increase data load

5. A Tableau dashboard uses multiple data sources with complex joins and many filters. Performance is poor. Which combined approach best improves query speed?

hard

A. Increase dashboard size and add more worksheets

B. Keep live connections but add more calculated fields

C. Use extracts for data sources, reduce filters, and simplify joins

D. Remove extracts and rely only on live data

Solution

1. Step 1: Identify performance bottlenecks

   Complex joins and many filters slow queries, especially on live data sources.

2. Step 2: Apply combined fixes

   Using extracts reduces database load, fewer filters reduce query complexity, and simpler joins speed data retrieval.

3. Step 3: Avoid opposite actions

   Adding calculated fields or more worksheets increases load; removing extracts loses speed benefits.

4. Final Answer:

   Use extracts for data sources, reduce filters, and simplify joins -> Option C

5. Quick Check:

   Extracts + fewer filters + simple joins = faster queries [OK]

Hint: Combine extracts, fewer filters, simpler joins for best speed [OK]

Common Mistakes:

• Adding more calculated fields slows performance
• Increasing dashboard size adds load
• Removing extracts loses caching benefits