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

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.

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.

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.

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.