Tableau-Desktop-Found Connecting to and Preparing Data Practice Question
What is the purpose of the 'Relationships' feature in Tableau's logical layer?
⚠ Common exam trap
Candidates frequently confuse relationships with physical joins, assuming relationships permanently merge tables or force a specific join type for every single visualization regardless of context.
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
✓
To create a flexible, multi-table logical model.
Relationships are dynamic, flexible connections that allow Tableau to join data sources intelligently based on the fields used in a visualization. By preserving the original tables, they prevent data loss (fan-out) and enable context-aware aggregations. Understanding this is essential for modern Tableau users, as it simplifies data modeling compared to the traditional, more rigid physical join methods that often caused data duplication.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To physically merge two tables into one.
Why it's wrong here
Physical merges are performed using Joins in the physical layer of the data source. Relationships are logical associations that do not physically merge the data tables, allowing the original tables to retain their grain and preventing accidental duplication during the analysis of related datasets.
- ✓
To create a flexible, multi-table logical model.
Why this is correct
Relationships allow you to relate tables without merging them physically. This creates a flexible model where Tableau automatically joins only the necessary tables based on the specific fields present in the current visualization, ensuring correct aggregation levels and preventing common issues like data fan-out.
- ✗
To force a strict inner join on all fields.
Why it's wrong here
Relationships are by design not a strict inner join; they act more like a dynamic, context-aware join. They are specifically intended to avoid the pitfalls of strict joins, such as losing unmatched rows or incorrectly inflating metrics, by handling joins at query time.
- ✗
To replace the need for data extracts.
Why it's wrong here
Relationships can be used with both live and extract connections. They are a modeling technique, not a storage engine. They do not replace the performance benefits of extracts, which are storage optimizations designed to store and query data in a high-speed, local compressed format.
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.