Blending data sources in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Primary and Secondary Data Sources in Tableau

In Tableau, when blending data from two sources, which statement correctly describes the role of the primary data source?

A The primary data source is only used to join tables before blending.

B The primary data source defines the view's structure and drives the filters and calculations.

C The primary data source is ignored if the secondary source has more records.

D The primary data source automatically duplicates all fields from the secondary source.

💡 Hint

Think about which data source controls the main visualization layout.

The primary data source in Tableau controls the view's structure, including filters and calculations. The secondary source provides additional data linked by common fields.

❓ dax_lod_result

intermediate

Result of a Tableau Data Blend with Different Granularity

Suppose you blend two data sources in Tableau: Source A has daily sales data, and Source B has monthly targets. If you create a view by day using Source A and blend Source B on month, what will happen to the target values?

A The monthly target value will be duplicated for each day in that month.

B The target value will be averaged across all days automatically.

C The target value will be null for all days except the first day of the month.

D The target value will be summed across all months.

💡 Hint

Consider how Tableau matches data when blending at different levels of detail.

When blending data at different granularities, Tableau duplicates the secondary source's value for each matching primary source row. Here, the monthly target repeats for each day.

❓ visualization

advanced

Choosing the Best Visualization for Blended Data

You have blended sales data from two sources: one with product details and another with regional targets. You want to show actual sales vs. target by region and product category. Which visualization best communicates this comparison clearly?

A A scatter plot with sales on X-axis and product category on Y-axis.

B A pie chart showing total sales by product category only.

C A line chart showing sales trends over time without target data.

D A stacked bar chart showing sales and target side by side for each region and category.

💡 Hint

Think about how to compare two related measures across categories and regions.

A stacked bar chart side by side for sales and target allows easy comparison across regions and categories, making differences clear.

🔧 Formula Fix

advanced

Troubleshooting Null Values in Blended Data

After blending two data sources in Tableau on the field 'Customer ID', you notice many null values in the secondary source fields. What is the most likely cause?

A The 'Customer ID' field has mismatched data types or formatting between the two sources.

B The primary data source has missing records for some customers.

C Tableau does not support blending on fields named 'Customer ID'.

D The secondary source is set as primary by mistake.

💡 Hint

Check how the linking field matches between sources.

Nulls often occur when the linking field values do not match exactly due to data type or formatting differences, causing no join match.

🎯 Scenario

expert

Designing a Data Blend for Performance and Accuracy

You need to blend a large transactional sales dataset with a smaller customer demographic dataset in Tableau. The sales data updates daily, and the demographic data updates monthly. How should you design the blend to optimize performance and ensure accurate reporting?

A Use the demographic data as primary source and blend sales data, filtering sales to last month only.

B Join both datasets outside Tableau before import to avoid blending.

C Use the sales data as primary source and blend the demographic data on Customer ID, filtering demographic data to latest month only.

D Blend both sources without filters and aggregate sales data at monthly level.

💡 Hint

Consider update frequency and data size when choosing primary source and filters.

Using the larger, frequently updated sales data as primary and filtering the smaller demographic data to the latest month reduces data volume and keeps reports accurate and performant.

Practice

1. What is the main purpose of blending data sources in Tableau?

easy

A. To create a single table by merging all data sources permanently

B. To combine data from different sources using common fields without merging tables

C. To replace the primary data source with a secondary one

D. To export data from Tableau to external databases

Solution

1. Step 1: Understand blending concept

   Blending connects data from different sources using common fields without merging them permanently.

2. Step 2: Compare options

   To combine data from different sources using common fields without merging tables correctly describes blending. Options A, C, and D describe other unrelated actions.

3. Final Answer:

   To combine data from different sources using common fields without merging tables -> Option B

4. Quick Check:

   Blending = combine without merging [OK]

Hint: Blending links data without merging tables [OK]

Common Mistakes:

• Confusing blending with joining or merging tables
• Thinking blending replaces the primary source
• Assuming blending exports data

2. Which of the following is the correct way to identify the linking field in Tableau data blending?

easy

A. The field with a red cross in the primary data source

B. The field with a blue checkmark in the secondary data source

C. The field with a green plus sign in the primary data source

D. The field with an orange chain link icon in the secondary data source

Solution

1. Step 1: Recognize linking field icon

   In Tableau, linking fields in the secondary data source show an orange chain link icon.

2. Step 2: Match options to icons

   The field with an orange chain link icon in the secondary data source correctly identifies the orange chain link icon as the linking field. Other options describe incorrect icons or colors.

3. Final Answer:

   The field with an orange chain link icon in the secondary data source -> Option D

4. Quick Check:

   Linking field = orange chain link icon [OK]

Hint: Look for orange chain link icon for linking fields [OK]

Common Mistakes:

• Confusing linking field icon with checkmarks or plus signs
• Looking for icons in the primary instead of secondary source
• Ignoring icon colors

3. Given two data sources: Primary with fields OrderID, Sales and Secondary with fields OrderID, CustomerName. If you blend on OrderID and create a view showing Sales and CustomerName, what will happen if an OrderID exists only in the secondary source?

medium

A. The view will exclude that OrderID because it is missing in the primary source

B. The view will show Sales as null and CustomerName for that OrderID

C. The view will show Sales and CustomerName as null

D. The view will cause an error and not display

Solution

1. Step 1: Understand primary source control

   In blending, the primary source controls the rows shown. If an OrderID is missing in primary, it won't appear.

2. Step 2: Analyze missing OrderID in primary

   Since the OrderID exists only in secondary, it will be excluded from the view.

3. Final Answer:

   The view will exclude that OrderID because it is missing in the primary source -> Option A

4. Quick Check:

   Primary source controls rows = missing keys excluded [OK]

Hint: Primary source controls rows shown in blending [OK]

Common Mistakes:

• Expecting secondary-only keys to appear in the view
• Thinking null values appear for missing primary keys
• Assuming blending causes errors on missing keys

4. You blended two data sources on CustomerID. However, the secondary data source fields show Null values in your view. What is the most likely cause?

medium

A. You forgot to refresh the data sources

B. The primary data source is missing the CustomerID field

C. The linking field CustomerID has mismatched data types between sources

D. The secondary data source is set as primary by mistake

Solution

1. Step 1: Check linking field compatibility

   Blending requires linking fields to have matching data types to join correctly.

2. Step 2: Identify cause of nulls

   If data types differ, Tableau cannot match keys, causing nulls in secondary fields.

3. Final Answer:

   The linking field CustomerID has mismatched data types between sources -> Option C

4. Quick Check:

   Matching data types needed for linking fields [OK]

Hint: Check data types of linking fields if nulls appear [OK]

Common Mistakes:

• Assuming missing fields cause nulls instead of mismatched types
• Confusing primary and secondary source roles
• Ignoring need to refresh data

5. You have two data sources: SalesData (Primary) with OrderID, SalesAmount and CustomerData (Secondary) with CustomerID, OrderID, Region. You want to create a view showing total sales by region. How should you blend and aggregate the data correctly?

hard

A. Blend on OrderID, use Region from secondary, and create a calculated field summing SalesAmount grouped by Region

B. Blend on CustomerID, use Region from secondary, and sum SalesAmount without grouping

C. Join the two sources on OrderID instead of blending, then sum SalesAmount by Region

D. Blend on Region, then sum SalesAmount grouped by OrderID

Solution

1. Step 1: Identify correct linking field

   OrderID exists in both sources and links sales to customer region.

2. Step 2: Blend on OrderID and aggregate

   Blend on OrderID, use Region from secondary, then sum SalesAmount grouped by Region for total sales by region.

3. Final Answer:

   Blend on OrderID, use Region from secondary, and create a calculated field summing SalesAmount grouped by Region -> Option A

4. Quick Check:

   Blend on OrderID + sum Sales by Region [OK]

Hint: Blend on common key, aggregate sales by region [OK]

Common Mistakes:

• Blending on wrong field like CustomerID or Region
• Not grouping sales by region
• Confusing blending with joining