Salesforce Analytics-Con-301 Exam Questions

Comprehensive and Detailed Explanation From Exact Extract:

The problem:

Custom SQL joins two multi-row tables, causing many-to-many duplication.

This artificially multiplies claim costs.

The extract becomes heavy and slow due to Custom SQL.

Tableau's recommended solution:

Use Relationships in the Logical Layer

Instead of physical joins

Tableau resolves many-to-many issues automatically

Query is generated at the appropriate granularity to avoid duplication

This is exactly Option A.

Relationships allow the Claims facts to remain at the claim grain and Members to remain at the member grain. Tableau resolves aggregations correctly, preventing inflated values.

Why the others are incorrect:

B --- Physical Join

Would continue the same duplication problem because multi-row joins multiply rows.

C --- LODs

Would require complex calculations and are error-prone.

They do NOT fix the duplication in the underlying extract.

D --- Table Calculations

Happen after Tableau aggregates the duplicated data --- too late to fix the inflated baseline numbers.

Thus, the only correct and modern solution is relationships.

Relationships documentation explaining resolution of many-to-many granularity issues.

Guidance recommending avoiding Custom SQL for performance reasons.

Logical Layer behavior preventing row-duplication errors.

Comprehensive and Detailed Explanation From Exact Extract:

Tableau Catalog provides multiple features for communicating data quality and freshness.

Data Quality Warnings (DQWs) are part of Catalog's metadata management system and are specifically designed to inform users about data issues, including when data is stale.

There are two visibility levels:

1. Standard Visibility Data Quality Warning

Appears subtly in metadata panels.

Intended for non-critical issues.

Does not guarantee the message will be seen by dashboard viewers.

2. High Visibility Data Quality Warning

Designed for urgent, critical, and highly visible alerts.

Displays a prominent warning indicator directly on connected dashboards, data sources, and workbooks.

Tableau documentation states high-visibility warnings are used when users must be alerted, such as:

Stale data

Incomplete refreshes

Data outages

Because the question emphasizes:

''important to alert dashboard viewers when data has not been refreshed''

A standard warning is not strong enough, but a High Visibility Data Quality Warning is explicitly designed for this scenario.

Evaluation of the choices:

A . Standard Visibility Data Quality Warning --- Not sufficient

It does not force dashboard users to notice the warning.

B . High Visibility Data Quality Warning --- Correct

This option is specifically meant to notify users of critical freshness issues, making it the perfect match for the requirement.

C . Certified Data Source --- Incorrect

Certification communicates trustworthiness, not freshness or alerts.

D . Lineage --- Incorrect

Lineage shows data relationships and dependencies, not refresh warnings.

Conclusion

To alert viewers about stale data in hourly-refreshed dashboards, the consultant must use a High Visibility Data Quality Warning.

Reference From Tableau Catalog Documentation

Description of Data Quality Warnings and their visibility levels.

Definition of High Visibility DQWs as critical alerts shown to dashboard viewers.

Catalog guidelines for stale data detection and communication.

Comprehensive and Detailed Explanation From Exact Extract:

To combine Excel and SQL Server data in the same logical data model, Tableau offers two supported capabilities:

Relationships

Recommended modern method for combining tables from multiple sources.

Supports cross-database relationships between Excel and SQL Server.

Maintains separate physical layers but integrates data at query time.

Cross-Database Joins

Allows joining data from different databases in the physical layer.

Fully supported for Excel + MS SQL Server.

Useful when granular row-level merging is needed.

Why the other options are incorrect:

C . Data Blending

Legacy feature, used only when no direct combination is possible.

Tableau recommends relationships instead.

Produces separate queries and may lose row-level detail.

D . Union

Requires tables to have equivalent structure.

Cannot union Excel with SQL Server unless identical column structure exists.

Not appropriate for most mixed-source reporting.

Therefore, the correct techniques are Relationships and Cross-Database Joins.

Tableau data modeling documentation recommending Relationships for multi-source modeling.

Cross-database join support list including Excel + SQL Server.

Comprehensive and Detailed Explanation From Exact Extract:

Tableau's official generative AI capability---Tableau Pulse and Einstein-powered Tableau AI features---are available only on Tableau Cloud, not Tableau Server.

Key Tableau facts:

Tableau Server (any version, including new ones) does not provide generative AI capabilities.

Tableau Cloud includes AI features such as:

Tableau Pulse

Einstein Copilot

Natural language questions

Automated insights

Upgrading Tableau Server does not provide generative AI.

Extensions and accelerators do not enable AI functionality.

Therefore, the customer must migrate from Tableau Server to Tableau Cloud to leverage generative AI.

Tableau AI/Pulse documentation stating availability only in Tableau Cloud.

Feature comparison charts showing generative AI unavailable on Tableau Server.

Comprehensive and Detailed Explanation From Exact Extract:

Tableau allows certain calculations to be materialized in extracts, meaning they are precomputed and stored inside the .hyper file to improve performance.

According to Tableau's extract documentation:

Materializable calculations must be compatible with the extract engine and must not depend on dynamic, view-based, or post-query logic.

Only row-level calculations and aggregation-level calculations without dependencies on runtime context can be materialized.

Tableau cannot materialize any calculation containing:

Table calculation functions

Functions requiring post-aggregation logic

View-dependent elements

Parameters that need runtime evaluation

Evaluation of the choices:

A . A row-level calculation --- Correct

Row-level calculations operate on each record individually before aggregation.

Tableau documentation specifies that these calculations can be pushed down into the extract and materialized because they do not depend on the visualization or user interaction.

Examples include concatenation, arithmetic, string manipulation, and row-based logic such as:

[Sales] * [Quantity] or IF [Region] = 'West' THEN 1 END

These can be precomputed inside the extract, improving performance.

B . A calculation that contains table calculation functions --- Not allowed

Table calculations (WINDOW_SUM, INDEX, RUNNING_SUM, RANK, etc.) depend on the table structure after aggregation and query execution.

Therefore, Tableau documentation states they cannot be materialized in extracts.

C . A calculation that contains parameters --- Not allowed

Parameters are evaluated at runtime, meaning the user can change their value.

Because of this, Tableau cannot permanently compute and store such a calculation inside an extract.

D . A calculation that contains an aggregation --- Generally not materialized

Aggregated calculations often depend on query context and cannot always be materialized.

Only simple, context-free aggregations might be materialized, but Tableau explicitly warns that aggregations are not guaranteed candidates for extract materialization.

Thus, this is not the best answer compared to row-level logic.

Conclusion

Only row-level calculations meet Tableau's exact requirements for materialization in extracts.

Reference From Tableau Consultant Documentation

Tableau Extract documentation describing materializable calculation types.

Tableau guidance stating table calculations and parameter-dependent calculations cannot be materialized.

Extract optimization guidelines describing row-level logic as eligible for materialization.