Sample question 1 — Connecting and Preparing Data
A data analyst creates a relationship between a Sales fact table and a Date dimension table. The Sales table has 10 million rows; the Date table has 3,650 rows (10 years daily). She wants the relationship to be as performant as possible. Which relationship optimization hint should she configure?
- A. A. Set cardinality to 'Many (Sales) to One (Date)' and set Referential Integrity to 'All Records
- B. B. Set cardinality to 'One to One' to maximize query efficiency between the two tables.
- C. C. Set cardinality to 'Many to Many' to allow Tableau to use a hash join strategy.
- D. D. Referential integrity and cardinality settings don't affect performance — leave them at defaults.
Answer: A. Many-to-One cardinality (many Sales rows per Date) is correct and provides an accurate hint to Tableau's query optimizer. 'All Records Match' for Referential Integrity tells Tableau that every Sales row has a matching Date row — allowing the optimizer to use inner joins instead of outer joins, generating simpler, faster SQL. One-to-One (B) is incorrect for this data model. Many-to-Many (C) uses a less efficient deduplication strategy. Cardinality and RI settings DO affect query performance optimization (D is wrong).
