- Assuming no other filters affect the calculation, how is Product X classified?
Answer: In, because the condition first limits eligible products and X is then within the top 5.
When working with dynamic sets in Tableau that combine a condition and a top N limit, the order of operations matters enormously. The condition acts as a filter first, narrowing the candidate pool, and then the top N ranking is applied only to the survivors of that condition — not to the full original list.
Here's how that plays out for Product X. The set starts with all products, then discards any product where SUM(Sales)<50,000. Two products that outrank X in profit are eliminated at this stage. Among the remaining eligible products, X sits fourth in profit — comfortably inside the top 5 cutoff. That makes C the correct answer: the condition gates who can compete for the top spots, and X clears both hurdles.
Answer A is wrong because Tableau absolutely supports combining a condition and a top N filter within a single dynamic set — that's a core feature of how sets are configured. Answer B reflects a common misconception: ranking sixth before the condition is applied is irrelevant once ineligible products are removed. The final ranking is determined after filtering, not before. Answer D invents a rule that doesn't exist; satisfying the sales condition doesn't waive the profit ranking requirement — both criteria must be met, in sequence.
A useful mental model: think of the condition as the qualifying round and the top N as the final round. Only qualifiers compete in the final. On Tableau exam questions involving dynamic sets, always ask yourself which step happens first and what the eligible pool looks like before the ranking is applied. - What should the analyst do to make the segment update according to the threshold?
Answer: Edit the set to use a condition based on the required aggregated profit-ratio calculation.
When working with Tableau sets, the critical distinction to understand is between fixed membership and condition-based membership. A set created by manually selecting marks captures a static snapshot — those exact members are locked in regardless of what happens to the underlying data. This question tests whether you understand how to make a set behave dynamically.
The correct approach is D: editing the set to use a condition based on an aggregated profit-ratio calculation. A condition-based set re-evaluates its membership criteria every time the data refreshes, so customers automatically enter or exit the set depending on whether they currently meet the threshold. This is exactly the dynamic behavior the analyst needs.
A is a distractor that misunderstands the problem — sorting by profit ratio does nothing to change set membership logic. Sorting is a display operation, not a segmentation rule.
B introduces context filters, which control query order and performance but have no bearing on whether set membership is fixed or dynamic. Adding a fixed set to context before a refresh still doesn't make that set recalculate its members.
C confuses sets with groups. Groups are purely static label-based clusters used to combine dimension members manually — they have no conditional logic and cannot automatically update based on a measure like profit ratio. Aliases are display names, not recalculation triggers.
A useful rule of thumb: if you ever need a segment that reacts to data changes, reach for a condition-based or formula-based set, not a selected-member set. The phrase "does not change after refresh" is a strong signal that you need to swap static selection for dynamic condition logic.
- Which set construction should the analyst use?
Answer: Combine the sets using shared members, producing their intersection.
When working with combined sets in Tableau, the key question to ask is: what relationship between the two sets defines my target segment? Here, the analyst wants customers who are both top revenue earners and profitable — meaning a customer must appear in both sets simultaneously to qualify. This is the textbook definition of a set intersection.
Combining [Top Revenue Customers] and [Profitable Customers] using shared members returns only the customers present in both sets — exactly the segment described. That makes B the correct choice.
A is wrong because a union returns every customer who satisfies either condition — top 20 by revenue or profitable. This inflates the segment by including high-revenue customers who lose money and profitable customers outside the top 20, which is the opposite of what the analyst needs.
C describes a set difference, which would return top revenue customers who are not profitable — essentially filtering out the very people the analyst wants to keep. This inverts the logic entirely.
D is a distractor that sounds similar to a union but frames it in terms of "groups" rather than sets. Tableau's native Combine Sets feature operates on sets specifically, and the word "every customer represented by either group" still describes a union — making this doubly wrong.
A helpful memory trick: think of set operations like a Venn diagram. Union = everything in both circles. Intersection = only the overlapping middle. Whenever a question uses language like "satisfies both" or "must meet all conditions," that's your signal to reach for the intersection. - Which running-action behavior should be configured?
Answer: Assign values to the set so each selection replaces the previous membership.
When working with Tableau set actions, the key concept to understand is how the running-action behavior controls what happens to set membership each time a user makes a new selection. Think of it as choosing a replacement strategy versus an accumulation strategy.
The business requirement here is precise: the set must contain exactly the currently selected marks, with no carryover from previous selections. This points directly to the Assign behavior (D). Assign replaces the entire set membership with whatever is currently selected — a clean swap every time. It's the only behavior that guarantees the set mirrors the active selection, nothing more and nothing less.
A is wrong because Keep freezes the set membership; it ignores the new selection entirely and preserves whatever was there before. This is the opposite of what the business wants — they explicitly need the set to update with each selection.
B is wrong because Add accumulates values over time. Each new selection appends to the existing membership, so old selections linger unless manually cleared. The business requirement states that previous values must not remain, ruling this out completely.
C is wrong because Remove does the opposite of adding — it excludes selected marks from the set. So clicking on an account would kick it out of [Focus Accounts], which contradicts the intent of building a focused selection from the clicked marks.
As a study tip, remember this shorthand: Assign = replace, Add = accumulate, Keep = freeze, Remove = exclude. On the Tableau exam, whenever a question mentions "exactly" or "replaces previous," that's your signal to choose Assign (D).
- How will Customer A's January mark normally be classified?
Answer: In, because membership is evaluated from Customer A's qualifying total, not separately for each month mark.
When working with Tableau sets, the most important concept to keep in mind is when membership is evaluated. A condition-based set asks a single question — does this member meet the condition? — and that question is answered using the member's total aggregated data, not the data visible in any particular view.
Customer A has annual sales of $120,000, which exceeds the $100,000 threshold. That evaluation happens once, at the member level. When you drag Month to the view, Tableau disaggregates the display, but it does not re-evaluate set membership for each row. Customer A is already marked In, and that classification travels with every mark belonging to Customer A — including January's $4,000 mark. That's why C is correct.
Choice A is wrong because adding a dimension to the view never converts a condition-based set into a dimension-specific one. The set definition doesn't change just because your view does. Choice B reflects a very common misconception: it assumes Tableau re-tests the threshold against the filtered, disaggregated value ($4,000). That would only be true if you had defined a row-level calculated field, not a set. Choice D is wrong because set membership has nothing to do with whether the set is on the Filters shelf — a customer's In/Out status is determined entirely by whether they satisfy the set's condition.
As a study tip, always ask yourself: at what grain was the set defined? If it was defined on Customer, membership is fixed at the Customer grain regardless of what else you add to the view. - Which change most directly produces the expected dynamic segmentation?
Answer: Add [Region] to context so the top set is evaluated from the region-filtered data.
Whenever you see a question about dynamic sets and filters in Tableau, the key concept to understand is filter evaluation order. Tableau processes filters in a specific sequence: context filters → dimension filters → measure filters. A dynamic set (like "Top 10 by SUM(Sales)") is evaluated against whatever data exists after context filters have been applied, but before standard dimension filters.
This is precisely why A is correct. When [Region] sits on the Filters shelf as a standard dimension filter, the Top 10 customer set is computed first — across all regions — and then the region filter narrows the view afterward. The set never "sees" the region restriction. By adding [Region] to context, you promote it to run before the set is evaluated, so the set calculation draws only from region-filtered data. The result is exactly what users expect: the top 10 customers within the selected region.
Option B describes converting to a fixed set, which permanently locks in specific customer names rather than dynamically recalculating — this defeats the purpose of a dynamic set entirely and requires manual intervention each time. Option C has the logic backwards: placing the customer set on Filters before [Region] doesn't change Tableau's evaluation order, because filter shelf position doesn't override the built-in processing hierarchy. Option D replaces the dimension filter with a measure filter, but measure filters evaluate even later in Tableau's order than dimension filters — this would make the segmentation problem worse, not better.
A helpful rule of thumb: if a filter needs to shape the data that another calculation sees, promote it to context. Think of context as "setting the stage" before all other computations run.
- Which design best satisfies the requirement without dashboard navigation?
Answer: Create a product-name set, show its set control, and use the set for In/Out encoding.
When a question asks about classifying items as "In" or "Out" while keeping all items visible, you're being tested on Tableau's set functionality — specifically the difference between sets, filters, parameters, and groups.
Sets are purpose-built for exactly this scenario. A set divides dimension members into two buckets — In and Out — and a set control lets dashboard users dynamically move members between those buckets with checkboxes. Critically, all members remain visible in the view; they're simply encoded differently based on membership. Answer A leverages this perfectly: create the set, expose the set control, and use the set field for color, shape, or another encoding to distinguish In from Out across worksheets sharing the data source.
Answer B is tempting but fundamentally wrong — a filter removes data from the view entirely. The requirement explicitly states that unchosen products "must remain visible," which filters cannot satisfy. Answer C fails because a parameter holds only a single value (or a fixed list with single selection), so it cannot support choosing "any number" of products simultaneously without complex workarounds. Answer D is impractical and misuses groups — groups are for static, predefined buckets edited by an author in the data pane, not something dashboard viewers can interact with dynamically at runtime.
A useful rule of thumb: whenever you see the phrases "any number of members," "In/Out classification," and "remain visible," that's a three-part signal pointing directly to sets with a set control. Filters hide; parameters hold one value; groups are static — only sets give you dynamic multi-member classification with full visibility.
- Which calculated-field logic correctly creates the four segments?
Answer: IF [High Sales Set] AND [High Profit Set] THEN 'Stars' ELSEIF [High Sales Set] THEN 'Volume' ELSEIF [High Profit Set] THEN 'Efficient' ELSE 'Other' END
When building mutually exclusive segments with nested IF logic in Tableau, order matters enormously. The most specific condition must come first — if a broader condition appears earlier, it "captures" records that should have matched a later, more specific branch.
Answer A is correct because it tests the intersection first: IF [High Sales Set] AND [High Profit Set] THEN 'Stars'. Only customers in both sets reach this branch. Customers who fall through are then tested individually — ELSEIF [High Sales Set] catches sales-only members ("Volume"), ELSEIF [High Profit Set] catches profit-only members ("Efficient"), and everyone else becomes "Other." Each branch is truly mutually exclusive because Tableau evaluates conditions top-to-bottom and exits at the first true match.
B fails immediately because it uses OR in the first condition, which catches any customer in either set and labels them "Stars." The subsequent ELSEIF branches become unreachable for those customers, so "Volume" and "Efficient" are never assigned correctly.
C places the AND condition after the individual set checks. By the time Tableau reaches ELSEIF [High Sales Set] AND [High Profit Set], customers in both sets have already been captured by the first IF [High Sales Set] branch and labeled "Volume" — the "Stars" segment is never populated.
D inverts the logic entirely, assigning "Stars" to customers in neither set (which should be "Other") and swapping the labels for "Efficient" and "Volume."
Strategy tip: In any multi-branch IF/ELSEIF calculation, always place the most restrictive (most conditions combined with AND) test first. Broad conditions early will silently swallow records that belong in specific segments.
- How should [Selected Customers] be used in the worksheet?
Answer: Place the set on Color, retaining both In and Out members in the displayed data.
When working with Tableau sets, the key question to ask is: what do I want to happen to the data that isn't selected? Sets have two states — In (selected members) and Out (everyone else) — and where you place a set on the view determines whether both states remain visible or one gets filtered away.
Here, the business needs both segments visible simultaneously with distinct colors, and the percent-of-total must include sales from all customers, not just the selected ones. Placing the set on Color achieves exactly this: Tableau splits marks into In and Out groups, renders each in a different color, and keeps all underlying data intact for table calculations. Your percent-of-total calculation can still reference the full dataset because no rows have been removed.
A is wrong because placing the set on Filters and selecting "In" removes Out members from the view entirely. You'd lose the unselected segment visually, and your percent-of-total would calculate only against the filtered subset — breaking both requirements.
C is a distractor that sounds plausible but misuses the concept of context filters. Adding a set to context changes the order of query operations; it doesn't create a dual-segment color display, and it still restricts which marks appear based on set membership.
D compounds the problem in A by duplicating worksheets — a workaround that defeats the purpose of a set action and creates synchronization headaches. It also still filters data in each sheet, corrupting the percent-of-total.
Study tip: On set questions, remember the rule — Filter removes, Color reveals. If the requirement is "show both," your answer almost always involves Color, not Filters.
- Which clearing-selection option should be used for the set action?
Answer: Add all values to the set, restoring every state as an In member.
When working with Set Actions in Tableau, the key concept to master is how the clearing behavior controls what happens to a set's membership when a user deselects everything. Each set action has three configurable options for what happens on clearing: keep current values, add all values, or remove all values. The question is asking which behavior restores the set to a "show everything" baseline.
The scenario requires that clearing a selection returns every state to membership in the set — meaning all states should be In. That maps directly to B: Add all values to the set. When the selection is cleared, Tableau adds every value back into the set, making all states In members and restoring the full, unfiltered baseline view. This is the standard pattern for "reset to show all" dashboard behavior.
Choice A is wrong because "Keep set values" preserves only the states from the last selection, leaving the set in a filtered state rather than resetting it — users would be stuck with whatever was last clicked. Choice C does the opposite of what you need: removing all values makes every state an Out member, which would blank out the dashboard rather than restore it. Choice D is a fabricated option — Tableau's set action clearing behavior does not include an "assign selected values" mode, making this a distractor testing whether you know the actual three options.
A useful tip: memorize the three clearing options as Keep / Add All / Remove All, and match them to outcomes — Add All = full inclusion (show everything), Remove All = full exclusion (show nothing). Exam questions almost always hinge on distinguishing these two.
