Pass the Salesforce Salesforce Foundations Analytics-101 Questions and answers with CertsForce

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.

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.

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.

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.

Opacity is the appropriate control when the objective is to change how intense or subdued the existing colors appear. In Tableau, the Color controls on the Marks card include an Opacity slider. Moving this control toward lower opacity makes marks increasingly transparent; increasing opacity makes the applied colors visually stronger and less transparent. Therefore, C is correct. The other options modify different properties. Border adds an outline around supported mark types and does not control the overall intensity of the fill color. Reversed inverts the ordering of a quantitative color palette—for example, changing a sequential palette so that lower values receive the darker intensity and higher values receive the lighter intensity. It changes which values receive each shade rather than controlling overall opacity. Stepped Color converts a continuous quantitative palette into a specified number of discrete color bands or bins. Tableau's current Color Palettes and Effects documentation explicitly identifies Opacity as the setting used to modify the transparency of marks. It separately defines Reversed as inverting the order of colors and Stepped Color as grouping quantitative values into uniform color bins. These distinctions make Opacity the correct setting for modifying visual color intensity.

To convert the existing bar chart into a stacked bar chart, the associate should drag another dimension to Color on the Marks card. The initial bar chart already contains a dimension on Columns and a measure on Rows. Adding another categorical dimension to Color partitions each bar according to the members of that second dimension. Tableau assigns a separate color to each resulting group and, because automatic stacking is enabled for bar marks by default, those groups are displayed cumulatively within each bar. For example, if Category is on Columns and SUM(Sales) is on Rows, adding Segment to Color divides each Category bar into Consumer, Corporate, and Home Office segments while preserving the bar's total Sales magnitude. Dragging another dimension to Size changes the visual size encoding rather than creating standard stacked segments. Adding another measure to Rows typically introduces an additional axis or measure structure. A measure placed on Color generally creates a quantitative gradient rather than categorical stacked segments. Tableau's official Stack Marks documentation describes this exact construction: a dimension on Columns, a measure on Rows, and another dimension used to color-encode the marks.

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.

Tableau provides direct single-click sorting controls from a header, an axis, and a field label, making A, C, and D correct. Tableau's official Sort Data in a Visualization documentation explicitly identifies these three locations. When the user hovers over an appropriate header, numerical axis, or field label, Tableau can display a sort icon. One click typically applies descending sorting, a second click changes it to ascending, and another interaction can clear the sort depending on context. A header is commonly generated by a discrete field and can expose sorting for its members. A numerical axis allows the associated categorical members to be sorted according to measure values. A field label can similarly provide direct sorting when applicable to the view's structure. The Tooltip area of the Marks card controls information displayed when the pointer hovers over a mark; it is not a sorting interface. The Worksheet and Analysis menus contain numerous authoring commands but are not the three direct locations identified by Tableau's single-click sorting workflow in this question. Official Tableau documentation specifically states: "Quickly sort from an axis, header, or field label," precisely matching A, C, and D.

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.

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.