Live vs extract connections in Tableau - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Live Connection Behavior

Which of the following statements best describes a live connection in Tableau?

A Data is queried directly from the source every time you interact with the visualization.

B Data is imported once and stored in Tableau's fast in-memory engine.

C Data is copied to a local file and refreshed only on demand.

D Data is aggregated and stored in a cloud database automatically.

💡 Hint

Think about how Tableau accesses data when you make changes in your dashboard.

A live connection means Tableau sends queries directly to the original data source each time you interact with the dashboard, ensuring up-to-date data but possibly slower performance.

🧠 Conceptual

intermediate

Extract Connection Characteristics

What is a key advantage of using an extract connection in Tableau?

A It requires a constant internet connection to the data source.

B It allows real-time data updates without manual refreshes.

C It automatically syncs data changes from the source instantly.

D It improves performance by storing a snapshot of data locally in a compressed format.

💡 Hint

Think about how extracts help speed up Tableau dashboards.

Extracts store a snapshot of the data locally in a compressed, optimized format, which improves performance but requires manual or scheduled refreshes to update.

🎯 Scenario

advanced

Choosing Between Live and Extract for a Large Dataset

You have a very large sales database that updates hourly. Your Tableau dashboard users want fast response times and reasonably fresh data. Which connection type should you choose?

A Use a live connection to always get the freshest data despite slower performance.

B Use an extract connection refreshed once a day to maximize performance.

C Use an extract connection refreshed every hour to balance speed and data freshness.

D Use a live connection with no caching to ensure data accuracy.

💡 Hint

Consider both data freshness and dashboard speed.

Refreshing extracts hourly provides a good balance between performance and data freshness for large datasets that update frequently.

🔧 Formula Fix

advanced

Troubleshooting Slow Dashboard Performance

Your Tableau dashboard connected live to a slow database is running very slowly. Which action will most likely improve performance?

A Switch to an extract connection and schedule regular refreshes.

B Use a live connection but disable caching.

C Disable data source filters to reduce query complexity.

D Increase the number of live queries sent simultaneously.

💡 Hint

Think about how extracts affect query speed.

Using extracts stores data locally in an optimized format, reducing query time and improving dashboard responsiveness compared to live connections to slow databases.

❓ visualization

expert

Visualizing Data Freshness Impact

You want to create a dashboard showing the impact of connection type on data freshness and performance. Which visualization best communicates this comparison?

A A pie chart showing percentage of live vs extract connections used.

B A scatter plot with connection type on X-axis, data freshness on Y-axis, and point size representing performance speed.

C A line chart showing data freshness over time for only extract connections.

D A bar chart comparing total data volume for live connections only.

💡 Hint

Think about how to show two variables and one measure together clearly.

A scatter plot can show connection type categories on one axis, data freshness on another, and use point size to represent performance speed, making the trade-offs clear.

Practice

1. Which statement best describes a live connection in Tableau?

easy

A. It only works with Excel files and not databases.

B. It stores a snapshot of data for faster access and offline use.

C. It shows real-time data directly from the source without storing a copy.

D. It requires manual data entry to update the dashboard.

Solution

1. Step 1: Understand live connection concept

   A live connection accesses data directly from the source in real-time without storing a copy.

2. Step 2: Compare with extract connection

   Extract connections store data snapshots for speed and offline use, unlike live connections.

3. Final Answer:

   It shows real-time data directly from the source without storing a copy. -> Option C

4. Quick Check:

   Live connection = real-time data [OK]

Hint: Live = real-time data, Extract = stored snapshot [OK]

Common Mistakes:

• Confusing extract with live connection
• Thinking live connections store data locally
• Assuming live connections work offline

2. Which of the following is the correct way to create an extract connection in Tableau?

easy

A. Click 'Data' > 'New Data Source' > Select 'Live' option

B. Click 'Data' > 'Extract Data' and save the snapshot

C. Use 'Refresh Data' to update live connection

D. Connect only to Excel files for extract

Solution

1. Step 1: Identify extract creation steps

   Extracts are created by selecting 'Extract Data' from the Data menu and saving a snapshot.

2. Step 2: Eliminate incorrect options

   Click 'Data' > 'New Data Source' > Select 'Live' option is for live connections, C is for refreshing live data, D is incorrect as extracts support many sources.

3. Final Answer:

   Click 'Data' > 'Extract Data' and save the snapshot -> Option B

4. Quick Check:

   Extract = 'Extract Data' option [OK]

Hint: Extract = 'Extract Data' menu option in Tableau [OK]

Common Mistakes:

• Choosing 'Live' instead of 'Extract' option
• Confusing refresh with extract creation
• Thinking extracts only work with Excel

3. If you have a slow database but need fast dashboard performance, which connection type should you choose in Tableau?

medium

A. Extract connection to improve speed

B. Manual data entry for accuracy

C. Live connection to get real-time data

D. No connection, use static images

Solution

1. Step 1: Analyze performance needs

   Slow databases cause delays with live connections, hurting dashboard speed.

2. Step 2: Choose connection type for speed

   Extract connections store data locally, improving performance despite slow sources.

3. Final Answer:

   Extract connection to improve speed -> Option A

4. Quick Check:

   Slow source + speed need = Extract [OK]

Hint: Slow source? Use extract for faster dashboards [OK]

Common Mistakes:

• Choosing live connection despite slow source
• Thinking manual entry is faster
• Ignoring extract refresh needs

4. You created an extract but the dashboard shows outdated data. What is the most likely cause?

medium

A. You forgot to refresh the extract after data changed

B. Live connection was used instead of extract

C. The data source is offline

D. Tableau does not support extracts

Solution

1. Step 1: Understand extract behavior

   Extracts are snapshots and do not update automatically without refresh.

2. Step 2: Identify cause of outdated data

   If data changed but extract wasn't refreshed, dashboard shows old data.

3. Final Answer:

   You forgot to refresh the extract after data changed -> Option A

4. Quick Check:

   Extract needs refresh to update [OK]

Hint: Extracts need refresh to show new data [OK]

Common Mistakes:

• Assuming extracts auto-update
• Confusing live and extract connections
• Ignoring data source availability

5. You need a Tableau dashboard that updates every hour with fresh data but must also work if the database is temporarily offline. What is the best connection strategy?

hard

A. Use a live connection with no extract

B. Use a live connection only for real-time data

C. Use manual data entry to update hourly

D. Use an extract connection with hourly refresh schedule

Solution

1. Step 1: Analyze requirements

   Dashboard needs fresh data every hour and offline availability if database is down.

2. Step 2: Evaluate connection options

   Live connection fails if database is offline; extract with scheduled refresh meets both needs.

3. Step 3: Choose best strategy

   Extract connection with hourly refresh updates data regularly and works offline.

4. Final Answer:

   Use an extract connection with hourly refresh schedule -> Option D

5. Quick Check:

   Fresh + offline = Extract with refresh [OK]

Hint: Extract + scheduled refresh = fresh and offline-ready [OK]

Common Mistakes:

• Choosing live connection ignoring offline need
• Thinking manual entry is practical
• Not scheduling extract refresh