Salesforce Analytics-101 Salesforce Certified Tableau Desktop Foundations Exam Practice Test

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 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.

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 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.

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.

The three applicable routes are Tooltip on the Marks card, Format > Font, and Worksheet > Tooltip, so C, E, and F are correct. Selecting Tooltip on the Marks card opens the Edit Tooltip dialog. This editor contains text-formatting controls that allow tooltip content to be formatted, including the application of bold styling to selected text. Tableau also provides an equivalent route through Worksheet > Tooltip, which opens the same tooltip-editing environment for the current worksheet. A third route is through Format > Font. Tableau's worksheet-level font formatting includes a specific Tooltip section. This enables formatting of tooltip text at the worksheet level, including font style settings such as bold. This method is useful when a consistent tooltip font treatment is required rather than individually formatting portions of the tooltip body. The keyboard sequences listed in A and D are not defined Tableau methods for accessing tooltip formatting options merely by hovering over a mark. Right-clicking an arbitrary field and selecting Format is primarily associated with field/view formatting and is not the specified route to the tooltip bolding controls in this question. Official Tableau documentation confirms both Tooltip on the Marks card and Worksheet > Tooltip, while current Font formatting documentation exposes Tooltip as a configurable font target.

Dimension filters support Multiple Values (drop-down) and Wildcard Match, making A and C correct. Dimensions typically contain categorical values. When a dimension filter is displayed as an interactive filter card, Tableau provides several categorical selection modes. Multiple Values (drop-down) presents dimension members in a compact drop-down control where the viewer can select multiple categories simultaneously. This is useful when a field contains several discrete members but screen space needs to be conserved. Wildcard Match provides a text input field that dynamically selects dimension members whose text matches a supplied character pattern. Tableau supports the asterisk as a wildcard. For example, entering tab* can match values beginning with "tab." This mode is appropriate for searchable text-based categorical dimensions. By contrast, Range of Values is associated primarily with continuous quantitative filters, where users specify minimum and maximum values. At most is likewise an open-ended quantitative/date filtering mode used to establish an upper boundary rather than a categorical dimension-selection mode. Tableau's official filtering documentation explicitly lists Multiple Values (Dropdown) and Wildcard Match among the available filter card modes for dimensions. It separately describes quantitative range and open-ended filtering behavior for measures and continuous fields.

A Relative dates filter is designed for date ranges that dynamically change relative to the current date, making B correct. This filter can represent periods such as the current week, previous month, year to date, or the last specified number of days, weeks, months, quarters, or years. The important distinction is that a relative date filter is dynamic. As the current date advances, Tableau recalculates the applicable range when the view is opened or refreshed. This behavior is appropriate for requirements based conceptually on TODAY() because the filter should continue tracking the present period rather than retaining fixed start and end dates. A Range of dates filter establishes a specific date interval and is better suited to fixed boundaries. A Starting Date or Ending Date represents an open-ended boundary from a particular date rather than a dynamically shifting interval relative to today. Tableau's official documentation states that relative date filters dynamically update to display a time period relative to when the view is opened. Examples include the current week, year to date, or past ten days. This functionality allows analysts to create dashboards that consistently display the most recent period without manually editing the filter as calendar time progresses. Relevant topics include date fields, relative date filtering, dynamic analysis, and interactive filter configuration.

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.

STARTSWITH is the function that returns a Boolean result, so D is correct. The function evaluates whether one string begins with a specified substring. Its conceptual syntax is STARTSWITH(string, substring). If the original string begins with that substring, Tableau evaluates the expression as TRUE; otherwise, it evaluates as FALSE. For example, STARTSWITH([Customer Name], "A") returns TRUE for values beginning with A and FALSE for other values. Because the output is Boolean, STARTSWITH is particularly useful in calculated fields, conditional expressions, filters, classifications, and data-quality logic. The other listed functions return different data types. CHAR converts a numeric character code to its corresponding character and therefore returns a string. FIND searches for the position of a substring and returns a numeric position. UPPER converts the supplied text to uppercase and returns another string. Consequently, only STARTSWITH directly produces the TRUE/FALSE result required by the question. This distinction is fundamental when selecting functions for Boolean calculations because Tableau evaluates Boolean fields differently from numeric and string-returning expressions.

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.

The supported choices are Country, Airport, and City, making A, B, and D correct. A geographic role tells Tableau how the values in a field should be interpreted geographically. Once Tableau recognizes the role, it can associate those values with built-in geocoding information and generate geographic fields such as Latitude (generated) and Longitude (generated) for map creation. Tableau's supported location data includes countries and regions, cities, states and provinces, postal codes, airport codes, and several other standardized geographic structures. Country and City are therefore standard geographic roles. Tableau also supports worldwide airport codes, enabling fields containing appropriate airport identifiers to be interpreted geographically. A general street Address is not one of the standard built-in geographic roles represented by the answer set. Exact street-address mapping normally requires appropriate coordinate information, spatial data, custom geocoding, or another supported technique. Time zone likewise is not a standard geographic role used by Tableau's built-in geocoding model. The distinction matters because assigning an unsupported semantic category does not automatically give Tableau coordinates. Official Tableau Desktop mapping guidance specifically identifies countries, cities, airport codes, and other supported geographic location categories for map creation.