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

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.

A Tableau packaged workbook uses the .twbx format to bundle a workbook with supporting local resources needed to use it outside the author's original environment. The correct elements are background images, custom shapes, and extract files. Tableau explicitly lists background images, custom shapes, and Tableau extract files (.hyper) among the resources that can be incorporated into a packaged workbook. These supporting assets are bundled so that another user does not need access to the original local paths used by the workbook author. Other packageable resources include custom geocoding, local cube files, Excel files, Access files, and text-based local data sources. A PDF version of the workbook is not automatically generated and embedded inside a .twbx, making C incorrect. A Tableau Datasource Customization .tdc file is likewise not listed among the standard resources incorporated into a packaged workbook. A .twbx is therefore fundamentally a portable Tableau workbook package rather than simply a workbook definition. This distinction is important when distributing workbooks that depend on local resources. Official Tableau Desktop documentation lists background images, custom shapes, and Tableau extract files among the files included in packaged workbooks.

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.

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.

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.

Hierarchies provide Tableau's native mechanism for drilling up and down through related levels of detail, making A correct. A hierarchy organizes dimensions into an ordered structure such as Region > State > City, Category > Sub-Category > Product, or a standard date hierarchy such as Year > Quarter > Month > Day. When a hierarchy field is placed in a visualization, Tableau displays plus and minus controls that permit the analyst to expand to a more detailed level or collapse to a higher level. Drilling down adds another hierarchy level to the view, increasing the level of detail. Drilling up removes a lower level and returns the analysis to a more aggregated perspective. This functionality allows analysts to move through different analytical granularities without manually adding and removing each related field. Bins serve a different purpose: they partition continuous numeric values into intervals. Groups consolidate selected dimension members into broader categories. Sets identify subsets of data according to membership logic or user selections. None of those constructs inherently provides structured drill-up/drill-down navigation. Tableau's official hierarchy documentation explicitly states that hierarchies allow users to quickly drill up or down to add or subtract levels of detail and identifies the plus and minus icons as the controls used for this operation.

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.

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.

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