Analytics-Con-301 Salesforce Certified Tableau Consultant Questions and Answers

For a performant live connection in Tableau Cloud, especially when dealing with large datasets that preclude the use of extracts, relating the tables in Tableau Desktop is the recommended approach. This method allows for flexibility in how the data is queried and can improve performance by leveraging Tableau’s relationships feature, which optimizes queries for the underlying database.

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.

When field agents are unable to access workbooks due to issues with security token-based credentials, the most immediate and least disruptive solution is to renew the security token. This can be done through the Data Connection settings on Tableau Server. Renewing the token will restore access for the field agents without requiring them to take any action or affecting other users.

In Tableau, the performance of calculated fields can vary based on the data type used. Calculations involving integers and Booleans are generally faster than those involving strings. This is because numerical operations are typically more efficient for a computer to process than string operations, which can be more complex and time-consuming. Therefore, when performance is a consideration, it is advisable to use integers or Booleans over strings whenever possible.

When “Apply to Nested Projects” is checked in Tableau Server, the permission rules set at the top-level project are enforced for all assets in the project and all nested projects. This means that any custom access previously granted to nested projects will be overridden, and the permissions will revert to those defined at the top-level project. This action ensures consistent application of the data governance strategy across all divisions.

The most efficient way to limit report visibility to specific user groups on Tableau Server is to manage permissions directly on the server. By granting access to the report only to the sales and marketing user groups, the client ensures that only members of these groups can view the report. This method is straightforward and does not require the additional steps involved in setting up row-level security or user filters.

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 processed 1 2 .

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.

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.

To modify the Percent Contribution calculated field to use a Level of Detail (LOD) expression and accurately calculate the percentage contribution of each manufacturer to the total quantity, follow these steps:

Open the CC Workbook and Access the Worksheet :

Double-click on the CC workbook from the desktop to open it in Tableau Desktop.

Navigate to the Manufacturers worksheet by selecting its tab at the bottom of the window.

Modify the Percent Contribution Calculated Field :

Navigate to the Data pane and find the " Percent Contribution " calculated field.

Right-click on the " Percent Contribution " field and select ' Edit ' .

Modify the formula to incorporate an LOD expression that calculates the total quantity across all manufacturers and the specific quantity per manufacturer:

{FIXED [Manufacturer]: SUM([Quantity] )} / {SUM([Quantity])}Quantity ])}

This formula uses {FIXED [Manufacturer]: SUM([Quantity] )} to compute the total quantity contributed by each manufacturer, regardless of other dimensions in the view. The total quantity {SUM([Quantity])} calculates the grand total across all manufacturers. The division calculates the percentage contribution.

Click ' OK ' to save the updated calculated field.

Enter Percentage for Newell :

With the updated " Percent Contribution " field, drag it onto the view to update the chart or table.

Identify the value corresponding to ' Newell ' in the updated visualization.

Round this value to the nearest hundredth of a percent as required.

Enter this value into the " Newell % Contribution " parameter. To do this, locate the parameter in the Data pane or on the dashboard, right-click it, and choose ' Edit ' . Enter the calculated percentage for Newell.

Save Your Changes :

From the File menu, click ' Save ' to store all the modifications you have made to the workbook.

To compute the required calculations and update the worksheet in Tableau Desktop, follow these steps:

Compute Average Sales by Segment for Each Category and Year :

Open the CC workbook and navigate to the Categorical Sales worksheet.

Drag the ' Sales ' field to the Rows shelf if it ' s not already there.

Drag the ' Segment ' field to the Rows shelf as well, placing it next to ' Category ' and ' Year ' .

Right-click on the ' Sales ' field in the Rows shelf and select ' Quick Table Calculation ' > ' Average ' . This will compute the average sales for each segment within each category and year.

Create a Calculation for Year-over-Year Percentage Change :

Right-click in the data pane and select ' Create Calculated Field ' .

Name the calculated field something descriptive, e.g., " YoY Sales Change " .

Enter the formula to calculate the year-over-year percentage change:

(ZN(SUM([Sales])) - LOOKUP(ZN(SUM([Sales] )), -1)) / ABS(LOOKUP(ZN(SUM([Sales])), -1))

Click ' OK ' to save the calculated field.

Replace the Original Measure with the Year-over-Year Percentage Change in the Crosstab :

Remove the original ' Sales ' measure from the view by dragging it off the Rows shelf.

Drag the newly created " YoY Sales Change " calculated field to the Rows shelf where the ' Sales ' field was originally.

Format the " YoY Sales Change " field to display as a percentage. Right-click on the field in the Rows shelf, select ' Format ' , and adjust the number format to percentage.

Save Your Changes :

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

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.

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.

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.

To effectively curate and document data for obtaining data lineage, particularly from a data source connected to a data lake, the recommended tool is:

Tableau Catalog with Tableau Data Management Add-on : This add-on enhances the capabilities of Tableau Catalog, providing extensive features for data management, including detailed data lineage, impact analysis, and metadata management.

Functionality : The Tableau Catalog with the Data Management Add-on allows users to see the full history and lineage of the data, trace its usage across all Tableau content, and understand dependencies. It also facilitates better governance and transparency in data handling.

Why Choose this Tool : For a client needing comprehensive data lineage and documentation capabilities, this add-on ensures that data stewards and users can maintain and utilize a well-managed data environment. It supports robust data governance practices necessary for large and complex data ecosystems like those typically associated with data lakes.

References

The recommendation is based on the functionalities offered by the Tableau Data Management Add-on, as described in Tableau ' s official documentation on managing and documenting data sources for enhanced governance and operational efficiency.

Comprehensive and Detailed Explanation From Exact Extract:

The key requirements:

Tableau Cloud

Extracts (not live data)

Need RLS

Want low maintenance

Have Tableau Data Management

These requirements point directly to:

Data Policies (Virtual Connections RLS)

Tableau Data Management enables Virtual Connections and Data Policies , which provide:

Centralized row-level security

Integration with user identity via USERNAME()

Reusable RLS logic across all downstream workbooks

Works with extracts , unlike database RLS

Minimal long-term maintenance

This is Tableau’s recommended enterprise RLS method for Tableau Cloud with extracts.

Why the other options are incorrect:

A. Built-in RLS in Snowflake

Only works with live connections.

This client uses daily extracts , so database RLS is bypassed.

C. Manual user filter

High maintenance, must be edited manually per user — not scalable.

D. Dynamic user filter

Functional but must be recreated in each workbook , not centralized.

More maintenance than a data policy.

Therefore, Data Policy is the only low-maintenance, centralized RLS solution.

Data Policies and Virtual Connections documentation describing centralized RLS

Tableau Cloud & Extracts guidelines showing that database RLS cannot be reused

RLS strategy best practices recommending Data Policies for scalable governance

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.