Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
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.
SIMULATION
From the desktop, open the NYC
Property Transactions workbook.
You need to record the performance of
the Property Transactions dashboard in
the NYC Property Transactions.twbx
workbook. Ensure that you start the
recording as soon as you open the
workbook. Open the Property
Transactions dashboard, reset the filters
on the dashboard to show all values, and
stop the recording. Save the recording in
C:\CC\Data\.
Create a new worksheet in the
performance recording. In the worksheet,
create a bar chart to show the elapsed
time of each command name by
worksheet, to show how each sheet in
the Property Transactions dashboard
contributes to the overall load time.
From the File menu in Tableau Desktop,
click Save. Save the performance
recording in C:\CC\Data\.
To record the performance of the Property Transactions dashboard in the NYC Property Transactions.twbx workbook and analyze it using a bar chart, follow these detailed steps:
Open the NYC Property Transactions Workbook:
From the desktop, double-click the NYC Property Transactions.twbx workbook to open it in Tableau Desktop.
Start Performance Recording:
Before doing anything else, navigate to the 'Help' menu in Tableau Desktop.
Select 'Settings and Performance', then choose 'Start Performance Recording'.
Open the Property Transactions Dashboard and Reset Filters:
Navigate to the Property Transactions dashboard within the workbook.
Reset all filters to show all values. This usually involves selecting the dropdown on each filter and choosing 'All' or using a 'Reset' button if available.
Stop the Performance Recording:
Go back to the 'Help' menu.
Choose 'Settings and Performance', then select 'Stop Performance Recording'.
Tableau will automatically open a new tab displaying the performance recording results.
Save the Performance Recording:
In the performance recording results tab, go to the 'File' menu.
Click 'Save As' and navigate to the C:\CC\Data\ directory.
Save the file, ensuring it is stored in the desired location.
Create a New Worksheet for Performance Analysis:
Return to the NYC Property Transactions workbook and create a new worksheet by clicking on the 'New Worksheet' icon.
Drag the 'Command Name' field to the Columns shelf.
Drag the 'Elapsed Time' field to the Rows shelf.
Ensure that the 'Worksheet' field is also included in the analysis to break down the time by individual sheets within the dashboard.
Choose 'Bar Chart' from the 'Show Me' options to display the data as a bar chart.
Customize and Finalize the Bar Chart:
Adjust the axes and labels to clearly display the information.
Format the chart to enhance readability, applying color coding or sorting as needed to emphasize sheets with longer load times.
Save Your Work:
Once the new worksheet and the performance recording are complete, ensure all work is saved.
Navigate to the 'File' menu and click 'Save', confirming that changes are stored in the workbook.
Tableau Help Documentation: Provides guidance on how to start and stop performance recordings and analyze them.
Tableau Visualization Techniques: Offers tips on creating effective bar charts for performance data.
By following these steps, you have successfully recorded and analyzed the performance of the Property Transactions dashboard, providing valuable insights into how each component of the dashboard contributes to the overall load time. This analysis is crucial for optimizing dashboard performance and ensuring efficient data visualization.
A client has a published dashboard. They change the dashboard and then republish it. Now, users report that their web browser bookmarks to the dashboard
are broken.
What are two possible causes for this issue? Choose two.
When a client republishes a dashboard after making changes and users report broken bookmarks, the likely causes include:
The dashboard was published to a different project: Changing the project location alters the URL path, causing bookmarks to point to a now non-existent dashboard location.
The dashboard was published with a new name: Altering the dashboard's name changes its URL, resulting in broken bookmarks as the previous URL no longer leads to the intended dashboard.
A shipping clerk wants to use a Sankey diagram to analyze the flow of goods between different categories, shipping modes, and locations to spot bottlenecks and optimize the most critical paths. The company uses Tableau Cloud.
How should the shipping clerk create a chart that depicts the above information?
Comprehensive and Detailed Explanation From Exact Extract:
Tableau Cloud does not natively contain a Sankey diagram in Show Me. Such advanced charts often require:
A custom extension
Or specialized templates built into Tableau Exchange
A sandboxed Viz Extension allows users to embed specialized visualization components (like Sankey diagrams) securely in Tableau Cloud. These extensions are designed for advanced chart types that are not available natively.
Accelerators provide prebuilt dashboards but are not intended for custom visual types such as Sankey.
Connectors relate to connecting to data sources, not visualization.
Show Me does not include a Sankey option.
Therefore, downloading a sandboxed Viz Extension is the correct approach.
Viz Extensions documentation explaining support for custom charts, including Sankey.
Tableau Exchange listing providing sandboxed visualization extensions for non-native chart types.
Show Me panel documentation showing Sankey is not an included chart type.
A client is concerned that a dashboard has experienced degraded performance after they added additional quick filters. The client asks a consultant to improve performance.
Which two actions should the consultant take to fulfill the client's request? Choose two.
Comprehensive and Detailed Explanation From Exact Extract:
Quick filters are one of the most expensive features in Tableau because they require queries to populate value lists and dynamic recalculations when filters change.
According to Tableau performance documentation:
1. Add an ''Apply'' Button
This prevents Tableau from re-running queries every time the user selects a filter value.
Queries are executed once when the user presses Apply.
This is a documented best practice for filter-heavy dashboards.
2. Replace Quick Filters with Filter Actions
Filter actions are far more efficient because:
They leverage the existing view context
They do not require separate filter UI queries
They avoid the overhead of quick filter value lists
Tableau recommends using filter actions instead of multiple quick filters for better performance.
Why the other options are incorrect:
B . Add filters to Context: Context filters make downstream filters faster, but do not reduce quick filter processing cost; they can even increase extract size and slow down the dashboard.
C . Only Relevant Values: This actually slows performance because Tableau must re-evaluate the entire data set to determine relevancy every time filters update.
Thus, A and D are the correct performance-improvement approaches.
Tableau Performance Checklist recommending Apply button for multi-select filters.
Performance documentation advising the use of Filter Actions over multiple quick filters.
Filtering best practices explaining the cost of Only Relevant Values.
100 questions covering all exam domains, starting from $20
Exam domains verified against: Official Salesforce Analytics-Con-301 exam guide, last checked September 2026.
Map current analytics infrastructure and business requirements to Tableau capabilities and future state architecture. Assess existing data structures for quality, lineage, and performance risks to inform migration and upgrade planning.
Sample question from this domain above: Q3
Design data transformation strategies and row-level security structures that meet governance and performance requirements. Select appropriate connection methods including Tableau Bridge, Web Data Connectors, and custom SQL for optimal data delivery.
Sample question from this domain above: Q2
Build advanced visualizations and table calculations using order of operations, LOD expressions, and aggregations. Optimize workbook performance by identifying resource-intensive queries, inefficient calculations, and design elements that impact speed.
Develop governance strategies for content security, data quality, and certification. Design content distribution approaches and workbook lifecycle processes including build, test, deployment, and maintenance on Tableau Server or Cloud.
Common questions about the exam itself
