Tableau Quiz: Sorting Grouping And Sets
10 questions · exam conditions
0:00
Sorting Grouping And SetsQuestion 1 of 10

A worksheet has Region and then Sub-Category on Rows, with SUM(Sales) on Columns. Some sub-categories do not occur in every region. The analyst configures Sub-Category with a descending nested sort by SUM(Sales).

How will Tableau order the Sub-Category headers?

It will use one descending Sub-Category order based on sales aggregated across all regions.
It will independently order the available sub-categories by sales within each region.
It will sort regions by sales but retain the data source order for sub-categories.
It will alphabetize sub-categories within each region because some members are missing.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Sorting Grouping And Sets

Practice Sorting Grouping And Sets 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 Sorting Grouping And Sets, 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 worksheet has Region and then Sub-Category on Rows, with SUM(Sales) on Columns. Some sub-categories do not occur in every region. The analyst configures Sub-Category with a descending nested sort by SUM(Sales).

How will Tableau order the Sub-Category headers?

  1. It will use one descending Sub-Category order based on sales aggregated across all regions.
  2. It will independently order the available sub-categories by sales within each region. (correct answer)
  3. It will sort regions by sales but retain the data source order for sub-categories.
  4. It will alphabetize sub-categories within each region because some members are missing.
Explanation: When you see a question about sorting in Tableau, the critical concept to keep in mind is the difference between a global sort and a nested sort. A nested sort doesn't apply one universal ranking — it re-ranks the inner field within each instance of the outer field. In this view, Region is the outer dimension and Sub-Category is the inner dimension. When you configure a descending nested sort on Sub-Category by SUM(Sales), Tableau independently ranks the sub-categories available within each region based on that region's own sales figures. So if "Phones" is the top seller in the East but only third in the West, the headers will reflect those different orderings per region. That's exactly what B describes, making it correct. A is wrong because it describes a global sort — one fixed ranking applied uniformly across all regions. That's what you'd get if you sorted Sub-Category as a standalone dimension outside of a nested context. C incorrectly suggests regions are sorted while sub-categories fall back to data source order, which misunderstands what a nested sort does entirely — it acts on the inner dimension, not the outer one. D introduces a misconception that missing members somehow force alphabetical ordering. Tableau handles sparse data gracefully; missing sub-categories in a region simply don't appear, but the sort logic for present members is unaffected. A useful rule of thumb: nested = local. Whenever you see "nested sort" on an inner dimension, think of it as each parent group getting its own independent ranking. Remembering that distinction will help you confidently navigate sorting questions on the exam.

Question 2

A data source contains separate Customer Segment members named Small Business, Home Office, and Consumer. A manager wants Small Business and Home Office to appear as SMB, with their sales aggregated into one mark, while Consumer remains separate.

Which approach best meets the requirement?

  1. Assign the alias SMB to both original members and retain the original dimension.
  2. Manually sort both original members next to each other and hide one header.
  3. Create a group containing both original members, rename it SMB, and use the group. (correct answer)
  4. Create a set containing both original members and place the set only on Filters.
Explanation: When you need to combine dimension members and aggregate their measures into a single mark, think about which Tableau feature is designed specifically for that purpose: grouping. Groups let you bucket multiple members under one label, and when you place that group on a shelf, Tableau treats all grouped members as one — aggregating their sales, counts, or whatever measure you're using into a single mark. Creating a group containing Small Business and Home Office, renaming it SMB, and using that group field on your view is exactly what answer C describes — and it's the right approach. The result is two marks: SMB (with combined sales) and Consumer (unchanged). That perfectly matches the manager's requirement. Here's why the other options fall short. A is a common trap — aliases only change the display label of a member; they don't merge members or aggregate their data. You'd still get two separate marks, just both labeled "SMB," which would be confusing and incorrect. B is a visual workaround, not a data solution. Sorting and hiding headers might cosmetically disguise the separation, but the underlying marks and measures remain split — totals won't combine. D sets are powerful for in/out filtering and calculations, but placing a set only on Filters doesn't relabel or merge dimension members in the view; it simply restricts which records appear. Study tip: On the Tableau exam, whenever a question asks you to merge members and aggregate their data into one mark, groups are almost always the answer. Aliases = rename only; Sets = filter/highlight logic; Groups = combine and consolidate.

Question 3

A dynamic Product set has two rules: its Condition tab retains products whose total sales exceed ten thousand dollars, and its Top tab retains the five products with the greatest total profit. In the current filtered data, only three products satisfy the sales condition.

Which products will be members of the set?

  1. The five most profitable products overall, regardless of whether they satisfy the condition.
  2. All three qualifying products plus the next two products ranked by overall profit.
  3. No products, because fewer than five members satisfy the required sales condition.
  4. Up to three products, ranked by profit from among those satisfying the sales condition. (correct answer)
Explanation: When a dynamic set has multiple rules — a Condition tab and a Top tab — Tableau applies them together using an AND logic, not independently. Think of each rule as a filter that the same pool of products must pass through simultaneously. The set doesn't run one rule first and then the other in isolation; it finds members that satisfy both constraints at once. In this scenario, the Condition tab requires total sales exceeding $10,000, and the Top tab requests the five products with greatest total profit. Because both rules must be satisfied, Tableau first limits candidates to those meeting the sales condition — only three products here — and then selects the top profit-ranked products from within that qualifying group. Since only three products qualify, the set can contain at most three members, ranked by profit among them. That makes D correct. Choice A is wrong because it ignores the Condition rule entirely, treating the Top rule as if it operates on the full product list. Choice B reflects a misunderstanding of how the two rules interact — there's no "fill remaining slots" behavior that pulls in non-qualifying products to reach the Top N count. Choice C assumes the set requires exactly five members to function, but Tableau simply returns however many qualifying members exist — fewer than five is a valid result, not an error. A useful mental model: think of Condition and Top as two overlapping circles in a Venn diagram — only the intersection becomes the set. On the exam, whenever you see a set with multiple rules, always ask yourself which products survive all rules together, not each one separately.

Question 4

An analyst creates a Customer set containing accounts targeted by a marketing campaign. A bar chart must retain every customer while visually distinguishing targeted customers from all other customers as In and Out.

Which use of the set most directly produces the required comparison?

  1. Place the set on Filters and select In while leaving Customer Name in the view.
  2. Convert the set to a group and place only its targeted member on Filters.
  3. Add the set as a context filter and retain both available membership values.
  4. Place the set on Color and keep both In and Out membership values visible. (correct answer)
Explanation: When working with Tableau sets, the key question to ask is: what does this set need to do in the view? Sets have two membership states — In and Out — and how you use them determines whether you filter data or encode it visually. The requirement here is critical: every customer must remain visible, but targeted customers need to be visually distinguished from the rest. That points directly to encoding, not filtering. Placing the set on Color (answer D) assigns one color to In members and another to Out members, keeping all customers in the bar chart while making the distinction immediately visible. This is exactly what sets are designed for when used as a dimension on a shelf. Answer A fails because filtering to only the In members removes all non-targeted customers from the view entirely — the opposite of what's needed. You'd lose the "all other customers" portion of the comparison. Answer B compounds this problem: converting to a group and filtering to only targeted members again excludes everyone else, and you lose the dynamic membership behavior of a set altogether. Answer C introduces context filters, which control filtering scope and query order — not visual distinction. Even retaining both values in a context filter still frames the set as a filter mechanism, which risks excluding records depending on configuration, rather than encoding membership as a visual mark property. The study tip here: Sets on Filters remove rows; sets on Color (or other encoding shelves) keep all rows and add visual meaning. When a question says "retain every record but distinguish a subset," that's your cue to think encoding, not filtering.

Question 5

An analyst groups California, Oregon, and Washington as West Coast in a State group and enables Include Other. After a data refresh, a previously unseen state appears in the source and has not been assigned to a named group.

How will the new state be represented when the State group is used in the view?

  1. It will appear under Other because that member is not assigned to a named group. (correct answer)
  2. It will appear as its own member until the analyst manually adds it to Other.
  3. It will be added to West Coast because that is the only explicitly named group.
  4. It will be excluded because group membership is fixed when the group is created.
Explanation: When working with Tableau groups, a critical feature to understand is the Include Other option. This setting controls what happens to dimension members that exist in your data but haven't been explicitly assigned to any named group. When you enable Include Other, Tableau automatically creates a catch-all bucket called "Other" that captures any unassigned members — including ones that didn't exist when you originally built the group. This is exactly the scenario described: a new state appears after a data refresh, and because it was never mapped to a named group, Tableau routes it directly into the Other bucket. That makes A the correct answer — the new state will appear under Other automatically, with no manual intervention required. B is wrong because it implies the new state floats independently in the view until the analyst acts. That's actually the behavior you'd see if Include Other were disabled — unassigned members would appear as their own values. With Include Other enabled, nothing goes unclassified. C is wrong because group membership doesn't work by proximity or assumption. Tableau never infers that a new member "probably belongs" to an existing named group. Members must be explicitly assigned. D is wrong because it fundamentally misunderstands what groups do. Groups are dynamic relative to the data — they don't freeze membership at creation time. New data values are evaluated against existing group definitions on every render. Study tip: On Tableau exam questions about groups, always ask yourself: "Is Include Other on or off?" That single toggle completely changes how unassigned members behave, and the exam loves testing this distinction.

Question 6

A bar chart displays Product Name and SUM(Profit). Product Name is sorted descending by the field SUM(Sales), although Sales is not displayed. The analyst then applies a standard Order Date dimension filter that retains only the latest month.

Assuming no context or FIXED calculations are involved, what happens to the product order?

  1. The order remains based on all-time sales until the data source is refreshed.
  2. The order changes to descending profit because Sales is absent from the view.
  3. The marks are filtered to the month, but Tableau preserves the previously cached order.
  4. The order is recalculated by sales using only records retained for the latest month. (correct answer)
Explanation: Whenever you see a question about sorting in Tableau, the key concept to keep in mind is when sorting is evaluated relative to filtering. In Tableau's query order of operations, dimension filters are applied before the final result is rendered — meaning the sort recalculates on whatever data survives the filter, not on the full dataset. In this scenario, the bar chart sorts Product Name by SUM(Sales) descending. Even though Sales isn't a visible pill in the view, Tableau still queries it behind the scenes to compute the sort order. When the Order Date filter restricts records to only the latest month, that filter runs first, trimming the underlying data. The sort then executes on that filtered subset, so the product ranking reflects only the latest month's sales figures. That makes D the correct answer. A is wrong because Tableau does not cache or "lock in" a previous sort order and wait for a refresh — the sort is a live calculation evaluated each time the query runs. B misunderstands how Tableau handles hidden sort fields; a field doesn't need to be displayed in the view to drive the sort. Tableau will still compute SUM(Sales) in the background and use it for ordering. C describes behavior that simply doesn't exist in standard Tableau — there is no preserved cached order separate from the live query. Tableau recalculates on every interaction unless you've explicitly encoded a fixed order (like a manual sort or a FIXED LOD). As a study tip: remember that in Tableau, filters shrink the data first, then all aggregations and sorts recalculate on what remains — unless you deliberately elevate something to context or use an LOD expression.

Question 7

A dashboard set action adds selected State marks to a State set. Users should be able to click a state, clear the selection, and still see that state highlighted as a set member until another action changes membership.

How should the set action be configured for clearing the selection?

  1. Choose Add all values to set, which places every possible state into the set when no marks are selected.
  2. Choose Keep set values, which preserves the current membership when the selection is cleared. (correct answer)
  3. Choose Remove all values from set, which empties the set each time the user deselects marks.
  4. Choose Assign values to set, which reapplies the most recently selected state after the selection is cleared.
Explanation: When working with Tableau set actions, the key concept to understand is what happens to set membership when a user clears their selection — this is controlled by the "Clearing the selection will" behavior, and choosing the right option determines the user experience between interactions. The scenario requires that a selected state stays highlighted as a set member even after the user clicks away — essentially "locking in" the last selection until something new happens. This is exactly what B, Keep set values, does: it freezes the current set membership in place when no marks are selected, so the visualization continues reflecting the last meaningful user action. A is a trap that sounds intuitive but causes the opposite problem — adding all values collapses the meaningful distinction between set members and non-members, effectively breaking any conditional formatting or filtering tied to the set. C is perhaps the most tempting distractor: removing all values seems like a "clean slate" approach, but it means every time a user clicks away, the set empties and any highlighting disappears entirely — the opposite of what the scenario requires. D describes behavior that doesn't actually exist in Tableau's set action options; "Assign values to set" is one of the action trigger behaviors (replacing set membership with selected marks), not a clearing behavior, making this a terminology trap. For the exam, memorize Tableau's three clearing behaviors as a trio: Keep (preserve), Add all (fill), Remove all (empty). When a question asks about maintaining state between interactions, "Keep set values" is almost always your answer.

Question 8

Set F contains customers who purchased Furniture, and Set T contains customers who purchased Technology. Both sets are based on Customer Name. The analyst needs a set containing customers who purchased exactly one of the two categories, excluding customers who purchased both.

Which sequence of combined-set operations produces the required membership?

  1. Create the intersection of F and T, then add the union of F and T.
  2. Create the union of F and T, then intersect that result with F.
  3. Create the union of F and T, then exclude the intersection of F and T. (correct answer)
  4. Create F except T and T except F separately, then take the intersection of those two results.
Explanation: Whenever you see a question about combined sets in Tableau, translate the problem into the language of set theory before evaluating any answer choice. Here, you need customers in exactly one category — a classic symmetric difference: members of F or T, but not both. The cleanest way to build this is in two steps. First, take the union of F and T, which captures every customer who bought Furniture, Technology, or both. Then, exclude the intersection of F and T — the customers who bought both categories. What remains is precisely the customers who belong to only one set. That's option C, and it directly mirrors the symmetric difference formula: (F∪T)∖(F∩T)(F \cup T) \setminus (F \cap T). A is backwards in its logic — adding a union to an intersection gives you the full union, not the exclusive members. Intersecting first and then adding the union doesn't remove anyone; it only expands membership. B takes the union of F and T and then intersects it with F alone, which simply returns all of F. Intersecting with only one of the original sets ignores T's exclusive members entirely. D sounds clever — "F except T" gives you F-only customers, and "T except F" gives you T-only customers. Those two results together would be exactly what you want, but the final step ruins it: taking the intersection of two non-overlapping groups produces an empty set. You'd want the union of those two results, not the intersection. As a study habit, sketch a two-circle Venn diagram and shade the region the question describes before evaluating any option — it makes set logic visual and nearly impossible to confuse.

Question 9

At the end of a quarter, an analyst selects ten customer marks and creates a set from the selection. No condition or Top rule is added. During the next refresh, customer sales rankings change and a new customer becomes one of the ten highest-selling customers.

What membership behavior should the analyst expect?

  1. The selected set automatically replaces lower-ranked members with the new top customer.
  2. The selected customer names remain members unless the set is manually edited. (correct answer)
  3. The set becomes empty because fixed selections are invalidated by a refresh.
  4. The set adds the new top customer while retaining all ten original members.
Explanation: When working with sets in Tableau, the most important distinction to understand is between fixed sets and computed sets. A fixed set captures specific member names at the time of creation — it's a static snapshot, not a dynamic query. A computed set, by contrast, uses conditions or Top rules to re-evaluate membership on every refresh. Because the analyst manually selected ten customer names without adding any condition or Top rule, this is a fixed set. Fixed sets remember who was selected, not why they were selected. When the data refreshes and rankings shift, Tableau doesn't re-run any logic — it simply checks whether those same named members still exist in the data. As long as the customers haven't been removed from the data source entirely, they remain in the set. That makes B correct: the original ten customer names stay as members unless the analyst manually edits the set. A is wrong because automatic replacement of lower-ranked members describes computed set behavior driven by a Top rule — which was explicitly not added here. C is wrong because fixed sets are not invalidated by refreshes; they only lose members if those members disappear from the underlying data entirely, and even then the set isn't emptied — it just ignores the missing names. D is wrong because fixed sets don't grow dynamically; adding the new top customer while retaining all ten originals would require computed logic, which doesn't exist in this scenario. Your study tip: whenever a Tableau question mentions a set with no condition or Top rule, think "fixed = frozen names." Any dynamic behavior requires an explicit condition or Top N rule.

Question 10

A worksheet uses a dynamic Top ten Customer set based on SUM(Sales). The analyst adds Region as a standard dimension filter and selects Central, expecting the set to identify the top ten customers within Central. Instead, some globally high-ranking customers disappear after the filter, leaving fewer than ten visible set members.

What change should the analyst make so the Top ten set is computed within Central?

  1. Add the Region filter to context before evaluating the Top ten Customer set. (correct answer)
  2. Convert the Region filter to a measure filter based on SUM(Sales).
  3. Place the Customer set on Filters and retain only its In membership.
  4. Change Region to a continuous field before applying the selected value.
Explanation: Whenever you see a question about sets and filters producing unexpected results in Tableau, you should immediately think about filter order of operations. Tableau evaluates filters in a strict sequence: context filters → sets → dimension filters → measure filters. This hierarchy is the key to this entire question. Because the Top ten Customer set is evaluated before dimension filters in the default order, it first identifies the global top ten customers across all regions. When the Region dimension filter for Central is applied afterward, it simply hides customers not in Central — it doesn't recompute the set within Central. This is why fewer than ten customers appear: some global top-ten customers belong to other regions and get filtered out after the set is already locked in. The fix, as answer A correctly states, is to add the Region filter to context. Promoting Region to a context filter moves it earlier in the evaluation sequence — before sets are computed. Now the set sees only Central data and correctly identifies the top ten customers within that region. Answer B is wrong because converting Region to a measure filter would move it even later in the evaluation order, making the problem worse, not better. Answer C misunderstands the issue — placing the Customer set on Filters and keeping "In" members only doesn't change when or how the set is computed; it just controls what rows are shown. Answer D is a distractor with no logical basis; whether Region is discrete or continuous has no effect on filter evaluation order. Your study tip: memorize Tableau's filter order — Extract → Data Source → Context → Sets → Dimension → Measure → Table Calc. Questions about unexpected set or filter behavior almost always hinge on this sequence.