Practice Free Analytics-101 Salesforce Certified Tableau Desktop Foundations Exam Questions Answers With Explanation

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.

A basic bar chart can be created from a measure without requiring a dimension, making A correct. Tableau can construct an initial visualization automatically when a field is double-clicked in the Data pane. Official Tableau documentation demonstrates that double-clicking a quantitative measure such as Profit automatically adds it to the view and creates a bar chart. At this stage, no dimension is required; Tableau displays the aggregated value of the measure as a single bar. The remaining visualization types fundamentally depend on categorical partitioning. A highlight table uses dimensions to establish the table's row and column structure and measures to encode values through color or text. A treemap normally requires one or more dimensions to define individual rectangles, with measures controlling properties such as size and color. A stacked bar requires a categorical field to partition a bar into multiple stacked segments. A dimension can certainly be added later to a basic bar chart—for example, Category on Columns and Sales on Rows—to produce multiple bars. However, the question asks which visualization can be created without a dimension. Tableau's official field-dragging documentation specifically demonstrates that double-clicking a measure alone produces an automatic bar chart.

Because the group field contains an enabled Other group, ungrouping one of the explicitly grouped members causes that member to be placed into Other. Therefore, A is correct. Tableau groups allow analysts to combine individual members of a dimension into higher-level categories. When the Include "Other" option is enabled, all members that are not assigned to one of the explicitly defined groups are collected automatically into an Other category. Tableau's official Group Your Data documentation specifically describes the behavior of removing members from an existing group. The analyst opens Edit Group, selects the member, and chooses Ungroup. Tableau removes the selected member from its current explicit group. Critically, the documentation states that if an Other group exists, the removed members are added to it. The underlying original dimension member is not deleted. However, option B is incomplete for this exact scenario because the question explicitly states that the Other group exists; Tableau does not merely leave the member ungrouped—it places it into Other. No new single-member group is automatically created, eliminating C, and removing one member does not delete the entire group, eliminating D. This behavior is central to Tableau's dimension grouping and Other-category management.

Relationships are designed to preserve each table's level of detail and keep logical tables separate within the data source, making A and B correct. Unlike physical joins, relationships do not flatten participating tables into one combined row-level table when the data source is created. Tableau keeps each logical table distinct and evaluates the relationship dynamically based on fields actually used in a visualization. This architecture helps Tableau analyze data residing at different granularities while reducing the duplication and data-loss risks that can occur with fixed physical joins. Tableau's official relationship documentation explicitly states that relationships maintain each table's native level of detail and create independent domains at multiple granularities. The tables are not merged together in the data source. Option C describes the behavior of joins or unions in the physical layer. Physical tables can be combined to form one logical table, but this is not what a relationship does. Option D is also incorrect because relationships do not require the author to choose a fixed join type such as inner, left, right, or full outer. Tableau determines appropriate joins contextually during analysis. Relevant Tableau Desktop concepts include logical tables, physical tables, relationships, contextual joins, cardinality, and preservation of granularity.

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.

The associate should place Region on Color on the Marks card. A discrete dimension placed on Color partitions the marks according to the dimension's members. Consequently, the visualization produces a separate line for each Region while preserving the existing date field on Columns and Sales measure on Rows. For example, if Region contains Central, East, South, and West, Tableau separates the original Sales line into four distinct series and assigns a categorical color to each region. The lines remain plotted against the same continuous date and Sales axes, which satisfies the requirement for multiple distinct lines on the same axis. Placing Region on Rows or Columns would partition the visualization into separate panes or headers rather than overlaying distinct regional lines within the same plotting area. Path controls the order in which Tableau connects marks in a line or polygon and therefore does not provide the required categorical separation. Tableau's Marks card is specifically designed to encode fields by visual properties such as Color, Size, Label, Detail, Tooltip, and Path. Official Tableau documentation confirms that placing a discrete field—typically a dimension—on Color assigns a distinct categorical color to each value.

A story point is an individual visualization state within a Tableau story, normally represented by a worksheet or dashboard. Therefore, A is correct. Tableau defines a story as a sequence of visualizations that collectively communicate information, provide context, demonstrate relationships, or support a data-driven narrative. Each individual sheet contained in that sequence is called a story point. A story can contain multiple points, and each point can present a different worksheet, dashboard, filter state, annotation, or analytical stage. Option C describes the overall story, not an individual story point. The distinction is important: the story represents the complete ordered narrative, while the story point represents one step within that narrative. Option B is not an official Tableau object or definition. Option D refers to controls within the story workspace and does not define a story point. This functionality allows an analyst to guide viewers through findings in a controlled sequence while preserving interactive visualization capabilities where supported. Official Tableau Desktop documentation explicitly states that a story is a collection of sheets arranged in sequence and that each individual sheet in a story is called a story point.