Practice Free Analytics-Con-301 Exam Online Questions
Question #1
A client wants to provide sales users with the ability to perform the following tasks:
・ Access published visualizations and published data sources outside the company network.
・ Edit existing visualizations.
・ Create new visualizations based on published data sources.
. Minimize licensing costs.
Which site role should the client assign to the sales users?
- A . Explorer (can publish)
- B . Site Administrator
- C . Viewer
- D . Creator
Correct Answer: A
A
Explanation:
The Explorer (can publish) site role in Tableau is designed for users who need to access, edit, and create visualizations based on published data sources, even when they are outside the company network. This role allows users to perform web editing and save their work, making it suitable for sales users who need these capabilities. It is also a cost-effective option as it does not require the full capabilities and associated costs of the Creator license.
Reference: The information about the Explorer (can publish) role and its capabilities can be found in the official Tableau documentation on site roles and permissions12. This role is appropriate for users who need to interact with published content and create new visualizations without the need for full site administration or advanced content creation tools that come with the Creator role3.
A
Explanation:
The Explorer (can publish) site role in Tableau is designed for users who need to access, edit, and create visualizations based on published data sources, even when they are outside the company network. This role allows users to perform web editing and save their work, making it suitable for sales users who need these capabilities. It is also a cost-effective option as it does not require the full capabilities and associated costs of the Creator license.
Reference: The information about the Explorer (can publish) role and its capabilities can be found in the official Tableau documentation on site roles and permissions12. This role is appropriate for users who need to interact with published content and create new visualizations without the need for full site administration or advanced content creation tools that come with the Creator role3.
Question #1
A client wants to provide sales users with the ability to perform the following tasks:
・ Access published visualizations and published data sources outside the company network.
・ Edit existing visualizations.
・ Create new visualizations based on published data sources.
. Minimize licensing costs.
Which site role should the client assign to the sales users?
- A . Explorer (can publish)
- B . Site Administrator
- C . Viewer
- D . Creator
Correct Answer: A
A
Explanation:
The Explorer (can publish) site role in Tableau is designed for users who need to access, edit, and create visualizations based on published data sources, even when they are outside the company network. This role allows users to perform web editing and save their work, making it suitable for sales users who need these capabilities. It is also a cost-effective option as it does not require the full capabilities and associated costs of the Creator license.
Reference: The information about the Explorer (can publish) role and its capabilities can be found in the official Tableau documentation on site roles and permissions12. This role is appropriate for users who need to interact with published content and create new visualizations without the need for full site administration or advanced content creation tools that come with the Creator role3.
A
Explanation:
The Explorer (can publish) site role in Tableau is designed for users who need to access, edit, and create visualizations based on published data sources, even when they are outside the company network. This role allows users to perform web editing and save their work, making it suitable for sales users who need these capabilities. It is also a cost-effective option as it does not require the full capabilities and associated costs of the Creator license.
Reference: The information about the Explorer (can publish) role and its capabilities can be found in the official Tableau documentation on site roles and permissions12. This role is appropriate for users who need to interact with published content and create new visualizations without the need for full site administration or advanced content creation tools that come with the Creator role3.
Question #3
A business analyst needs to create a view in Tableau Desktop that reports data from both Excel and MSSQL Server.
Which two features should the business analyst use to create the view? Choose two.
- A . Relationships
- B . Cross-Database Joins
- C . Data Blending
- D . Union
Correct Answer: A,B
A,B
Explanation:
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.
A,B
Explanation:
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.
Question #4
A client is migrating their data warehouse. They visualize the data in workbooks hosted on Tableau Server with Tableau Data Management enabled and want to see how many workbooks will be impacted.
What should the consultant do to quickly identify how many workbooks will be impacted?
- A . In Tableau Server, select the database from External Assets, then select the Lineage tab.
- B . Leverage the Tableau Developer API to query the workbooks’ metadata.
- C . Complete the migration and let users report errors as they are noticed.
- D . Open each workbook and identify the data source.
Correct Answer: A
A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When Tableau Data Management is enabled, Tableau Catalog provides Lineage capabilities that map connections between:
External databases
Tables
Data sources
Workbooks
Fields
Tableau documentation states that the Lineage tab for any external asset (such as a database or table):
Shows all connected workbooks
Shows dependencies and impact analysis
Allows admins to instantly assess how many analytics assets will be affected by a data warehouse migration
Option A directly uses Tableau Catalog to perform exactly this task.
Option B is unnecessary because the Catalog lineage tool already provides this information without development effort.
Option C is completely inappropriate because it offers no analysis or planning.
Option D is too time-consuming and unnecessary, especially when Tableau Catalog provides an automated dependency map.
Therefore, the correct method is to use the Lineage tab in External Assets.
Tableau Catalog lineage documentation showing how to view impacted workbooks.
External Assets and data source dependency features in Tableau Data Management.
Impact analysis best practices for data warehouse migration using Tableau Catalog.
A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When Tableau Data Management is enabled, Tableau Catalog provides Lineage capabilities that map connections between:
External databases
Tables
Data sources
Workbooks
Fields
Tableau documentation states that the Lineage tab for any external asset (such as a database or table):
Shows all connected workbooks
Shows dependencies and impact analysis
Allows admins to instantly assess how many analytics assets will be affected by a data warehouse migration
Option A directly uses Tableau Catalog to perform exactly this task.
Option B is unnecessary because the Catalog lineage tool already provides this information without development effort.
Option C is completely inappropriate because it offers no analysis or planning.
Option D is too time-consuming and unnecessary, especially when Tableau Catalog provides an automated dependency map.
Therefore, the correct method is to use the Lineage tab in External Assets.
Tableau Catalog lineage documentation showing how to view impacted workbooks.
External Assets and data source dependency features in Tableau Data Management.
Impact analysis best practices for data warehouse migration using Tableau Catalog.
Question #5
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.
- A . New credentials were embedded into the data source.
- B . The dashboard was published to a different project.
- C . Tableau Server was upgraded.
- D . The dashboard was published with a new name.
Correct Answer: B,D
B,D
Explanation:
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.
B,D
Explanation:
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.
Question #6
A consultant creates a histogram that presents the distribution of profits across a client’s customers. The labels on the bars show percent shares. The consultant used a quick table calculation to create the labels.
Now, the client wants to limit the view to the bins that have at least a 15% share. The consultant creates a profit filter but it changes the percent labels.
Which approach should the consultant use to produce the desired result?
- A . Use a calculation with TOTAL() function instead of a quick table calculation.
- B . Add the [Profit] filter to the context.
- C . Filter with a table calculation WINDOW_AVG(MIN([Profit]), first(), last())
- D . Filter with the table calculation used to create labels.
Correct Answer: B
B
Explanation:
When a filter is applied directly to the view, it can affect the calculation of percentages in a histogram because it changes the underlying data that the quick table calculation is based on. To avoid this, adding the [Profit] filter to the context will maintain the original calculation of percent shares while filtering out bins with less than a 15% share. This is because context filters are applied before any other calculations, so the percent shares calculated will be based on the context-filtered data, thus preserving the integrity of the original percent labels.
Reference: The solution is based on the principles of context filters and their order of operations in Tableau, which are documented in Tableau’s official resources and community discussions123.
When a histogram is created showing the distribution of profits with labels indicating percent shares using a quick table calculation, and a need arises to limit the view to bins with at least a 15% share, applying a standard profit filter directly may undesirably alter how the percent labels calculate because they depend on the overall distribution of data. Placing the [Profit] filter into the context makes it a "context filter," which effectively changes how data is filtered in calculations:
Create a Context Filter: Right-click on the profit filter and select "Add to Context". This action changes the order of operations in filtering, meaning the context filter is applied first.
Adjust the Percent Calculation: With the profit filter set in the context, it first reduces the data set to only those profits that meet the filter criteria. Subsequently, any table calculations (like the percent share labels) are computed based on this reduced data set.
View Update: The view now updates to display only those bins where the profits are at least 15%,
and the percent share labels recalculated to reflect the distribution of only the filtered (contextual)
data.
Reference: Context Filters in Tableau: Context filters are used to filter the data passed down to other filters, calculations, the marks card, and the view. By setting the profit filter as a context filter, it ensures that calculations such as the percentage shares are based only on the filtered subset of the data.
B
Explanation:
When a filter is applied directly to the view, it can affect the calculation of percentages in a histogram because it changes the underlying data that the quick table calculation is based on. To avoid this, adding the [Profit] filter to the context will maintain the original calculation of percent shares while filtering out bins with less than a 15% share. This is because context filters are applied before any other calculations, so the percent shares calculated will be based on the context-filtered data, thus preserving the integrity of the original percent labels.
Reference: The solution is based on the principles of context filters and their order of operations in Tableau, which are documented in Tableau’s official resources and community discussions123.
When a histogram is created showing the distribution of profits with labels indicating percent shares using a quick table calculation, and a need arises to limit the view to bins with at least a 15% share, applying a standard profit filter directly may undesirably alter how the percent labels calculate because they depend on the overall distribution of data. Placing the [Profit] filter into the context makes it a "context filter," which effectively changes how data is filtered in calculations:
Create a Context Filter: Right-click on the profit filter and select "Add to Context". This action changes the order of operations in filtering, meaning the context filter is applied first.
Adjust the Percent Calculation: With the profit filter set in the context, it first reduces the data set to only those profits that meet the filter criteria. Subsequently, any table calculations (like the percent share labels) are computed based on this reduced data set.
View Update: The view now updates to display only those bins where the profits are at least 15%,
and the percent share labels recalculated to reflect the distribution of only the filtered (contextual)
data.
Reference: Context Filters in Tableau: Context filters are used to filter the data passed down to other filters, calculations, the marks card, and the view. By setting the profit filter as a context filter, it ensures that calculations such as the percentage shares are based only on the filtered subset of the data.
Question #7
A client is using the Tableau Content Migration Tool to move content from an old Tableau Server to a new Tableau Server.
Which content will need to be moved using a different tool or process?
- A . Published data sources that use live connections
- B . Tableau Prep flows
- C . Published data sources that use extracts
- D . Workbooks
Correct Answer: B
B
Explanation:
When migrating content between Tableau servers, certain types of content may require special consideration or different tools for migration:
Tableau Prep Flows: These are specific to Tableau Prep and are not included in the standard content migration capabilities of the Tableau Content Migration Tool. Tableau Prep flows often require separate processes for migration due to their distinct setup and integration with data sources and workflows.
Published Data Sources and Workbooks: These can typically be migrated directly using the Tableau Content Migration Tool, which supports moving published data sources (both live connections and extracts) and workbooks without requiring additional tools.
Reference: Tableau Help and Support: Offers comprehensive tutorials and guidelines on using different tools for migrating various types of content, including the specific requirements for migrating Tableau Prep flows which are not covered by the standard content migration tool.
B
Explanation:
When migrating content between Tableau servers, certain types of content may require special consideration or different tools for migration:
Tableau Prep Flows: These are specific to Tableau Prep and are not included in the standard content migration capabilities of the Tableau Content Migration Tool. Tableau Prep flows often require separate processes for migration due to their distinct setup and integration with data sources and workflows.
Published Data Sources and Workbooks: These can typically be migrated directly using the Tableau Content Migration Tool, which supports moving published data sources (both live connections and extracts) and workbooks without requiring additional tools.
Reference: Tableau Help and Support: Offers comprehensive tutorials and guidelines on using different tools for migrating various types of content, including the specific requirements for migrating Tableau Prep flows which are not covered by the standard content migration tool.
Question #8
A consultant wants to improve the performance of reports by moving calculations to the data layer and materializing them in the extract.
Which calculation should the consultant use?
- A . ZN([Sales])*(1 – ZN([Discount]))
- B . CASE [Sector Parameter]WHEN 1 THEN "green"WHEN 2 THEN "yellow"
- C . SUM([Profit])/SUM([Sales])
- D . POWER(ZN(SUM([Sales]))/LOOKUP(ZN(SUM([Sales])), FIRST()),ZN(1/(INDEX()-1)))- 1END
Correct Answer: C
C
Explanation:
To improve performance by moving calculations to the data layer and materializing them in the extract, the consultant should choose calculations that benefit from pre-computation and significantly reduce the load during query time:
Aggregation-Level Calculation: The formula SUM([Profit])/SUM([Sales]) calculates a ratio at an aggregate level, which is ideal for pre-computation. Materializing this calculation in the extract means that the complex division operation is done once and stored, rather than being recalculated every time the report is accessed.
Performance Improvement: By pre-computing this aggregate ratio, Tableau can utilize the pre-calculated fields directly in visualizations, which speeds up report loading and interaction times as the heavy lifting of data processing is done during the data preparation stage.
Reference: Materialization in Extracts: This concept involves pre-calculating and storing complex aggregations or calculations within the Tableau data extract itself, improving performance by reducing the computational load during visualization rendering.
C
Explanation:
To improve performance by moving calculations to the data layer and materializing them in the extract, the consultant should choose calculations that benefit from pre-computation and significantly reduce the load during query time:
Aggregation-Level Calculation: The formula SUM([Profit])/SUM([Sales]) calculates a ratio at an aggregate level, which is ideal for pre-computation. Materializing this calculation in the extract means that the complex division operation is done once and stored, rather than being recalculated every time the report is accessed.
Performance Improvement: By pre-computing this aggregate ratio, Tableau can utilize the pre-calculated fields directly in visualizations, which speeds up report loading and interaction times as the heavy lifting of data processing is done during the data preparation stage.
Reference: Materialization in Extracts: This concept involves pre-calculating and storing complex aggregations or calculations within the Tableau data extract itself, improving performance by reducing the computational load during visualization rendering.
Question #9
A new Tableau user created a simple dashboard on Tableau Server using supply chain data. Now, the user wants to know if they created the dashboard in accordance with specific performance best practices.
Which approach should the consultant recommend for the client to make this determination?
- A . Use inbuilt dashboards in Tableau Server to troubleshoot the performance.
- B . Use Performance Recording on Tableau Server.
- C . Use Performance Recording in Tableau Desktop.
- D . Run Workbook Optimizer.
Correct Answer: D
D
Explanation:
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.
Reference: The Workbook Optimizer’s functionality is detailed in Tableau’s official documentation, which explains how it assesses workbooks against a set of rules derived from best practices1. Additionally, the Performance Recording feature in Tableau Desktop and Server can be used to identify performance issues, but the Workbook Optimizer gives a more comprehensive analysis of the workbook’s adherence to best practices23.
D
Explanation:
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.
Reference: The Workbook Optimizer’s functionality is detailed in Tableau’s official documentation, which explains how it assesses workbooks against a set of rules derived from best practices1. Additionally, the Performance Recording feature in Tableau Desktop and Server can be used to identify performance issues, but the Workbook Optimizer gives a more comprehensive analysis of the workbook’s adherence to best practices23.
Question #10
An analyst needs to interactively set a reference date to drive table calculations without leaving a view.
Which action should the analyst use?
- A . Running action
- B . Filter action
- C . Parameter action
- D . Highlight action
Correct Answer: C
C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau’s documentation on Parameter Actions states that they allow users to interactively update a parameter directly from the view―without opening the parameter control box. To “interactively set a reference date” that drives a table calculation:
A parameter must hold that reference date.
A parameter action allows clicking or selecting a mark in the view to update the parameter value.
Table calculations can then reference that parameter to change their computation dynamically.
Filter actions modify which data is shown, not a reference date.
Running actions change sheets, not computation parameters.
Highlight actions visually accent marks but do not set values.
Thus, parameter actions are the only mechanism that meets the requirement.
Parameter Actions overview describing interactive parameter updates.
Use cases where parameter actions drive table calculations.
Action type comparison showing that only parameter actions update a computation value.
C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau’s documentation on Parameter Actions states that they allow users to interactively update a parameter directly from the view―without opening the parameter control box. To “interactively set a reference date” that drives a table calculation:
A parameter must hold that reference date.
A parameter action allows clicking or selecting a mark in the view to update the parameter value.
Table calculations can then reference that parameter to change their computation dynamically.
Filter actions modify which data is shown, not a reference date.
Running actions change sheets, not computation parameters.
Highlight actions visually accent marks but do not set values.
Thus, parameter actions are the only mechanism that meets the requirement.
Parameter Actions overview describing interactive parameter updates.
Use cases where parameter actions drive table calculations.
Action type comparison showing that only parameter actions update a computation value.