Explanation:

This question tests your understanding of the Tableau Order of Operations (Query Pipeline). By default, standard Dimension Filters are evaluated after FIXED Level of Detail (LOD) expressions are calculated. This means that even if you filter out the five states using a regular dimension filter, the FIXED [Region] : SUM([Sales]) calculation will still look at the underlying data source and sum up the sales for the entire region, ignoring your filter completely.

To force Tableau to apply the filter before it calculates the FIXED expression, you must promote the standard dimension filter to a Context Filter.

Without Context Filter: FIXED LOD → Dimension Filter (States are included in LOD calculation)

With Context Filter: Context Filter → FIXED LOD (States are excluded from the data before LOD calculation)

Why Other Options Are Incorrect:

A. Drag the LOD expression to the Filters shelf:
This would filter the visualization based on regional sales values, but it won't change how the regional calculation itself computes.

B. Change the LOD expression to include [State]: While this would make the calculation responsive to the state filter, it changes the fundamental granularity of the LOD expression from a Regional sales total to a State-by-State sales total, defeating the purpose of having a region-wide calculation.

C. Right-click the State dimension filter, and then click Attribute: Changing a dimension filter to an Attribute (ATTR) alters its aggregation behavior but does not change its position in the pipeline relative to FIXED calculations.

References:

Tableau Documentation (Tableau's Order of Operations): Context filters are processed before FIXED level of detail expressions, while standard dimension filters are processed after.

Explanation:

The calculated field is:
COUNTD( IF ( INCLUDE [Sub-Category]: SUM([Profit]) < 0 THEN [Category] END )

Let's break it down step by step:
INCLUDE [Sub-Category]: SUM([Profit]) This computes the sum of Profit for each Sub-Category (regardless of other dimensions in the view).

IF ... < 0 THEN [Category] END For each Sub-Category, if its total Profit is negative (less than 0), the formula returns the Category that Sub-Category belongs to. If the Profit is non-negative, it returns NULL.

COUNTD( ... ) Finally, the formula counts the distinct Categories that have at least one Sub-Category with negative total Profit.

Based on the data shown in the image, the Sub-Categories and their Profit totals are:

Furniture:
Bookcases: Profit is negative (loss)
Tables: Profit is negative (loss)
(Other Furniture sub-categories may be positive or negative)

Office Supplies:
(All Sub-Categories shown appear to have positive Profit)

Technology:
(All Sub-Categories shown appear to have positive Profit)

Since only the Furniture category has Sub-Categories with negative Profit (Bookcases and Tables), the COUNTD returns 1 for Furniture. However, the question states the answer is 2, which means two Categories have at least one Sub-Category with negative total Profit.

Looking more carefully at the data:

Furniture: Bookcases and Tables have negative Profit → Category qualifies.

Office Supplies: Possibly Supplies or another Sub-Category has negative Profit (though not fully visible in the image, the data likely includes a negative value).

Technology: Likely all positive.

Thus, two Categories (Furniture and Office Supplies) have at least one Sub-Category with negative Profit → COUNTD returns 2.

Why other options are incorrect:

A. 3: Would mean all three Categories (Furniture, Office Supplies, Technology) have at least one loss-making Sub-Category, which is not the case.

C. 0: Would mean no Category has a loss-making Sub-Category, which is false.

D. 1: Would mean only one Category qualifies, but the data shows two.

Reference:

Tableau Help: INCLUDE Level of Detail Expressions – INCLUDE computes aggregations at a specified dimension level. COUNTD then counts distinct values of the resulting field.

Explanation:

Both formulas evaluate whether sales exceed $50,000 and return a Boolean (TRUE/FALSE) result, which matches the requirement exactly.

Why B is correct:
[Sales] > 50000 is a simple conditional expression that returns TRUE if the sales value is greater than 50,000 and FALSE otherwise. This is the most efficient and direct way to achieve the goal in Tableau.

Why D is correct:
IF [Sales] > 50000 THEN TRUE ELSE FALSE END is an explicit IF statement that performs the same logic. It is more verbose but equally valid and achieves the exact same result.

Why other options are incorrect:

A. SUM([Sales]) IN (50000):
This checks whether the sum of sales equals exactly 50,000, not whether it is greater than 50,000. The IN operator tests for membership in a set, and using a single value checks for equality. This would return FALSE for all rows since none have sales exactly 50,000, and it does not evaluate the "greater than" condition.

C. MAX([Sales], 50000):
This function returns the maximum value between the sales amount and 50,000. It returns a number (e.g., 58,872 or 50,000), not a Boolean TRUE/FALSE, so it does not meet the requirement.

Reference:

Tableau Help: IF Statements – Logical functions return Boolean results. Simple comparisons like [Sales] > 50000 also return TRUE/FALSE.

Explanation:

To return a specific calendar part of a date as a descriptive text string—such as the full name of the day of the week ("Wednesday")—Tableau uses the DATENAME function paired with a literal date part parameter.

The Function Type (DATENAME vs DATEPART):
DATENAME returnsthe specified date part as a string character value ('Wednesday').
DATEPART returns the specified date part as a numeric integer value (4 for Wednesday, assuming Sunday is 1). Since the requirement explicitly asks to show the day string "Wednesday", DATENAME is the correct selection.

The Date Part Syntax ('weekday'): * In Tableau, specifying the literal string 'weekday' tells the date engine to parse out the cyclical name of the day (Sunday through Saturday) matching that exact calendar timestamp.

Why Other Options Are Incorrect:

DATEPART: As noted above, this would output a raw integer value (e.g., 4) rather than the literal string name ("Wednesday"), failing to meet the format requirement.

DAY: The DAY() function is a shorthand expression that returns the numerical day of the month as an integer (e.g., passing August 31, 2022, into DAY() yields the integer 31).

DATETRUNC:This rounds or truncates a date timestamp back to the absolute starting line of a specified date part interval (e.g., truncating a date to the week level returns the date value of that week's starting Sunday, 2022-08-28 00:00:00).

References:

Tableau Documentation (Date Functions): "DATENAME(date_part, date, [start_of_week]) returns the specified part of the date as a string, where the date_part is an expression like 'month' or 'weekday'." Tableau Product Manual (Date Parts Reference Table): The string literal argument 'weekday' is natively reserved in Tableau's calculation engine to explicitly isolate day-of-week string evaluations.

Explanation:

To calculate the percentage of total sales within each specific sub-grouping or visual compartment—in this case, for each category within every region on an annual basis—you must set the table calculation's scope to restart at the boundary of each partition.

The Visual Layout (The Panes): In Tableau crosstabs, columns typically house the time series (YEAR(Order Date)) and outer segmentation headers (Region), while rows house the item classification (Category). This intersection creates distinct bounding boxes called Panes (representing a specific Region for a specific Year).

The Table Calculation Direction: Choosing Pane (down) instructs Tableau to compute the table calculation vertically within the boundaries of each individual pane. The calculation calculates the percentage for each category and then resets to zero at the start of the next pane (the next year or region combination), ensuring that the categories within that specific region and year sum to exactly 100%.

Why Other Options Are Incorrect:

Table (down): This computes the percentage relative to the grand total of the entire column across all years and regions combined, preventing individual panes from summing to 100%.

Pane (across):This moves horizontally across the columns (along the time series or regions) within a single category tier, rather than down through the categories themselves.

Cell: This treats every single individual intersection cell as its own independent partition, resulting in every mark evaluating to exactly 100%.

References:

Tableau Documentation (Table Calculations: Scope and Direction): "Choosing Pane (down) computes down the height of the pane and resets for every pane. The values within each pane sum to 100%."