Salesforce Analytics-Con-301 Dumps - Pass Salesforce Certified Tableau Consultant Exam in First Attempt 2026

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.

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.

Tableau Help: Offers guidance on creating calculated fields and using table calculations.

Tableau Desktop User Guide: Provides instructions on formatting and saving worksheets.

These steps allow you to manipulate data within Tableau effectively, using table calculations to analyze trends and changes in sales data by category and segment over years.

Topic 3, Knowledge-Based Section B

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.

Reference

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.

When dashboards are published to Tableau Cloud, the function USERNAME() returns the user's Tableau Cloud username, which is the email address associated with their Tableau Cloud account.

Tableau documentation states:

On Tableau Cloud, the value returned by USERNAME() is always the user's email address.

Row-Level Security (RLS) is typically implemented using a comparison of USERNAME() to an email field in the data source.

For secure filtering, the field compared to USERNAME() must match the authentication identity exactly.

Looking at the provided table:

''Abbreviated Name'' contains short custom codes like ''SMiller,'' which do not match Tableau Cloud usernames.

''Lower Case Name'' contains names like ''sean miller,'' which also do not match Tableau Cloud usernames.

''Email'' contains the full email address for each user, such as ''Sean.Miller@superstore.com,'' which is the only field that corresponds to what USERNAME() returns in Tableau Cloud.

Therefore, the correct field to reference is Email.

Tableau Cloud authentication documentation stating USERNAME() returns the user's email address.

Row-Level Security setup guidance recommending the comparison USERNAME() = [Email Field].

Tableau security practices indicating only the email column will match USERNAME() values on Tableau Cloud.

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.