Free and Premium Salesforce Analytics-101 Dumps Questions Answers

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.

The associate can access the palette controls from the Color legend, making A correct. When a discrete dimension is placed on Color, Tableau generates a categorical color legend that identifies each dimension member and its assigned color. From the Color legend, the analyst can access Edit Colors, where a different palette can be selected and individual members can be assigned specific colors. This provides an alternative to opening the color configuration from the Marks card. The Format menu controls broader formatting characteristics such as fonts, borders, alignment, shading, and other presentation settings. Although newer Tableau versions include workbook-level palette functionality, the question concerns changing the palette associated with the dimension already encoded in the visualization, for which the Color legend is the direct alternative to the Marks card. Edit Caption modifies descriptive text associated with an object or field rather than its visual encoding. Edit in Shelf is also unrelated to palette management. Official Tableau documentation states that users can open the menu in the upper-right corner of a categorical color legend and select Edit Colors, after which they can choose or modify the palette assigned to the field's members.

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.

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.

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.

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 associate should select More under To a Server, making D correct. Tableau Desktop organizes available connectors on the Connect pane into broad categories such as To a File and To a Server. Frequently used server connectors may be displayed directly, but Tableau provides the More option to expose the complete list of supported server-based connection types available in the installation. Official Tableau connector documentation repeatedly states: For a complete list of data connections, select More under To a Server. This workflow is used when locating database and server connectors such as Microsoft SQL Server, PostgreSQL, SharePoint Lists, and other supported platforms. Selecting More under To a File instead displays file-based connection types and therefore does not satisfy a requirement specifically involving server connections. Choosing File > New creates a new workbook and does not expose the complete server connector list. "Connecting to Data" is not the command required to reveal all server options. This distinction is operationally important because the Connect pane intentionally surfaces common connector choices while More exposes the broader connector catalog. Current Tableau documentation for multiple server connectors confirms the More under To a Server workflow for viewing the complete connection list.

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.

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.

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.

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 correct configuration is Logical tables that use a single table extract, making C correct. In Tableau's data model, a union operates in the physical layer. The two unioned physical tables are merged into one resulting logical table. Tableau explicitly describes logical tables as containers that can contain multiple physical tables joined or unioned together. When an extract is stored using Logical Tables, Tableau creates one extract table for each logical table in the data source. Because the scenario contains one logical table composed of the two unioned physical tables, the extract is consequently represented as a single extract table. This is different from using Physical Tables storage. Physical storage retains an extract table for each physical table and is subject to additional eligibility restrictions. Tableau's current terminology replaced the older "Single Table" and "Multiple Tables" extract terminology with Logical Tables and Physical Tables, respectively. Official Tableau documentation states that physical tables joined or unioned inside a logical table are merged as part of that logical table, and that Logical Tables extract storage creates one extract table per logical table. Therefore, a two-table union forming one logical table corresponds to a logical/single-table extract structure.