Pass the Tableau Certified Consultant TCC-C01 Questions and answers with ExamsMirror

To improve the loading time of the pipeline dashboard, which primarily suffers from long query execution times due to a comprehensive Relative Date filter:

Relative Date Filter Issue: The existing Relative Date filter on "Created Date" covers a broad range (5 years), leading to significant data processing overhead as it includes granular date calculations over a large dataset.

Optimized Approach: By replacing the Relative Date filter with a Multiple Values (Dropdown) filter based on YEAR([Created Date]), the filter granularity is reduced. Filtering by year simplifies the query by limiting the volume of data processed and reducing the complexity of the filter condition.

Implementation Benefit: This approach still provides the flexibility to view data across different years but does so by reducing the load on the database during query execution, which is critical for improving the performance of the dashboard.

ReferencesThis recommendation aligns with Tableau performance optimization strategies, specifically regarding the management of date filters to minimize their impact on query load, as discussed in Tableau performance tuning sessions and guides.

For modeling shipping costs based on varying vendor contracts and ensuring speed in dashboard performance, the suggested approach involves:

Calculated Field with Parameter: Utilize a calculated field that dynamically references a user-selected parameter for the shipping vendor. This parameter adjusts the cost calculations based on selected vendor characteristics (like volume and speed).

Aggregate Results: After calculating individual shipping costs, aggregate these costs to provide a concise, summarized view of potential expenses for the upcoming week. This method ensures the dashboard remains performant by reducing the load of processing individual line items in real-time.

Why This Works: By using parameters and calculated fields, the dashboard can quickly adapt to user inputs without needing to re-query the entire dataset. Aggregating the results further improves performance and user experience by simplifying the output.

ReferencesThis strategy leverages Tableau's capability to handle dynamic calculations with parametersand is recommended for scenarios where performance and user-driven interaction are priorities. Tableau’s performance optimization resources and dashboard design guidelines detail these techniques.

To ensure that each sales representative sees only data relevant to their territory, the best approach in the absence of a Tableau Data Management license involves using a joined data source with entitlements:

Data Source Configuration: Create a data source that joins the sales data table with an entitlements table. The entitlements table contains mappings of sales representatives to their respective territories.

Data Source Filter: Implement a data source filter that restricts data based on the current user’s access rights. This filter references the joined entitlements to dynamically control data visibility based on the logged-in user.

Publishing the Data Source: Publish this filtered data source to Tableau Server. All workbooks or dashboards connecting to this data source inherently respect the row-level security established by the data source filter.

ReferencesThis approach aligns with Tableau’s capabilities for implementing row-level security directly within the data source, as detailed in the Tableau security management and data modeling best practices.

To build efficient extracts from large data sources, it is crucial to minimize the load and optimize the performance of the extracts:

A. Keep only the data required for analysis by using extract filters: This best practice involves using filters to reduce the volume of data extracted, thus focusing only on the data necessary for analysis.

B. Use aggregate data for visible dimensions, whenever possible: Aggregating data at the time of extraction reduces the granularity of the data, which can significantly improve performance and reduce the size of the extract.

E. Hide all unused fields: Removing fields that are not needed for analysis from the extract reduces the complexity and size of the data model, which in turn enhances performance and speeds up load times.

These practices are endorsed in Tableau’s official documentation and training sessions as effective ways to enhance the performance of Tableau extracts and optimize dashboard responsiveness.

Using an extract filter is an effective way to reduce the amount of data in a Tableau extract. Extract filters allow you to specify a subset of the data to include, which can significantly decrease the size of the extract by excluding unnecessary data. This is particularly useful when you only need partial data from a larger SQL Server data source.

References:The recommendation to use extract filters to reduce data size is supported by Tableau’s best practices for optimizing extracts.These practices suggest keeping the extract’s data set short through filtering1.Additionally, discussions in the Tableau Community confirm that hiding fields and using extract filters before extracting data can help reduce the extract size2.

When dealing with large datasets in SQL Server and needing to create a manageable extract in Tableau, using an extract filter is the most direct and effective method to limit the data included:

Extract Filter: This involves setting filters that apply directly when the data is extracted from the source. This means that only the data meeting the specified criteria will be extracted and loaded into Tableau, significantly reducing the size of the extract.

To apply an extract filter, in the Data Source page in Tableau, drag the fields you want to filter by to the Filters shelf. Then, configure the desired filter criteria. When you create the extract, choose the option to "Add Filters to Extract" and select the configured filters. This ensures that only the data that meets these conditions is extracted from the SQL Server.

This approach not only minimizes the data volume but also speeds up performance in Tableau because it processes a smaller subset of the full dataset.

ReferencesThis procedure is described in detail in Tableau's help documentation on managing extracts and optimizing performance by using extract filters, which is recommended for scenarios involving large datasets or when specific subsets of data are required for analysis.

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.

To complete the Pareto chart in the "City Pareto" worksheet of your Tableau Desktop and add reference lines to illustrate how the data compares to the Pareto principle, follow these 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 City Pareto worksheet by selecting its tab at the bottom of the window.

Construct the Pareto Chart:

Ensure that sales data is aggregated by city. If not, drag the 'City' dimension to the Columns shelf and the 'Sales' measure to the Rows shelf.

Sort the sales data in descending order to properly align the cities according to their sales contribution.

To create a running total of sales, right-click on the 'Sales' measure on the Rows shelf, select 'Quick Table Calculation', and choose 'Running Total'.

Drag the 'Number of Records' field to the Rows shelf next to the Sales running total. Right-click on it, select 'Quick Table Calculation', and choose 'Running Total'. Set its calculation to 'Percent of Total' from the 'Edit Table Calculation' option to represent the percentage of cities.

Add Reference Lines for the Pareto Principle:

Click on the Analytics tab in the sidebar.

Drag a 'Reference Line' element and drop it onto the chart area.

Set the Reference Line for the Sales axis at 80% to represent the typical Pareto cutoff where 80% of effects come from 20% of causes.

Add another Reference Line on the axis representing the percentage of cities, set at 20%, to visually assess the Pareto principle.

Adjust the Appearance of the Chart:

Format the reference lines by right-clicking on them, selecting 'Edit', and choosing a distinct style or color to make them stand out.

Ensure the chart is clear and labels are appropriately adjusted for easy understanding of the data visualization.

Save Your Changes:

From the File menu, click 'Save' to ensure all your changes are stored.

References:

Tableau Help: Offers detailed guidance on creating Pareto charts and adding reference lines.

Tableau Visualization Best Practices: Provides tips on effectively displaying cumulative data and principles such as Pareto.

By following these steps, you will have successfully enhanced the City Pareto worksheet to include a complete Pareto chart with reference lines that illustrate how the sales data compares to the Pareto principle, making it easier to analyze and communicate the distribution of sales across cities.

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.

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.

References:

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.

To shape the data in the "US Population Estimates" data source and enter the total number of records into the "Total Records" parameter in Tableau Desktop, follow these 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 Population worksheet by selecting its tab at the bottom of the window.

Format and Shape the Data:

Ensure the data types match those specified in the requirements: Sex, Origin, Race as strings; Year, Age, Population as whole numbers.

To verify or change the data type, click on the dropdown arrow next to each field name in the Data pane and select "Change Data Type" if necessary.

Calculate Total Number of Records:

Create a new calculated field named "Total Records". To do this, right-click in the Data pane and select "Create Calculated Field".

Enter the formulaCOUNT([Record ID])orSUM([Number of Records])depending on how the data source identifies each row uniquely.

Drag this new calculated field onto the worksheet to display the total number of records.

Enter the Value into the Total Records Parameter:

Locate the "Total Records" parameter in the Data pane. Right-click on the parameter and select "Edit".

Manually enter the number displayed from the calculated field into the parameter, ensuring accuracy to meet the data shaping requirement.

Save Your Changes:

From the File menu, click 'Save' to ensure all your changes are stored.

References:

Tableau Desktop Guide: Provides detailed instructions on managing data types, creating calculated fields, and updating parameters.

Tableau Data Shaping Techniques: Outlines effective methods for manipulating and structuring data for analysis.

This process will ensure the data in the "US Population Estimates" is accurately shaped according to the specified format and that the total number of records is correctly calculated and entered into the designated parameter. This thorough approach ensures data integrity and accuracy in reporting.