Analytics-101 Salesforce Certified Tableau Desktop Foundations Questions and Answers

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.

A basic scatter plot requires one measure on Columns and another measure on Rows, so D is correct. A scatter plot displays the relationship between two quantitative variables. One measure determines the horizontal position of each mark, while the second measure determines its vertical position. For example, placing SUM(Sales) on Columns and SUM(Profit) on Rows establishes a two-dimensional quantitative coordinate system. A dimension may then be added to Detail, Color, Shape, or another Marks property to create separate marks for entities such as customers, products, or states. However, that additional dimension is not the fundamental axis requirement identified by the question. The minimum structural requirement is two quantitative measures defining the x- and y-axes. A dimension plus a measure normally produces a categorical view such as a bar chart rather than a scatter plot. Two dimensions likewise do not supply the pair of quantitative scales required to analyze numerical correlation or distribution. Tableau's visual construction model distinguishes continuous quantitative measures, which generate axes, from discrete fields, which generally create headers. A scatter plot relies on two quantitative axes and therefore requires measures on both Rows and Columns. This is consistent with Tableau's standard scatter-plot construction methodology and its continuous-field behavior.

The correct function is CONTAINS, making D correct. Its syntax is conceptually CONTAINS(string, substring), and it returns a Boolean result indicating whether the specified substring exists anywhere within the source string. For example, CONTAINS([Product Name] , "Office") evaluates to TRUE for records where Product Name contains the sequence "Office" and FALSE where it does not. This makes CONTAINS useful for classification calculations, conditional logic, filtering, validation, and text-based segmentation. The other functions perform different operations. RTRIM removes trailing spaces and returns a string. SPLIT separates a string using a delimiter and returns the requested substring component. ENDSWITH does return a Boolean value, but it tests specifically whether the original string ends with the supplied substring. The requirement is to determine whether a substring occurs somewhere within the column value, so ENDSWITH is too restrictive. Tableau's official String Functions reference explicitly defines CONTAINS(string, substring) as returning TRUE when the supplied string contains the specified substring and identifies its output data type as Boolean. The same documentation distinguishes CONTAINS from STARTSWITH, ENDSWITH, trimming functions, and string parsing functions. Relevant topics include calculated fields, string functions, Boolean calculations, and text manipulation.

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.

To create a join in a data source that already uses relationships, the associate must double-click a logical table in the canvas, making C correct. Tableau's data model has two layers. The top-level logical layer contains logical tables connected by relationships. A join cannot be created directly between these logical tables because joins operate in the underlying physical layer. Double-clicking a logical table opens its physical Join/Union canvas. From there, the associate can drag or double-click additional physical tables and define the required join clauses and join type. This distinction is fundamental to Tableau's modern data model. Relationships connect logical tables while keeping them separate and preserving their natural level of detail. Joins merge physical tables into one logical table using an explicitly defined join configuration. Selecting Add in the Connections pane adds another connection; it does not itself create the join. Dragging a table directly onto the top-level logical canvas generally creates a relationship rather than a physical join. Double-clicking a table in the Tables pane is not the step used to enter the physical layer of an existing logical table. Tableau's official documentation explicitly instructs users to double-click a logical table to open the physical layer where joins and unions can be created.

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.

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.

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.