Tableau-Desktop-Found Connecting to and Preparing Data Practice Question
You are connecting Tableau Desktop to a large transactional database containing millions of rows. You need to improve workbook performance and reduce query load on the live database during exploratory analysis. What is the most effective connection and data storage strategy to achieve this?
⚠ Common exam trap
Candidates suggest using live connections to keep data fresh, ignoring that this causes severe performance degradation on large datasets. They fail to recognize extracts as the standard solution for scale.
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
✓
Convert the connection to an extract and store the resulting hyper file locally
Creating a Tableau extract compresses the data, stores it locally, and utilizes columnar storage technology, which significantly enhances query performance for large datasets. This approach reduces network latency and frees up transactional database resources. While live connections ensure real-time accuracy, extracts are the industry standard for optimizing desktop performance during complex exploratory analysis sessions involving millions of rows.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Switch the connection type to Live and apply custom SQL with heavy aggregation
Why it's wrong here
Custom SQL with heavy aggregation still executes against the live database on each interaction, so query load and latency remain. Live connections suit small datasets or real-time freshness requirements; the stem's millions of rows and reduced load demand an extract, which materialises data locally.
- ✗
Maintain a live connection and enable serial execution mode for all queries
Why it's wrong here
Serial execution mode forces queries to run one at a time, adding latency without reducing load on the live database; it addresses concurrency, not data volume. A live connection still pushes every exploratory query to the transactional system. An extract would be correct here, storing a local snapshot to cut query load.
- ✓
Convert the connection to an extract and store the resulting hyper file locally
Why this is correct
A Tableau extract materialises the query results into a local hyper file, so exploratory analysis reads from that columnar in-memory store rather than issuing repeated queries against the live transactional database, directly reducing query load and improving workbook performance.
- ✗
Use an incremental refresh schedule on a live connection without creating an extract
Why it's wrong here
Incremental refresh applies only to extracts; a live connection issues queries against the source on every interaction, so no schedule reduces database load or speeds exploration. Extracts with incremental refresh suit large datasets needing periodic updates, but the stem requires reduced live query load during exploration.
About these practice questions
This Tableau-Desktop-Found question is part of Courseiva's 126-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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 Tableau (Salesforce) exam blueprint
This Tableau-Desktop-Found practice question is part of Courseiva's free Tableau (Salesforce) 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 Tableau-Desktop-Found exam.