Analytics-101 Questions and Answers

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.

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.

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.

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.

Standard deviation is available as a native aggregation for a measure and does not require the author to create either a table calculation or a calculated field. Therefore, C is correct. When a measure is used in a Tableau view, its aggregation can be changed through the field menu. In addition to commonly used functions such as SUM, AVG, MIN, MAX, and COUNT, Tableau provides Standard Deviation and Standard Deviation (Population) as built-in aggregation choices. The calculation is performed directly over the records contributing to the current mark. Running Total and Percent of Total are different because they are table calculations. They operate on already aggregated values after Tableau has constructed the visualization and depend on the addressing and partitioning of the view. Sample covariance is supported through calculation functionality such as covariance functions but is not presented as the equivalent direct aggregation option in the basic measure aggregation menu represented by this question. Implementing covariance typically involves specifying the two expressions whose covariance is required. Tableau's official Data Aggregation documentation explicitly lists standard deviation among the aggregations available for measures, including sample and population forms. Consequently, it can be selected directly without constructing an additional calculated field or applying a quick table calculation.

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.

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.