Analytics-101 Dumps with Practice Exam Questions Answers

Tableau supports creating groups either directly from selected marks in a visualization or from a field in the Data pane. Therefore, A and D are correct. For the first method, the analyst selects one or more marks in the view. Tableau exposes a grouping control in the selection tooltip or toolbar. Activating the Group command combines the dimension members represented by those marks into a new group. This method is particularly effective when the analyst identifies categories visually during exploration. For the second method, the analyst can right-click a dimension in the Data pane and select Create > Group. Tableau opens the Create Group dialog, where multiple members can be selected and grouped explicitly. Option C represents another Tableau capability, but not grouping: dragging one dimension directly onto another in the Data pane is used to create a hierarchy. Hierarchies organize related dimensions into drillable levels rather than consolidating dimension members into a group. Opening the general drop-down menu at the top of the Data pane is likewise not the specified procedure for creating a visual group. Tableau's official Group Your Data documentation identifies exactly these two core workflows: create a group by selecting data in the view or create a group from a field in the Data pane.

Because the first measure is on the Rows shelf, Tableau creates a vertical quantitative axis in the visualization. To construct a combined axis, the associate should drag the second measure directly onto that existing vertical axis, making B correct. A combined axis allows multiple measures to share the same axis instead of displaying them in separate panes or on independent dual axes. When the second measure is dragged onto the existing axis and Tableau displays the appropriate drop indicator, Tableau creates a shared Measure Values-based view containing both measures. The orientation matters. Fields on Rows normally produce a vertical y-axis, whereas fields on Columns normally generate a horizontal x-axis. Consequently, because the first measure was specifically placed on Rows, the target is the vertical axis rather than the horizontal axis. Dropping the second measure on the Marks card would encode that field through a mark property rather than create a combined quantitative axis. Dropping it on Filters would restrict records or values and would not combine the measures. This mechanism should also be distinguished from a dual-axis chart, where two independent axes are layered. A combined axis instead places multiple measures on a shared axis and commonly uses Measure Names and Measure Values for differentiation.

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.

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.

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.