Analytics-101 Salesforce Certified Tableau Desktop Foundations Questions and Answers

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.

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 multi-connection data source created for a cross-database join can be filtered and can also be converted to or used with an extract, making A and C correct. Cross-database joins allow Tableau to combine tables originating from different supported connections into one logical data source. Tableau supports these joins with either live connections or in-memory extracts. Consequently, the associate can create an extract of the resulting multi-connection data source. Data source filters can also be used to reduce the records Tableau brings into the analytical environment, subject to connector-specific limitations. The other two choices conflict with documented multi-connection restrictions. Tableau explicitly states that stored procedures are not available for multi-connection data sources, eliminating B. A union appends rows from structurally similar tables. In a multi-connection environment, Tableau Desktop requires tables being unioned to come from the same connection; tables from different databases cannot be unioned directly in Tableau Desktop. Therefore, D does not meet the scenario involving tables across multiple connections. Tableau's official cross-database documentation explains that a cross-database join requires a multi-connection data source, supports both live and extract-based operation, prohibits stored procedures for such sources, and limits unions to tables within the same connection.

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.

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.

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.

Tableau provides three principal scope levels for reference lines: Entire Table, Per Pane, and Per Cell. Therefore, A, B, and D are correct. Scope determines the partition of the visualization over which Tableau calculates and displays the reference line. Entire Table computes one reference value based on all applicable marks in the view. This is appropriate for a global benchmark such as overall average Sales. Per Pane creates a separate reference line for each pane. For example, if a visualization is partitioned by Region, Tableau can calculate an independent average for each regional pane. Per Cell is still more granular and can calculate a separate reference line for each cell defined by the row and column structure of the view. Maximum is not a scope; it is a possible statistical value or computation that can be used to determine the reference-line value. Similarly, Fill Above concerns formatting or shading behavior associated with analytical reference objects and does not define the calculation scope. Official Tableau documentation explicitly states that the terms Table, Pane, and Cell define the scope for reference lines and related analytical objects. These options control whether the benchmark applies globally or independently to specific partitions of the visualization.

Tableau dashboard actions can directly change Parameters and Sets, so B and C are correct. A parameter action allows a user to modify a parameter value by interacting directly with marks in a visualization. For example, selecting a mark can assign the mark's Sales value to a parameter, which can subsequently drive a calculated field, reference line, filter logic, or another analytical component. Tableau provides the dashboard action type Change Parameter specifically for this purpose. A set action similarly modifies the membership of an existing set based on interaction with marks. The action can assign selected values to the set, add values, or remove values. This enables sophisticated interactive behavior such as proportional brushing, dynamic comparisons, drill-down effects, and conditional calculations. Tableau identifies this action type as Change Set Values. Groups and bins do not have equivalent dashboard action types that dynamically modify their definitions through viewer interaction. They are data organization constructs configured during authoring. The Tableau Actions documentation explicitly lists Change Parameter and Change Set Values among supported action types. Parameter Actions documentation confirms that visualization interaction can update the target parameter, while Set Actions documentation confirms that interactions can modify values contained in a target set.

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.