Tableau TCC-C01 Practice Exams
Last updated on Oct 21,2026- Exam Code: TCC-C01
- Exam Name: Tableau Certified Consultant
- Certification Provider: Tableau
- Latest update: Oct 21,2026
Question #41
A stakeholder has multiple files saved (CSV/Tables) in a single location. A few files from the location are required for analysis. Data transformation (calculations) is required for the files before designing the visuals.
The files have the following attributes:
– All files have the same schema.
– Multiple files have something in common among their file names.
– Each file has a unique key column.
Which data transformation strategy should the consultant use to deliver the best optimized result?
- A . Use join option to combine/merge all the files together before doing the data transformation (calculations).
- B . Use wildcard Union option to combine/merge all the files together before doing the data transformation (calculations).
- C . Apply the data transformation (calculations) in each require file and do the wildcard union to combine/merge before designing the visuals.
- D . Apply the data transformation (calculations) in each require file and do the join to combine/merge before designing the visuals.
Correct Answer: B
B
Explanation
Moving calculations to the data layer and materializing them in the extract can significantly improve the performance of reports in Tableau. The calculation ZN([Sales])*(1 – ZN([Discount]))is a basic calculation that can be easily computed in advance and stored in the extract, speeding up future queries. This type of calculation is less complex than table calculations or LOD expressions, which are better suited for dynamic analysis and may not benefit as much from materialization12.
References: The answer is based on the best practices for creating efficient calculations in Tableau, as described in Tableau’s official documentation, which suggests using basic and aggregate calculations to improve performance1.Additionally, the process of materializing calculations in extracts is detailed in Tableau’s resources2.
Given that all files share the same schema and have a common element in their file names, the wildcard union is an optimal approach to combine these files before performing any transformations.
This strategy offers the following advantages:
Efficient Data Combination: Wildcard union allows multiple files with a common naming scheme to be combined into a single dataset in Tableau, streamlining the data preparation process.
Uniform Schema Handling: Since all files share the same schema, wildcard union ensures that the combined dataset maintains consistency in data structure, making further data manipulation more straightforward.
Pre-Transformation Combination: Combining the files before applying transformations is generally more efficient as it reduces redundancy in transformation logic across multiple files. This means transformations are written and processed once on the unified dataset, rather than repeatedly for each individual file.
References:
Wildcard Union in Tableau: This feature simplifies the process of combining multiple similar files into a single Tableau data source, ensuring a seamless and efficient approach to data integration and preparation.
B
Explanation
Moving calculations to the data layer and materializing them in the extract can significantly improve the performance of reports in Tableau. The calculation ZN([Sales])*(1 – ZN([Discount]))is a basic calculation that can be easily computed in advance and stored in the extract, speeding up future queries. This type of calculation is less complex than table calculations or LOD expressions, which are better suited for dynamic analysis and may not benefit as much from materialization12.
References: The answer is based on the best practices for creating efficient calculations in Tableau, as described in Tableau’s official documentation, which suggests using basic and aggregate calculations to improve performance1.Additionally, the process of materializing calculations in extracts is detailed in Tableau’s resources2.
Given that all files share the same schema and have a common element in their file names, the wildcard union is an optimal approach to combine these files before performing any transformations.
This strategy offers the following advantages:
Efficient Data Combination: Wildcard union allows multiple files with a common naming scheme to be combined into a single dataset in Tableau, streamlining the data preparation process.
Uniform Schema Handling: Since all files share the same schema, wildcard union ensures that the combined dataset maintains consistency in data structure, making further data manipulation more straightforward.
Pre-Transformation Combination: Combining the files before applying transformations is generally more efficient as it reduces redundancy in transformation logic across multiple files. This means transformations are written and processed once on the unified dataset, rather than repeatedly for each individual file.
References:
Wildcard Union in Tableau: This feature simplifies the process of combining multiple similar files into a single Tableau data source, ensuring a seamless and efficient approach to data integration and preparation.
Question #42
Topic 2, hands-on labLab Section
From the desktop, open the CC workbook.
Open the Incremental worksheet.
You need to add a line to the chart that shows the cumulative percentage of sales contributed by each product to the incremental sales.
From the File menu in Tableau Desktop, click Save.
Correct Answer: To add a line showing the cumulative percentage of sales contributed by each product to the incremental sales in the Incremental worksheet of your Tableau Desktop, follow these detailed steps:
* Open the CC Workbook and Access the Worksheet:
– From the desktop, double-click on the CC workbook to open it in Tableau Desktop.
– Navigate to the Incremental worksheet by clicking on its tab at the bottom of the window.
* Calculate Cumulative Sales Percentage:
– Create a new calculated field to compute the cumulative percentage of sales. Right-click in the Data pane and select ‘Create Calculated Field’.
– Name this field "Cumulative Sales Percentage".
– Enter the following formula to calculate the running sum of sales as a percentage of the total sales:
(RUNNING_SUM(SUM([Sales])) / TOTAL(SUM([Sales])) [Sales]))
* Click ‘OK’ to save the calculated field.
* Add the Cumulative Sales Percentage Line to the Chart:
– Drag the "Cumulative Sales Percentage" field to the Rows shelf, placing it next to the existing Sales measure.
– Ensure that the cumulative line appears as a continuous line. Right-click on the "Cumulative Sales Percentage" field on the Rows shelf, select ‘Change Chart Type’, and choose ‘Line’.
– Adjust the axis to synchronize or dual-axis if necessary. Right-click on the axis of the "Cumulative Sales Percentage" and select ‘Synchronize Axis’ if it’s on a dual-axis setup.
* Format the Cumulative Sales Percentage Line:
– Click on the "Cumulative Sales Percentage" line in the visualization.
– Navigate to the ‘Format’ pane to adjust the line style, thickness, and color to make it distinct from other data in the chart.
* Save Your Changes:
– From the File menu, click ‘Save’ to ensure all your changes are stored.
References:
* Tableau Help: Provides additional details on creating calculated fields and customizing line charts.
* Tableau User Guide: Offers extensive instructions on formatting charts, including line types and axis synchronization.
By following these steps, you will successfully add a cumulative sales percentage line to your chart, enhancing the visualization to reflect the incremental contribution of each product to the overall sales in a dynamic and informative manner.
* Open the CC Workbook and Access the Worksheet:
– From the desktop, double-click on the CC workbook to open it in Tableau Desktop.
– Navigate to the Incremental worksheet by clicking on its tab at the bottom of the window.
* Calculate Cumulative Sales Percentage:
– Create a new calculated field to compute the cumulative percentage of sales. Right-click in the Data pane and select ‘Create Calculated Field’.
– Name this field "Cumulative Sales Percentage".
– Enter the following formula to calculate the running sum of sales as a percentage of the total sales:
(RUNNING_SUM(SUM([Sales])) / TOTAL(SUM([Sales])) [Sales]))
* Click ‘OK’ to save the calculated field.
* Add the Cumulative Sales Percentage Line to the Chart:
– Drag the "Cumulative Sales Percentage" field to the Rows shelf, placing it next to the existing Sales measure.
– Ensure that the cumulative line appears as a continuous line. Right-click on the "Cumulative Sales Percentage" field on the Rows shelf, select ‘Change Chart Type’, and choose ‘Line’.
– Adjust the axis to synchronize or dual-axis if necessary. Right-click on the axis of the "Cumulative Sales Percentage" and select ‘Synchronize Axis’ if it’s on a dual-axis setup.
* Format the Cumulative Sales Percentage Line:
– Click on the "Cumulative Sales Percentage" line in the visualization.
– Navigate to the ‘Format’ pane to adjust the line style, thickness, and color to make it distinct from other data in the chart.
* Save Your Changes:
– From the File menu, click ‘Save’ to ensure all your changes are stored.
References:
* Tableau Help: Provides additional details on creating calculated fields and customizing line charts.
* Tableau User Guide: Offers extensive instructions on formatting charts, including line types and axis synchronization.
By following these steps, you will successfully add a cumulative sales percentage line to your chart, enhancing the visualization to reflect the incremental contribution of each product to the overall sales in a dynamic and informative manner.
Question #43
A client wants to count all the distinct orders placed in 2010. They have written the following calculation, but the result is incorrect.
IF YEAR([Date])=2010 THEN COUNTD ([OrderID]) END
Which calculation will produce the correct result?
- A . IF MIN(YEAR([Date]))=2010 THEN WINDOW_COUNTD([OrderID]) END
- B . IF YEAR([Date])=2010 THEN {COUNTD ([OrderID])} END
- C . COUNTD(IF YEAR([Date])=2010 THEN [OrderID] END)
- D . COUNT(IF YEAR([Date])=2010 THEN [OrderID] END)
Correct Answer: C
C
Explanation
The correct calculation to count all distinct orders placed in 2010 involves placing the conditional inside the aggregation function, not the other way around. Here’s how to correct the client’s calculation:
– Original Calculation Issue: The client’s original calculation attempts to apply the COUNTD function within an IFstatement, which does not work as expected because the COUNTD function cannot conditionally count within the scope of the IFstatement.
– Correct Calculation: COUNTD (IF YEAR([Date]) = 2010 THEN [OrderID] END). This calculation checks each order date; if the year is 2010, it returns the OrderID. The COUNTD function then counts all unique Order IDs that meet this condition.
– Why It Works: This method ensures that each order is first checked for the year condition before being counted, effectively filtering and counting in one step. It efficiently processes the data by focusing the distinct count operation only on relevant records.
References: This approach is consistent with Tableau’s guidance on using conditional logic inside aggregation functions for accurate and efficient data calculations, as detailed in the Tableau User Guide under "Aggregations and Calculations".
C
Explanation
The correct calculation to count all distinct orders placed in 2010 involves placing the conditional inside the aggregation function, not the other way around. Here’s how to correct the client’s calculation:
– Original Calculation Issue: The client’s original calculation attempts to apply the COUNTD function within an IFstatement, which does not work as expected because the COUNTD function cannot conditionally count within the scope of the IFstatement.
– Correct Calculation: COUNTD (IF YEAR([Date]) = 2010 THEN [OrderID] END). This calculation checks each order date; if the year is 2010, it returns the OrderID. The COUNTD function then counts all unique Order IDs that meet this condition.
– Why It Works: This method ensures that each order is first checked for the year condition before being counted, effectively filtering and counting in one step. It efficiently processes the data by focusing the distinct count operation only on relevant records.
References: This approach is consistent with Tableau’s guidance on using conditional logic inside aggregation functions for accurate and efficient data calculations, as detailed in the Tableau User Guide under "Aggregations and Calculations".
Question #44
A client has many published data sources in Tableau Server. The data sources use the same databases and tables. The client notices different departments give different answers to the same business questions, and the departments cannot trust the data. The client wants to know what causes data sources to return different data.
Which tool should the client use to identify this issue?
- A . Tableau Prep Conductor
- B . Ask Data
- C . Tableau Catalog
- D . Tableau Resource Monitoring Tool
Correct Answer: C
C
Explanation
The Tableau Catalog is part of the Tableau Data Management Add-on and is designed to help users understand the data they are using within Tableau. It provides a comprehensive view of all the data assets in Tableau Server or Tableau Online, including databases, tables, and fields. It can help identify issues such as data quality, data lineage, and impact analysis. In this case, where different departments are getting different answers to the same business questions, the Tableau Catalog can be used to track down inconsistencies and ensure that everyone is working from the same, reliable data source.
References: The recommendation for using Tableau Catalog is based on its features that support data discovery, quality, and governance, which are essential for resolving data inconsistencies across different departments12.
When different departments report different answers to the same business questions using the same databases and tables, the issue often lies in how data is being accessed and interpreted differently across departments. Tableau Catalog, a part of Tableau Data Management, can be used to solve this problem:
Visibility: Tableau Catalog gives visibility into the data used in Tableau, showing users where data comes from, where it’s used, and who’s using it.
Consistency and Trust: It helps ensure consistency and trust in data by providing detailed metadata management that can highlight discrepancies in data usage or interpretation.
Usage Metrics and Lineage: It offers tools for tracking usage metrics and understanding data lineage, which can help in identifying why different departments might see different results from the same underlying data.
References:
Tableau Catalog Usage: The Catalog is instrumental in providing a detailed view of the data environment, allowing organizations to audit, track, and understand data discrepancies across different users and departments.
C
Explanation
The Tableau Catalog is part of the Tableau Data Management Add-on and is designed to help users understand the data they are using within Tableau. It provides a comprehensive view of all the data assets in Tableau Server or Tableau Online, including databases, tables, and fields. It can help identify issues such as data quality, data lineage, and impact analysis. In this case, where different departments are getting different answers to the same business questions, the Tableau Catalog can be used to track down inconsistencies and ensure that everyone is working from the same, reliable data source.
References: The recommendation for using Tableau Catalog is based on its features that support data discovery, quality, and governance, which are essential for resolving data inconsistencies across different departments12.
When different departments report different answers to the same business questions using the same databases and tables, the issue often lies in how data is being accessed and interpreted differently across departments. Tableau Catalog, a part of Tableau Data Management, can be used to solve this problem:
Visibility: Tableau Catalog gives visibility into the data used in Tableau, showing users where data comes from, where it’s used, and who’s using it.
Consistency and Trust: It helps ensure consistency and trust in data by providing detailed metadata management that can highlight discrepancies in data usage or interpretation.
Usage Metrics and Lineage: It offers tools for tracking usage metrics and understanding data lineage, which can help in identifying why different departments might see different results from the same underlying data.
References:
Tableau Catalog Usage: The Catalog is instrumental in providing a detailed view of the data environment, allowing organizations to audit, track, and understand data discrepancies across different users and departments.
Question #45
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.
References:
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.
References:
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 #46
A client wants guidance for Creators to build efficient extracts from large data sources.
What are three Tableau best practices that the Creators should use? Choose three.
- A . Keep only the data required for analysis by using extract filters.
- B . Use aggregate data for visible dimensions, whenever possible.
- C . Use only live connections as they are always faster than extracts.
- D . Include all the data from the original data source in the extract.
- E . Hide all unused fields.
Correct Answer: A B E
A B E
Explanation
To build efficient extracts from large data sources, it is crucial to minimize the load and optimize the performance of the extracts:
A B E
Explanation
To build efficient extracts from large data sources, it is crucial to minimize the load and optimize the performance of the extracts:
Question #47
A client builds a dashboard that presents current and long-term stock measures. Currently, the data is at a daily level. The data presents as a bar chart that presents monthly results over current and previous years. Some measures must present as monthly averages.
What should the consultant recommend to limit the data source for optimal performance?
- A . Limit data to current and previous years and leave data at daily level to calculate the averages in the report.
- B . Limit data to current and previous years, move calculating averages to data layer, and aggregate dates to monthly level.
- C . Move calculating averages to data layer and aggregate dates to monthly level.
- D . Limit data to current and previous years as well as to the last day of each month to eliminate the need to use the averages.
Correct Answer: B
B
Explanation
For optimal performance, it is recommended to limit the data to what is necessary for analysis, which in this case would be the current and previous years. Moving the calculation of averages to the data layer and aggregating the dates to a monthly level will reduce the granularity of the data, thereby improving the performance of the dashboard. This approach aligns with best practices for optimizing workbook performance in Tableau, which suggest simplifying the data model and reducing the number of records processed12.
References: The recommendation is based on the guidelines provided in Tableau’s official documentation on optimizing workbook performance, which includes tips on data management and aggregation for better performance12.
B
Explanation
For optimal performance, it is recommended to limit the data to what is necessary for analysis, which in this case would be the current and previous years. Moving the calculation of averages to the data layer and aggregating the dates to a monthly level will reduce the granularity of the data, thereby improving the performance of the dashboard. This approach aligns with best practices for optimizing workbook performance in Tableau, which suggest simplifying the data model and reducing the number of records processed12.
References: The recommendation is based on the guidelines provided in Tableau’s official documentation on optimizing workbook performance, which includes tips on data management and aggregation for better performance12.
Question #48
A client has a dashboard that uses a bar chart to visualize sales by Sub-Category and a detail table that has all the orders for the products within Sub-Category. The table has more than 10,000 rows of data and is slow to load.
A consultant plans to add an action so when the client interacts with the bar chart, only the relevant data appears in the table.
What will provide the fastest rendering of the dashboard?
- A . Add a filter action, set "Run action on" to Select, and set "Clearing the selection will" to Exclude all values.
- B . Add a highlight action and set Target Highlighting to Sub-Category.
- C . Add a highlight action and set Target Highlighting to All Fields.
- D . Add a filter action, set "Run action on" to Menu, and set "Clearing the selection will" to Show all values.
Correct Answer: A
A
Explanation
To optimize the dashboard rendering, particularly when dealing with a large dataset, a filter action is the most effective tool. Here’s why the specified choice is optimal:
– Add a filter action: This action creates a direct filter on the detail table based on the selection in the bar chart. It ensures that only data related to the selected sub-category is loaded into the table, significantly reducing load time and improving performance.
– Set "Run action on" to Select: This setting means the filter action will be triggered as soon as the user selects a bar in the bar chart. Immediate activation of the filter ensures that the dashboard is interactive and responsive.
– Set "Clearing the selection will" to Exclude all values: When the selection is cleared, this setting ensures that no data is shown, which avoids loading the entire dataset unnecessarily. This maintains performance when no sub-category is actively selected.
References: This strategy follows Tableau’s performance best practices by using actions to limit the amount of data processed and rendered, as detailed in the Tableau User Guide and training materials on Dashboard Actions for optimizing large datasets.
A
Explanation
To optimize the dashboard rendering, particularly when dealing with a large dataset, a filter action is the most effective tool. Here’s why the specified choice is optimal:
– Add a filter action: This action creates a direct filter on the detail table based on the selection in the bar chart. It ensures that only data related to the selected sub-category is loaded into the table, significantly reducing load time and improving performance.
– Set "Run action on" to Select: This setting means the filter action will be triggered as soon as the user selects a bar in the bar chart. Immediate activation of the filter ensures that the dashboard is interactive and responsive.
– Set "Clearing the selection will" to Exclude all values: When the selection is cleared, this setting ensures that no data is shown, which avoids loading the entire dataset unnecessarily. This maintains performance when no sub-category is actively selected.
References: This strategy follows Tableau’s performance best practices by using actions to limit the amount of data processed and rendered, as detailed in the Tableau User Guide and training materials on Dashboard Actions for optimizing large datasets.
Question #49
A client wants to migrate their Tableau Server to Tableau Cloud. The Tableau Server is configured with three sites: Finance, Strategy, and Marketing. A consultant must provide a solution that minimizes user impact and costs.
Which configuration should the consultant recommend for Tableau Cloud to meet the client’s requirements?
- A . One Tableau Cloud instance configured with a Finance project folder, Strategy project folder, and Marketing project folder
- B . One Tableau Cloud instance with two sites for Strategy and Marketing, and one Tableau Server instance for Finance
- C . Three separate Tableau Cloud instances for Finance, Strategy, and Marketing
- D . One Tableau Cloud instance configured with all workbooks in a single project
Correct Answer: A
A
Explanation
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.
References: 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.
A
Explanation
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.
References: 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.
Question #50
A client wants to flag orders that have sales higher than the regional average.
Which calculated field will produce the required result?
- A . [Sales]
>
{FIXED [Order ID]: SUM([Sales])} - B . {FIXED [Order ID]: SUM([Sales])}
>
{FIXED [Region]: SUM([Sales])} - C . {FIXED [Order ID]: SUM([Sales])}
>
{FIXED [Region]: AVG ({FIXED [Order ID]: SUM([Sales])})} - D . {FIXED [Order ID]: SUM([Sales])}
>
{INCLUDE [Region]: AVG ({FIXED [Order ID]: SUM([Sales])})}
Correct Answer: C
C
Explanation
To flag orders with sales higher than the regional average, the correct calculated field would compare the sum of sales for each order against the average sales of all orders within the same region:
– Correct Formula: {FIXED [Order ID]: SUM([Sales])} > {FIXED [Region]: AVG ({FIXED [Order ID]: SUM([Sales]) }) }
– This calculation uses a Level of Detail (LOD) expression:
– The left part of the formula {FIXED [Order ID]: SUM([Sales])} calculates the total sales for each individual order.
– The right part {FIXED [Region]: AVG ({FIXED [Order ID]: SUM([Sales])})} calculates the average sales per order within each region.
– The>operator is used to compare these two values to determine if the sales for each order exceed the regional average.
References: This formula utilizes Tableau’s LOD expressions to perform complex comparisons across different dimensions of the data, as explained in Tableau’s official training materials on LOD calculations.
C
Explanation
To flag orders with sales higher than the regional average, the correct calculated field would compare the sum of sales for each order against the average sales of all orders within the same region:
– Correct Formula: {FIXED [Order ID]: SUM([Sales])} > {FIXED [Region]: AVG ({FIXED [Order ID]: SUM([Sales]) }) }
– This calculation uses a Level of Detail (LOD) expression:
– The left part of the formula {FIXED [Order ID]: SUM([Sales])} calculates the total sales for each individual order.
– The right part {FIXED [Region]: AVG ({FIXED [Order ID]: SUM([Sales])})} calculates the average sales per order within each region.
– The>operator is used to compare these two values to determine if the sales for each order exceed the regional average.
References: This formula utilizes Tableau’s LOD expressions to perform complex comparisons across different dimensions of the data, as explained in Tableau’s official training materials on LOD calculations.