Tableau Quiz: Marks Card Encodings
10 questions · exam conditions
0:00
Marks Card EncodingsQuestion 1 of 10

A monthly sales view currently shows one aggregate line across all customer segments. The analyst wants a separate line for each segment but does not want segment colors, text labels, or additional panes.

Which Marks card encoding should be used?

Place Customer Segment on Detail to partition the single line into separate paths without adding colors or labels
Place Customer Segment on Label and configure Tableau to suppress all overlapping label text
Place Customer Segment on Color and hide the color legend from the view
Place Customer Segment on Size so each segment is represented by a line of a different thickness
← Back to quizzes

Tableau Quiz

Tableau Quiz: Marks Card Encodings

Practice Marks Card Encodings 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 Marks Card Encodings, 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 monthly sales view currently shows one aggregate line across all customer segments. The analyst wants a separate line for each segment but does not want segment colors, text labels, or additional panes.

Which Marks card encoding should be used?

  1. Place Customer Segment on Detail to partition the single line into separate paths without adding colors or labels (correct answer)
  2. Place Customer Segment on Label and configure Tableau to suppress all overlapping label text
  3. Place Customer Segment on Color and hide the color legend from the view
  4. Place Customer Segment on Size so each segment is represented by a line of a different thickness
Explanation: When you see a question about splitting a single mark into multiple paths without changing the visual appearance, think about what each Marks card property actually does to your data — specifically, which ones add visible encodings versus which ones simply reorganize the underlying partitions. Detail is Tableau's way of saying "break this mark apart using this field, but don't change how anything looks." Placing Customer Segment on Detail tells Tableau to draw a separate line for each segment while keeping all lines the same color, size, and style, with no labels generated. That's exactly what the analyst needs — choice A is correct. Choice B places the field on Label, which generates visible text annotations on the view. Even if you suppress overlapping labels, you're fighting the tool rather than using it correctly, and some labels may still appear depending on density and settings. Choice C puts the field on Color, which does partition the lines correctly but immediately applies distinct color encoding to each segment and generates a color legend in the view — two things the analyst explicitly wants to avoid. Hiding the legend removes only the legend card, not the color encoding itself. Choice D uses Size, which isn't a meaningful encoding for line identity in this context. Tableau would attempt to map segment values to line thickness, which is visually confusing, semantically wrong, and doesn't solve the partitioning problem cleanly. Study tip: Memorize Detail as the "invisible partition" property — it increases the level of granularity of marks without adding any visual channel. Anytime a question asks you to split marks without changing appearance, Detail is almost always the answer.

Question 2

A view contains one mark per product. The analyst must show SUM(Profit) with a continuous color gradient and make each of three product categories visually identifiable without using text labels. Category is currently on Color, but dragging SUM(Profit) to Color would replace that categorical encoding.

Which Marks card arrangement best meets both requirements?

  1. Keep Category on Color and place SUM(Profit) on Detail
  2. Place SUM(Profit) on Color and Category on Shape (correct answer)
  3. Place both SUM(Profit) and Category on the Color property
  4. Place Category on Detail and SUM(Profit) on Size
Explanation: When a question asks you to encode two different types of data simultaneously on a Tableau marks card, your first instinct should be to check whether those two data types — one quantitative, one categorical — can coexist on the same shelf or need to be split across different shelves. SUM(Profit) is a continuous quantitative measure, making it a natural fit for Color as a gradient. Category is a discrete dimension that needs a preattentive visual channel capable of distinguishing three groups — Shape handles exactly that, since Tableau supports multiple distinct shapes per mark. Placing SUM(Profit) on Color and Category on Shape (answer B) satisfies both requirements cleanly: you get a continuous color gradient and three visually identifiable categories, with no text labels required. Answer A fails the color requirement entirely — keeping Category on Color means you get categorical color swatches, not a continuous profit gradient. Profit on Detail adds it to the tooltip but provides zero visual encoding. Answer C sounds appealing, but Tableau does not allow two fields to simultaneously share the Color shelf in a blended continuous/categorical way; dragging a measure to Color replaces whatever is already there, so you'd lose category encoding. Answer D encodes Category on Detail (invisible) and Profit on Size — Size can represent magnitude, but the question explicitly requires a color gradient for Profit, and Category remains visually unidentifiable. A useful rule of thumb: Shape is your best friend when Color is already "taken" by a measure. On the Tableau exam, watch for scenarios where two encoding needs compete for Color — that's your cue to reach for Shape or Size for the categorical dimension.

Question 3

A view has one mark per Product Category. The analyst wants Color to show Segment only when all underlying rows for a category have the same segment. Categories containing multiple segments should remain one mark and be represented by a single ambiguous member rather than being split.

Which field placement best meets the requirement?

  1. Place Segment on Color as a dimension so Tableau preserves one category mark
  2. Place Segment on Detail and assign the resulting marks a common color
  3. Place MIN(Segment) on Color so mixed categories receive an ambiguity indicator
  4. Place ATTR(Segment) on Color so mixed categories are represented by an asterisk (correct answer)
Explanation: When Tableau places a dimension on Color, it splits marks — so if a category spans multiple segments, you'd get multiple marks per category, breaking the "one mark per category" requirement. This question tests your understanding of ATTR(), one of Tableau's special aggregations designed specifically for the scenario where you want to display a field's value only when it's unambiguous. ATTR(Segment) evaluates whether all rows in a partition share the same value. If they do, it returns that value. If they don't, it returns an asterisk (*) — a built-in ambiguity indicator that keeps the mark intact rather than splitting it. This is exactly what the passage describes: single-segment categories get a meaningful color, and mixed categories stay as one mark shown with a neutral, recognizable signal. D is the right answer. Option A is the classic trap here. Placing Segment on Color as a dimension forces Tableau to create one mark per dimension member per category, splitting mixed categories into multiple marks — the opposite of what's needed. Option B places Segment on Detail, which also splits marks for the same reason; adding a common color afterward doesn't undo the mark explosion. Option C uses MIN(Segment), which does aggregate and avoids splitting, but MIN returns the alphabetically first segment for mixed categories — it silently picks a "winner" rather than signaling ambiguity. That's misleading, not the asterisk behavior the requirement calls for. Your study tip: memorize that ATTR() = "one value or asterisk." On the Tableau exam, any time a question involves preserving mark granularity while conditionally displaying a field's value, ATTR() is almost always the right tool.

Question 4

A bar chart has Region on Rows and SUM(Sales) on Columns, producing one bar for each region. The analyst wants each bar to display its regional sales total without creating additional marks.

Which action should the analyst take?

  1. Place Order ID on Label so the label displays an order-level identifier for each bar
  2. Place SUM(Sales) on Label and format the displayed number (correct answer)
  3. Place Region on Detail and enable labels for every resulting mark
  4. Place Sales (unaggregated) on Detail and insert the field into the label text
Explanation: When working with labels in Tableau, the key question to ask is: what level of detail do I want the label to represent, and does it match the existing marks? Here, the view already has one bar per region, so the goal is simply to display each bar's aggregated sales value — no structural changes needed. Placing SUM(Sales) on Label (answer B) is the correct move because SUM(Sales) is already the measure driving the bar lengths. Dropping it onto Label displays that same aggregated value as text on each bar, and you can format the number (currency, thousands separator, decimal places) without adding any new marks or changing the view's granularity. Clean, direct, and exactly what the analyst needs. Answer A is a trap: placing Order ID on Label introduces a dimension that exists at a finer grain than Region. Tableau would either show a meaningless aggregated count or force a disaggregation, neither of which produces a clean regional total on each bar. Answer C misunderstands the Detail shelf — adding Region to Detail when Region is already on Rows does nothing meaningful to the view structure, and "enabling labels for every mark" still wouldn't surface the sales total in a useful way without explicitly placing a measure on Label. Answer D compounds the problem: placing Sales unaggregated on Detail explodes the view to the row level, multiplying your marks and breaking the one-bar-per-region structure entirely. The study tip here: always match the label field's aggregation level to the existing mark granularity. If the mark represents a regional sum, the label should reference that same aggregate — SUM(Sales), not the raw field.

Question 5

A line chart has Month on Columns, SUM(Sales) on Rows, and Region on Color, creating one line per region. Region is also available for use in the label text. The analyst wants each line labeled with its region only at the most recent endpoint.

Which configuration most directly produces the requested labels without filtering out earlier months?

  1. Place Month on Detail as well as Columns, then label every mark with the Region field value
  2. Filter the view to the latest month only, then place Region on Label to display the name
  3. Place Region on Label and configure the label setting to display text only at the end of each line (correct answer)
  4. Place Region on Shape and enable labels for highlighted marks to approximate endpoint labeling
Explanation: When working with line charts in Tableau, a key concept is mark-level label control — Tableau gives you granular options for where labels appear on a line, not just whether they appear. This question tests whether you know how to use those built-in label placement settings rather than working around them with filters or field manipulation. The cleanest solution is C: placing Region on Label and then opening the Label shelf options to select "End of line" (or "Most recent" in time-based views). Tableau's line mark type has a dedicated label positioning setting that places text only at the final data point of each line — exactly what the analyst needs. No data is removed, no view structure changes, and each line gets its region name right at its endpoint. Answer A introduces unnecessary complexity. Adding Month to Detail doesn't change which marks are labeled or where labels appear — it would just fragment the view into individual marks, and labeling every mark would clutter every data point, not just the endpoint. Answer B is a common trap: filtering to only the latest month technically shows a label at "the end," but it destroys the rest of the chart. The question explicitly states the analyst doesn't want to filter out earlier months, so this approach breaks the core requirement. Answer D misunderstands how Shape and highlighting work. Shape changes the mark type, and highlight-based labels are conditional on user interaction — neither reliably places a static region label at the line endpoint. Study tip: Whenever a question asks about label placement on line charts, go straight to the Label shelf's line-specific options — Tableau has built-in "end of line" functionality precisely for this use case.

Question 6

A scatter plot contains one mark per Order ID. Each order has exactly one Ship Mode. Color already displays a continuous profit measure, and the analyst must distinguish the four ship modes without replacing that color encoding or adding text to every mark.

Which Marks card change best satisfies the requirement?

  1. Place Ship Mode on Detail so each mode receives a visible symbol
  2. Place Ship Mode on Color alongside the existing continuous profit field
  3. Place Ship Mode on Label and hide the resulting text labels
  4. Place Ship Mode on Shape and retain the profit measure on Color (correct answer)
Explanation: When Tableau's Marks card is already using Color for a continuous measure, you need to think carefully about which other channels can carry categorical information without displacing or conflicting with what's already there. Each shelf on the Marks card serves a distinct visual role, and understanding those roles is the key to this question. Shape is the perfect solution here. Placing Ship Mode on Shape assigns a distinct geometric symbol (circle, square, triangle, etc.) to each of the four modes while leaving Color completely untouched — the continuous profit gradient remains fully intact. That's exactly what D does, and it's why D is correct. A is tempting but wrong. Detail increases the granularity of marks and can affect aggregation, but it does not produce a visible distinguishing symbol. Marks on Detail all look identical unless another channel differentiates them — so the four ship modes would still be visually indistinguishable. B is a critical trap. Tableau does not allow a continuous field and a discrete field to coexist on Color simultaneously. Dragging Ship Mode to Color would replace the profit measure, which the question explicitly forbids. C tries to be clever, but placing Ship Mode on Label and then hiding the labels is self-defeating — you've added nothing visible to the view. Hidden labels communicate nothing to the reader. Study tip: Memorize which Marks card shelves can stack without conflict. Color accepts only one encoding at a time, but Shape and Color are completely independent channels — you can always use both simultaneously. When a question restricts Color, Shape is your first candidate for adding a second categorical dimension visually.

Question 7

A dual-axis view displays SUM(Sales) as bars and SUM(Profit) as a line. The Marks area contains an All card and separate cards for SUM(Sales) and SUM(Profit). The analyst wants to color only the profit line by Region while leaving every sales bar in its current single color.

Where should Region be placed?

  1. On Color in the All Marks card, then manually reset the bar colors
  2. On Detail in the SUM(Sales) Marks card to isolate the line encoding
  3. On Color in the SUM(Profit) Marks card only (correct answer)
  4. On Color in the SUM(Sales) Marks card only
Explanation: When working with dual-axis charts in Tableau, the key concept is independent Marks card control. Each measure in a dual-axis view gets its own Marks card, and whatever you place on a measure-specific card affects only that mark type. The shared "All" card, by contrast, applies properties to every mark simultaneously. Since you want Region to drive color exclusively on the profit line, you should place Region on Color within the SUM(Profit) Marks card — answer C. This tells Tableau to segment and color the line by Region while leaving the SUM(Sales) Marks card completely untouched, so all bars retain their original single color. Answer A is a tempting workaround but fundamentally flawed. Placing Region on the All card applies it to both marks at once, coloring bars and the line by Region. Manually resetting bar colors afterward is fragile — it doesn't remove the dimension from the bars' encoding, it just masks the symptom. Answer B misunderstands how Detail works. Placing Region on Detail in the SUM(Sales) card would actually subdivide the sales bars by Region (creating separate marks per region), which changes the bar structure rather than isolating the line's color encoding. Answer D is the mirror-image mistake of C — placing Region on Color in the SUM(Sales) card colors the bars by Region, which is exactly what you're trying to avoid. Study tip: On dual-axis questions, always ask yourself which Marks card is "in scope." If a property should affect only one measure, use that measure's specific card — never the All card.

Question 8

A circle view is filtered to one subcategory. It contains two orders on different exact dates, with sales of 100 and 300. Before Order Date is added, the view has one circle and SUM(Sales) is on Size. You then place exact Order Date on Detail.

How will Tableau encode the marks after Order Date is added to Detail?

  1. It will create two circles sized by sales values of 100 and 300 (correct answer)
  2. It will retain one circle sized by total sales of 400
  3. It will create two circles that are both sized by total sales of 400
  4. It will retain one circle and use date only as hidden descriptive metadata
Explanation: Whenever you see a question about adding a field to Detail in Tableau, the core concept to understand is mark granularity — Detail controls how finely Tableau disaggregates your data into individual marks. Before Order Date is added, Tableau has no way to distinguish the two orders from each other, so it aggregates them into a single mark: one circle with SUM(Sales) = 400. The moment you place exact Order Date on Detail, you're telling Tableau to treat each unique date as a separate mark. Since the two orders fall on different exact dates, Tableau now sees two distinct rows of data and renders two separate circles — one for the order with sales of 100 and one for the order with sales of 300. Size is driven by SUM(Sales) at each mark's level of detail, so each circle reflects its own individual sales value. That's exactly what answer A describes, making it correct. Answer B is wrong because adding Order Date to Detail does change the view — Tableau disaggregates the data, so you cannot retain a single circle once the granularity increases. Answer C is tempting but misunderstands how aggregation works after disaggregation: once the marks split, each circle's SUM(Sales) is computed within its own partition (100 and 300 respectively), not across the full 400. Answer D is wrong because Detail is not hidden metadata — it actively changes which marks are drawn by altering granularity. Study tip: Think of Detail as a "split instruction." Every unique value of a Detail field creates a new mark. When combined with a measure on Size, each new mark sizes itself by its own aggregated value, not the grand total.

Question 9

A view initially contains one circle for each of four regions. The data contains six products in each region, and every product belongs to exactly one of three categories. You drag Product to Detail and Category to Color on the Marks card.

Assuming every region contains all six products, how many marks will the view contain, and what will determine their colors?

  1. Four marks, with each regional mark colored by its aggregated category
  2. Twenty-four marks, with each product-region mark colored by its category (correct answer)
  3. Twelve marks, with one mark for each region-category combination
  4. Seventy-two marks, with one mark for each region-product-category combination
Explanation: When you add a field to Detail on the Marks card in Tableau, you're telling the view to disaggregate the data down to that level of granularity — creating a separate mark for every unique combination of the fields currently on the Marks card. This question tests whether you understand how Detail and Color interact to determine the number of marks. Here's the logic: the view starts with four regions (four marks). When you drag Product to Detail, Tableau breaks each regional mark into individual product marks — six products per region gives you 4×6=244 \times 6 = 24 marks. Dragging Category to Color then colors each of those 24 marks by the category that product belongs to, but it does not further split the marks, because Category is already implicitly determined by each product. The result is 24 marks, each colored by its product's category — confirming answer B. A is wrong because adding Product to Detail disaggregates the view; you no longer have just four regional marks. C suggests Tableau would aggregate products within each region by category (4×3=124 \times 3 = 12), but that would only happen if Category were on Detail — Product on Detail keeps each product as its own mark. D multiplies regions × products × categories (4×6×3=724 \times 6 \times 3 = 72), treating Category as an additional splitting dimension, but since every product belongs to exactly one category, adding Category to Color introduces no new combinations. Study tip: Always ask yourself, "What fields are on Detail (or other Marks shelves)?" — those fields define granularity. Color, Size, and Tooltip color or style existing marks; they only increase mark count if they introduce a new dimension not already represented.

Question 10

A scatter plot has one mark per customer. SUM(Profit) is a continuous field on Color, producing a diverging gradient. Each customer has a different aggregated profit value. An analyst converts the SUM(Profit) pill on Color from continuous to discrete.

What is the expected result after the conversion?

  1. The marks are automatically divided into a fixed set of profit-range bins, and the legend updates to show those bin boundaries
  2. The mark count increases because placing a discrete measure on Color adds it to the view's level of detail, creating new partitions
  3. Each distinct aggregated profit value is treated as a categorical color member, while the aggregation level and mark count remain unchanged (correct answer)
  4. The color encoding retains a continuous gradient, but the legend switches from a continuous axis to a list of discrete color swatches
Explanation: When you toggle a measure pill from continuous to discrete in Tableau, you're changing how Tableau encodes the values — not how it calculates them. The aggregation (SUM, in this case) stays exactly the same, and so does the level of detail driving the marks. All you're changing is the visual treatment: instead of mapping values along a color gradient, Tableau assigns each distinct value its own categorical color slot. That's precisely why C is correct. Each customer already has a unique aggregated profit value, so each value becomes its own discrete color member. The mark count doesn't change because no new dimension has entered the view — the LOD is still one mark per customer. A is wrong because Tableau does not automatically create bins when you switch a measure to discrete. Binning requires an explicit "Create Bins" action on a dimension or measure field. The conversion here does nothing to group values into ranges. B describes what happens when you add a new discrete dimension to Color — that would introduce a new partition and potentially increase mark count. But converting an existing pill from continuous to discrete doesn't inject a new dimension into the view's LOD, so mark count is unaffected. D gets the logic exactly backwards. Continuous encoding produces the gradient with a continuous axis legend; discrete encoding produces a categorical list of color swatches. D describes the legend updating correctly but incorrectly claims the gradient is retained — those two things are mutually exclusive. A useful rule of thumb: in Tableau, continuous vs. discrete controls how values are encoded visually, not how they're aggregated or how marks are partitioned. Keep those two concepts separate on exam day.