Tableau Quiz: Tableau Interface
10 questions · exam conditions
0:00
Tableau InterfaceQuestion 1 of 10

A green continuous MONTH(Order Date) pill is on the Columns shelf, producing a time axis. For this worksheet only, a developer wants twelve discrete month headers instead. Other worksheets should continue using the field's current defaults.

Which interface action best meets the requirement?

Open the pill menu on Columns and select the discrete Month date part.
Convert Order Date to a dimension from the Data pane for the workbook.
Move the existing green date pill from Columns to the Rows shelf.
Select Order Date and choose a text table from Show Me.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Tableau Interface

Practice Tableau Interface 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 Tableau Interface, 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 green continuous MONTH(Order Date) pill is on the Columns shelf, producing a time axis. For this worksheet only, a developer wants twelve discrete month headers instead. Other worksheets should continue using the field's current defaults.

Which interface action best meets the requirement?

  1. Open the pill menu on Columns and select the discrete Month date part. (correct answer)
  2. Convert Order Date to a dimension from the Data pane for the workbook.
  3. Move the existing green date pill from Columns to the Rows shelf.
  4. Select Order Date and choose a text table from Show Me.
Explanation: When working with date fields in Tableau, the most important distinction to recognize is continuous vs. discrete and date value vs. date part. A green pill represents a continuous measure, which plots dates on a smooth axis. A blue pill represents a discrete dimension, which creates individual headers — exactly what "twelve discrete month headers" describes. The question also adds a scope constraint: the change must apply only to this worksheet, not alter the field's defaults workbook-wide. This makes A the right move. Right-clicking the green MONTH pill on Columns and selecting the discrete Month date part (the blue option in the pill menu) converts it to a discrete date part in context — just for that shelf placement, on that worksheet. You get twelve labeled month headers without touching the underlying field definition. B is wrong because converting Order Date to a dimension in the Data pane changes the field's default behavior for every worksheet in the workbook, violating the scope requirement. C is wrong because moving the pill to Rows changes its position on the canvas but does nothing to toggle it from continuous to discrete — you'd still have a continuous axis, just oriented vertically. D is wrong because using Show Me with a text table restructures the entire view type and doesn't specifically address converting a date to discrete month headers; it's a blunt instrument when a precise adjustment is needed. The study tip here: whenever a question mentions "this worksheet only" or "without affecting other sheets," that's a signal to use local controls — pill menus, shelf interactions — rather than Data pane edits, which always have workbook-wide scope.

Question 2

A developer opens Show Me and finds that a desired visualization type is unavailable. The worksheet already contains several fields, but the developer is uncertain whether the selected fields satisfy that visualization's requirements.

What should the developer do first to diagnose the issue using the Tableau interface?

  1. Remove all fields from the worksheet, close Show Me, and rebuild the view manually.
  2. Move every pill to the Marks card, reopen Show Me, and test the type again.
  3. Convert all selected fields to dimensions, reopen Show Me, and select the desired type.
  4. Hover over the unavailable Show Me type, review its field requirements, and adjust the selected fields. (correct answer)
Explanation: When a visualization type appears grayed out in Show Me, Tableau is signaling a mismatch between the fields you've selected and what that chart type requires. The key skill being tested here is knowing how to use Show Me's built-in diagnostic features before making any changes to your worksheet. The smartest first step is D: hover over the grayed-out visualization type. Tableau will display a tooltip listing exactly which field types and quantities are required — for example, "1 date, 1 measure" for a line chart. Once you see those requirements, you can compare them against your current selections and make a precise, targeted adjustment. This is a built-in diagnostic tool that costs you nothing and gives you exact guidance. Choice A is counterproductive — removing all fields and rebuilding from scratch discards your existing work and skips the diagnostic step entirely. You'd be solving blindly rather than using the information Tableau gives you. Choice B moves pills to the Marks card, which changes the structure of your view without actually addressing the field-type mismatch; it's also an arbitrary action taken without understanding the root cause. Choice C converts all fields to dimensions, which is a drastic change that would likely break your view further, since most chart types require at least one measure — and again, you'd be guessing instead of diagnosing. The broader strategy here: on Tableau exam questions involving Show Me, always think "what does Tableau tell me before I act?" Tableau's interface is designed to guide you — hovering, reading tooltips, and checking field type indicators are diagnostic steps that come before any restructuring of the view.

Question 3

A scatter plot already contains one mark per customer because Customer ID is on Detail. Customer Name is not in the view. The analyst wants each customer's name to appear only when the pointer hovers over that customer's mark, without adding a persistent label or changing the axes.

Which action best satisfies the requirement?

  1. Drag Customer Name to Label on the Marks card and hide overlapping labels.
  2. Drag Customer Name to Tooltip on the Marks card and format the tooltip as needed. (correct answer)
  3. Drag Customer Name to the Columns shelf and suppress the resulting headers.
  4. Drag Customer Name to the Pages shelf and display the page history controls.
Explanation: When you see a question about surfacing additional data in a Tableau view without altering the chart structure, think about the Marks card shelves and what each one actually does to the visualization. The key distinction here is persistent versus on-demand display of information. Dragging Customer Name to Tooltip (choice B) is exactly the right move. The Tooltip shelf stores fields that appear only when a viewer hovers over a mark — no labels clutter the view, axes remain unchanged, and the data is still accessible. You can even format the tooltip text to control exactly how the name appears. The distractors each introduce problems the requirement explicitly rules out. Choice A adds a persistent label directly on the mark, which is the opposite of "on-demand" — labels are always visible and, when hidden for overlap, become inconsistently displayed rather than hover-triggered. Choice C drags Customer Name to Columns, which restructures the entire chart by adding a new axis or dimension, fundamentally changing the view layout — exactly what the requirement says to avoid. Choice D places Customer Name on the Pages shelf, which creates a paging control that filters the view one customer at a time; it doesn't reveal the name on hover and dramatically changes how the user interacts with the data. A useful rule of thumb: on Tableau exam questions, whenever the requirement says "show information only on hover," your answer is almost always the Tooltip shelf. It's the only shelf on the Marks card designed specifically for contextual, interaction-triggered display.

Question 4

Two discrete dimensions are on the Columns shelf in this order: Region, then Segment. The resulting headers are grouped first by Region and then by Segment. The developer wants Segment to become the outer grouping while retaining both dimensions on Columns.

Which action produces the requested nesting?

  1. Drag the Segment pill to the left of Region on the Columns shelf. (correct answer)
  2. Drag the Segment pill to the right of Region on the Columns shelf.
  3. Move Segment from Columns to Color on the Marks card.
  4. Sort the Segment pill in descending order within each Region.
Explanation: When dimensions are placed on the Columns shelf, Tableau reads them left to right to determine grouping hierarchy — the leftmost pill becomes the outer (primary) grouping, and each pill to its right becomes progressively more nested inside it. This is the core concept being tested here. With Region to the left and Segment to the right, your view groups by Region first, then subdivides each region into segments. To flip that hierarchy — making Segment the outer grouping — you simply drag Segment to the left of Region on the Columns shelf. That makes Segment the new outer dimension and Region the nested one, which is exactly what answer A describes. No other changes to the view are needed. Answer B does the opposite: moving Segment to the right of Region only deepens its current nesting, making it more inner, not outer. Answer C removes Segment from the column headers entirely and encodes it as color on the Marks card — this changes how the data is visually distinguished, but Segment would no longer act as a structural grouping on Columns at all, which contradicts the requirement to retain both dimensions there. Answer D is a red herring; sorting a pill controls the order of values within a group (ascending vs. descending) but has absolutely no effect on which dimension serves as the outer or inner grouping. A useful mental model: think of the Columns shelf like folders within folders — the leftmost dimension is the outermost folder. When a question asks about changing nesting order, go straight to the left-to-right position of the pills.

Question 5

A dual-axis view has SUM(Sales) and SUM(Profit) as separate mark layers. The Marks area displays an All card, a SUM(Sales) card, and a SUM(Profit) card. Both layers currently use circles.

How should a developer change only the Profit layer to bars while leaving the Sales layer as circles?

  1. Select SUM(Profit) in the Data pane and choose bars in Show Me.
  2. Select the All Marks card and change its mark type to Bar.
  3. Select the SUM(Sales) Marks card and change its mark type to Bar.
  4. Select the SUM(Profit) Marks card and change its mark type to Bar. (correct answer)
Explanation: When working with dual-axis charts in Tableau, understanding how the Marks card hierarchy works is essential. A dual-axis view creates three Marks cards: an All card that controls shared properties across both layers, and one individual card per measure — in this case, SUM(Sales) and SUM(Profit). Changes made to an individual measure's card affect only that layer, while changes to the All card cascade down to both. To change only the Profit layer to bars, you select the SUM(Profit) Marks card and change its mark type to Bar. This isolates the change to that single layer, leaving the Sales layer untouched — which is exactly what D does and why it's correct. Answer A is wrong because the Show Me panel replaces or restructures your entire view rather than editing a single mark layer's type. It's not a surgical tool for adjusting one axis in a dual-axis chart. Answer B is the most tempting trap: changing the All card's mark type does affect both layers simultaneously, so it would convert both Sales and Profit to bars — the opposite of what's needed. Answer C compounds the confusion by selecting the wrong individual card; changing SUM(Sales) to Bar would make the Sales layer bars and leave Profit as circles, which is backwards. A useful pattern to remember: in Tableau, individual Marks cards override the All card for that layer. Whenever a question asks you to format one layer differently from another in a dual-axis view, your first instinct should be to reach for that measure's specific Marks card.

Question 6

A developer needs a text table with one row per Category and separate columns for Sales, Profit, and Quantity. Only those three measures should appear, and each cell should display the corresponding value.

Which arrangement most directly creates the requested view using Tableau's generated fields?

  1. Place Category on Rows, Measure Values on Columns, and Measure Names on Detail; filter Measure Names to the three measures.
  2. Place Category on Rows, Measure Names on Columns, and Measure Values on Text; filter Measure Names to the three measures. (correct answer)
  3. Place Measure Names on Rows, Category on Text, and Measure Values on Color; filter Measure Names to the three measures.
  4. Place Category on Columns, Measure Values on Rows, and Measure Names on Filters; filter Measure Names to the three measures.
Explanation: When Tableau needs to display multiple measures side by side in a text table, it relies on two auto-generated fields: Measure Names and Measure Values. Measure Names acts as a categorical dimension containing the names of your measures, while Measure Values is a special container that holds the corresponding numeric values. Understanding which shelf each belongs on is the core skill being tested here. For a text table with one row per Category and one column per measure, you want Category driving the rows and Measure Names driving the columns — that's what creates the column headers "Sales," "Profit," and "Quantity." Measure Values then goes on Text so each cell displays the actual number. Finally, filtering Measure Names to only your three measures keeps the view clean. This is exactly what B describes, making it the correct answer. A is close but misuses Detail for Measure Names. Placing Measure Names on Detail doesn't create separate columns — it just adds granularity to the marks without structuring the column headers you need. C inverts the logic entirely, putting Measure Names on Rows and Category on Text. This would produce one row per measure rather than one row per Category, which is the opposite of what was requested. D swaps the axes (Category on Columns, Measure Values on Rows) and buries Measure Names on the Filters shelf only. Filters alone can't generate column headers, so the multi-column structure never appears. A handy rule: in a standard Measure Names/Measure Values text table, Measure Names goes on Columns, Measure Values goes on Text, and your dimension goes on Rows — memorize that triplet.

Question 7

A workbook author intentionally hid several obsolete fields. Later, one hidden field is needed again, but it is not currently listed among the visible fields in the Data pane.

Which sequence restores the field through the Data pane?

  1. Open Show Me, enable hidden measures, and drag the field onto the worksheet.
  2. Use the Data pane search box, locate the field's data values, and select Include.
  3. Choose Show Hidden Fields, locate the grayed field, and then select Unhide. (correct answer)
  4. Add the field name to the Filters shelf and select the hidden members.
Explanation: When working with hidden fields in Tableau, it helps to think of "hiding" and "showing" as a visibility toggle managed directly within the Data pane — not through filters, search, or Show Me. Hidden fields still exist in your data source; they're simply suppressed from view to reduce clutter. To restore a hidden field, you right-click anywhere in the Data pane and select Show Hidden Fields. This causes all hidden fields to appear grayed out, visually distinguishing them from active fields. You then right-click the grayed field and choose Unhide, which returns it to full visibility. That's exactly what option C describes, making it the correct answer. Option A is a trap because Show Me controls chart type recommendations based on the fields already on your shelves — it has no mechanism for surfacing hidden fields or enabling hidden measures. Option B misleads you into thinking the search box can locate hidden fields by their data values; the Data pane search filters visible fields by name, and "Include" is a filter concept, not a visibility action. Option D is especially tricky — adding a field name to the Filters shelf and selecting hidden members sounds plausible, but the Filters shelf operates on data-level filtering (which rows appear), not on whether a field is visible in the Data pane. You cannot restore a hidden field's visibility through filtering. A helpful rule of thumb: anything related to field visibility in Tableau lives in the Data pane's right-click context menu, while anything related to data filtering lives on the Filters shelf. Keep those two concepts separate and questions like this become straightforward.

Question 8

A worksheet contains an aggregated scatter plot with SUM(Sales) on Columns and SUM(Profit) on Rows. It currently displays one mark for the entire data set. An analyst wants one mark for each Region, distinguished by color, while keeping both existing axes.

Which action should the analyst take?

  1. Drag Region from the Data pane to Color on the Marks card. (correct answer)
  2. Drag Region from the Data pane to the Columns shelf.
  3. Drag Region from the Data pane to the Filters shelf.
  4. Select Region in the Data pane and apply Show Me.
Explanation: When working with scatter plots in Tableau, the key concept to understand is how the Marks card controls the visual encoding of data — color, size, shape, label, and detail — without restructuring the axes or the underlying aggregation logic. The analyst's goal is to split that single aggregated mark into one mark per Region while keeping SUM(Sales) on Columns and SUM(Profit) on Rows intact. Dragging Region to Color on the Marks card (answer A) accomplishes exactly this: Tableau partitions the data by Region, computes SUM(Sales) and SUM(Profit) for each, and plots a distinct, color-coded mark per Region — all without touching the existing shelf structure. Answer B is a common trap. Placing Region on the Columns shelf would add a new axis for Region, breaking the scatter plot into separate panels rather than keeping a single plot with colored marks. You'd lose the two-axis format the question explicitly says to preserve. Answer C — dragging Region to the Filters shelf — would restrict which Regions appear in the view, not create separate marks for each one. Filtering removes data; it doesn't disaggregate it. Answer D, using Show Me, hands control to Tableau's automatic chart-type recommendations, which would likely restructure the entire view based on what Show Me thinks is best — unpredictable and not targeted to this specific need. The study tip here: whenever a question asks you to differentiate marks visually while preserving the existing view structure, think Marks card first — Color, Size, Shape, and Detail all add granularity without altering your axes.

Question 9

A worksheet shows monthly sales. During a presentation, the analyst wants to step through one month at a time using playback controls and optionally display the history of earlier marks.

Which placement provides this interface behavior?

  1. Place Month on the Pages shelf and use the page playback controls. (correct answer)
  2. Place Month on the Filters shelf and display a single-value filter.
  3. Place Month on Detail and enable mark labels for the worksheet.
  4. Place Month on Columns and change the mark type to a line.
Explanation: When a question describes "stepping through values one at a time with playback controls" and "showing a history of earlier marks," that's the signature description of Tableau's Pages shelf — a feature worth knowing cold for this exam. The Pages shelf breaks a view into a sequence of pages, one per member of the field placed on it. Placing Month on the Pages shelf (answer A) gives you exactly the interface described: forward/back playback buttons, a speed slider, and a "Show history" checkbox that trails earlier marks on screen as you advance through months. No other shelf replicates this behavior. Answer B is a common trap. A single-value filter does let you display one month at a time, but it's just a dropdown or slider — there are no playback controls and no history trail. Filters control what's included, not how you animate through values. Answer C misunderstands the Detail shelf. Placing a dimension on Detail adds granularity to marks without changing the visual structure at all — it doesn't create any navigation controls or sequential playback. Answer D places Month on Columns, which creates a standard time-series line chart showing all months simultaneously. That's useful for trend analysis, but it's the opposite of stepping through one month at a time. The memory hook here is: Pages = Playback. Whenever a question mentions animation, stepping through values sequentially, or displaying mark history, the Pages shelf is almost certainly the answer. No other shelf in Tableau provides native playback controls — that functionality belongs exclusively to Pages.

Question 10

A bar view contains one aggregated mark for each Product Category. A developer wants to expose variation among individual products within each category but does not want product names displayed as headers, labels, colors, or shapes.

Where should Product Name be placed?

  1. On Color in the Marks card, assigning a color to each product.
  2. On Label in the Marks card, displaying text for the product marks.
  3. On Detail in the Marks card, increasing the view's level of detail. (correct answer)
  4. On Columns beside Category, creating visible product headers in the view.
Explanation: When working with Tableau's Marks card, it helps to understand that each shelf controls a different visual property of your marks. The core question here is: how do you increase granularity in a view without changing what the user sees visually? Placing Product Name on Detail (answer C) tells Tableau to disaggregate the data down to the individual product level, creating one mark per product within each category — without altering color, shape, size, or labels. The marks still look the same visually, but the underlying data granularity increases. This is exactly what Detail is designed for: changing the level of detail of the view silently, behind the scenes. Answer A (Color) would work to disaggregate the data, but it assigns a distinct color to every product — directly violating the requirement that product names not appear as colors. Answer B (Label) places product names as visible text on each mark, which also violates the constraint against displaying product names as labels. Answer D (Columns) adds Product Name as a header on the column shelf, creating a visible axis or header for each product — again, explicitly what the question says to avoid. Notice the pattern: A, B, and D all expose product identity visually in the view, just through different channels (color, text, headers). Only Detail hides that identity from the viewer while still affecting how Tableau aggregates your data. Study tip: On Tableau exam questions, Detail is your go-to when you need to change granularity without any visual side effects. If the question mentions "no visible change," think Detail first.