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

When considering a migration from Tableau Server to Tableau Cloud, two critical factors to consider are the client’s need for single sign-on (SSO) and the volume of concurrent extract refreshes.

Single Sign-On (SSO): Tableau Cloud supports SSO, which can streamline user authentication and enhance security. If the client plans to leverage SSO, Tableau Cloud may be a suitable choice1.

Concurrent Extract Refreshes: The number of concurrent extract refreshes is a significant factor because it impacts performance and resource allocation. Tableau Server might be more appropriate if the client has a high volume of concurrent extract refreshes, as it allows for more control over the infrastructure to manage these workloads2.

To improve the performance of a Tableau workbook, it is best practice to streamline the data being used. This can be achieved by using filters to limit the data to only what is necessary for analysis, hiding fields that are not being used to reduce the complexity of the data model, and aggregating values to simplify the data and reduce the number of rows that need to be processed. These steps can help reduce the load on the server and improve the speed of the workbook.

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.

The discrepancy between the count of workbooks in the Connected Workbooks tab and the lineage count in Tableau Catalog can occur because of user permissions. In Tableau Data Management, the visibility of connected workbooks is subject to the permissions set by administrators. If a user does not have permission to view certain workbooks, they will not see them listed in the Connected Workbooks tab, even though these workbooks are part of the data source’s lineage and are counted in Tableau Catalog.

Comprehensive and Detailed Explanation From Exact Extract:

In Tableau Cloud, database-level RLS can be used only with live connections because:

Tableau Cloud issues SQL queries using the logged-in user's identity.

Extracts break RLS because data is pulled out of the database and stored in Tableau’s hyper file.

To leverage existing RLS rules, Tableau must query the database directly for the user.

Therefore:

Requirement 1:

The Tableau Cloud username (email) must exist in the database

so that the database can enforce RLS using the authenticated identity.

Requirement 2:

Only live data connections support database-native RLS.

Extracts bypass database security and therefore cannot use RLS defined in the database.

Option D is incorrect because RLS is enforced in the database, not configured in Tableau Cloud.

Option B is incorrect because extracts cannot use database RLS.

Thus, correct answers are A and C.

Tableau Cloud live connection security requirements.

Database RLS documentation requiring matching database user identities.

Explanation that extracts bypass database permission systems.

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.

The best approach to ensure performance while providing data for only the last day (yesterday) in the dataset is to use a calculated field that filters the data to include only yesterday's date:

Filter on calculation [Ship Date]=TODAY()-1: This calculated field dynamically computes yesterday's date by subtracting one day from today’s date. This approach ensures that each day, only the data for the previous day is loaded, which keeps the volume of data minimal and improves performance.

Dynamic Date Calculation: The use of TODAY()-1 ensures the filter remains up-to-date with the changing dates, without the need for manual updates, providing accuracy and timeliness in the dashboard.

This approach is efficient because it avoids the overhead of processing the entire dataset and focuses only on the relevant day’s data. It also aligns with Tableau’s capabilities for creating dynamic filters using date functions, as highlighted in the Tableau help documentation on date calculations and filters.

References

This solution utilizes Tableau’s built-in date functions and dynamic calculations to optimize performance, as recommended in Tableau’s performance optimization resources and date calculation guidelines.

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.

References

This 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.

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.

To visualize the path students take as they change majors across different grade levels, a Sankey Diagram is highly effective. This type of visualization illustrates the flow and quantity between different stages or categories:

Sankey Diagram: It allows for a visual representation of students' movements between majors over time. Each flow's thickness is proportional to the number of students moving from one major to another, giving a clear, immediate visual cue of major popularity and student migration patterns.

To create a Sankey Diagram in Tableau, you typically need to prepare the data specifically for this type of chart. The data must include source (starting major), target (ending major), and the value (number of students). It often requires custom calculations and data reshaping to get the data in a format that a Sankey can use.

Once the data is prepared, you can use a combination of calculated fields, path binning, and line charts to simulate the flow effect in Tableau. External plugins or web-based integrations might also be employed for more direct implementations.

References

Sankey Diagrams are not natively supported in Tableau but can be implemented through creative use of data preparation and calculations, as suggested in advanced Tableau user communities and demonstrated in various Tableau public galleries.

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.

Comprehensive and Detailed Explanation From Exact Extract:

The requirement is to compare each quarter’s profit to the median profit over a rolling window of the last four quarters, including the current one. This is a classic use case for WINDOW_ table calculations in Tableau.

Tableau documentation explains:

WINDOW_MEDIAN( expression, start, end ) computes the median of the expression over a window of rows defined by start and end, which are offsets relative to the current row.

To create a rolling calculation that includes the current row and the three preceding rows, the window frame must span four rows ending at the current row.

Conceptually, the correct pattern is:

Current quarter’s profit: SUM([Profit])

Rolling four-quarter median: WINDOW_MEDIAN(SUM([Profit]), previous_3, current)

In actual Tableau syntax, that pattern is written with a frame that begins three rows before the current row and ends at the current row.

Among the options provided:

Options A and B use INDEX() or FIRST() as the start of the window, which creates frames anchored to either the first row or varying positions in the partition, not a consistent four-quarter trailing window.

Option D anchors the frame relative to LAST(), which makes the window depend on the final row in the partition, not a trailing four-quarter window for each bar.

Option C uses a fixed frame of four rows expressed as (3, 0) in the argument list. While, in exact Tableau syntax, a trailing 4-row frame is typically written with a negative start offset and zero as the end offset, this option is clearly intended to represent the frame “three rows back through the current row” and is therefore the only answer that matches the required rolling four-quarter window conceptually.

So, using a WINDOW_MEDIAN over a four-row frame ending at the current row, as shown in option C, is the intended solution for coloring each bar based on whether:

SUM([Profit]) > rolling_median_over_last_4_quarters

Tableau table calculation reference describing WINDOW_ functions and their start/end frame parameters.

Examples in Tableau help that use WINDOW_SUM or WINDOW_AVG with a frame spanning a fixed number of previous rows to compute rolling-window metrics.

Best practices for using WINDOW_MEDIAN to compute rolling medians over sliding time windows.

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

To calculate the Total Sales Value for all categories as displayed in the table, an LOD expression is ideal. An LOD calculation in Tableau allows you to compute values at the data level that is different from the view level. In this case, since the Total Sales Value appears consistent across different sub-categories within each category, an LOD expression can be used to fix the Total Sales Value irrespective of the sub-category detail. Here's how to set it up:

Go to the Calculations area by right-clicking in the data pane and selecting "Create Calculated Field".

Enter a name for the calculation, such as "Total Sales Value".

Enter the LOD expression: { FIXED [Category] : SUM([Sales]) }. This calculation fixes the total sales to the category level, effectively summing sales for all sub-categories within each category, irrespective of how the data is broken down in the view.

Drag this new calculated field into your visualization alongside the existing measures.

This method ensures that the Total Sales Value reflects the total for each category across all its sub-categories, matching the uniform values shown across different rows for each category in your table.

References

The explanation utilizes the concept of Level of Detail calculations in Tableau, which allows for advanced aggregations independent of the view level details. This concept is covered extensively in Tableau's official documentation and relevant training materials such as Tableau's online help resources.

The problem:

The client wants:

Percent of total sales for each region compared to ALL regions,

even when Region is filtered.

However, the calculation currently behaves like a table calculation:

SUM([Sales]) / TOTAL(SUM([Sales]))

This recalculates the total after Region filters are applied, so removing a region changes the denominator.

Tableau Documentation — How to prevent recalculation:

To keep percent-of-total unchanged when filtering, Tableau’s recommended method is to use FIXED LOD expressions to lock the granularity.

Two values must be fixed:

Numerator: Sales for that specific region{ FIXED [Region] : SUM([Sales]) }

Denominator: Total sales across all regions, independent of filters{ FIXED : SUM([Sales]) }(FIXED with no dimension = entire data set)

Then compute the percentage:

{ FIXED [Region] : SUM([Sales]) } / { FIXED : SUM([Sales]) }

This ensures:

The region sales remain accurate.

The overall total remains constant, even if filters remove regions.

Region filtering no longer recalculates percent-of-total.

Why the other options are incorrect:

A. {FIXED [Region]: SUM([Sales])} / SUM([Sales])

The denominator is still affected by filters → recalculates % of total.

B. {FIXED [Region]: SUM([Sales])} / { [Sales] }

{[Sales]} is not valid syntax and does not fix granularity.

D. {FIXED [Region]: SUM([Sales])}

This gives only the numerator — no percent-of-total calculation.

The only correct LOD solution is option C.

Tableau LOD Expression Guide: FIXED for filter-independent calculations.

Tableau Percent-of-Total Best Practices: use FIXED LOD to avoid recalculation when filters change.

Order of Operations: FIXED LODs occur before dimension filters, keeping totals stable.

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.

To improve the performance of a Tableau dashboard while maintaining accurate counts, particularly when dealing with unknown or NULL BrowserIDs in the data tables, the following steps are recommended:

Modify the Browser Table: Add a new row to the Browser Table labeled "Unknown," assigning it a unique BrowserID, e.g., 0 or 4.

Update the Site Visitor Table: Replace all NULL BrowserID entries with the BrowserID assigned to the "Unknown" entry. This ensures every record in the Site Visitor Table has a valid BrowserID that corresponds to an entry in the Browser Table.

Change Referential Integrity Setting: Change the Referential Integrity setting from "Some Records Match" to "All Records Match." This change assumes all records in the primary table have corresponding records in the secondary table, which improves query performance by allowing Tableau to make optimizations based on this assumption.

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 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 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 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 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 formula COUNT([Record ID]) or SUM([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.

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.