Analytics-101 Salesforce Certified Tableau Desktop Foundations Questions and Answers

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

The associate should select More under To a Server, making D correct. Tableau Desktop organizes available connectors on the Connect pane into broad categories such as To a File and To a Server. Frequently used server connectors may be displayed directly, but Tableau provides the More option to expose the complete list of supported server-based connection types available in the installation. Official Tableau connector documentation repeatedly states: For a complete list of data connections, select More under To a Server. This workflow is used when locating database and server connectors such as Microsoft SQL Server, PostgreSQL, SharePoint Lists, and other supported platforms. Selecting More under To a File instead displays file-based connection types and therefore does not satisfy a requirement specifically involving server connections. Choosing File > New creates a new workbook and does not expose the complete server connector list. "Connecting to Data" is not the command required to reveal all server options. This distinction is operationally important because the Connect pane intentionally surfaces common connector choices while More exposes the broader connector catalog. Current Tableau documentation for multiple server connectors confirms the More under To a Server workflow for viewing the complete connection list.

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

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.

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.

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.

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.