Salesforce Analytics-Con-301 Exam Dumps

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.

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.

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.

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.

To identify which workbooks need to be updated to point to a new data source after a migration, a consultant should use Tableau Advanced Management. This component of Tableau provides comprehensive management capabilities including the ability to track workbook dependencies and data source usage across your entire Tableau environment. Using Tableau Advanced Management allows consultants to assess the impact of changes in the data source on connected workbooks and efficiently manage updates.

The issue occurs because of Tableau's Order of Operations.

Key Tableau logic:

Top N filters are a type of Dimension filter.

Dimension filters are evaluated after Context filters.

When you place Region on Filters (as a standard dimension filter), Tableau:

First applies the Customer Name Top 10 filter across the entire data set, not per region.

Then limits the view to the selected region(s).

This results in seeing the global Top 10 customers, not the Top 10 per region.

How to fix it:

To force Tableau to compute Top 10 customers within each region, the Region filter must be applied before the Top N Customer filter.

This is done by making Region a Context Filter.

Effect of a Context Filter:

Context filters are executed before the Top N filter.

Region becomes the context.

Tableau then evaluates the Top 10 customers inside each region's subset of data.

This produces the correct ''Top 10 customers per region''.

Why the other options are incorrect:

A . Extract filter

Applies once when creating the extract; does not control Top N logic inside the workbook.

B . Dimension filter

This is what the analyst already has --- and it causes the unwanted behavior because it happens after the Top N filter.

C . Table Calculation filter

Top N is not a table calculation; table calc filters cannot fix this problem.

Only the Context Filter changes the execution order so Top N works per region.

Tableau Order of Operations showing Context Filters applied before Top N filters.

Best practices recommending Context Filters when Top N must be computed within subcategories.

Filtering documentation explaining that Top N filters require context when additional dimensional filters are present.