Tableau Quiz: Dashboard Filters And Actions

10 questions · exam conditions

0:00

Dashboard Filters And ActionsQuestion 1 of 10

A dashboard contains a source worksheet built from a customer data source and a target worksheet built from an orders data source. The source identifies geography with the field State Abbreviation, while the target contains both State Name and State Code. The abbreviations in the source have the same values and data type as State Code, but the field names differ.

Which filter-action configuration will most reliably filter the target to the states selected in the source?

Choose All Fields, because Tableau automatically matches fields that contain equivalent geographic values.

Choose Selected Fields and map State Abbreviation in the source to State Code in the target.

Choose Selected Fields and map State Abbreviation in the source to State Name in the target.

Choose All Fields and assign both worksheets the same geographic role for their state fields.

← Back to quizzes

Tableau Quiz

Tableau Quiz: Dashboard Filters And Actions

Practice Dashboard Filters And Actions 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 Dashboard Filters And Actions, 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

Which filter-action configuration will most reliably filter the target to the states selected in the source?

Choose All Fields, because Tableau automatically matches fields that contain equivalent geographic values.
Choose Selected Fields and map State Abbreviation in the source to State Code in the target. (correct answer)
Choose Selected Fields and map State Abbreviation in the source to State Name in the target.
Choose All Fields and assign both worksheets the same geographic role for their state fields.

Explanation: When a filter action connects worksheets from different data sources, Tableau cannot automatically detect relationships between fields — it needs you to tell it explicitly which field in the source maps to which field in the target. This is the core concept being tested here. Because the source field State Abbreviation shares the same values and data type as State Code in the target, the correct move is to use Selected Fields and create an explicit mapping between those two fields. Tableau will then pass the selected abbreviation values and match them against State Code — a reliable, exact match. That's why B is correct. A is tempting but wrong. The "All Fields" option works well when both worksheets share identically named fields. When field names differ across data sources — as they do here — Tableau has no reliable way to know that State Abbreviation corresponds to State Code rather than State Name, so automatic matching will fail or produce no filter effect at all. C uses the right mechanism (Selected Fields) but maps to the wrong target field. State Name likely contains full state names like "California," while State Abbreviation contains values like "CA." Mismatched value formats mean the filter will return no results, even though the mapping was explicitly defined. D combines the flawed "All Fields" approach with geographic roles, which control how Tableau visualizes geographic data — they don't resolve field-name mismatches in filter actions. Geographic roles and filter-action field matching are separate systems. As a study tip: whenever a filter action crosses data sources, your default instinct should be Selected Fields with explicit mapping — it's almost always more reliable than relying on Tableau to figure it out automatically.

Question 2

A dashboard filter action runs on Select from a regional map to a customer-detail worksheet. Under Clearing the selection will, the action is configured as Leave the filter. A user selects the West mark and then clicks a blank area of the map.

What should the user expect on the customer-detail worksheet?

The worksheet continues to show West customers even though the source mark is no longer selected. (correct answer)
The worksheet returns to all customers because clearing a selection always clears its action filter.
The worksheet becomes blank because no source mark remains available to supply filter values.
The worksheet continues showing West customers, but the filter changes automatically to a context filter.

Explanation: When you encounter a question about filter actions in Tableau, focus on the "Clearing the selection will" setting — it's the key to predicting worksheet behavior after a user deselects a mark. Tableau offers three options for this setting: Show All Values, Exclude All Values, and Leave the Filter. "Leave the Filter" means exactly what it says — when the selection is cleared, the filter stays frozen in its last active state. So when the user clicks a blank area of the map (clearing the West selection), the customer-detail worksheet doesn't react at all; it simply continues displaying West customers as if the selection were still active. That makes A correct. B is wrong because it describes the behavior of Show All Values, not "Leave the Filter." Clearing a selection does not always reset the filter — that assumption is the trap this distractor is setting. C describes the behavior of Exclude All Values, which would blank out the worksheet when no source mark is selected. That's a different configuration entirely and doesn't apply here. D is a fabricated scenario. Tableau does not automatically promote a filter action's filter into a context filter upon clearing a selection — that's a manual step a developer takes in the data pane, and it has nothing to do with the "Clearing the selection will" setting. Study tip: Memorize all three "Clearing the selection will" behaviors as a trio — Show All, Exclude All, Leave the Filter — and associate each with a concrete visual outcome. Exam questions often test whether you can distinguish between them in realistic user-interaction scenarios.

Question 3

A dashboard displays a summary worksheet and a detailed worksheet. When a user selects a product category in the summary, the detailed worksheet must retain every product mark for comparison, but products in the selected category should stand out while the others become visually de-emphasized.

Which dashboard action best satisfies the requirement without changing the detailed worksheet's population of marks?

Create a filter action that passes Product Category and uses Show all values when the selection is cleared.
Create a highlight action that matches Product Category between the source and target worksheets. (correct answer)
Create a set action that assigns the category to a set and hides all out-of-set products.
Create a parameter action that writes the category to a parameter used as a worksheet filter.

Explanation: When a dashboard requirement says marks must stay visible while some become visually emphasized, that's your signal to think about highlight actions versus actions that filter or alter data. The critical distinction is between changing which marks appear and changing how marks look. A highlight action — answer B — is precisely the right tool here. It colors the matching marks (products in the selected category) while leaving all other marks in place but visually dimmed. The detailed worksheet's full population of marks never changes; every product remains on the view, satisfying the comparison requirement exactly. The distractors each introduce a population change or the wrong mechanism. A is tempting because "Show all values" sounds like it preserves marks, but a filter action still removes non-matching marks during an active selection — "Show all values" only governs what happens after the selection is cleared, not during it. C uses a set action to define in-set versus out-of-set members, but then pairs it with hiding out-of-set products, which explicitly removes marks from the view — the opposite of what's required. D writes a value to a parameter that drives a worksheet filter, which again filters the mark population down to the selected category, eliminating the comparison context entirely. The pattern to remember: whenever a question says "all marks must remain visible" alongside "selected items should stand out," highlight actions are almost always the answer. Filter actions, set-based hiding, and parameter-driven filters all reduce the mark population. Highlight actions change appearance only — that's their defining advantage.

Question 4

A dashboard set action targets a set named Chosen Products. Running the action uses Assign values to set, and clearing the selection uses Keep set values. A user selects the Bikes and Chairs marks together and then clicks a blank area of the source worksheet.

What is the resulting membership of Chosen Products?

Bikes and Chairs remain in the set because the assigned membership is retained when the selection is cleared. (correct answer)
The set becomes empty because clearing the source selection removes all previously assigned members.
Every product enters the set because clearing a selection causes the action to select all source values.
Only the previously existing members remain because Assign values to set cannot replace set membership.

Explanation: When working with Tableau set actions, you need to track two separate behaviors: what happens when a selection is made and what happens when the selection is cleared. These are configured independently, and confusing them is exactly what this question tests. Here, the action is configured with Assign values to set on selection and Keep set values on clear. When the user selects Bikes and Chairs, those two members are assigned to Chosen Products — straightforward enough. The critical moment is when the user clicks a blank area, which triggers the "clearing" behavior. Because the clearing behavior is set to Keep set values, Tableau simply leaves the set membership exactly as it was last assigned. Bikes and Chairs remain in the set. Answer A is correct. Answer B describes what would happen if the clearing behavior were set to Remove all values from set, which empties the set entirely — that's a different configuration option, not this one. Answer C describes the behavior of Add all values to set, the option that floods the set with every available member when the selection clears — again, not configured here. Answer D mischaracterizes how Assign values to set works; it absolutely does replace existing membership when a selection is made, overwriting whatever was there before with the newly selected values. A useful study habit: when you see a set action question, mentally split it into two rows — "on selection" and "on clear" — and evaluate each independently. The exam frequently tests whether you conflate the two behaviors, so treating them as distinct configurations will save you from traps like B and C.

Question 5

A dashboard action is configured to run on Menu rather than Select or Hover. The action's source worksheet displays marks with tooltips enabled.

What interaction is required to run the action?

The user must hover over a mark long enough for Tableau to run the action automatically.
The user must select a mark, after which Tableau runs the action immediately without another command.
The user must open the mark's tooltip or context menu and explicitly choose the named action. (correct answer)
The user must use the worksheet's filter menu and choose the action from the list of field values.

Explanation: When you see a question about dashboard actions in Tableau, anchor your thinking around the three trigger modes: Select, Hover, and Menu. Each mode defines the exact user gesture required to fire the action, and confusing them is one of the most common mistakes on this exam. The Menu trigger is the most deliberate of the three. When an action is set to Menu, nothing happens automatically — the user must first click a mark to open its tooltip, then explicitly click the named action link that appears within that tooltip (or right-click to access the context menu). The action only runs when the user consciously chooses it by name. That matches C perfectly: the user opens the tooltip and explicitly selects the action. A describes behavior closer to the Hover trigger, where Tableau runs the action automatically after the cursor lingers over a mark — no click required. The key word "automatically" gives this away as wrong for Menu mode. B describes the Select trigger, where clicking a mark is sufficient to fire the action immediately, with no additional step. Menu mode always requires that second, deliberate interaction inside the tooltip. D is a fabrication — there is no mechanism in Tableau where actions are chosen from a field's filter menu. This distractor may sound plausible if you're conflating dashboard actions with filter controls, but they are entirely separate features. A handy memory anchor: Menu = most manual. If you rank the triggers by how much the user must do — Hover (least), Select (middle), Menu (most) — the order matches the letters M-S-H reversed, but "Menu demands more" captures the key idea for exam day.

Question 6

A source worksheet contains marks at the combination of Customer Segment and Region. A filter action targets another worksheet, but under Selected Fields it maps only Customer Segment. The user simultaneously selects the Consumer-West mark and the Corporate-East mark.

Assuming the action is not configured to exclude selections, which records can remain in the target?

Only Consumer-West and Corporate-East records, because Tableau preserves each selected mark's complete dimensional combination.
Consumer and Corporate records from any region, because only Customer Segment is transferred by the action. (correct answer)
Only records belonging to both Consumer and Corporate, because multiple selected values are combined with an AND condition.
All records from West and East, because Region remains part of the source marks even though it is not mapped.

Explanation: When a filter action uses Selected Fields mapping, Tableau doesn't pass the entire mark's dimensional fingerprint to the target — it passes only the values from the fields you explicitly map. This distinction is the heart of what this question is testing. Here, the action maps only Customer Segment. So when you select the Consumer-West mark and the Corporate-East mark, Tableau extracts just the Customer Segment values: Consumer and Corporate. Those two values are sent to the target as an OR filter (multiple selected values within a single field are always unioned, not intersected). The target therefore shows all records where Customer Segment is Consumer or Corporate, regardless of region. That makes B the correct answer. A is wrong because it assumes Tableau preserves the full dimensional combination of each mark. Selected Fields mapping deliberately breaks that pairing — Region is simply not transmitted, so the Consumer-West and Corporate-East pairings are lost the moment the filter is applied. C confuses how multiple values within a single field are combined. An AND condition between Consumer and Corporate would require a record to belong to both segments simultaneously, which is impossible. Multiple values in a single-field filter always use OR logic in Tableau. D is wrong because Region is never mapped by the action. The fact that Region exists on the source marks is irrelevant — unmapped fields are silently ignored and contribute nothing to the target filter. As a study rule: whenever you see a filter action question involving Selected Fields, ask yourself which fields are actually mapped — only those fields travel to the target, and multi-value selections within one field always use OR.

Question 7

A dashboard contains Sales and Profit worksheets. Filter cards for Region and City originate from the Sales worksheet. Region is applied to both worksheets, but City is applied only to Sales. The City card is configured to show Only Relevant Values. A user selects West in Region and then Seattle in City.

Which result is expected?

Both worksheets show only Seattle because relevant-value settings automatically extend the City filter to all Region targets.
Sales shows Seattle, while Profit shows the entire West region; the City list is limited to cities relevant to West. (correct answer)
Sales shows Seattle, while Profit remains unfiltered; the City setting prevents Region from affecting other worksheets.
Both worksheets show the West region, while Seattle affects only which values appear on the City filter card.

Explanation: When working with dashboard filters in Tableau, you need to track two separate things simultaneously: which worksheets a filter applies to, and how filter cards display their values. Conflating these two concepts is exactly what the wrong answers exploit. Here's the logic: Region is applied to both worksheets, so selecting West correctly narrows both Sales and Profit to the West region. City, however, is scoped only to the Sales worksheet — meaning it controls what Sales displays, but Profit has no awareness of it. When you select Seattle in City, Sales filters down to Seattle, while Profit continues showing all of West (its last known filter state from Region). Meanwhile, "Only Relevant Values" is purely a display setting for the filter card itself — it limits which cities appear in the dropdown to those matching the current Region selection. This is answer B, and it's correct. Answer A is wrong because "Only Relevant Values" does not extend the City filter's scope to additional worksheets. It only controls what appears in the filter card list, not where the filter is applied. Answer C incorrectly suggests that Profit remains completely unfiltered — but Region is applied to Profit, so Profit still shows West. The City setting has no power to block Region from functioning on its targeted sheets. Answer D gets things backwards: Seattle does affect what Sales displays, not merely what appears in the filter card. A useful rule of thumb: treat filter scope (which sheets are affected) and filter card display settings (how values appear in the UI) as completely independent. Questions on the Tableau exam frequently blur these two to test whether you can keep them straight.

Question 8

A dashboard filter action passes Region from a map to an order-details worksheet. The action has Exclude selected and is configured to Show all values when the source selection is cleared. A user selects East and later clears the selection.

Which sequence of target states should occur?

The target first shows only East orders and then returns to orders from every region.
The target first shows only East orders and then becomes blank after the selection is cleared.
The target first hides East orders and then remains filtered to all regions except East.
The target first hides East orders and then returns to orders from every region. (correct answer)

Explanation: When working with Tableau filter actions, two settings control the behavior: the filter mode (Include vs. Exclude) and the clearing behavior (Show all values, Keep filtered values, or Exclude all values). These two settings operate independently, and questions like this one test whether you understand both simultaneously. Here, the action uses Exclude mode, which means the selected value is removed from the target — the opposite of the default Include behavior. So when the user selects East, the target worksheet shows every region except East. That rules out answers A and B immediately, since both describe the target showing East orders first, which would only happen with Include mode. When the selection is cleared, the Show all values setting kicks in, resetting the target to its unfiltered state — meaning all regions reappear. This confirms D as correct: the target first hides East orders (Exclude), then returns to all regions when cleared (Show all values). Answer C is the sneaky distractor. It correctly identifies that East orders are hidden first, but claims the filter persists after clearing — that would describe the Keep filtered values clearing behavior, not Show all values. Don't confuse these two clearing options. A and B both assume Include mode is active, just disagreeing on what clearing does. A correctly maps "Show all values" to returning all data but applies it to the wrong initial filter mode. B imagines the target goes blank, which corresponds to "Exclude all values" clearing behavior. Study tip: Memorize the three clearing behaviors and practice pairing them with both Include and Exclude modes — Tableau exam questions frequently test one setting while disguising the other.

Question 9

A dashboard has separate Region Summary and Category Summary worksheets, both targeting an Order Details worksheet through filter actions. Each action is configured to run on Select and to Leave the filter when its source selection is cleared. A user first selects West in Region Summary and then selects Furniture in Category Summary.

Assuming the two action filters remain active, which orders appear in Order Details?

All West orders, because the first action filter takes precedence over filters triggered later.
All Furniture orders, because the second action replaces the target's existing action filter.
Orders that are either from West or in Furniture, because separate dashboard actions combine with OR logic.
Orders that are both from West and in Furniture, because active filters on different fields intersect. (correct answer)

Explanation: When multiple dashboard filter actions target the same worksheet, think of each action as writing to its own dedicated filter slot — one per source sheet. Tableau doesn't merge or replace those filters; it keeps them independent and applies them simultaneously. The result set shown in the target sheet must satisfy all active filters at once, which means the conditions intersect (AND logic, not OR). In this scenario, selecting West in Region Summary creates a Region filter on Order Details, and selecting Furniture in Category Summary creates a separate Category filter. Because both selections remain active ("Leave the filter" keeps each filter alive after selection), Order Details must satisfy both conditions together — showing only orders that are from West and in the Furniture category. D is correct. A is wrong because Tableau doesn't assign priority based on the order in which actions are triggered. Both filters coexist simultaneously with equal standing. B is wrong because the second action targets a different field (Category) than the first (Region); it has no reason to overwrite the Region filter. Actions only interfere with each other when they share the same source field. C is wrong because independent filters on different fields combine with AND logic, not OR. OR logic would mean a West order with no Furniture items would still appear — that's not how Tableau's filter stack works. A helpful mental model: picture each action filter as a separate WHERE clause in a SQL query. Two active WHERE clauses on different columns always intersect the data, not union it. When studying filter actions, always ask yourself how many distinct fields are being filtered and whether any actions share a source field.

Question 10

A dashboard has a numeric parameter named Selected Sales Total. A parameter action uses Sales as its source field and SUM as its aggregation. The source view permits users to select multiple marks. A user selects three marks representing different subcategories.

How will Tableau determine the value written to the parameter?

It writes the Sales value from the first selected mark, because a parameter stores only one scalar value and Tableau resolves the ambiguity by using mark selection order.
It writes the Sales value from the last selected mark, because each successive mark selection overwrites the parameter before the action finalizes.
It writes the sum of Sales across the selected marks as one aggregated scalar value, because the configured SUM aggregation is applied to the entire selection before writing. (correct answer)
It leaves the parameter unchanged, because parameter actions cannot process a selection that contains more than one mark.

Explanation: When you encounter a question about parameter actions, the key concept to anchor on is this: a parameter always holds a single scalar value — but that doesn't mean Tableau ignores multi-mark selections. It means Tableau must resolve multiple values into one before writing. Here's how it works: when a parameter action is configured with an aggregation (like SUM, AVG, MIN, etc.), Tableau applies that aggregation across all selected marks first, then writes the resulting single value to the parameter. So if a user selects three marks with Sales values of 1,000, 2,500, and 500, Tableau computes

1000 + 2500 + 500 = 4000

and writes 4,000 to the parameter. That's exactly what C describes — the aggregation collapses the selection into one scalar, satisfying the parameter's single-value requirement. A is wrong because Tableau does not use selection order to resolve ambiguity. There's no "first mark wins" logic in parameter actions. B is similarly wrong — parameter actions don't finalize sequentially per mark; the entire selection is evaluated together. D reflects a common misconception that multi-mark selections simply break parameter actions. They don't — the configured aggregation exists precisely to handle this scenario. The study tip here is to remember that the aggregation setting on a parameter action isn't decorative. It's the mechanism that makes multi-mark selections valid. On the exam, if you see a question where a parameter action has a configured aggregation and multiple marks are selected, trust that the aggregation will fire across the full selection and produce one clean scalar output.