A client has a dashboard that renders in less than 10 seconds. The client receives a request to add a new calculated field that will return TRUE if a Project contains any one of the values "Project 1" or "Project 2" and FALSE otherwise. After adding the function found below, the dashboard's render time increases to 14 seconds from 10 seconds.
[Project] = 'Project 1' OR [Project] = 'Project 2'
Which function should the consultant use to reduce the render time?
Comprehensive and Detailed Explanation From Exact Extract:
Tableau documentation states that IN expressions are optimized internally for better query performance than multiple OR statements. They are pushed efficiently to the data source and simplified during query compilation.
The original expression uses two OR conditions, which increases the complexity of row-level evaluation:
[Project] = 'Project 1' OR [Project] = 'Project 2'
Tableau's performance guidelines recommend replacing multiple OR comparisons with an IN expression whenever possible:
[Project] IN ('Project 1', 'Project 2')
This reduces rendering time by minimizing row evaluation overhead and creating a cleaner, optimized logical condition.
Option D achieves this exactly.
Option A is logically incorrect because a project cannot simultaneously equal both values.
Option B is syntactically incorrect because IN expects a list, not an OR inside the list.
Option C is simply a reformatting of the original OR expression and provides no performance improvement.
Option D is the only valid, optimized solution.
Tableau calculation optimization guidance recommending IN over OR for performance.
Tableau's query performance notes indicating that OR statements expand logical branches and slow down evaluation.
Best practices for row-level calculations suggesting simplified logical expressions.
A performance recording of a workbook shows that a query to an extracted data source is taking too long.
Which area should the consultant focus on optimizing if "Executing Query" is taking a long time?
Comprehensive and Detailed Explanation From Exact Extract:
In Tableau Performance Recording, ''Executing Query'' refers to the amount of time Tableau spends executing the SQL or hyper query generated by the workbook. When an extract is used, the query is executed against the .hyper extract, not the original database.
Tableau documentation identifies several causes of slow query execution within extracts, including:
Nested row-level calculations
Complex logic in calculated fields
Multiple Levels of Detail (LOD) expressions
Non-optimized expressions that force Tableau to compute additional temporary tables
These directly increase query complexity and cause longer ''Executing Query'' durations.
Therefore, optimizing the query requires simplifying or replacing:
Nested calculations
Unnecessary LOD expressions
Complex expressions that increase the workload on the extract engine
Option A is incorrect because the number of VizQL processes affects concurrency, not query execution time.
Option B is partially relevant, but dashboard filters affect the overall workload, not the specific query complexity. If the performance recording shows ''Executing Query'' as the slow section, the query itself (not the filter UI layer) is the problem.
Option D does not apply because extracts use the hyper engine, not the underlying database. Optimizing the original database structure does not change the extract query execution time.
Thus, the consultant should focus on simplifying nested calculations and LODs to reduce extract query complexity.
Tableau Performance Recording guide describing ''Executing Query'' as dependent on calculation complexity.
Tableau extract engine documentation explaining that nested logic, multiple LODs, and granular calculations generate slower extract queries.
Best practices recommending simplification of calculated fields to improve extract query performance.
A client has a Tableau Cloud deployment. Currently, dashboards are available only to internal users.
The client needs to embed interactive Tableau visualizations on their public website.
Data is < 5,000 rows, updated infrequently via manual refresh.
Cost is a priority.
Which product should the client use?
Comprehensive and Detailed Explanation From Exact Extract:
Tableau documentation explains:
Tableau Public
Free platform.
Allows public sharing and embedding of fully interactive dashboards.
Ideal for small datasets and infrequent updates.
Does not require user-based licensing.
Embedding is unrestricted because all content is publicly visible.
This perfectly matches the scenario:
Public-facing website
Low cost priority
Small dataset
Manual, infrequent updates
Why the other options are incorrect:
A . Tableau Cloud (per user)
Requires paid licenses.
Does not allow unrestricted public embedding without expensive add-ons.
Designed for secure internal use, not public web-wide embedding.
C . Tableau Embedded Analytics
A paid embedding solution requiring proper licensing.
Designed for large-scale, secure, programmatic embedding --- too costly for this use case.
D . Tableau Server (per core)
Requires server infrastructure & licensing.
Far more expensive than Tableau Public.
Thus, Tableau Public is the correct, cost-effective solution.
Tableau Public documentation describing free embedding for public websites.
Comparison guides showing Tableau Cloud/Server require licensing for embedding.
Public vs. Enterprise Tableau deployment best practices.
A client has a sales dataset that contains fields named Customer ID, Region, Item, and Sales Amount. Each row represents a single sale. There may be multiple sales for each Customer ID.
The client wants to visualize the average total customer sales by region.
Which Level of Detail (LOD) expression should a consultant recommend?
Comprehensive and Detailed Explanation From Exact Extract:
The requirement is:
Compute total sales per customer, not per transaction.
Then compute the average of those customer totals, grouped by region.
Tableau documentation states that FIXED LOD expressions are used to calculate values at a specific level of granularity regardless of the view.
To solve the business need:
Step 1:
Calculate total customer sales for each Customer ID within each Region:
{ FIXED [Customer ID], [Region] : SUM([Sales Amount]) }
This produces one number per customer per region.
Step 2:
Compute the average of those totals:
AVG( { FIXED [Customer ID], [Region] : SUM([Sales Amount]) } )
This yields:
Average total customer sales by region
This is exactly option C.
Why the other options are incorrect:
A . EXCLUDE Region: Would combine regions and incorrectly calculate overall totals.
B . FIXED Region: AVG(Sales Amount): Computes average of line-level sales, not customer totals.
D . FIXED Customer ID + Region: AVG(Sales Amount): Averages individual transactions, not customer totals.
Only option C matches the required two-step logic.
LOD Expressions: FIXED for computing customer-level aggregates.
Nested LOD usage for first calculating customer totals, then averaging them at a higher level.
Tableau guidance: SUM inside FIXED for per-customer totals, AVG outside for averaging customers.
A Tableau consultant tasked with evaluating a data structure is handed the below sample dataset.
Which two statements are true about the dataset? Choose two.

The dataset shown is a classic ''wide'' format'':
A single row per state
Separate columns for each year: 2019, 2020, 2021, 2022, 2023, 2024
Tableau's documentation on data structure and pivoting explains:
Why A is TRUE
Tableau documentation identifies wide datasets (multiple columns representing categories such as years, months, or similar time periods) as high-maintenance structures because:
For every new year, a new column must be added.
Metadata and calculations must be updated each time.
This type of structure is described as having poor scalability and higher maintenance.
This dataset fits that exact description, so A is correct.
Why C is TRUE
According to Tableau's ''Pivot Data from Columns to Rows'' section:
Wide datasets can and should often be pivoted so that repeated columns (such as year columns) become rows.
Pivoting enables dynamic capabilities such as:
Year filters (year selector)
Time-series analysis
Consistent aggregations
Simplified calculations
Pivoting this dataset would produce:
State
Year
Value
Alabama
2019
2300.39
Alabama
2020
3030.39
...
...
...
This makes the dataset tall and tidy, which Tableau identifies as better for analysis and dashboard interactivity.
Therefore, C is correct.
Why B is FALSE
The column names (2019, 2020, 2021...) are simply numbers.
Tableau documentation stresses that good metadata includes descriptive column names.
These column names:
Do not indicate what the measure represents (Revenue? Sales? Population?)
Only show the year, not the meaning of the metric
Thus they are not considered accurate or descriptive column names.
Why D is FALSE
The dataset is already denormalized, not normalized.
Denormalized data means combining multiple attributes (like multiple years) into one table, which is exactly what this dataset already does.
Tableau documentation explains that wide data is already denormalized, and the recommended fix is pivoting, not further denormalization.
Therefore, D is incorrect.
Jeffrey Howard
2 months agoMelissa Gonzalez
2 months agoGerald Turner
3 months agoAndrew Rivera
3 months agoWilliam Baker
4 months agoMargaret Rogers
4 months agoMaria Scott
5 months agoGary Harris
5 months agoHarold Nguyen
6 months agoRebecca Perez
6 months agoJoseph Campbell
7 months agoPaul Edwards
6 months agoStephanie Flores
6 months agoFrank Thomas
6 months agoBrian Carter
6 months agoKimberly Peterson
7 months agoLoreta
7 months agoAndra
8 months agoMarlon
8 months agoKrissy
8 months agoLaurel
8 months agoChristiane
9 months agoRaylene
9 months agoSabine
9 months agoKenia
9 months agoFrancesco
10 months agoReiko
10 months agoJudy
10 months agoVirgina
10 months agoVi
11 months agoTasia
11 months agoBelen
11 months agoKami
11 months agoIsabelle
12 months agoJames
12 months agoDenny
1 year agoMila
1 year agoKattie
1 year agoGilma
1 year agoLaurene
1 year agoCyril
1 year agoSage
1 year agoLennie
1 year agoErasmo
1 year agoJoseph
1 year agoKing
1 year agoIvette
1 year agoVallie
1 year ago