Tableau Quiz: Drag And Drop Workflow
10 questions · exam conditions
0:00
Drag And Drop WorkflowQuestion 1 of 10

A worksheet contains Category on Columns and SUM(Sales) on Rows, producing one aggregated mark for each category. Customer Name is not currently used in the view.

You drag Customer Name to Detail on the Marks card. Which result should you expect?

Each category is partitioned into customer-level marks, with no separate visual encoding applied to customer names.
Each category retains one aggregated mark, and the view's level of detail remains unchanged at the category level.
Customers become column headers nested inside Category, creating a separate pane for each customer within each category.
Customer Name replaces Category as the primary grouping because Detail accepts only one dimension at a time.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Drag And Drop Workflow

Practice Drag And Drop Workflow in Tableau with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Drag And Drop Workflow, giving you a quick way to practice the rules, question types, and explanations that matter most for Tableau.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

A worksheet contains Category on Columns and SUM(Sales) on Rows, producing one aggregated mark for each category. Customer Name is not currently used in the view.

You drag Customer Name to Detail on the Marks card. Which result should you expect?

  1. Each category is partitioned into customer-level marks, with no separate visual encoding applied to customer names. (correct answer)
  2. Each category retains one aggregated mark, and the view's level of detail remains unchanged at the category level.
  3. Customers become column headers nested inside Category, creating a separate pane for each customer within each category.
  4. Customer Name replaces Category as the primary grouping because Detail accepts only one dimension at a time.
Explanation: When you drag a field to the Marks card in Tableau, you need to ask yourself: does this change what is being drawn, or only how it looks or how finely it's computed? Detail is a special Marks card property — it increases the granularity of the view (adds more marks) without applying any visual encoding like color, size, or shape. In this scenario, adding Customer Name to Detail means Tableau now computes SUM(Sales) at the Category + Customer Name level of detail. Instead of one bar per category, you get one mark per customer within each category — but no visual difference in encoding is applied to distinguish customers from one another. That's exactly what A describes: customer-level partitioning with no separate visual encoding. B is wrong because Detail does change the level of detail. You will have more marks, not the same single aggregated mark per category. C describes what would happen if you dragged Customer Name to Columns — nesting it as a column header — which is a completely different action than dropping it on Detail. D reflects a fundamental misunderstanding: Detail doesn't replace dimensions, and the Marks card can hold multiple dimensions simultaneously; Customer Name would simply be added alongside Category. A practical tip to remember: think of the Marks card properties in two groups — encoding properties (Color, Size, Shape, Label, Tooltip) and the granularity property (Detail). Detail behaves like adding a dimension to the view's underlying data structure without visually differentiating the new marks. Any time a question asks about adding granularity without visual encoding, Detail is your answer.

Question 2

A view has Region on Columns and SUM(Sales) on Rows. Category is not used in the view, and each region contains sales from all three categories.

You drag Category from the Data pane to the Filters shelf and retain only Furniture and Office Supplies. What does Tableau display?

  1. Regional sales marks recalculated from only the two retained categories, with Region still defining the columns. (correct answer)
  2. Two category marks for every region because every field placed on Filters also enters the level of detail.
  3. Regional sales marks based on all categories, with the excluded category merely hidden from the tooltip.
  4. Two category columns replacing Region because the most recently dragged dimension controls the view layout.
Explanation: Whenever you see a question about Filters in Tableau, the key distinction to understand is that the Filters shelf controls which data is included in calculations — it does not add dimensions to the view or change how marks are structured. When you drag Category to the Filters shelf and keep only Furniture and Office Supplies, Tableau recalculates SUM(Sales) using only the rows that match those two categories. The view structure — Region on Columns, SUM(Sales) on Rows — stays exactly the same. You still get one bar (or mark) per region, but each bar now reflects sales from only the two retained categories. That makes A correct. B is wrong because placing a dimension on the Filters shelf never adds it to the view's level of detail. Only shelves like Columns, Rows, Detail, Color, Size, or Shape affect level of detail. The filter quietly restricts data behind the scenes without creating new marks. C describes how a tooltip filter or a display toggle might behave, but that's not what a standard dimension filter does. Excluded categories are removed from the underlying query entirely — their sales don't contribute to any aggregation, hidden or otherwise. D confuses the Filters shelf with a layout shelf. Dragging a dimension to Filters never rearranges columns or replaces existing dimensions in the view structure. Only placing a field on Columns or Rows controls the visual layout. A reliable rule of thumb: Filters change the data, not the structure. If you want a dimension to create new marks or columns, it needs to be on a view shelf — not the Filters shelf.

Question 3

A worksheet has Category on Rows and SUM(Sales) on Columns. No other dimensions are present. You drag the existing Category pill from Rows to the Filters shelf without holding a modifier key, and then retain two categories.

What is the expected result after applying the filter?

  1. Category remains on Rows, and the view shows individual sales bars for only the two retained categories.
  2. Category leaves Rows, and the view shows a single aggregate sales mark covering the two retained categories. (correct answer)
  3. Category leaves Rows, but separate bars still appear because filter selections implicitly define mark-level detail.
  4. Category remains on Rows, all three category bars stay visible, and the two retained categories are highlighted.
Explanation: Whenever you see a question about dragging a pill to the Filters shelf in Tableau, ask yourself: what happens to the structure of the view, not just the data? Filters control which data is included, but a field's presence on a shelf is what determines how marks are drawn. When you drag Category from Rows to Filters, you are physically removing it from Rows. Tableau does not duplicate the pill — it moves it. With no dimension left on Rows or Columns, there is no field to split marks into separate bars. The view collapses to a single aggregate mark representing the combined SUM(Sales) of your two retained categories. This confirms answer B. Answer A is the most tempting trap: it assumes the pill stays on Rows while also appearing on Filters. But without holding a modifier key (like Ctrl on Windows), dragging a pill moves it rather than copying it. Category leaves Rows entirely, so separate bars cannot exist. Answer C contains a subtle misconception — filters do not implicitly add detail to a view. A dimension must be on Rows, Columns, Detail, or another encoding shelf to split marks. Filtering by a field only restricts rows in the data; it never creates mark-level granularity on its own. Answer D describes highlighting behavior, not filtering. Holding a modifier during a drag or using Tableau's highlight feature produces that effect. Simply applying a dimension filter does not keep all original marks visible and highlighted. The key habit to build: always track where each pill lives. Moving a pill off a shelf removes its role in structuring the view, regardless of where it lands next.

Question 4

Using default aggregation and stacking settings, you place discrete YEAR(Order Date) on Columns and SUM(Sales) on Rows. The data contains four regions with sales in each of three years.

What happens when you drag Region from the Data pane to Color on the Marks card?

  1. Three yearly bars are divided into four colored marks, one mark for each region-year combination. (correct answer)
  2. Four regional bars are divided into three colored marks, one mark for each year-region combination.
  3. Twelve bars appear side by side because placing Region on Color also adds it to Columns.
  4. Three single-mark bars remain because fields on Color do not change the view's level of detail.
Explanation: When you add a field to Color on the Marks card, you're increasing the level of detail of the view — Tableau breaks each existing mark into finer pieces based on that new dimension. This is the core concept being tested here. Starting with discrete YEAR(Order Date) on Columns and SUM(Sales) on Rows, you have three bars — one per year. Each bar is a single aggregated mark. When you drag Region to Color, Tableau disaggregates each year's bar by region, producing four colored segments stacked within each year's bar. That's four region segments × three years = twelve total marks, displayed as three stacked bars. This is exactly what A describes, making it correct. B gets the structure backwards — it implies four regional bars each split by year, which would require Region on Columns and Year on Color, not the other way around. The dimension on Columns drives how many bar groups you see, not the field on Color. C confuses Color with Columns. Dragging a field to Color never places it on a shelf — it only partitions marks by color within the existing axis structure. You still see three bar positions, not twelve side-by-side bars. D reflects a common misconception that Color is purely cosmetic. In reality, adding a dimension to Color does change the level of detail, splitting aggregated marks into sub-marks. Color is one of several mark properties (alongside Size, Detail, etc.) that can increase granularity. Study tip: Remember that any dimension dropped onto a Marks card property — Color, Size, Detail, Tooltip — increases the view's level of detail, just like adding it to a shelf does.

Question 5

Category is on Columns and SUM(Sales) is on Rows. You want to compare Sales and Profit by category without creating a combined axis.

You drag Profit from the Data pane to an empty position on the Rows shelf immediately beside SUM(Sales). What does Tableau create?

  1. A single combined axis containing both measures, with Measure Names colors distinguishing Sales from Profit.
  2. A second row of panes with a separate SUM(Profit) axis, both pane rows sharing the same Category column headers. (correct answer)
  3. One row of bars whose heights represent SUM(Sales) added to SUM(Profit) for each category.
  4. A nested row dimension header for Profit because Tableau treats every second pill on Rows as a discrete field.
Explanation: When you place multiple continuous measures side by side on the Rows shelf in Tableau, you're controlling axis behavior — and this is the key concept being tested here. Tableau distinguishes between dropping a measure onto an existing pill (which blends axes) versus dropping it beside a pill as a separate field (which creates independent axes). When you drag Profit to an empty slot on Rows next to SUM(Sales), Tableau treats each pill as its own continuous axis. The result is B: two separate row panes, each with its own axis — one for SUM(Sales) and one for SUM(Profit) — while both share the same Category column headers across the top. This is called a dual-pane or separate axes layout, and it's the default behavior when adding a second measure to Rows without combining axes. Answer A describes what happens when you drop a measure onto an existing axis or use the "dual axis" option — Tableau then layers both measures onto one shared axis and uses Measure Names/Colors to differentiate them. That's a deliberate action, not the default drop behavior. Answer C describes a stacked or additive calculation, which Tableau doesn't perform automatically by placing two pills on Rows — those remain independent aggregations. Answer D is simply false; Tableau doesn't convert a continuous measure into a discrete dimension header just because of its position on the shelf. A helpful rule of thumb: side by side on Rows = separate panes with separate axes; dropped onto an existing axis = combined axis. Remembering this distinction will help you quickly eliminate distractors on any axis-behavior question.

Question 6

Category is on Columns. The Rows shelf is empty, and no measure is currently present in the worksheet.

What results from dragging Sales directly to Text on the Marks card?

  1. Each category receives a color gradient based on SUM(Sales), but no numeric value appears as text.
  2. A vertical sales axis is created, with one unlabeled bar displayed for each category column.
  3. Each category pane displays a text mark showing the aggregated SUM(Sales) for that category. (correct answer)
  4. Individual transaction-level sales amounts are listed as text because measures on Text are not aggregated.
Explanation: When you drag a field to the Text mark in Tableau, you're telling Tableau to display values as labels inside each mark's pane. The key question is always: what kind of mark does Tableau create, and how is the data aggregated? Here, Category is on Columns with no measure on Rows, so Tableau builds a text table (crosstab-style view). Dragging Sales to Text places it as a measure on the Marks card, where Tableau automatically aggregates it as SUM(Sales). The result is exactly what C describes — each category column displays a text mark showing the aggregated SUM(Sales) for that category. This is the correct answer. A is wrong because dropping a field on Text has nothing to do with color encoding. Color gradients only appear when a measure is placed on the Color mark, not Text. No color behavior is triggered here. B describes what happens when you drag Sales to Rows — that action creates a vertical axis and generates bar marks. Dragging to Text never creates an axis or bars; it produces text labels, not geometric marks tied to an axis. D contains a dangerous misconception: Tableau always aggregates measures by default, regardless of which mark property you use. Placing Sales on Text does not produce transaction-level (disaggregated) values unless you explicitly turn off aggregation in the Analysis menu. SUM is applied automatically. Study tip: Memorize the effect of each Marks card property — Color, Size, Label, Detail, Tooltip, and Text each have distinct behaviors. Exam questions frequently test whether you can distinguish between what happens on Rows/Columns versus the Marks card.

Question 7

In Tableau Desktop on Windows, Category is on Columns and SUM(Sales) is on Rows, producing sales bars by category.

You hold Ctrl while dragging the SUM(Sales) pill from Rows to Label on the Marks card. What is the expected result?

  1. SUM(Sales) moves to Label, and Tableau automatically substitutes Number of Records on the Rows axis.
  2. SUM(Sales) moves from Rows to Label, leaving a text-only view with no vertical sales axis.
  3. SUM(Sales) remains on Rows, while Label receives an unaggregated copy of the Sales field.
  4. SUM(Sales) remains on Rows and a duplicate pill on Label displays sales values on each bar. (correct answer)
Explanation: When working with pills in Tableau, understanding the difference between dragging and Ctrl+dragging is essential. Dragging a pill moves it from its current location, while holding Ctrl while dragging creates a copy, leaving the original pill in place. This distinction is what the question is testing. In this scenario, you Ctrl+drag SUM(Sales) from Rows to Label on the Marks card. Because you're copying rather than moving, SUM(Sales) stays on Rows, preserving your bar chart's vertical axis. Simultaneously, a duplicate SUM(Sales) pill appears on the Label shelf, causing Tableau to display the sales value as a label directly on each bar. The result is a labeled bar chart — arguably the most common use case for this exact technique. D is correct for exactly this reason: the original pill remains on Rows and a duplicate lands on Label. A is wrong because Tableau does not auto-substitute Number of Records when you move or copy a measure — that replacement behavior doesn't exist in this context. B describes what would happen if you moved (not copied) SUM(Sales) to Label — removing it from Rows would collapse the axis, leaving a text-only view. The key word the question uses is "hold Ctrl," which signals a copy, not a move. C is wrong on two counts: while a copy does stay on Rows, the Label pill receives an aggregated copy (SUM(Sales)), not an unaggregated version of the raw Sales field. Study tip: On Tableau exam questions, whenever you see "Ctrl+drag," immediately think copy, not move — the original pill stays put.

Question 8

A data source has at least one order in every month from January 2024 through December 2025. You place SUM(Sales) on Rows.

You drag Order Date to Columns and choose the continuous Month date option. How is time represented?

  1. A continuous numeric axis containing the individual day number for every order record.
  2. Twelve discrete month-name headers that combine each month across both calendar years.
  3. Two discrete year headers because continuous dates are automatically aggregated at the year level.
  4. A continuous timeline with 24 monthly positions spanning January 2024 through December 2025. (correct answer)
Explanation: When you drag a date field to Columns in Tableau, the single most important distinction to understand is discrete vs. continuous — and within continuous dates, whether the result is a timeline or an axis of raw numbers. Choosing the continuous Month option tells Tableau to treat each month-year combination as a unique point along a true time axis. Because it's continuous, Tableau renders a numeric axis that flows from the earliest date to the latest — in this case, January 2024 through December 2025. With 24 months in that range, you get 24 evenly spaced positions plotted along an unbroken timeline. That's exactly what D describes, making it the correct answer. A is wrong because a continuous axis of individual day numbers would only appear if you chose the Day date part, and even then, it would show calendar day numbers (1–31), not a full timeline. This confuses the continuous date level with a raw numeric field. B describes the discrete Month option — where Tableau strips away the year and groups all Januaries together, all Februaries together, etc., producing 12 labeled headers. Choosing continuous specifically preserves the year context, so months are never collapsed across years. C is wrong because continuous dates do not auto-aggregate to year level. Aggregation to year happens when you drop a date field and Tableau defaults to the discrete Year pill — a completely different interaction than manually selecting continuous Month. Study tip: On Tableau exam questions, map every date choice to two axes: discrete (headers/pills = blue) vs. continuous (axis = green), and date part (strips year) vs. date value (keeps full context). That matrix resolves most date questions quickly.

Question 9

A worksheet has Segment followed by Category on the Rows shelf and SUM(Sales) on the Columns shelf. The view therefore nests Category within Segment.

You drag the Category pill to the left of Segment on the Rows shelf. What is the resulting organization of the view?

  1. Category becomes the outer row grouping, with Segment nested within each category. (correct answer)
  2. Segment remains the outer row grouping, but categories are sorted alphabetically within it.
  3. Category moves to Columns, producing a separate sales axis for each category.
  4. Segment and Category are combined into a single concatenated row header.
Explanation: When you place multiple dimensions on the Rows shelf in Tableau, their left-to-right order determines a hierarchy: the leftmost pill becomes the outer grouping, and each pill to its right is nested inside that grouping. Think of it like a Russian nesting doll — the outermost doll is always the leftmost dimension. In the original view, Segment is left of Category, so rows are organized as Segment → Category. When you drag Category to the left of Segment, you flip that hierarchy: Category is now the outer doll, and Segment nests inside each category. That makes A the correct answer — Category becomes the outer row grouping with Segment nested within it. B is wrong because reordering pills doesn't trigger an alphabetical sort — it restructures the nesting relationship entirely. Sorting is a separate action applied via the sort menu or toolbar. C is wrong because dragging a pill within the Rows shelf keeps it on Rows; it would only move to Columns if you explicitly dragged it to the Columns shelf or dropped it there. D is wrong because Tableau doesn't concatenate dimension headers just from reordering — concatenated headers are a specific feature you get when you hold Shift while dropping a dimension onto an existing pill, creating a combined field. Study tip: On Tableau exam questions about shelf order, always ask yourself "which pill is leftmost?" That pill wins the outer grouping. Visualizing the nesting hierarchy from left to right will quickly eliminate distractors like B, C, and D.

Question 10

A worksheet contains Region on Columns and SUM(Sales) on Rows. There is one bar for each region, and Profit is not yet used.

You drag Profit to Color on the Marks card. Which statement correctly describes the resulting view?

  1. Each region receives separate Sales and Profit bars because Color creates an additional measure axis.
  2. Bar heights change to SUM(Profit), while each bar's color continues to represent SUM(Sales).
  3. Bar heights continue to represent SUM(Sales), while each bar's color represents SUM(Profit) for that region. (correct answer)
  4. Bar heights represent Sales plus Profit because measures on Color are merged with measures on Rows.
Explanation: When you place a measure on the Color shelf in Tableau, you're encoding that measure through color — you are not replacing, combining, or splitting the existing axis measure. The existing structure of the view (what's on Rows and Columns) stays intact. Think of the Marks card as a layer of additional visual encoding on top of the base chart. In this scenario, SUM(Sales) remains on Rows, so bar height continues to represent Sales for each region. Dragging Profit to Color simply tells Tableau to shade each bar according to that region's SUM(Profit), producing a color gradient across the bars. That's exactly what C describes — bar heights represent Sales, bar colors represent Profit. C is correct. A is wrong because dragging a measure to Color does not create a new axis or generate additional bars. A new axis only appears when you drop a measure directly onto Rows or Columns, or use a dual-axis configuration. B has the encoding backwards. Color is carrying Profit, not Sales. The bar heights — controlled by what's on Rows — still reflect SUM(Sales). Nothing on the Rows shelf changed. D describes a behavior that simply doesn't exist in Tableau. Placing a measure on Color never merges or adds its values to the axis measure. The two fields remain independent encodings. A helpful rule of thumb: the shelf determines the encoding. Rows/Columns control position (axis), Color controls color, Size controls size, and so on. Dropping a field on Color only ever affects color — it leaves every other encoding untouched.