Tableau-Desktop-Found Understanding Tableau Concepts Practice Question
A marketing analyst connects Tableau Desktop to a Microsoft Excel workbook containing a single sheet of campaign records. She wants to build several visualizations without repeatedly re-importing the file, and she needs the workbook's data to remain available inside the Tableau workbook even when the original .xlsx file is moved to an archive folder. Which connection type should she use?
⚠ Common exam trap
The trap here is assuming that any connection to Excel automatically embeds the data, when only an extract actually copies the records into the workbook.
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
✓
Extract connection
An extract stores a compressed snapshot of the source data inside the Tableau workbook, so the visualizations keep working after the original Excel file is relocated. A live connection, a cross-database join, or a server refresh schedule all depend on the source file remaining reachable, which the scenario explicitly rules out by archiving the .xlsx.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Live connection to the Excel workbook
Why it's wrong here
A live connection to Excel keeps Tableau querying the source file each time the view is rendered, so the data is not stored inside the .twb or .twbx. Once the .xlsx file is moved to an archive folder, Tableau can no longer reach the records and the visualizations break, which conflicts with the stated requirement that the data remain available inside the Tableau workbook.
- ✗
Cross-database join to the Excel workbook
Why it's wrong here
A cross-database join lets Tableau combine tables from different source systems in a single data source, but it still requires those sources to be reachable at query time. It does not copy the Excel records into the workbook, so archiving the .xlsx would break the connection and defeat the goal of keeping the data self-contained and reusable.
- ✗
Publish the workbook to Tableau Server and rely on scheduled refresh
Why it's wrong here
Publishing to Tableau Server and scheduling refreshes automates data updates, but the workbook still depends on the Excel file being accessible to the server's refresh process. If the .xlsx is moved to an archive folder that the server cannot reach, refreshes fail and the embedded data goes stale, so this does not satisfy the requirement to keep data available inside the workbook.
- ✓
Extract connection
Why this is correct
An extract creates a hyper file that stores a snapshot of the Excel data inside the Tableau workbook's packaged file, so the visualizations continue to render after the original .xlsx is moved. This matches the analyst's need to avoid re-importing and to keep data available independently of the source file's location, making the extract the right connection choice here.
About these practice questions
One of 126 original Tableau-Desktop-Found practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.