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.

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.

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.

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.

The associate should place Region on Color on the Marks card. A discrete dimension placed on Color partitions the marks according to the dimension's members. Consequently, the visualization produces a separate line for each Region while preserving the existing date field on Columns and Sales measure on Rows. For example, if Region contains Central, East, South, and West, Tableau separates the original Sales line into four distinct series and assigns a categorical color to each region. The lines remain plotted against the same continuous date and Sales axes, which satisfies the requirement for multiple distinct lines on the same axis. Placing Region on Rows or Columns would partition the visualization into separate panes or headers rather than overlaying distinct regional lines within the same plotting area. Path controls the order in which Tableau connects marks in a line or polygon and therefore does not provide the required categorical separation. Tableau's Marks card is specifically designed to encode fields by visual properties such as Color, Size, Label, Detail, Tooltip, and Path. Official Tableau documentation confirms that placing a discrete field—typically a dimension—on Color assigns a distinct categorical color to each value.

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.

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.

The correct answer is Treemaps. A treemap represents data as a set of rectangles. Tableau uses one or more dimensions to define the rectangular structure, while a measure placed on Size determines each rectangle's relative area. Tableau automatically lays out the rectangles to use the available visualization space efficiently. The analyst therefore controls relative size through the measure encoded on Size rather than manually resizing the generated rectangles with the ordinary Marks card size slider. For example, if Sub-Category defines the rectangles and Sales is placed on Size, categories with larger aggregated Sales values receive proportionally larger rectangles. Changing the Sales values or replacing the field on Size changes the relative areas, while Tableau recalculates the layout automatically. Pie charts have mark-size controls and can be resized through the Marks card. Area charts derive their visual area from their axes and underlying measures. Histograms use bars representing bins and frequencies and have different bar-sizing behavior. Tableau's official Treemap documentation identifies Size and Color as the crucial encodings and explains that a measure on Size determines the areas of the rectangles. The resulting treemap geometry is automatically laid out according to those values rather than manually sized mark by mark.

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.