Data relationships model in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Tableau Data Relationships

In Tableau, what is the main advantage of using a data relationship model over a traditional join?

A It permanently merges all tables into one large table before analysis, reducing query time.

B It disables filtering between tables to avoid data duplication.

C It allows Tableau to maintain the original tables separately and combine data only when needed, improving performance and flexibility.

D It requires all tables to have the same number of rows to work correctly.

💡 Hint

Think about how Tableau handles data at query time versus data preparation time.

Data relationships keep tables separate and combine them only when needed, which helps Tableau optimize queries and handle different levels of detail.

❓ dax_lod_result

intermediate

Result of a Relationship Filter in Tableau

Given two tables: Orders and Customers related by CustomerID, if you filter Customers to only those in 'USA', what happens to the Orders table in a relationship model?

A Only Orders with CustomerID in USA are included in the view.

B All Orders are shown regardless of Customer location.

C Orders table is filtered first, then Customers are filtered.

D The filter causes an error because relationships do not support filtering.

💡 Hint

Consider how filters propagate through relationships in Tableau.

Filters on one table in a relationship propagate to related tables, so filtering Customers to USA limits Orders to those customers.

❓ data_modeling

advanced

Modeling Many-to-Many Relationships

You have three tables: Students, Courses, and Enrollments. Students and Courses have a many-to-many relationship through Enrollments. How should you model this in Tableau using relationships?

A Create a relationship only between Students and Courses, ignoring Enrollments.

B Join Students and Courses directly on StudentID and CourseID.

C Merge all three tables into one flat table before importing to Tableau.

D Create relationships from Students to Enrollments and from Courses to Enrollments, keeping all tables separate.

💡 Hint

Think about how to represent many-to-many relationships without losing detail.

Using Enrollments as a bridge table with relationships to Students and Courses preserves many-to-many details and allows flexible analysis.

🔧 Formula Fix

advanced

Troubleshooting Incorrect Aggregation in Relationships

You created relationships between Sales and Products tables. When you add Product Category and sum of Sales Amount to a view, the totals are incorrect and inflated. What is the most likely cause?

A The Products table has missing Product Category values causing nulls.

B The relationship is many-to-many and Tableau is duplicating sales when aggregating by category.

C The Sales Amount field is not numeric, causing aggregation errors.

D The relationship is inactive and needs to be activated manually.

💡 Hint

Consider how many-to-many relationships affect aggregation.

Many-to-many relationships can cause duplication in aggregation because multiple product rows relate to the same sales row, inflating sums.

🎯 Scenario

expert

Designing a Flexible Sales Dashboard with Relationships

You need to build a sales dashboard that shows sales by region, product, and time. The data source has separate tables for Sales, Regions, Products, and Dates. You want to allow users to filter by any dimension without duplicating data or creating complex joins. What is the best approach using Tableau's data relationships?

A Create relationships from Sales to Regions, Products, and Dates tables, keeping them separate and letting Tableau combine data dynamically.

B Join all tables into one large table before importing to Tableau to simplify filtering.

C Use data blending instead of relationships to connect the tables.

D Create calculated fields in Sales to replicate Regions and Products data for filtering.

💡 Hint

Think about how Tableau relationships optimize performance and flexibility.

Using relationships keeps tables separate, avoids data duplication, and allows flexible filtering across dimensions without complex joins.