Performance considerations in Tableau - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an extract for better performance in Tableau.

Tableau

CREATE EXTRACT [1] FROM data_source

Drag options to blanks, or click blank then click option'

ADATA

BFAST

CTABLE

DTABLEAU

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'FAST' or 'TABLEAU' instead of 'TABLE' causes syntax errors.

Trying to extract 'DATA' is too vague and incorrect.

In Tableau, creating an extract from a table improves performance by reducing live queries.

2fill in blank

medium

Complete the Tableau calculation to limit data for faster dashboard loading.

Tableau

IF [Order Date] [1] DATE("2023-01-01") THEN [Sales] ELSE 0 END

Drag options to blanks, or click blank then click option'

A=

B<=

C!=

D>=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<=' would include older dates, not limiting data.

Using '!=' or '=' filters incorrectly and may exclude needed data.

Using >= filters data to only include orders from 2023 onward, improving performance.

3fill in blank

hard

Fix the error in the Tableau LOD expression to calculate average sales per customer.

Tableau

{ FIXED [Customer ID] : AVG([1]) }

Drag options to blanks, or click blank then click option'

A[Sales]

BSales

CSUM([Sales])

DAVG([Sales])

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting brackets causes syntax errors.

Using aggregation inside LOD causes wrong calculations.

The correct syntax uses the field name with square brackets: [Sales].

4fill in blank

hard

Fill both blanks to optimize Tableau dashboard performance by reducing data and aggregation.

Tableau

SUM(IF [Region] [1] "West" THEN [Sales] ELSE 0 END) / COUNTD([2])

Drag options to blanks, or click blank then click option'

A=

B!=

C[Customer ID]

D[Order ID]

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' includes unwanted regions.

Counting [Order ID] may not reflect customer aggregation.

Filtering region with = 'West' limits data. Counting by [Customer ID] aggregates correctly.

5fill in blank

hard

Fill all three blanks to create a calculated field that improves performance by filtering and aggregating sales.

Tableau

SUM(IF [Category] [1] "Furniture" AND [Sales] [2] 1000 THEN [3] ELSE 0 END)

Drag options to blanks, or click blank then click option'

A=

B>

C[Sales]

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' filters wrong sales values.

Not summing [Sales] causes calculation errors.

Filter category with = 'Furniture', sales greater than 1000, and sum the [Sales] field.

Practice

1. Which of the following is a simple way to improve Tableau dashboard performance?

easy

A. Increase the number of worksheets in the dashboard

B. Add more filters to the dashboard

C. Use complex nested calculations

D. Use data extracts instead of live connections

Solution

1. Step 1: Understand data connection types

   Data extracts are snapshots of data stored locally, which load faster than live connections querying databases in real-time.

2. Step 2: Compare impact of filters and calculations

   Adding more filters or complex calculations slows performance, while extracts speed it up.

3. Final Answer:

   Use data extracts instead of live connections -> Option D

4. Quick Check:

   Extracts improve speed = A [OK]

Hint: Choose extracts over live connections for faster dashboards [OK]

Common Mistakes:

• Thinking more filters always improve performance
• Believing complex calculations run faster
• Assuming more worksheets speed up dashboards

2. Which Tableau feature syntax is correct for creating an extract?

easy

A. Data > Extract Data > Click 'Extract'

B. File > Export > Extract Data

C. Worksheet > Create Extract

D. Dashboard > Extract > New

Solution

1. Step 1: Recall Tableau menu paths

   Extracts are created via the Data menu by selecting 'Extract Data' and then clicking 'Extract'.

2. Step 2: Verify other options

   Other menu paths do not exist or are incorrect for extract creation.

3. Final Answer:

   Data > Extract Data > Click 'Extract' -> Option A

4. Quick Check:

   Correct extract creation path = D [OK]

Hint: Extracts are created from the Data menu in Tableau [OK]

Common Mistakes:

• Looking under File or Dashboard menus for extract options
• Confusing export with extract
• Trying to create extracts from worksheets

3. Given a dashboard with 3 filters and 5 complex calculations, what is the likely impact on performance?

medium

A. Dashboard will load faster due to filters

B. No impact on performance

C. Performance will slow down due to complex calculations and filters

D. Performance improves with more calculations

Solution

1. Step 1: Understand filter and calculation effects

   Each filter and complex calculation requires processing, increasing load time.

2. Step 2: Combine effects on dashboard speed

   Multiple filters plus complex calculations compound and slow dashboard performance.

3. Final Answer:

   Performance will slow down due to complex calculations and filters -> Option C

4. Quick Check:

   More filters + complex calcs = slower performance [OK]

Hint: More filters and complex calcs usually slow dashboards [OK]

Common Mistakes:

• Assuming filters always speed up dashboards
• Ignoring calculation complexity
• Believing performance is unaffected by dashboard elements

4. You notice your Tableau dashboard is slow. Which of these is a likely cause and fix?

medium

A. Using live connection with many filters; switch to extract and reduce filters

B. Using extracts with no filters; add more filters to speed up

C. Using simple calculations; replace with complex calculations

D. Dashboard has few worksheets; add more worksheets to improve speed

Solution

1. Step 1: Identify performance bottlenecks

   Live connections with many filters cause slow queries and dashboard lag.

2. Step 2: Apply fixes

   Switching to extracts reduces query time; reducing filters lowers processing load.

3. Final Answer:

   Using live connection with many filters; switch to extract and reduce filters -> Option A

4. Quick Check:

   Extracts + fewer filters = faster dashboards [OK]

Hint: Switch live to extract and cut filters to fix slow dashboards [OK]

Common Mistakes:

• Adding filters to speed up
• Replacing simple with complex calculations
• Adding worksheets to improve speed

5. You have a large dataset and a slow dashboard. Which combined approach best improves performance?

hard

A. Use extracts, add many filters, and complex calculations

B. Use extracts, limit filters, and simplify calculations

C. Use live connection, add many filters, and complex calculations

D. Use live connection, no filters, and complex calculations

Solution

1. Step 1: Analyze dataset size and dashboard speed

   Large datasets slow dashboards especially with live connections and complex processing.

2. Step 2: Combine best practices

   Extracts reduce data load time, fewer filters reduce query complexity, and simple calculations reduce processing.

3. Final Answer:

   Use extracts, limit filters, and simplify calculations -> Option B

4. Quick Check:

   Extracts + fewer filters + simple calcs = best speed [OK]

Hint: Combine extracts, fewer filters, simple calcs for best speed [OK]

Common Mistakes:

• Adding many filters with extracts
• Using live connections for large data
• Relying on complex calculations