Explanation:

The analyst needs to get the Customer ID and Customer Name for only the orders that were returned. This means the result should include only the orders that have a matching return record in the Returns table. Orders that were not returned should be excluded entirely.

Why Inner join is correct:
An Inner join returns only the rows where there is a match in both tables based on the join key (e.g., Order ID). Since Orders is the leading table and the requirement is to include only orders that were returned, the Inner join will correctly filter to only those orders that exist in both Orders and Returns.
This matches the requirement exactly: "only the orders that were returned."
Why other options are incorrect:

A. Left join:
A Left join would return all rows from the Orders table and only matching rows from Returns. Orders without a matching return would still appear, with null values for Returns fields. This would include orders that were not returned, which does not meet the requirement.

B. Unmatched only join:
This is not a standard join type in Tableau Prep. Tableau Prep offers Left, Right, Inner, and Full Outer joins, but not an "Unmatched only" join. This option does not exist.

D. Full join:
A Full join returns all rows from both tables, regardless of matches. This would include orders without returns and returns without orders, which is far broader than the requirement.

Reference:

Tableau Prep Help: Join Data – An Inner join returns only rows where the join condition is met in both tables, effectively filtering to only matching records. This is the appropriate choice when you need only the intersection of two datasets.

Explanation:

This question tests your understanding of how to control dashboard filtering behavior without breaking existing interactions.

The Current State: The map chart (Profits by State) has the quick "Use as Filter" toggle enabled. By default, when this shortcut is turned on, clicking a data point on the map will broadcast a filter action to every other worksheet currently residing on the dashboard canvas (affecting both Sales over time and the Detail table).

The Requirement: The analyst wants the map selection to only filter the Detail table. This means the Sales over time line chart needs to stop responding to that map selection.

The Solution: Every individual worksheet container on a dashboard has a context drop-down menu option called Ignore Actions. Activating this setting on the Sales over time sheet tells Tableau's action engine to immunize this specific visual container from any incoming filter broadcasts originating from other sheets on the dashboard. Consequently, the map will continue to filter the Detail table, while Sales over time remains static and unaffected.

Why Other Options Are Incorrect:

A. Select Remove Dashboard Item...: This will delete the entire Sales over time chart completely from the dashboard canvas interface.

C. Select Deselect...: There is no configuration option named "Deselect" in the sheet container context menu that alters action target routing.

D. Deselect Use as Filter from drop-down menu of Profits by State: Disabling this shortcut on the map would completely turn off its filtering capability across the entire dashboard, meaning it would stop filtering the Detail table as well.

References:

Tableau Documentation (Filter Actions and Interactivity): "To prevent a sheet from being filtered by dashboard actions altogether, click the drop-down menu on the sheet container you want to isolate and select Ignore Actions."

Explanation:

This configuration question tests your understanding of Tableau Dashboard Actions and how different execution behaviors change the user experience.

The Name Field: The prompt explicitly states that the link inside the tooltip must be named exactly "Click here to know more!". Whatever text string you type into the Name field of a URL action dialog box determines the literal hyperlink label shown to the end user inside the tooltip pane.

The "Run action on" Trigger (Menu): * Menu: This selection tells Tableau to place a text hyperlink inside the standard tooltip popover window when a user hovers over or clicks a data mark. The action does not execute instantly; instead, it waits for the user to explicitly click that text link. This matches the exact visual interface layout shown in image_c08047.png.

Why Other Options Are Incorrect:

Select: Running a URL action on Select triggers the hyperlink instantly the moment a user clicks on a bar mark, opening the web browser immediately without displaying a text link inside a tooltip first.

Hover: Running a URL action on Hover automatically launches the target website background window immediately when a mouse pointer skims over the top of a visual bar mark.

References:

Tableau Documentation (URL Actions): "Select Menu if you want the action to run from a link inside the tooltip menu when a user clicks or hovers over a mark."

Explanation:

The Rank field is a table calculation that recomputes dynamically based on the data currently in the view. When you filter out the sub-category where [Overall Rank] = 1 (Phones), the partition changes, and Rank values are recalculated for the remaining rows.

Since the Rank is computed within each Category (Furniture and Technology separately), filtering Phones (Technology) affects only the Technology partition. The Furniture partition remains unchanged because no Furniture sub-category was removed.

Technology partition after Phones is removed:

Machines (189,239) → Rank changes from 2 → 1
Accessories (167,380) → Rank changes from 3 → 2
Copiers (149,528) → Rank changes from 4 → 3
Thus, the three sub-categories whose Rank changes are Accessories, Copiers, and Machines.

Why other options are incorrect:

A. Furnishings, B. Tables, C. Chairs, and G. Bookcases: These belong to the Furniture category. Since no Furniture sub-category was filtered, their Rank values remain unchanged (Chairs = 1, Tables = 2, Bookcases = 3, Furnishings = 4).

G. Phones:This sub-category is filtered out entirely, so it no longer appears in the view. Its Rank does not "change" because it is removed.

Reference:

Tableau Help: RANK Function and Filters – Table calculations are computed on the filtered data in the view. When a dimension is filtered out, the partition changes, and RANK recalculates for the remaining rows.

Explanation:

The analyst needs to count the number of different types of awards that have been won. This requires counting the distinct (unique) values in the Award field, not the total number of awards won or the number of people.

Why D is correct:

COUNTD([Award]) calculates the distinct count of unique award types in the dataset. For example, if the awards include "Oscar," "Grammy," "Oscar," and "Emmy," COUNTD([Award]) would return 3 (Oscar, Grammy, Emmy).

This directly matches the requirement of counting the number of different types of awards.

Why other options are incorrect:

A. COUNTD([NAME]):
This counts the number of distinct people who have won awards, not the number of distinct award types. This does not meet the requirement.

B. COUNT([Award]):
This counts the total number of awards won (including duplicates). For example, if the dataset has "Oscar," "Grammy," and "Oscar," COUNT([Award]) would return 3, not the number of different types (which would be 2).

C. WINDOW_COUNT([Award]):
This is a table calculation that counts the number of rows in a window (a partition of the data). It is used for dynamic aggregations within a view, not for calculating a static distinct count of a dimension.

Reference:

Tableau Help: COUNTD Function – COUNTD returns the number of distinct (unique) values in a field.