Tableau Quiz: Annotations And Captions
10 questions · exam conditions
0:00
Annotations And CaptionsQuestion 1 of 10

A dashboard contains a worksheet showing one mark per state. The author adds a mark annotation to Oregon that includes the state name and aggregated sales. A category filter later changes Oregon's sales and moves its mark, but Oregon remains in the view.

What should the author expect from the annotation after the filter is applied?

It remains at its original coordinates and continues displaying the original sales value.
It follows Oregon's mark, and dynamically inserted sales text reflects the filtered value.
It follows Oregon's mark, but all annotation text remains fixed at its original value.
It disappears because mark annotations are invalidated whenever an aggregate changes.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Annotations And Captions

Practice Annotations And Captions 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 Annotations And Captions, 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 dashboard contains a worksheet showing one mark per state. The author adds a mark annotation to Oregon that includes the state name and aggregated sales. A category filter later changes Oregon's sales and moves its mark, but Oregon remains in the view.

What should the author expect from the annotation after the filter is applied?

  1. It remains at its original coordinates and continues displaying the original sales value.
  2. It follows Oregon's mark, and dynamically inserted sales text reflects the filtered value. (correct answer)
  3. It follows Oregon's mark, but all annotation text remains fixed at its original value.
  4. It disappears because mark annotations are invalidated whenever an aggregate changes.
Explanation: When working with annotations in Tableau, the key distinction to understand is how different annotation types behave dynamically. A mark annotation is anchored to a specific mark in the view — it travels with that mark as data changes, and any dynamic field references it contains (like aggregated measures inserted via the Insert menu) update automatically to reflect the current query results. This is exactly what makes B correct. When a category filter changes Oregon's sales and repositions its mark, the annotation follows the mark to its new location. Because the sales value was inserted as a dynamic field reference rather than typed as static text, Tableau re-evaluates it against the filtered data and displays the updated figure. The annotation stays connected to Oregon's mark in both position and data. A is wrong because it describes the behavior of a point annotation, which is anchored to fixed coordinates in the view rather than to a specific mark. A mark annotation does not stay at its original coordinates — it moves with the mark. C contains a half-truth that makes it a dangerous trap. It correctly states the annotation follows the mark, but claims the text stays fixed. In reality, dynamically inserted field values recalculate whenever the underlying data context changes; only text you manually typed as a literal string would remain unchanged. D is incorrect because mark annotations are not invalidated by aggregate changes. Tableau handles this gracefully by refreshing dynamic values — the annotation persists and updates rather than disappearing. Study tip: Remember the three annotation types (mark, point, area) by their anchors — mark follows the mark, point follows coordinates, area follows a region. On exam questions, this anchor behavior is almost always the key variable being tested.

Question 2

A worksheet on a dashboard contains a data-quality warning that applies to the entire view. The warning must remain directly below the visualization even when dashboard filters remove every mark associated with the affected records.

Which caption-based solution is most appropriate?

  1. Show and edit the worksheet caption so the warning remains associated with the view. (correct answer)
  2. Add a mark annotation to an affected record so the warning follows that record.
  3. Add a point annotation at the center so the warning remains below the view.
  4. Place the warning in a tooltip so it appears whenever users hover over the view.
Explanation: When a question asks about keeping a persistent warning or message tied to a view (not to specific data points), you should immediately think about the difference between view-level and mark-level features in Tableau. The key constraint here is that the warning must remain visible even when filters eliminate every mark from the view. The worksheet caption (answer A) is the right tool precisely because it belongs to the worksheet itself, not to any underlying data. You enable it via Worksheet → Show Caption, then type your warning text. Since the caption is anchored to the view container, it persists below the visualization regardless of what filters do to the marks — even an empty view still displays the caption. Answer B fails because a mark annotation is attached to a specific data record. If dashboard filters remove that record, the annotation disappears along with it — exactly the scenario the question says must be avoided. Answer C is a closer trap: a point annotation is placed at fixed coordinates in the view space rather than on a record, so it survives some filtering. However, point annotations don't reliably sit below the visualization; they float within the plot area itself. More importantly, captions are the purpose-built, cleaner solution for view-level messaging. Answer D places the warning in a tooltip, which only appears on hover and is invisible by default. A data-quality warning that users must actively discover by hovering isn't much of a warning at all. Study tip: On Tableau exam questions, whenever you see "must remain visible regardless of data" or "persistent message for the entire view," that's your signal to think caption — it's the only view-level text element that isn't data-dependent.

Question 3

The same worksheet is used in both an executive dashboard and an analyst dashboard. A callout explaining an unusual mark should appear only in the executive dashboard; adding the annotation to the shared worksheet would otherwise expose it in both places.

Which approach best limits the annotation to the intended dashboard?

  1. Duplicate the worksheet, annotate the duplicate, and use it only in the executive dashboard. (correct answer)
  2. Annotate the shared worksheet, then hide its annotation from the analyst dashboard layout.
  3. Add a worksheet caption and configure it to display only for executive dashboard users.
  4. Convert the callout to a point annotation so it becomes local to one dashboard.
Explanation: When a single worksheet appears in multiple dashboards, any annotation added directly to that worksheet becomes part of the worksheet itself — meaning it shows up everywhere that worksheet is used. There is no built-in Tableau mechanism to toggle annotation visibility per dashboard. That's the core concept this question is testing: understanding what belongs to the worksheet versus what belongs to the dashboard. The cleanest solution is A — duplicating the worksheet and annotating only the copy. The original stays clean for the analyst dashboard, while the annotated duplicate lives exclusively in the executive dashboard. This gives you full control with zero risk of cross-contamination. It's a straightforward structural fix that works within how Tableau actually behaves. B is tempting but incorrect: Tableau does not offer a way to hide or suppress individual annotations on a per-dashboard basis. Once an annotation is on a worksheet, it renders wherever that worksheet appears — you can't selectively suppress it in one dashboard layout. C describes worksheet captions, which are a separate feature entirely. Captions appear below the view and are not configurable by user role or dashboard context. There is no "display only for executive users" toggle at the caption level. D misrepresents how annotation types work. Point, mark, and area annotations are all worksheet-level objects regardless of type. Changing the annotation style doesn't restrict it to a single dashboard instance. The key study takeaway: in Tableau, annotations live on the worksheet, not the dashboard. Any time you need dashboard-specific content, the reliable answer is duplication — create a separate worksheet version for each distinct use case.

Question 4

A Tableau story has four story points created from the same dashboard, each with a different filter state. The presenter wants the story navigator to identify the points as "Baseline," "Expansion," "Correction," and "Outlook" without changing the titles shown inside the dashboard.

What should the presenter modify?

  1. The story point captions displayed for the four saved story states (correct answer)
  2. The worksheet captions embedded within the dashboard's individual views
  3. The dashboard title separately for each worksheet used by the story
  4. The mark annotations attached to the filtered marks in each state
Explanation: When working with Tableau stories, it helps to distinguish between two separate layers of labeling: what appears inside a dashboard or view, and what appears in the story navigator to identify each story point. These are independent of each other, and questions like this are testing whether you know which control belongs to which layer. Each story point has a caption — the editable label that appears in the navigator strip at the top (or bottom) of the story. By double-clicking a story point's caption, you can type a custom name like "Baseline" or "Outlook." This changes only the navigator label, leaving everything inside the dashboard — titles, view names, filters — completely untouched. That makes A the correct answer: modifying the story point captions is exactly the right tool for this job. B is wrong because worksheet captions belong to individual sheets, not to the story navigator. Changing them would alter labels within the views themselves, which is precisely what the presenter wants to avoid. C is a trap because dashboard titles are also part of the dashboard content — editing them would change what's visible inside the dashboard, not in the story navigator, and you cannot set a unique dashboard title per story point anyway. D is a red herring; mark annotations highlight specific data points on a viz and have nothing to do with navigation labels or story structure. A useful pattern to remember: in Tableau, story point captions = navigator identity, while dashboard/worksheet titles = content identity. When a question asks you to label story states without touching the underlying views, always reach for the caption.

Question 5

A dashboard author is annotating the highest-sales mark. The callout must contain the sentence "Current sales: [value]" and must show the new aggregated value when users change a region filter.

How should the value be added to the annotation?

  1. Type the currently displayed value directly into the annotation's text editor.
  2. Insert the aggregated sales field into the annotation using the Insert menu. (correct answer)
  3. Copy the value from the tooltip and paste it into a worksheet caption.
  4. Include the unaggregated sales field in a static dashboard text object.
Explanation: When working with annotations in Tableau, the key distinction to understand is the difference between static values and dynamic references. An annotation that simply displays a typed number will never update — it's frozen in place. A truly useful annotation responds to user interactions like filter changes, which requires inserting a live field reference. This is exactly what the Insert menu does when editing annotation text. By inserting an aggregated measure (such as SUM(Sales)) directly into the annotation's text editor, Tableau embeds a dynamic token that recalculates whenever the view changes — including when a region filter is applied. This makes B the correct approach: the annotation reads "Current sales: [SUM(Sales)]" and automatically reflects the filtered result. A is a common trap. Typing the currently displayed value produces a hardcoded string. It looks correct at authoring time but will never update when filters change, making the annotation misleading rather than helpful. C is a misfire on two levels: tooltips serve a different purpose than annotations, and pasting into a worksheet caption doesn't create a mark-level callout at all — captions describe the sheet, not individual data points. D compounds several errors: dashboard text objects are entirely disconnected from the viz's calculations, and using an unaggregated field wouldn't produce a single summary value anyway. As a study tip, whenever a Tableau question mentions that something must update dynamically with user interaction (filters, parameters, selections), look for answers involving inserted field tokens or calculated references — never manually typed values.

Question 6

An analyst maintains a scatter plot whose marks change after each monthly refresh. The analyst wants a callout anchored at the location representing a policy threshold of ten percent, regardless of which mark happens to be nearest that location.

Which annotation type best meets this requirement?

  1. A mark annotation attached to the mark currently nearest the threshold
  2. An area annotation covering the entire side beyond the threshold
  3. A point annotation placed at the threshold's axis-coordinate location (correct answer)
  4. A mark annotation attached to every mark that crosses the threshold
Explanation: When working with Tableau annotations, the key question to ask yourself is: what is being anchored — a data point, a region, or a coordinate in space? This distinction drives everything. A point annotation is tied to a fixed location defined by axis coordinates, meaning it stays put no matter how the underlying data changes. This is exactly what the analyst needs: a callout locked to the ten-percent threshold position on the axis, not to any particular mark. Because the scatter plot refreshes monthly and marks shift around, C is the right choice — the annotation remains anchored to the coordinate regardless of which mark is nearby. Choice A fails because a mark annotation attaches to a specific data point. After each refresh, the mark nearest the threshold could be a completely different record, so the annotation would drift to wherever that new mark lands — defeating the purpose of a stable threshold callout. Choice D has the same fundamental problem as A, just multiplied. Attaching a mark annotation to every crossing mark ties the labels to volatile data points. As marks move in and out of the threshold zone each month, annotations would appear and disappear unpredictably. Choice B might seem appealing since area annotations are also coordinate-based and data-independent, but an area annotation is designed to highlight a region, not a precise threshold line or point. Covering the entire area beyond the threshold is visually noisy and doesn't serve as a clean callout at the policy value itself. Your study tip: memorize that point annotations = fixed coordinates, mark annotations = tied to data, and area annotations = regions. Exam questions often test whether you know which type survives a data refresh intact.

Question 7

An operations dashboard highlights a delayed shipment. The explanation must be visible immediately when the dashboard opens, must move with that shipment's mark after sorting, and may disappear if the shipment is filtered from the view.

Which method most directly satisfies all three requirements?

  1. Place the explanation in the mark's tooltip, which is always rendered on the canvas and requires no user interaction to display.
  2. Attach a mark annotation directly to the delayed shipment's mark, which is persistently visible, follows the mark when sorting reorders it, and disappears when the mark is filtered out. (correct answer)
  3. Place a point annotation at the shipment's current screen location, which remains tied to the mark's position and follows it through sorting and filtering changes.
  4. Add the explanation as a worksheet caption beneath the view, which is immediately visible and repositions itself whenever the associated shipment mark moves.
Explanation: When a question asks about annotations in Tableau, focus on three properties: persistence (visible without interaction), positional binding (moves with the mark), and filter responsiveness (disappears when the mark leaves the view). Each annotation type behaves differently across these dimensions. A mark annotation attaches directly to a specific data mark. It renders on the canvas the moment the view loads — no hover or click required — and because it's bound to the mark's underlying data point, it repositions automatically when sorting reorders the marks. Critically, if a filter removes that shipment from the view, the annotation disappears along with it. This is precisely the behavior the scenario demands, making B the correct answer. Choice A is factually wrong about tooltips: they are not always rendered on the canvas. Tooltips only appear on hover, which violates the "immediately visible" requirement. Choice C describes a point annotation, which is placed at a fixed coordinate on the canvas rather than bound to a mark. Point annotations do not follow marks when sorting changes the layout — they stay anchored to their original screen position, so after resorting, the annotation would point at empty space or the wrong mark. Choice D is incorrect because worksheet captions are static text blocks positioned beneath the entire view. They have no awareness of individual marks and cannot reposition when a specific mark moves. A good study habit here is to memorize the three annotation types — mark, point, and area — and map each one to its binding behavior. Mark annotations bind to data; point and area annotations bind to coordinates. That distinction alone answers most annotation questions you'll encounter.

Question 8

A dual-axis view has a Sales mark and a Profit mark that currently overlap. The author wants a callout that stays associated with Profit if later filtering causes the two marks to separate.

What should the author do before creating the callout?

  1. Create an area annotation around both marks and name the area Profit.
  2. Right-click the overlapping location and create a point annotation at that coordinate.
  3. Select the Sales mark and type the word Profit into its mark annotation.
  4. Select the Profit mark and create a mark annotation from that selected mark. (correct answer)
Explanation: Tableau's three annotation types behave very differently when data changes, so identifying which annotation type "stays with" a specific data point is the key skill being tested here. A mark annotation attaches directly to a selected mark — meaning it travels with that mark if the view changes due to filtering, sorting, or axis rescaling. This is exactly what the scenario requires: a callout that remains associated with Profit even when the two marks separate. To create one correctly, you must first select the specific mark you want to annotate (the Profit mark), then right-click and choose Annotate → Mark. That's why D is correct — selecting the Profit mark before creating the annotation ensures the callout is bound to Profit's data point, not to a fixed location. A describes an area annotation, which anchors to a fixed rectangular region of the view, not to any particular mark. If the marks separate through filtering, the annotation stays in its original area, not with Profit. B is a point annotation, which pins to specific axis coordinates — again, a fixed location in the view rather than a dynamic mark. If Profit moves, the annotation won't follow. C is a trap: selecting the Sales mark and typing "Profit" into its annotation would create a mark annotation attached to the wrong mark. Labeling it "Profit" doesn't change which mark it's bound to. A handy rule: if you need an annotation that travels with data, always use a mark annotation and select the correct mark first — the selection determines ownership.

Question 9

A scatter plot contains a dense group of marks in the upper-right portion of the view. The author wants to label that region as an "emerging segment" without attaching the label to any one customer, because the individual customers may change after filtering.

Which annotation approach best supports the intended interpretation?

  1. Create a mark annotation on the customer nearest the center of the group.
  2. Create a point annotation on the highest customer within the group.
  3. Create an area annotation spanning the relevant upper-right region. (correct answer)
  4. Create separate mark annotations for every customer currently in the group.
Explanation: When working with annotations in Tableau, the key distinction is understanding that the three annotation types — mark, point, and area — serve fundamentally different purposes. Mark annotations attach to specific data points, point annotations anchor to a fixed coordinate in the view, and area annotations define a rectangular region independent of any individual mark. Choosing the right type depends on whether your message belongs to a data point, a coordinate, or a region. Here, the author wants to label a cluster of customers as an "emerging segment" without tying the label to any specific individual — precisely because filtering could change which customers appear. An area annotation is the right tool because it spans a defined region of the view and remains stable regardless of which marks come and go within it. That's answer C. Answer A fails because a mark annotation is bound to a specific customer record. If that customer is filtered out, the annotation disappears entirely — the opposite of what's needed. Answer B has the same core problem: a point annotation placed on a specific customer's coordinates sounds stable, but in practice it's still tied to a data-driven position that shifts with filtering, and it draws attention to one individual rather than the group. Answer D compounds the problem by multiplying mark annotations across every customer in the group — not only does this clutter the view, but it still collapses when those customers are filtered. A useful rule of thumb: if your annotation describes a region or concept rather than a specific data point, reach for an area annotation. It's the only type designed to exist independently of individual marks.

Question 10

A dashboard shows that customer cancellations increased during the same month a pricing change was introduced. The workbook contains no control group or analysis establishing that the pricing change caused the increase.

Which caption most appropriately guides interpretation without overstating the evidence?

  1. The pricing change caused cancellations to rise, confirming the expected customer response.
  2. Cancellations rose after the pricing change, proving the new prices reduced retention.
  3. The pricing change and higher cancellations occurred together; the view does not establish causation. (correct answer)
  4. Higher cancellations caused the pricing change, although the direction requires further validation.
Explanation: When a dashboard displays two events happening at the same time, you're being tested on one of data literacy's most critical distinctions: correlation vs. causation. Just because two things occur together doesn't mean one caused the other. A well-designed caption should accurately reflect what the data actually shows — nothing more, nothing less. Option C is the strongest choice because it honestly describes what the workbook contains: a temporal overlap between a pricing change and rising cancellations. The phrase "does not establish causation" is the key — it respects the boundary of the evidence without dismissing the relationship entirely. This is exactly how responsible data communication works. Option A fails because it uses the word "caused" and frames the result as a confirmation, neither of which the data supports. Asserting causation without a control group or analytical foundation is a significant misrepresentation of the evidence. Option B commits the same error — "proving" is an even stronger claim than the data warrants, and labeling something "proven" when it's only correlational is a classic analytical overreach. Option D introduces a reverse-causation narrative (cancellations caused the pricing change) that has no support in the passage whatsoever, making it not just unsupported but actively misleading in a different direction. A useful strategy: whenever you see captions with words like caused, proved, confirmed, or demonstrated, treat them as red flags. On the Tableau exam, questions about data communication frequently test whether you can identify language that overreaches the evidence. Always ask yourself — does the visualization actually establish this claim, or does it merely suggest it?