Analytics-101 Salesforce Certified Tableau Desktop Foundations Questions and Answers

The correct option is Nested because the Sub-category members must be sorted independently within each Category based on Sales. A nested sort evaluates the measure separately inside each pane or parent dimensional grouping. In this example, the Home sub-categories should be sorted according to their Home Sales values, while the Bath sub-categories must be sorted independently according to the Bath Sales values. For Home, Bulk has Sales of $50 and Accessory has $60, so ascending order is Bulk followed by Accessory. For Bath, Accessory has $45 and Bulk has $75, so ascending order is Accessory followed by Bulk. This demonstrates why a single global ordering is insufficient: the correct Sub-category order differs between the two Category groups. A non-nested field sort can produce a consistent order based on aggregated values across the view, which would not satisfy the requirement to rank Sub-category independently inside each Category. Manual sorting would require explicit maintenance, while data source order simply follows the ordering supplied by the underlying source. Tableau's official sorting documentation states that nested sorting considers values independently per pane and sorts the values separately within those panes.

Double-clicking a continuous numeric measure such as Sales in an empty Tableau worksheet automatically produces a bar chart, making C correct. Tableau uses intelligent defaults when fields are double-clicked in the Data pane. With a single measure and no dimensions already defining the view, Tableau aggregates the measure—normally using its default aggregation such as SUM—and adds it to the visualization. The Automatic mark type resolves to a bar, producing a single bar representing the aggregated Sales value. Tableau's official documentation provides this exact construction using the Profit measure. It states that double-clicking Profit automatically adds the field to the view in an intelligent way, and the documented resulting visualization is a bar chart of Profit. Sales is the same type of field—a quantitative measure—so the same automatic-view rule applies. A line chart ordinarily requires an ordered dimension such as a date field to provide a sequence across which values can be connected. A pie chart requires additional categorical structure for meaningful segmentation. A text table is generally created when a dimension is double-clicked first and subsequent fields refine that cross-tabular structure. Therefore, a lone continuous numeric measure double-clicked in a new worksheet produces the automatic single-measure bar visualization.

A continuous date field produces a green pill and generates an axis, making B and C correct. Tableau uses color as an immediate visual cue for discrete versus continuous fields. Green pills represent continuous fields, whereas blue pills represent discrete fields. A date can function in either form. When the analyst chooses a continuous date value such as continuous Month or continuous Year, Tableau represents the field as an unbroken temporal range rather than a finite collection of date-part headers. When this continuous date is placed on the Rows shelf, Tableau generates a continuous axis corresponding to the selected temporal granularity. The axis behaves similarly to other continuous quantitative axes in the sense that values occupy positions along an uninterrupted scale. Option A instead characterizes a discrete date part, such as discrete Month, where Tableau creates categorical headers or labels like January, February, and March. Option D is likewise associated with discrete fields because discrete pills are blue. Tableau's official Continuous Dates documentation states that continuous dates create an axis and that converting a date field to continuous causes the field to turn green. Tableau's general field-role documentation separately confirms that continuous fields create axes while discrete fields create headers.

For a standard custom latitude field, Tableau recommends a Number (decimal) data type and a Measure data role. Therefore, A and B are correct. Latitude represents a numeric coordinate, including fractional values such as 40.7128, so Number (decimal) is the appropriate data type. Treating latitude as a measure enables Tableau to position coordinate values continuously on an axis rather than interpreting each coordinate as an independent categorical member. Tableau's official mapping guidance states that, in most cases, latitude and longitude fields should have a data type of Number (decimal), a data role of Measure, and the corresponding Latitude or Longitude geographic role. When used in a map, Longitude is normally placed on Columns and Latitude on Rows as continuous measures. This differs from geographic fields such as Country, State, or City, which are usually string dimensions. Although specialized mapping scenarios can convert latitude or longitude to dimensions, that is not the standard configuration addressed by this question. The official Tableau mapping documentation explicitly specifies the Number (decimal) + Measure configuration for latitude and longitude fields when preparing geographic data for mapping.

Opacity is the appropriate control when the objective is to change how intense or subdued the existing colors appear. In Tableau, the Color controls on the Marks card include an Opacity slider. Moving this control toward lower opacity makes marks increasingly transparent; increasing opacity makes the applied colors visually stronger and less transparent. Therefore, C is correct. The other options modify different properties. Border adds an outline around supported mark types and does not control the overall intensity of the fill color. Reversed inverts the ordering of a quantitative color palette—for example, changing a sequential palette so that lower values receive the darker intensity and higher values receive the lighter intensity. It changes which values receive each shade rather than controlling overall opacity. Stepped Color converts a continuous quantitative palette into a specified number of discrete color bands or bins. Tableau's current Color Palettes and Effects documentation explicitly identifies Opacity as the setting used to modify the transparency of marks. It separately defines Reversed as inverting the order of colors and Stepped Color as grouping quantitative values into uniform color bins. These distinctions make Opacity the correct setting for modifying visual color intensity.

The icon displayed to the right of the legend title is Tableau's highlighting control. Therefore, clicking it controls legend highlighting, making C the correct answer. Legend highlighting is an interactive analytical feature that allows the viewer to focus on specific marks associated with a selected legend member. When highlighting is enabled and a value such as Business Class or First Class is selected, Tableau emphasizes the corresponding marks while visually dimming unrelated marks. This makes it possible to investigate one category without filtering other categories out of the visualization. Tableau supports both one-way and two-way legend highlighting. The icon displayed at the top of the legend indicates the available highlighting mode. In two-way highlighting, interaction can occur from either the legend or marks in the visualization. The Edit Colors command is accessed through the legend's menu or other color controls, not by clicking this highlighter icon. Likewise, the icon does not expose filter settings and does not hide or display the legend itself. Official Tableau documentation explicitly states that the icon at the top of the legend represents legend highlighting and can be used to control highlighting behavior.

Tableau provides direct single-click sorting controls from a header, an axis, and a field label, making A, C, and D correct. Tableau's official Sort Data in a Visualization documentation explicitly identifies these three locations. When the user hovers over an appropriate header, numerical axis, or field label, Tableau can display a sort icon. One click typically applies descending sorting, a second click changes it to ascending, and another interaction can clear the sort depending on context. A header is commonly generated by a discrete field and can expose sorting for its members. A numerical axis allows the associated categorical members to be sorted according to measure values. A field label can similarly provide direct sorting when applicable to the view's structure. The Tooltip area of the Marks card controls information displayed when the pointer hovers over a mark; it is not a sorting interface. The Worksheet and Analysis menus contain numerous authoring commands but are not the three direct locations identified by Tableau's single-click sorting workflow in this question. Official Tableau documentation specifically states: "Quickly sort from an axis, header, or field label," precisely matching A, C, and D.

Tableau provides three principal scope levels for reference lines: Entire Table, Per Pane, and Per Cell. Therefore, A, B, and D are correct. Scope determines the partition of the visualization over which Tableau calculates and displays the reference line. Entire Table computes one reference value based on all applicable marks in the view. This is appropriate for a global benchmark such as overall average Sales. Per Pane creates a separate reference line for each pane. For example, if a visualization is partitioned by Region, Tableau can calculate an independent average for each regional pane. Per Cell is still more granular and can calculate a separate reference line for each cell defined by the row and column structure of the view. Maximum is not a scope; it is a possible statistical value or computation that can be used to determine the reference-line value. Similarly, Fill Above concerns formatting or shading behavior associated with analytical reference objects and does not define the calculation scope. Official Tableau documentation explicitly states that the terms Table, Pane, and Cell define the scope for reference lines and related analytical objects. These options control whether the benchmark applies globally or independently to specific partitions of the visualization.

To convert the existing bar chart into a stacked bar chart, the associate should drag another dimension to Color on the Marks card. The initial bar chart already contains a dimension on Columns and a measure on Rows. Adding another categorical dimension to Color partitions each bar according to the members of that second dimension. Tableau assigns a separate color to each resulting group and, because automatic stacking is enabled for bar marks by default, those groups are displayed cumulatively within each bar. For example, if Category is on Columns and SUM(Sales) is on Rows, adding Segment to Color divides each Category bar into Consumer, Corporate, and Home Office segments while preserving the bar's total Sales magnitude. Dragging another dimension to Size changes the visual size encoding rather than creating standard stacked segments. Adding another measure to Rows typically introduces an additional axis or measure structure. A measure placed on Color generally creates a quantitative gradient rather than categorical stacked segments. Tableau's official Stack Marks documentation describes this exact construction: a dimension on Columns, a measure on Rows, and another dimension used to color-encode the marks.