Tableau-Desktop-Found Connecting to and Preparing Data Practice Question
Exhibit
ERROR: Unable to create extract. The data source contains a circular dependency.
Refer to the exhibit. You are attempting to join several tables in a physical layer and receive the error shown. What is the most likely cause?
⚠ Common exam trap
Candidates often assume the error is due to missing join keys or incorrect data types, overlooking the logical structure of their schema which may contain circular dependencies preventing a valid join path.
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
✓
You have joined tables in a way that creates an infinite loop
A circular dependency occurs when tables are linked in a way that creates an infinite loop or a closed path of joins. In the physical layer, Tableau requires a linear or hierarchical structure. This error is common when users create complex join paths that don't follow a logical, tree-like hierarchy, and resolving it requires simplifying the join structure or using relationships instead of physical joins.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The data files are too large for the extract engine
Why it's wrong here
File size is unrelated to circular dependency errors. Circularity refers to the logical structure of your join keys, not the volume of records. Tableau's extract engine is highly scalable and handles massive datasets, so you should focus on the schema logic rather than the physical file size.
- ✓
You have joined tables in a way that creates an infinite loop
Why this is correct
Circular dependencies are caused by join logic where Table A connects to B, B to C, and C back to A. This creates a loop that the database engine cannot resolve. You must restructure the joins to be linear or use relationships, which handle multi-table links much better.
- ✗
The primary keys are missing from all tables
Why it's wrong here
While primary keys are good practice for performance, their absence will not cause a circular dependency error. The error specifically addresses the topological structure of the join connections, not the quality or presence of keys within the underlying database schema or the flat file structure.
- ✗
The join condition involves incompatible data types
Why it's wrong here
Incompatible data types result in join failures or empty sets, but they do not cause a 'circular dependency' error. A circular dependency is a structural issue regarding how the tables are connected to one another, which is independent of the specific values or types within the columns.
Visual reference
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.