Analytics-Con-301 Exam Questions & Answers

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.

To minimize user impact and costs while migrating from Tableau Server to Tableau Cloud with multiple sites, the best solution is:

Single Tableau Cloud Instance with Multiple Projects: Instead of multiple sites which could imply higher management overhead and possibly higher costs, configuring one Tableau Cloud instance with different project folders for each former site (Finance, Strategy, Marketing) is most efficient.

Benefits: This setup maintains organizational separation of data and access similar to having different sites but leverages the unified management and simplicity of a single cloud instance. It reduces complexity in user access management and integration points.

Implementation: Each project folder acts like a mini-site within the larger instance, where specific permissions and content can be managed independently, akin to the original server setup but within a single cloud-based environment.

Reference

This recommendation is in line with best practices for cloud migration focusing on consolidation and cost efficiency, as suggested in Tableau's official documentation for cloud migration strategies.

Comprehensive and Detailed Explanation From Exact Extract:

Key details from the scenario:

The dashboard is on a command center screen.

The environment cannot access the internet.

The data source is real-time (live).

The dashboard must keep itself refreshed automatically.

No human interaction should be required.

From Tableau's documentation:

Dashboard Extension API

Tableau's Extension API allows developers to create custom extensions that can automate refreshing a live dashboard at intervals.

The extension is hosted on the company's internal web server, which solves the ''no internet access'' limitation.

This is the only method in the listed options that:

Works offline

Can auto-refresh the dashboard

Supports a ''screen-based'' live monitoring use case

Uses the existing live connection (no need for extracts)

Thus, A is correct.

Why the other options are wrong:

B. Schedule a Prep Flow

Prep flows do not refresh dashboards.

They only refresh prepared data sources.

The dashboard still won't auto-update unless reopened.

C. Download an extension from Tableau Exchange

Tableau Exchange requires internet access, which the company does not have.

Also, ''sandboxed extensions'' cannot refresh the dashboard at timed intervals.

D. Use extracts and scheduled extract refresh

Extracts require:

A Tableau Server / Cloud schedule

Internet access for Cloud

And extracts are not real-timeThis contradicts the requirement for real-time data and an offline environment.

The Workbook Optimizer is a tool specifically designed to evaluate a workbook against performance best practices. It provides feedback on key design characteristics and offers concrete guidance on how to improve workbook performance. This tool is beneficial for both new and experienced Tableau users to ensure their dashboards are optimized for performance1.

To minimize the impact on users when reverting to a previous version of a published data source in Tableau Server, the consultant should use the built-in revision history feature. By selecting a previous version from the revision history and clicking 'Restore', the data source will revert to that version without the need for a full server backup restoration or manual recreation of the data source. This process is quick and has the least amount of disruption to users.