Cross-database joins in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Cross-Database Joins in Tableau

Which statement best describes how Tableau handles cross-database joins?

A Tableau requires exporting all data into a single database before joining tables from different sources.

B Tableau combines data from different databases by creating a temporary in-memory join during query execution.

C Tableau cannot join tables from different databases directly; it only supports blending.

D Tableau duplicates all data from one database into the other to perform the join.

💡 Hint

Think about how Tableau processes data without moving it permanently.

Tableau performs cross-database joins by creating a temporary in-memory join at query time, allowing seamless combination of data from different sources without data duplication.

❓ dax_lod_result

intermediate

Result of Cross-Database Join with Filters

Given two tables from different databases joined in Tableau: Sales and Products. Sales has 1000 rows, Products has 100 rows. After applying a filter on Products to only include category 'Electronics' (20 products), how many rows will the joined result contain?

A All 1000 sales rows where the product is in 'Electronics' category, approximately 200 rows.

B All 1000 sales rows regardless of product category.

C Only 20 rows, one for each product in 'Electronics'.

D Exactly 1000 rows, but with nulls for non-matching products.

💡 Hint

Consider how the join and filter on the product table affect the sales rows.

The join filters sales rows to those matching products in the 'Electronics' category. If about 20% of sales are for electronics, the result will be about 200 rows.

❓ data_modeling

advanced

Designing Efficient Cross-Database Joins

You have two large tables from different databases: Orders (5 million rows) and Customers (500,000 rows). You want to join them in Tableau. Which design choice will optimize performance?

A Join without filters and use calculated fields to filter after joining.

B Use a full outer join to keep all data from both tables.

C Duplicate the Customers table into the Orders database before joining.

D Use an inner join on customer ID and apply filters to reduce data before joining.

💡 Hint

Think about reducing data volume before joining.

Applying filters before joining reduces the data volume, improving join performance. Inner join limits rows to matching keys, which is efficient.

🔧 Formula Fix

advanced

Troubleshooting Nulls in Cross-Database Join

After creating a cross-database join between Orders and Customers on Customer ID, many rows in the Orders table show nulls for customer fields. What is the most likely cause?

A The join type is left join from Customers to Orders, causing unmatched Orders rows to show nulls.

B The data source connection for Customers is broken, so fields cannot load.

C Customer IDs in Orders do not match any IDs in Customers, causing nulls in joined fields.

D Tableau does not support cross-database joins with Customer ID keys.

💡 Hint

Consider data quality and matching keys.

If Customer IDs in Orders do not exist in Customers, the join will produce nulls for customer fields in those rows.

❓ visualization

expert

Visualizing Cross-Database Join Results

You joined Sales data from a SQL Server database with Marketing Campaigns data from a cloud database using a cross-database join in Tableau. You want to create a dashboard showing total sales by campaign and campaign start date. Which visualization approach best follows best practices?

A Use a line chart with campaign start date on x-axis and total sales on y-axis, grouping by campaign.

B Use a pie chart showing total sales per campaign and a separate table listing campaign start dates.

C Use a scatter plot with campaign start date on x-axis and total sales on y-axis, with campaign names as labels.

D Use a bar chart with campaigns on the x-axis, total sales on the y-axis, and campaign start date as a color gradient.

💡 Hint

Think about how to show trends over time and compare campaigns clearly.

A line chart with campaign start date on the x-axis and total sales on the y-axis grouped by campaign clearly shows sales trends over time per campaign, following best visualization practices.