Analytics-101 Exam Dumps - Salesforce Foundations Questions and Answers

The icon displayed to the right of the legend title is Tableau's highlighting control. Therefore, clicking it controls legend highlighting, making C the correct answer. Legend highlighting is an interactive analytical feature that allows the viewer to focus on specific marks associated with a selected legend member. When highlighting is enabled and a value such as Business Class or First Class is selected, Tableau emphasizes the corresponding marks while visually dimming unrelated marks. This makes it possible to investigate one category without filtering other categories out of the visualization. Tableau supports both one-way and two-way legend highlighting. The icon displayed at the top of the legend indicates the available highlighting mode. In two-way highlighting, interaction can occur from either the legend or marks in the visualization. The Edit Colors command is accessed through the legend's menu or other color controls, not by clicking this highlighter icon. Likewise, the icon does not expose filter settings and does not hide or display the legend itself. Official Tableau documentation explicitly states that the icon at the top of the legend represents legend highlighting and can be used to control highlighting behavior.

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.

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.

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

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

A relationship is particularly appropriate when the tables being combined contain data at different levels of detail, making D correct. Tableau relationships operate in the logical layer of the data model and preserve each logical table's native granularity. Tableau determines the necessary joins dynamically during analysis according to the fields used in the visualization. This behavior is materially different from a physical join. A join merges records into a single physical table before analysis. If tables have different granularities, a physical join can duplicate measure values or remove records depending on the join structure and matching keys. Relationships reduce that risk because Tableau aggregates relevant information according to each table's natural level of detail before combining results as required by the visualization. Official Tableau guidance explicitly recommends relationships for combining data from different levels of detail. Relationships also preserve independent logical tables rather than flattening them into a single physical table. Option B merely describes where tables reside and does not determine whether a relationship or join is preferable. Options A and C likewise do not identify the principal modeling scenario addressed by relationships. Relevant Tableau Desktop concepts include logical tables, physical tables, relationships, joins, aggregation behavior, and preservation of level of detail.

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.

In Tableau, blue identifies discrete fields, regardless of whether the field is classified as a dimension or a measure. Therefore, both Discrete dimensions and Discrete measures appear blue, making B and C correct. Tableau separates two different field characteristics. The first is the semantic role: dimension or measure. The second is the behavioral classification: discrete or continuous. These concepts are related but not equivalent. A discrete field contains distinct values and normally creates headers when added to Rows or Columns. Tableau represents the pill in blue. Most dimensions are discrete by default, so blue dimensions are common. Measures are generally continuous, but a measure can be converted to discrete; once it is discrete, its pill also becomes blue. Continuous fields appear green. Continuous dimensions—most commonly continuous date dimensions—and continuous measures therefore use green pills and typically create axes rather than headers. Tableau's official Dimensions and Measures documentation explicitly presents four valid combinations: discrete dimensions, continuous dimensions, discrete measures, and continuous measures. It shows discrete dimensions and discrete measures as blue, while both continuous forms are green. This distinction is foundational to predicting how Tableau will structure a visualization.