Tableau Quiz: Stories
10 questions · exam conditions
0:00
StoriesQuestion 1 of 10

An analyst creates the first story point from a Sales dashboard filtered to West, with Technology selected and sales sorted descending. The second point should begin with exactly that state, after which the analyst will change only the region to East.

Which authoring approach most directly creates the required second story point while preserving the first point?

Create a blank story point, add the dashboard again, and manually reproduce the original filter and sort settings.
Duplicate the first story point, change its Region filter to East, and update the duplicated story point.
Change the first story point to East, update it, and then duplicate the updated story point.
Duplicate the first story point, change its Region filter to East, and update the original story point instead.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Stories

Practice Stories 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 Stories, 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

An analyst creates the first story point from a Sales dashboard filtered to West, with Technology selected and sales sorted descending. The second point should begin with exactly that state, after which the analyst will change only the region to East.

Which authoring approach most directly creates the required second story point while preserving the first point?

  1. Create a blank story point, add the dashboard again, and manually reproduce the original filter and sort settings.
  2. Duplicate the first story point, change its Region filter to East, and update the duplicated story point. (correct answer)
  3. Change the first story point to East, update it, and then duplicate the updated story point.
  4. Duplicate the first story point, change its Region filter to East, and update the original story point instead.
Explanation: When working with Tableau stories, understanding how story points preserve versus share state is essential. Each story point captures a snapshot of a sheet or dashboard at a specific moment — duplicating a story point creates an independent copy of that captured state, meaning changes to one copy don't affect the other. The scenario requires two story points: the first showing West/Technology/descending, and the second starting from that exact same state but with Region changed to East. The most direct path is to duplicate the first story point, which instantly gives you a second point with all the same settings intact. You then change only the Region filter to East on the duplicated point and click Update to save that new state. This is exactly what B describes — it preserves the original first point untouched while efficiently building the second. A is inefficient and error-prone. Manually recreating the filter, category selection, and sort order from a blank story point wastes time and risks mismatching the original configuration. C is the most dangerous trap: if you change the first story point to East and update it, you've overwritten the original West state — now you'd need to rebuild Point 1 from scratch, which is the opposite of "preserving the first point." D sounds similar to B but has a critical error: it says to update the original story point after changing the duplicate to East, which would push the East changes back onto Point 1, again corrupting it. A good rule of thumb: when you need a new story point that starts from an existing state, always duplicate first, then modify — never modify the source and update before duplicating.

Question 2

Four story points reference the same dashboard but preserve different Region filter states. The author later edits the source dashboard by adding a KPI worksheet and changing the dashboard layout.

What is the expected effect on the existing story points?

  1. Only the most recently created point receives the changes because earlier points are stored as static dashboard copies.
  2. All points referencing the dashboard reflect its revised design while retaining their saved point-specific states where applicable. (correct answer)
  3. No existing point changes until each point is deleted and recreated from the revised source dashboard.
  4. Each point receives a separate dashboard copy, but all saved Region states are reset to the dashboard default.
Explanation: When you see a question about Tableau stories, the key concept to keep in mind is how story points reference dashboards rather than store independent copies of them. A story point is essentially a bookmark — it captures a specific interactive state (like a filter selection) but points back to the live source dashboard for its layout and content. This means when the author adds a KPI worksheet and updates the layout of the source dashboard, every story point that references that dashboard automatically reflects those structural changes. At the same time, each point's saved state — in this case, the Region filter selections — is preserved independently, because those states are stored at the point level, not the dashboard level. That's exactly what answer B describes, making it correct. Answer A is wrong because story points are not static snapshots of a dashboard; they are live references. Only the most recently created point receiving changes is a fabricated behavior with no basis in how Tableau stories actually work. Answer C is wrong because it implies story points are completely decoupled from their source until manually rebuilt — the opposite of how referencing works. You never need to delete and recreate points to receive dashboard edits. Answer D is wrong on two counts: story points do not each hold a separate dashboard copy, and saved filter states are not wiped when the source dashboard changes — they persist unless you explicitly reset them. A useful rule of thumb: think of a story point as a filter memory on top of a shared dashboard. Layout lives in the dashboard; state lives in the point. Changes to either layer stay in their own lane.

Question 3

A story contains points titled Overview, Customer Risk, and Recommended Action. The author wants Recommended Action to appear second but must preserve the saved filters and annotations associated with all three points.

Which action should the author take?

  1. Drag the Recommended Action story point to the second position in the story navigator. (correct answer)
  2. Rename Customer Risk to Recommended Action and rename the final point Customer Risk.
  3. Duplicate Recommended Action in the second position and delete both original remaining points.
  4. Sort the story-point captions alphabetically and then update each point's source worksheet.
Explanation: When working with Tableau stories, it's important to understand that story points are more than just titles — each one carries its own saved state, including filters, annotations, and layout settings. Questions like this test whether you know how to reorganize story points without accidentally destroying that embedded data. Dragging a story point to a new position in the story navigator (answer A) is exactly the right move here. Tableau allows you to reorder story points by simply clicking and dragging them along the navigator strip. This repositions the point visually while keeping all of its saved filters and annotations completely intact. The content travels with the tile, not with the position. Answer B is a naming trick that doesn't actually move anything. Swapping captions between points creates the illusion of reordering, but the saved states remain tied to their original positions — you'd end up with the wrong data behind each label, which defeats the purpose entirely. Answer C involves duplicating a story point, which does carry over the content, but deleting the two "original remaining points" means you lose the saved filters and annotations for both Overview and Customer Risk permanently. The question explicitly requires preserving all three points' data. Answer D is a fabrication. Tableau has no native feature to sort story point captions alphabetically, and manually relinking each point to a different source worksheet would strip out the saved states you're trying to protect. The key study tip here: on Tableau exam questions about stories, any action that deletes, renames, or rebuilds a story point risks losing its saved state. Dragging to reorder is always the safest, non-destructive option.

Question 4

A story will be presented on a fixed-resolution display. Its first point contains a dashboard designed for a wide layout, while a later point contains a worksheet that was previously viewed in a smaller window. The author wants every point to occupy a consistent presentation area.

Which approach is most appropriate?

  1. Assign a different story size to each point so every source view retains its original dimensions.
  2. Duplicate the widest point because duplicated points automatically resize all other source views.
  3. Resize each story-point caption because caption dimensions control the displayed view dimensions.
  4. Set a single story size for the presentation and configure the contained views to fit that common area. (correct answer)
Explanation: When working with Tableau stories, the key concept to understand is that a story has one size setting that applies to the entire presentation — not individual sizes per point. This size determines the canvas area where each story point's content is displayed, and all views within the story should be designed or configured to fit that shared space. The correct approach, D, reflects exactly this: you set a single story size for the whole presentation, then adjust each contained view (dashboard or worksheet) to fit that common area. This ensures visual consistency across every point, regardless of what size the source view was originally built or viewed in. Tableau gives you options like "Fit Width," "Fit Height," or "Entire View" to help views adapt to the story's canvas. Choice A is tempting but wrong — Tableau stories do not support per-point sizing. There is only one size setting for the entire story, so trying to assign different sizes to individual points isn't possible. Choice B describes a feature that doesn't exist; duplicating a story point copies its content and layout but has no effect on resizing other points' source views. Choice C confuses caption text boxes with layout control — captions are simply title labels beneath a story point navigator button, and they have no influence over how the view itself is rendered or sized. A useful tip: on the Tableau exam, whenever you see a question about story formatting or consistency, remember that stories operate with a single shared canvas size. Any question suggesting per-point sizing or automatic resizing through duplication is describing behavior that doesn't exist in Tableau.

Question 5

A story point must display a sales map and a profit trend together. A single Region filter must control both views, and later story points must preserve different Region selections.

Which design best satisfies these requirements?

  1. Place both worksheets independently in one story point and configure the story navigator to synchronize their Region filters.
  2. Create one story point for the map and another for the trend, then give both points the same caption.
  3. Combine the views in a dashboard, apply the Region filter to both worksheets, and use that dashboard in each story point. (correct answer)
  4. Add the map to the story, duplicate the point, and replace the duplicated map with the profit trend.
Explanation: When building Tableau stories, you need to think in layers: what goes inside a story point versus what the story point itself contains. A story is a sequence of points, each of which can hold either a single worksheet or a dashboard. The key constraint here is that filters must control multiple views simultaneously and each story point must independently preserve its own Region selection. Dashboards are the natural home for coordinated views. When you place both the sales map and the profit trend inside a single dashboard and apply the Region filter to both sheets, that filter controls both views as one unit. You then add that dashboard as a story point, and each story point maintains its own snapshot of filter state. This is exactly what option C describes, making it the correct design. Option A fails because story points do not have a built-in navigator mechanism that synchronizes filters across independent worksheets placed side by side — that synchronization is a dashboard feature, not a story feature. Option B is a red herring: giving two story points the same caption is purely cosmetic and does nothing to link their filters or display both views together within a single point. Option D describes duplicating a story point and swapping one worksheet for another, which means the two views exist on separate story points rather than together, breaking the requirement that both appear simultaneously. The study tip to remember: whenever a question asks you to coordinate filters across multiple views, that's your signal to reach for a dashboard, not a story-level workaround. Dashboards filter; stories sequence.

Question 6

During a presentation, a user explores a story point by changing several filters and selecting marks. The author did not update the point and now wants to return that point to the state previously saved in the story.

What should the author do?

  1. Select Revert to discard the unsaved interactions and restore the story point's saved state. (correct answer)
  2. Select Update to reload the saved state while retaining the temporary filter selections.
  3. Select Duplicate to restore the original state and remove the temporary interactions.
  4. Select Blank to reload the source view using the story point's saved settings.
Explanation: When working with Tableau Stories, it helps to understand the lifecycle of a story point. A story point captures a "snapshot" of a view — including filters, marks, and selections — at the moment it was saved. During a presentation, viewers (or authors) can interact with a story point by changing filters or selecting marks, but those interactions are temporary and exist only in memory until the point is explicitly updated. When an author wants to discard those temporary interactions and return to the last saved snapshot, Revert is the correct tool. Selecting Revert tells Tableau to throw away any unsaved changes and restore the story point exactly as it was when it was last saved — making A the correct answer. B is a trap because Update does the opposite: it saves the current interactive state as the new snapshot, permanently overwriting the previous saved version. Using Update would make the temporary changes permanent, which is exactly what the author wants to avoid. C is wrong because Duplicate creates a copy of the story point in its current (modified) state. It doesn't restore anything — it just gives you a new point based on whatever the view looks like right now, temporary changes included. D is wrong because Blank adds an entirely new, empty story point to the story. It has nothing to do with restoring or reloading an existing point's saved state. A helpful memory anchor: think of Revert and Update as opposites — Update commits changes, Revert cancels them. On exam questions involving story point management, always ask whether the goal is to save the current state or discard it.

Question 7

A story currently contains three approved story points. While viewing the second point, an author changes a date filter and wants to preserve the original second point while adding the revised view immediately after it.

Which command should the author use after changing the filter?

  1. Use Update so the revised state replaces the saved state of the second story point.
  2. Use Revert so the revised state becomes a copy of the second story point.
  3. Use Save as New so the revised state is stored as an additional story point. (correct answer)
  4. Use Blank so the current view state is appended without replacing the second story point.
Explanation: When working with Tableau Stories, you need to understand how the three story point commands interact with existing content. The key distinction is between replacing a story point's saved state versus creating a new one alongside it. In this scenario, the author wants to preserve the original second point while also keeping the modified view — meaning two separate story points should exist after the operation. That's exactly what Save as New does: it captures the current view state (with the changed date filter) and inserts it as a brand-new story point, leaving the original second point completely untouched. C is your answer. A describes the Update command, which overwrites the currently selected story point with the new view state. If the author used Update, the original second point would be permanently replaced — the opposite of what was asked. B misrepresents Revert, which doesn't create a copy at all. Revert discards any unsaved changes and restores the story point back to its last saved state. It's an undo-style command, not a duplication tool. D introduces Blank, which creates an entirely empty story point rather than capturing the current filtered view. It wouldn't carry over any of the modified state the author wants to save, making it useless here. A helpful way to remember this: think of story point commands in terms of their direction. Revert goes backward (undo), Update goes sideways (replace), and Save as New goes forward (add). Whenever a question asks you to preserve and extend, Save as New is almost always the right move.

Question 8

An author tries to drag a second worksheet beside the first worksheet in an existing story point. The goal is to present both worksheets simultaneously and preserve their shared interactive state.

What should the author do instead?

  1. Place the worksheets in a dashboard and use the dashboard as the content of the story point. (correct answer)
  2. Duplicate the story point and arrange the two point captions beside one another in the navigator.
  3. Add the second worksheet as a story caption and enable worksheet interaction for the caption.
  4. Create two consecutive story points and configure the navigator to render both points simultaneously.
Explanation: When working with Tableau stories, it's important to understand what a story point can actually contain. A story point holds a single piece of content — one worksheet, one dashboard, or one text box. You cannot arrange multiple standalone worksheets side by side within a single story point the way you might arrange objects on a dashboard. This is exactly why A is the correct approach. When you need to display two worksheets simultaneously and maintain their shared interactive state (like filters or highlights that affect both), the right move is to combine them into a dashboard first. Dashboards are designed precisely for this — they let you place multiple worksheets in a shared layout and wire them together through actions or shared data sources. You then use that dashboard as the story point's content, giving you both the multi-sheet display and the interactivity you need. B is wrong because duplicating story points creates two separate sequential slides — the viewer sees one, then navigates to the other. That breaks the "simultaneous" requirement entirely. C is a fabricated feature; story captions are text overlays for annotation purposes and have no "worksheet interaction" toggle that would render a second sheet. D is similarly fictional — the story navigator is designed to move between points one at a time, and there is no configuration option to render multiple points at once. A helpful rule of thumb: whenever a story-related question mentions showing multiple worksheets together or preserving shared interactivity, think dashboard first, then story point. Dashboards are the composition layer; stories are the presentation layer.

Question 9

A five-point story must guide an audience through a fixed sequence. The author does not want viewers to jump directly to a named point by selecting its caption, but viewers must still be able to move forward and backward.

Which navigator configuration best supports this presentation?

  1. Use caption boxes so viewers can select any point by its descriptive label.
  2. Use numbered tabs so viewers can select any point by its assigned number.
  3. Use dots so viewers can jump among points without seeing descriptive labels.
  4. Use arrows only so navigation is restricted to moving sequentially between adjacent points. (correct answer)
Explanation: When a question asks about navigator configuration in Tableau, focus on two things: what the navigator displays (labels, numbers, or dots) and what it allows (free jumping vs. sequential movement). The passage gives you two constraints: no direct jumping to named points, and movement must be forward/backward only. Arrows-only navigation directly satisfies both requirements. Arrows restrict movement to adjacent points — one step forward or one step back — preventing viewers from skipping ahead. There are no labels or numbers displayed, so no point can be selected by name or number. This makes D the answer that matches the scenario precisely. A fails because caption boxes display descriptive labels, which is exactly what the author wants to avoid. A viewer could read "Point 3: Climax" and jump there directly, breaking the intended sequence. B has the same core problem — numbered tabs still allow direct access to any specific point; a viewer can simply click "4" to skip ahead. The only difference from A is that numbers replace labels, but the freedom to jump remains. C might seem appealing since dots don't show descriptive labels, but dots still let viewers click any dot to jump to a non-adjacent point. It prevents label-based jumping but not arbitrary jumping, so it only solves half the problem. A useful pattern to remember: on navigator questions, ask yourself two questions — what does the viewer see, and what can the viewer do? The correct configuration must satisfy both constraints, not just one. Arrows are the only option that controls both display and movement simultaneously.

Question 10

A workbook contains a worksheet named Legacy Detail. That worksheet is referenced by one story point and also exists as a normal worksheet tab. The author deletes only the story point because it is no longer part of the narrative.

What happens to Legacy Detail?

  1. The worksheet is deleted because its story point was the workbook's active reference to the view.
  2. The worksheet remains in the workbook because deleting a story point does not delete its source sheet. (correct answer)
  3. The worksheet becomes a dashboard because Tableau preserves deleted story content as a new container.
  4. The worksheet remains only as a hidden story asset and can no longer be opened from its tab.
Explanation: Whenever you see a question about deleting story points in Tableau, the key distinction to keep in mind is the difference between a story point and the source sheet it references. A story point is essentially a snapshot or a pointer — it displays an existing worksheet or dashboard inside the story, but it does not own that content. This means that when you delete a story point, you are removing the narrative frame around the view, not the view itself. Legacy Detail was already living as a standalone worksheet tab before it was ever added to the story. Deleting the story point simply removes that reference; the underlying worksheet continues to exist and remains fully accessible from its tab. Answer B correctly captures this behavior. A is wrong because Tableau does not use a "last active reference" rule for worksheets. Sheets persist in the workbook independently of whether any story or dashboard currently references them. C describes behavior that simply does not exist — Tableau has no mechanism that converts deleted story content into a dashboard automatically. D is wrong because worksheets referenced by story points are never hidden or locked to the story; they remain normal, fully accessible tabs throughout. A useful rule of thumb: in Tableau, deletion of a container never cascades to the source content. Deleting a story point, a dashboard, or a layout container removes the organizational wrapper, not the underlying sheets. When studying workbook management, always ask yourself whether an action targets the container or the content — the exam frequently tests that boundary.