Free Practice Questions for Salesforce Analytics-101 Exam

The correct answer is Treemaps. A treemap represents data as a set of rectangles. Tableau uses one or more dimensions to define the rectangular structure, while a measure placed on Size determines each rectangle's relative area. Tableau automatically lays out the rectangles to use the available visualization space efficiently. The analyst therefore controls relative size through the measure encoded on Size rather than manually resizing the generated rectangles with the ordinary Marks card size slider. For example, if Sub-Category defines the rectangles and Sales is placed on Size, categories with larger aggregated Sales values receive proportionally larger rectangles. Changing the Sales values or replacing the field on Size changes the relative areas, while Tableau recalculates the layout automatically. Pie charts have mark-size controls and can be resized through the Marks card. Area charts derive their visual area from their axes and underlying measures. Histograms use bars representing bins and frequencies and have different bar-sizing behavior. Tableau's official Treemap documentation identifies Size and Color as the crucial encodings and explains that a measure on Size determines the areas of the rectangles. The resulting treemap geometry is automatically laid out according to those values rather than manually sized mark by mark.

Tableau dashboard actions can directly change Parameters and Sets, so B and C are correct. A parameter action allows a user to modify a parameter value by interacting directly with marks in a visualization. For example, selecting a mark can assign the mark's Sales value to a parameter, which can subsequently drive a calculated field, reference line, filter logic, or another analytical component. Tableau provides the dashboard action type Change Parameter specifically for this purpose. A set action similarly modifies the membership of an existing set based on interaction with marks. The action can assign selected values to the set, add values, or remove values. This enables sophisticated interactive behavior such as proportional brushing, dynamic comparisons, drill-down effects, and conditional calculations. Tableau identifies this action type as Change Set Values. Groups and bins do not have equivalent dashboard action types that dynamically modify their definitions through viewer interaction. They are data organization constructs configured during authoring. The Tableau Actions documentation explicitly lists Change Parameter and Change Set Values among supported action types. Parameter Actions documentation confirms that visualization interaction can update the target parameter, while Set Actions documentation confirms that interactions can modify values contained in a target set.

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.

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.

A default aggregation can be specified for a measure, making A correct. Measures represent quantitative values and are normally aggregated when they are added to a visualization. For example, a Sales measure typically appears as SUM(Sales). Tableau allows the author to change the measure's default aggregation so that subsequent uses of the field can initially use AVG, MIN, MAX, COUNT, standard deviation, or another supported aggregation instead of SUM. The configuration is available from the Data pane by right-clicking the measure and selecting Default Properties > Aggregation. The choice becomes the default behavior when the field is subsequently added to a view, although the aggregation can still be overridden for an individual instance of the field. Dimensions do not use a default measure aggregation in this manner because their primary role is to partition and categorize the data. Bins are generated categorical fields representing numerical intervals. An already aggregated calculated expression also has restrictions because Tableau cannot arbitrarily aggregate an expression that is already defined at an aggregate level. Tableau's official Default Settings documentation specifically states that users can specify a default aggregation for any measure and documents the Data pane workflow for configuring it.

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.

Tableau allows a field to be renamed directly in the Data pane by making the field name editable or by selecting Rename from the field's contextual menu. Therefore, B and C are correct. For the first method, Tableau documentation specifies that the user can click a field name in the Data pane and hold the mouse button until the field name appears in an editable text box. The new name can then be entered and confirmed. Tableau also provides keyboard alternatives such as F2 or Ctrl+Enter. The second standard workflow is to open the field's contextual or drop-down menu and choose Rename. This changes the field name used within Tableau without changing the column name in the underlying data source. Replace References serves a different function. It substitutes one field for another throughout the workbook and is commonly used when replacing broken or obsolete field references; it is not simply a renaming command. Field Labels under formatting controls how field labels appear in a view rather than changing the Data pane field name. Tableau explicitly documents Data pane renaming and confirms that renamed fields retain the new Tableau-facing name within the workbook.

Dimensions are fields Tableau uses primarily to categorize, segment, and describe data. They typically contain qualitative information such as names, geographic locations, categories, dates, and identifiers. Therefore, C is correct. Tableau also states that dimensions affect the level of detail in a visualization. Adding another dimension can partition existing marks into more granular groups because Tableau incorporates the field's members into the view's dimensional structure. Therefore, B is correct. The dimension/measure classification is independent from the discrete/continuous classification. Although dimensions are commonly discrete, a dimension can also be continuous. Date fields are a standard example: a date may be represented as a discrete date part or a continuous date value. Therefore, E is correct. Option D instead describes measures, which generally contain quantitative numeric values and are aggregated. Option A is not an inherent defining characteristic of dimensions; formatting behavior depends on how a field is used and whether it is discrete or continuous. Official Tableau guidance identifies dimensions as qualitative fields that group or segment data and explicitly states that dimensions affect the level of detail in the view.