Analytics-101 Salesforce Certified Tableau Desktop Foundations Free Practice Exam Questions (2026 Updated)

Standard deviation is available as a native aggregation for a measure and does not require the author to create either a table calculation or a calculated field. Therefore, C is correct. When a measure is used in a Tableau view, its aggregation can be changed through the field menu. In addition to commonly used functions such as SUM, AVG, MIN, MAX, and COUNT, Tableau provides Standard Deviation and Standard Deviation (Population) as built-in aggregation choices. The calculation is performed directly over the records contributing to the current mark. Running Total and Percent of Total are different because they are table calculations. They operate on already aggregated values after Tableau has constructed the visualization and depend on the addressing and partitioning of the view. Sample covariance is supported through calculation functionality such as covariance functions but is not presented as the equivalent direct aggregation option in the basic measure aggregation menu represented by this question. Implementing covariance typically involves specifying the two expressions whose covariance is required. Tableau's official Data Aggregation documentation explicitly lists standard deviation among the aggregations available for measures, including sample and population forms. Consequently, it can be selected directly without constructing an additional calculated field or applying a quick table calculation.

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.

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.

A relationship is particularly appropriate when the tables being combined contain data at different levels of detail, making D correct. Tableau relationships operate in the logical layer of the data model and preserve each logical table's native granularity. Tableau determines the necessary joins dynamically during analysis according to the fields used in the visualization. This behavior is materially different from a physical join. A join merges records into a single physical table before analysis. If tables have different granularities, a physical join can duplicate measure values or remove records depending on the join structure and matching keys. Relationships reduce that risk because Tableau aggregates relevant information according to each table's natural level of detail before combining results as required by the visualization. Official Tableau guidance explicitly recommends relationships for combining data from different levels of detail. Relationships also preserve independent logical tables rather than flattening them into a single physical table. Option B merely describes where tables reside and does not determine whether a relationship or join is preferable. Options A and C likewise do not identify the principal modeling scenario addressed by relationships. Relevant Tableau Desktop concepts include logical tables, physical tables, relationships, joins, aggregation behavior, and preservation of level of detail.

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.

Tableau supports creating groups either directly from selected marks in a visualization or from a field in the Data pane. Therefore, A and D are correct. For the first method, the analyst selects one or more marks in the view. Tableau exposes a grouping control in the selection tooltip or toolbar. Activating the Group command combines the dimension members represented by those marks into a new group. This method is particularly effective when the analyst identifies categories visually during exploration. For the second method, the analyst can right-click a dimension in the Data pane and select Create > Group. Tableau opens the Create Group dialog, where multiple members can be selected and grouped explicitly. Option C represents another Tableau capability, but not grouping: dragging one dimension directly onto another in the Data pane is used to create a hierarchy. Hierarchies organize related dimensions into drillable levels rather than consolidating dimension members into a group. Opening the general drop-down menu at the top of the Data pane is likewise not the specified procedure for creating a visual group. Tableau's official Group Your Data documentation identifies exactly these two core workflows: create a group by selecting data in the view or create a group from a field in the Data pane.

The correct configuration is Logical tables that use a single table extract, making C correct. In Tableau's data model, a union operates in the physical layer. The two unioned physical tables are merged into one resulting logical table. Tableau explicitly describes logical tables as containers that can contain multiple physical tables joined or unioned together. When an extract is stored using Logical Tables, Tableau creates one extract table for each logical table in the data source. Because the scenario contains one logical table composed of the two unioned physical tables, the extract is consequently represented as a single extract table. This is different from using Physical Tables storage. Physical storage retains an extract table for each physical table and is subject to additional eligibility restrictions. Tableau's current terminology replaced the older "Single Table" and "Multiple Tables" extract terminology with Logical Tables and Physical Tables, respectively. Official Tableau documentation states that physical tables joined or unioned inside a logical table are merged as part of that logical table, and that Logical Tables extract storage creates one extract table per logical table. Therefore, a two-table union forming one logical table corresponds to a logical/single-table extract structure.

In Tableau, blue identifies discrete fields, regardless of whether the field is classified as a dimension or a measure. Therefore, both Discrete dimensions and Discrete measures appear blue, making B and C correct. Tableau separates two different field characteristics. The first is the semantic role: dimension or measure. The second is the behavioral classification: discrete or continuous. These concepts are related but not equivalent. A discrete field contains distinct values and normally creates headers when added to Rows or Columns. Tableau represents the pill in blue. Most dimensions are discrete by default, so blue dimensions are common. Measures are generally continuous, but a measure can be converted to discrete; once it is discrete, its pill also becomes blue. Continuous fields appear green. Continuous dimensions—most commonly continuous date dimensions—and continuous measures therefore use green pills and typically create axes rather than headers. Tableau's official Dimensions and Measures documentation explicitly presents four valid combinations: discrete dimensions, continuous dimensions, discrete measures, and continuous measures. It shows discrete dimensions and discrete measures as blue, while both continuous forms are green. This distinction is foundational to predicting how Tableau will structure a visualization.

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.

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.