Tableau-Desktop-Found Understanding Tableau Concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  When you need to perform a strict inner join

  Why it's wrong here

  If a strict inner join is required to force data dropping based on missing keys, a physical join remains the appropriate choice. Relationships act more like 'on-demand' joins that preserve all data from the related tables, which may not always align with the strict requirements of an inner join.

• ✓

  When combining tables with different levels of granularity

  Why this is correct

  Relationships are designed to handle different levels of detail effectively. Because they perform joins only when needed during analysis, they prevent the data duplication issues that occur when joining a high-level summary table to a granular transaction table, ensuring that metrics remain accurate at their appropriate levels.

• ✗

  When you need to physical merge two tables into a single extract

  Why it's wrong here

  Physical joins physically merge tables into a single result set in the extract. If the goal is a permanent, static merger at the storage level, physical joins are the correct tool. Relationships keep tables logically separate, which is more flexible but does not result in a single merged table.

• ✗

  When you want to remove unmatched rows from the primary table

  Why it's wrong here

  Relationships perform a 'left join' behavior by default that preserves rows even when no match exists, unless filter logic is applied. If the requirement is to explicitly remove rows that don't have matches, a physical join is required to enforce that specific exclusion behavior at the query level.