Explanation:

In Tableau stories, the navigator style determines how users move between story points. The Arrows only option displays the current story point number out of the total (e.g., "1/5" or "3/8") along with navigation arrows. This matches the requirement exactly—showing the current point number and the total count.

Why other options are incorrect:

B. Caption boxes: This is the default style that displays the full caption of each story point in a box below the story. It does not show the current/total point count.

C. Numbers: This shows a simple page number (e.g., "3") without indicating the total number of story points. It lacks the fraction format.

D. Dots:This displays a series of dots representing each story point, similar to a progress bar. It does not show numeric values or the total count.

Reference:

Tableau Help: Navigator Style for Stories – The "Arrows only" option shows the current point number and total count, while other styles serve different navigation purposes.

Explanation:

In Tableau dashboards, padding controls the amount of blank space (internal margin) around the edges of a dashboard object, such as a sheet, container, or text box. When there is excessive whitespace between two sheets, reducing the padding will bring them closer together.

Why C is correct:

Padding is the space between the content of a dashboard object and its border. It can be set individually for the top, bottom, left, and right sides.
To minimize whitespace between sheets, you would reduce the padding (specifically, the bottom padding of the top sheet or the top padding of the bottom sheet) to close the gap.
Padding settings are found in the Layout pane when a dashboard object is selected.

Why other options are incorrect:

. The background: This changes the color or image behind dashboard objects. It does not affect the spacing between sheets.

B. The position: Position controls the X/Y coordinates of a floating object. For tiled layouts, position is determined automatically, and adjusting it does not reduce whitespace—it only moves floating objects.

D. The size: Size controls the overall dimensions of the dashboard or an object. Resizing sheets might inadvertently reduce whitespace, but it is not the direct or intended control for minimizing whitespace between objects. Padding is the correct setting.

E. The border: Border controls the line style, color, and thickness around an object. It does not affect spacing or whitespace.

Reference:

Tableau Help: Dashboard Layout – Padding – Padding sets the amount of space between the object's contents and its outer edges. Reducing padding minimizes the whitespace around and between dashboard items.

Explanation:

To change the structural granularity of a dataset—such as converting highly detailed row frequencies (monthly data) into a more summarized representation (yearly data)—you must compress and group the rows using an Aggregate step in Tableau Prep.

The Core Logic: Moving from months to years means going from a lower level of detail to a higher, more summarized level of detail. This requires a mathematical grouping function (like SUM or AVG) to consolidate multiple monthly data points into a single annual record.

The Mechanism: * Inside the Aggregate step, you place the Year field into the Grouped Fields pane.

You place your numeric metrics (such as Prices, GDP, etc.) into the Aggregated Fields pane, selecting an aggregation type like SUM or AVG depending on the metric.

This reduces the row count by collapsing the twelve individual monthly rows for each year into one comprehensive annual row.

Why Other Steps Are Incorrect:

Clean Step: A Clean step is used for row-level transformations (splitting fields, renaming columns, filtering specific values, or changing data types). It cannot change the structural volume or granularity of the records by combining rows.

Pivot Step: A Pivot step converts data from columns to rows (tall format) or rows to columns (wide format). While it changes layout shapes, it is not designed to compress chronological frequencies (months to years) via mathematical groupings.

Join Step: A Join step combines data horizontally from two separate datasets based on a shared key field. It does not perform vertical summarization or row compression on its own.

References:

Tableau Prep Documentation (Aggregate and Group Values): "If you want to change the granularity of your data to make it less detailed, or to summarize data, you can create an Aggregate step to group and aggregate data."

Explanation:

The Position column in the table shows the relative position of each Segment, with Corporate at 0, Home Office at -1, and Consumer at -2. This indicates that the position is determined by the Sales measure, with the highest Sales value receiving position 0, the second highest receiving -1, and the lowest receiving -2.

Why FIRST is correct:

FIRST() is a table calculation function that returns the position of the current row relative to the first row in the partition.

In this view, the table is sorted by Sales in descending order (highest Sales first). Consumer has the highest Sales ($1,161,401) and appears first → FIRST() returns 0 for it.

However, the table in the exhibit shows Consumer at -2, Corporate at 0, and Home Office at -1, which suggests the sort order is ascending (lowest Sales first). Corporate has the lowest Sales ($706,146) and appears first → FIRST() returns 0 for it, Home Office second → -1, Consumer third → -2.

This matches the Position column exactly: Corporate 0, Home Office -1, Consumer -2.

Why other options are incorrect:

A. INDEX: INDEX() returns the index of the current row (e.g., 1, 2, 3) in the partition, starting from 1. It does not produce negative numbers and does not start at 0.

B. RANK: RANK() returns the rank of the current row (e.g., 1, 2, 3) based on a measure. It does not produce negative numbers or the 0, -1, -2 pattern. Ranks are positive integers (1, 2, 3).

D. LAST:LAST() returns the position relative to the last row in the partition. For the last row, it returns 0; for the second-to-last, it returns -1; for the third-to-last, it returns -2. If the table were sorted in descending order (highest Sales first), Consumer would be last and receive 0, which is not the pattern shown.

Reference:

Tableau Help:FIRST() Function – "FIRST returns the number of rows from the current row to the first row in the partition. For the first row in the partition, this is 0."

Explanation:

In Tableau Server/Cloud, an extract background task is not restricted to a single timeline automation. A workbook or data source can have multiple independent refresh schedules assigned to it simultaneously.

The Core Logic: To retain the existing routine (every Monday at 10:00) while introducing a secondary automation ruleset (last day of the month at 18:00), you must append a completely separate extract task.

The Mechanism: Navigating to the workbook's management page inside the Tableau Server web interface, clicking on the Extract Refreshes tab, and choosing New Extract Refresh allows an administrator or workbook owner to select an additional pre-defined server schedule without overwriting or altering the primary active Monday routine.

Why Other Options Are Incorrect:

A. Changing the schedule frequency:
Modifying the frequency of the existing schedule itself will globally rewrite that specific schedule slot. Doing this would replace the Monday automation entirely, causing the workbook to only update at the end of the month.

B. Changing the priority:
Adjusting schedule priority controls the processing order in the backgrounder queue when multiple tasks conflict at the exact same moment. It does not create new schedule timestamps or change runtime rules.

D. Configuring the Publish Workbook dialog box: While you can assign an initial schedule during the primary publishing phase from Tableau Desktop, adding multiple concurrent independent schedules to a single asset is managed directly via the Tableau Server/Cloud web browser interface post-publish.

References:

Tableau Server Documentation (Manage Refresh Schedules): "You can assign multiple schedules to a single workbook or data source. In the web environment, go to the Extracts Refresh tab for the asset to add or remove additional tasks."