Analytics-101 Salesforce Certified Tableau Desktop Foundations Question and Answers

The correct option is Nested because the Sub-category members must be sorted independently within each Category based on Sales. A nested sort evaluates the measure separately inside each pane or parent dimensional grouping. In this example, the Home sub-categories should be sorted according to their Home Sales values, while the Bath sub-categories must be sorted independently according to the Bath Sales values. For Home, Bulk has Sales of $50 and Accessory has $60, so ascending order is Bulk followed by Accessory. For Bath, Accessory has $45 and Bulk has $75, so ascending order is Accessory followed by Bulk. This demonstrates why a single global ordering is insufficient: the correct Sub-category order differs between the two Category groups. A non-nested field sort can produce a consistent order based on aggregated values across the view, which would not satisfy the requirement to rank Sub-category independently inside each Category. Manual sorting would require explicit maintenance, while data source order simply follows the ordering supplied by the underlying source. Tableau's official sorting documentation states that nested sorting considers values independently per pane and sorts the values separately within those panes.

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.

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 answer is Treemaps. A treemap represents data as a set of rectangles. Tableau uses one or more dimensions to define the rectangular structure, while a measure placed on Size determines each rectangle's relative area. Tableau automatically lays out the rectangles to use the available visualization space efficiently. The analyst therefore controls relative size through the measure encoded on Size rather than manually resizing the generated rectangles with the ordinary Marks card size slider. For example, if Sub-Category defines the rectangles and Sales is placed on Size, categories with larger aggregated Sales values receive proportionally larger rectangles. Changing the Sales values or replacing the field on Size changes the relative areas, while Tableau recalculates the layout automatically. Pie charts have mark-size controls and can be resized through the Marks card. Area charts derive their visual area from their axes and underlying measures. Histograms use bars representing bins and frequencies and have different bar-sizing behavior. Tableau's official Treemap documentation identifies Size and Color as the crucial encodings and explains that a measure on Size determines the areas of the rectangles. The resulting treemap geometry is automatically laid out according to those values rather than manually sized mark by mark.

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.

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.

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.

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