What are three reasons to use joins instead of relationships? (Choose three.)

Question

Options

• AYou need to use a specific join type.
• BYou need to create an extract that will have multiple tables.
• CYou need to use row-level security.
• DYou need to use a data model that supports shared dimensions.
• EYou need to connect to multiple databases.

• A
  86% (19)
• B
  5% (1)
• E
  9% (2)

Explanation

In Tableau, Joins operate at the physical layer and give you explicit, fixed control over how tables are combined - unlike Relationships, which are flexible and context-aware. A is correct because Joins let you specify the exact join type (inner, left, right, full outer), whereas Relationships handle joins dynamically without letting you control the type directly. C is correct because row-level security requires physical-layer filtering that joins enable - Relationships work at a higher logical level and lack that granular security control. D is correct because when building a data model with shared dimensions (e.g., a star schema where multiple fact tables share a date or product dimension), Joins give you explicit physical-layer control over how those shared tables connect.

B is wrong because multi-table extracts are actually a strength of Relationships, not Joins - Joins collapse everything into a single flat table. E is wrong because connecting to multiple databases is a cross-database capability that applies to both Joins and Relationships and isn't a distinguishing reason to prefer Joins.

Memory tip: Think "JRS Controls" - Join type, Row-level security, Shared dimensions - these are the three cases where you need the explicit, physical-layer control that only Joins provide.

No community discussion yet for this question.