Tableau Quiz: Hierarchies
10 questions · exam conditions
0:00
HierarchiesQuestion 1 of 10

A data source contains the dimensions Division, Department, and Team. Users should begin at Division and then drill to Department and Team by using Tableau's hierarchy controls.

Which configuration most directly supports the required navigation?

Create a hierarchy ordered Division, Department, Team, and place Division in the initial view.
Create a group from Division, Department, and Team, and place the group in the initial view.
Place the dimensions in a folder named Organization, and place Division in the initial view.
Concatenate Division, Department, and Team, and place the combined dimension in the initial view.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Hierarchies

Practice Hierarchies 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 Hierarchies, 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 data source contains the dimensions Division, Department, and Team. Users should begin at Division and then drill to Department and Team by using Tableau's hierarchy controls.

Which configuration most directly supports the required navigation?

  1. Create a hierarchy ordered Division, Department, Team, and place Division in the initial view. (correct answer)
  2. Create a group from Division, Department, and Team, and place the group in the initial view.
  3. Place the dimensions in a folder named Organization, and place Division in the initial view.
  4. Concatenate Division, Department, and Team, and place the combined dimension in the initial view.
Explanation: When a question asks about enabling drill-down navigation between related dimensions in Tableau, you should immediately think about hierarchies — Tableau's built-in feature that lets users expand and collapse levels using the plus/minus controls directly in the view. A hierarchy in Tableau is created by nesting dimensions in a specific order within the Data pane. When you build a hierarchy ordered Division → Department → Team and place Division in the view, Tableau automatically renders the drill-down controls, allowing users to click the "+" icon to expand to Department, then to Team. This is exactly what option A describes, making it the correct configuration — it's the only choice that uses the actual Tableau feature designed for this purpose. Option B is wrong because groups in Tableau combine members within a dimension (e.g., grouping "East" and "West" into "Americas") — they don't create navigable drill-down paths between separate dimensions. Option C is wrong because folders are purely organizational tools for the Data pane; they help analysts find fields more easily but have zero effect on how data behaves in a view or whether drill-down controls appear. Option D is wrong because concatenating dimensions merges them into a single flat string (e.g., "Sales / Marketing / Alpha Team"), which displays all levels simultaneously as one value — it eliminates the drill-down interaction entirely rather than enabling it. The key study tip here: Tableau has distinct features for organizing data (folders), combining members (groups), and enabling hierarchical navigation (hierarchies). Exam questions often mix these up deliberately, so always match the user interaction requirement to the correct feature.

Question 2

Two dashboard worksheets use the same Region, Country, State hierarchy from one data source. Both initially show Region. A user drills the first worksheet down to Country, but no dashboard action links the worksheets.

What should the dashboard author expect?

  1. Both worksheets drill to Country because the hierarchy definition is shared by the data source.
  2. Only the first worksheet drills to Country because drill state is maintained separately by each worksheet. (correct answer)
  3. Neither worksheet drills until Country is manually added to every worksheet using the hierarchy.
  4. The first worksheet drills to Country, while the second automatically filters to the selected region.
Explanation: When working with Tableau dashboards, it's important to distinguish between data source definitions (shared) and worksheet state (independent). Hierarchies are defined at the data source level, meaning all worksheets using that source have access to the same Region → Country → State structure — but that access doesn't mean worksheets behave as a single synchronized unit. Each worksheet in Tableau maintains its own independent view state. When a user drills down a hierarchy in one worksheet, Tableau updates only that worksheet's level of detail. The drill action is essentially a view change local to that sheet. Without a dashboard action — such as a filter action or highlight action explicitly linking the two worksheets — the second worksheet has no mechanism to receive or respond to what happened in the first. So you should expect only the first worksheet to show Country, confirming that B is correct. A is tempting because it's true that the hierarchy definition is shared, but that's about structure, not synchronized behavior. Sharing a hierarchy doesn't mean drilling one sheet propagates to another. C is wrong because drilling doesn't require manually adding fields — the hierarchy is already present in both worksheets, and users can drill interactively without any authoring changes. D describes behavior that would require a filter action configured between the two sheets; since no dashboard action links them, no automatic filtering occurs. A useful rule of thumb: in Tableau, data source = shared structure, worksheet = independent state. Whenever a question mentions two worksheets behaving in sync, look for an explicit dashboard action connecting them — if there isn't one, each sheet acts alone.

Question 3

An analyst creates a Country, State, City hierarchy for a symbol map. Several cities with identical names are plotted in the wrong locations even though users can drill through the three levels correctly.

What is the most appropriate next step?

  1. Reverse the hierarchy to City, State, Country so Tableau evaluates the most detailed field first.
  2. Place all hierarchy levels on Color so Tableau can infer the intended coordinates from formatting.
  3. Convert the hierarchy into a combined field so each city becomes a unique geographic member.
  4. Keep the drill hierarchy, then verify geographic roles and resolve ambiguous or unknown locations. (correct answer)
Explanation: Whenever you see a question about geographic mapping errors in Tableau, separate two distinct issues: navigation (can users drill through hierarchy levels?) and accuracy (are locations plotted in the correct places?). The passage tells you drilling works fine — so the hierarchy structure itself isn't broken. The real problem is geocoding: Tableau has misidentified or failed to identify certain cities. The right move, D, addresses this directly. Geographic roles tell Tableau how to interpret a field (as a city, state, country, etc.), and when multiple cities share the same name — think Springfield existing in dozens of U.S. states — Tableau can plot them ambiguously. Verifying geographic roles and using the "Edit Locations" dialog to resolve unknown or ambiguous members corrects the coordinates without dismantling the working hierarchy. A is wrong because reversing the hierarchy order doesn't affect geocoding at all. Tableau doesn't resolve geographic ambiguity by evaluating fields in a particular hierarchy sequence — location matching depends on roles and context, not evaluation order. B is wrong because placing fields on Color is a formatting and visual encoding choice. Color encodes categorical or quantitative differences; it has no influence on how Tableau assigns latitude and longitude coordinates to geographic members. C is wrong because combining fields into a single concatenated field is a workaround that destroys the drill-down functionality users rely on. It's also an overly destructive fix when the proper tool — editing geographic roles and resolving ambiguous locations — already exists natively in Tableau. Your study tip: on mapping questions, always ask yourself whether the issue is structure (hierarchy, fields) or geocoding (roles, coordinates). Most plotting errors point to geocoding, and Tableau's Edit Locations feature is the targeted fix.

Question 4

A retailer uses a 4-4-5 calendar. Users must drill from Fiscal Year to Fiscal Quarter to Fiscal Period to Week. The standard calendar Year, Quarter, Month, Day path does not represent these business periods.

Which design best provides the required drill navigation?

  1. Create calculated fiscal dimensions and arrange them in a custom hierarchy in the required order. (correct answer)
  2. Use the standard date hierarchy and relabel Month as Fiscal Period in the worksheet.
  3. Create aliases for calendar quarters and months, then retain the standard date hierarchy.
  4. Place the original date in a folder with Week and sort the folder by fiscal sequence.
Explanation: When you encounter questions about non-standard business calendars in Tableau, ask yourself: does the built-in date hierarchy actually match the business logic? If not, you need a custom solution — not a cosmetic fix. A 4-4-5 calendar groups weeks into periods that don't align with standard calendar months or quarters. The drill path Fiscal Year → Fiscal Quarter → Fiscal Period → Week requires each level to carry accurate fiscal logic, not just a renamed label. Answer A is correct because creating calculated fields for each fiscal dimension (Fiscal Year, Fiscal Quarter, Fiscal Period) lets you encode the actual 4-4-5 boundaries into the data. Arranging these calculations into a custom hierarchy gives users exactly the drill path the business requires — structurally and logically correct at every level. Answer B fails because relabeling "Month" as "Fiscal Period" in the worksheet is purely cosmetic. The underlying date groupings still follow calendar months, so the data behind the label is wrong. Answer C makes the same class of mistake — aliases change display names, not the actual groupings. Calendar quarters and months still define the aggregations, which won't match 4-4-5 periods. Answer D misunderstands how folders work in Tableau; placing a date field and a Week field in a folder doesn't create a hierarchy or encode any fiscal sequencing logic. Sorting a folder doesn't establish drill-down navigation. A useful rule of thumb: whenever the business calendar diverges from the Gregorian calendar, always reach for calculated dimensions and custom hierarchies. Surface-level fixes like aliases, relabeling, and folders cannot change how Tableau aggregates or navigates date data.

Question 5

Country, State, and City are arranged in a hierarchy. A dashboard also displays separate Country and State filters. Users report that selecting a country does not limit the State filter to states in that country.

Which change addresses the problem without altering the hierarchy's drill order?

  1. Move State above Country in the hierarchy and leave both filters configured to show all values.
  2. Keep the hierarchy order and configure the State filter to show only relevant values. (correct answer)
  3. Remove State from the hierarchy and convert the State filter into a context filter.
  4. Combine Country and State into one group and use that group as the State filter.
Explanation: When you see a question about filters not responding to each other on a Tableau dashboard, think about filter dependencies — specifically, how to make one filter aware of selections made in another. By default, filters in Tableau operate independently. That's exactly the problem here: the State filter shows all states regardless of which country is selected, because nothing tells it to pay attention to the Country filter. The fix is to configure the State filter to "Only Relevant Values", which instructs Tableau to dynamically limit the State filter's options based on what's already been filtered upstream — in this case, by Country. This resolves the disconnection without touching the hierarchy's drill order at all, making B the correct answer. A is wrong because moving State above Country in the hierarchy inverts the intended drill order (Country → State → City), which the question explicitly says to preserve. Reordering the hierarchy doesn't fix filter dependency anyway. C is tempting but misguided. Making State a context filter would establish filter priority, but removing State from the hierarchy breaks the drill-down structure. The question asks you to solve the problem without altering the hierarchy, so this disqualifies C. D creates a combined group, which is a workaround that loses the flexibility of having separate Country and State filters. It doesn't address the dependency problem — it sidesteps it clumsily and changes the user experience significantly. Study tip: On Tableau exam questions involving filter interactions, always check whether "Only Relevant Values" can solve the problem before considering structural changes like context filters or hierarchy modifications — it's the least invasive fix.

Question 6

A global sales data source uses Country, State or Province, and City. Some countries do not use a state-level administrative division, so State or Province is null for their records. The author nevertheless creates one hierarchy ordered Country, State or Province, City.

What is the likely drill behavior for a country whose intermediate level is null?

  1. Tableau skips State or Province for those records and drills directly from Country to City, preserving the two-level navigation.
  2. Tableau prompts the author to define an alternate drill path for countries that lack a state or province level.
  3. Tableau removes the country's cities because every hierarchy level must contain non-null values to expose child members.
  4. Tableau displays a null intermediate member, after which users can continue drilling to City. (correct answer)
Explanation: When working with hierarchies in Tableau, it helps to understand that Tableau is a display tool first — it renders what exists in the data rather than enforcing strict structural rules or blocking navigation. Keep that principle in mind whenever a question asks what happens when hierarchy levels have incomplete or null values. In this scenario, records for countries without a state-level division will have a null value in the State or Province field. When a user drills down from Country, Tableau faithfully exposes the next level in the defined hierarchy — even if that level's value is null. The result is a null intermediate member appearing in the view, and drilling further from that null member reveals City. The hierarchy still functions end-to-end; it just surfaces the gap honestly. That's why D is correct. A is tempting because it sounds like a "smart" workaround, but Tableau does not automatically skip levels or reroute drill paths based on null values. It respects the hierarchy definition as written. B describes a configuration prompt that simply doesn't exist in Tableau — the software never interrupts authoring to request alternate drill paths for individual members. C reflects a common misconception that nulls break child visibility entirely; in reality, cities remain accessible through the null intermediate step and are not removed from the hierarchy. A useful study pattern: Tableau questions about nulls often test whether you assume the software fixes or restricts based on missing data. Tableau generally surfaces nulls rather than hiding or rerouting around them — apply that default assumption when evaluating similar scenarios.

Question 7

A workbook has a hierarchy ordered State, Country, City. The intended navigation is Country, State, City. Several worksheets already use fields from this hierarchy.

What should the author do to correct the drill path while preserving the hierarchy and its fields?

  1. Apply ascending sorts to Country, State, and City on each worksheet using the hierarchy.
  2. Reorder the fields within the hierarchy in the Data pane to Country, State, City. (correct answer)
  3. Rearrange the visible field pills on one worksheet to Country, State, City.
  4. Set Country as the default sort field for both State and City in the data source.
Explanation: When working with hierarchies in Tableau, it's important to understand that a hierarchy's drill-down order is determined entirely by the sequence of fields within the hierarchy itself in the Data pane — not by how fields appear on individual worksheets. This question is testing whether you know where that drill path is actually defined. The fix here is B: reorder the fields within the hierarchy in the Data pane to Country, State, City. The hierarchy's top-to-bottom arrangement in the Data pane dictates the drill path for every worksheet that uses it. Changing the order there propagates the correct navigation — Country → State → City — universally, while keeping the hierarchy intact and all its fields in use. A is a trap because sorting fields ascending or descending controls how values are ordered alphabetically or numerically, not how levels relate to each other in a drill-down path. Sorting has no effect on hierarchy structure. C is wrong because rearranging pills on a single worksheet only affects that one view's display. It doesn't change the underlying hierarchy, so other worksheets remain broken and the drill path is still incorrect at the source. D is a distractor that sounds technical but doesn't match how Tableau works. Setting a "default sort field" for State and City doesn't define hierarchy levels or drill-down sequence — that concept simply doesn't fix hierarchy ordering. Study tip: On Tableau exam questions about hierarchies, always ask yourself where the property lives — the Data pane (structure), a worksheet (local display), or the data source (underlying data). Drill path is a Data pane concern, full stop.

Question 8

A company requests conditional drill paths. Consumer users should drill Segment, Category, Product. Enterprise users should drill Segment, Account, Product. The next level after Segment must therefore depend on the selected segment.

Which design most accurately addresses this requirement?

  1. Create one hierarchy ordered Segment, Category, Account, Product and hide whichever level is not relevant.
  2. Create one hierarchy ordered Segment, Product and use Category and Account only as worksheet filters.
  3. Create separate purpose-specific hierarchies, using duplicated or calculated dimensions where necessary. (correct answer)
  4. Create a group containing Category and Account, then place that group between Segment and Product.
Explanation: When you see a question about drill paths in Tableau, think about whether a single hierarchy can satisfy divergent user paths — or whether separate hierarchies are the cleaner, more maintainable solution. Here, two user groups need fundamentally different drill sequences after Segment: Consumer users go to Category, Enterprise users go to Account. Because Tableau hierarchies are fixed, linear sequences, a single hierarchy cannot branch based on the user or context. The only correct approach is to build two purpose-specific hierarchies — one ordered Segment → Category → Product, another ordered Segment → Account → Product — duplicating or using calculated dimensions as needed to avoid conflicts. This is exactly what C describes, and it directly maps to the branching requirement without compromising either user experience. A is tempting but flawed. You can't dynamically hide hierarchy levels mid-drill in a way that cleanly reroutes the path for different user types. Hiding a level doesn't create conditional branching — it just removes a step, potentially breaking the intended sequence or creating confusing gaps. B fails because using Category and Account only as worksheet filters removes them from the drill path entirely, which defeats the purpose — users need to drill through those dimensions, not filter by them separately. D misunderstands what a group does in Tableau. Groups aggregate dimension members into named buckets; they cannot represent two distinct fields that conditionally appear depending on context. As a study tip, remember: when requirements call for different users to follow different drill paths, separate hierarchies are almost always the right answer. Tableau hierarchies are rigid by design — fighting that rigidity with hacks like hiding levels or groups usually signals a wrong answer.

Question 9

A workbook author removes the hierarchy named Product Drill, which contains Category, Sub-Category, and Product Name. Existing worksheets already use those dimensions.

Which result should the author expect?

  1. The individual dimensions remain available, and existing worksheets retain the same drill-down controls as before.
  2. The hierarchy and its dimensions are deleted, causing all worksheets using them to become invalid.
  3. The hierarchy is removed, but its dimensions remain available and existing views retain their field usage. (correct answer)
  4. The hierarchy is removed only from worksheets created before the change but remains defined for new worksheets.
Explanation: When working with Tableau hierarchies, it's important to understand that a hierarchy is essentially an organizational wrapper — it groups existing dimensions to enable drill-down behavior, but it doesn't own or contain those fields in a permanent sense. The underlying dimensions exist independently in your data source. Removing a hierarchy like Product Drill simply dismantles that grouping structure. The fields — Category, Sub-Category, and Product Name — were always dimensions in their own right, and they remain fully available in the Data pane after the hierarchy is deleted. Any existing worksheets that used those fields continue to display them correctly; the fields just lose their drill-down nesting behavior. That's exactly what C describes, making it the correct answer. A is tempting but inaccurate on one key point: existing worksheets do not retain "the same drill-down controls as before." The expand/collapse hierarchy controls disappear because the hierarchy no longer exists. The fields remain, but the structured drill-down navigation is gone. B describes the behavior you'd expect if you deleted the actual data source connection or the fields themselves — not a hierarchy. Removing a hierarchy never deletes dimensions, so worksheets won't become invalid. D invents a concept that doesn't exist in Tableau. Hierarchies don't behave differently based on when a worksheet was created; removing a hierarchy affects all sheets uniformly, and there's no "grandfathering" mechanic. As a study tip, remember this distinction: in Tableau, organizing structures (hierarchies, folders, groups) can be removed without destroying the underlying fields. Questions that conflate the container with its contents are a common trap on this exam.

Question 10

Product Category, Product Sub-Category, and Product Name form a hierarchy in that order. A worksheet currently displays Product Category on Rows. The analyst wants to reveal Product Sub-Category while retaining Product Category, but does not yet want to show Product Name.

Which action produces the intended level of detail?

  1. Use the hierarchy's drill-down control once from Product Category in the current view. (correct answer)
  2. Use the hierarchy's drill-down control twice from Product Category in the current view.
  3. Replace Product Category on Rows with Product Sub-Category from the Data pane.
  4. Expand the hierarchy in the Data pane without adding another field to the view.
Explanation: When working with Tableau hierarchies, keep this principle in mind: the drill-down control (the small + icon that appears on a field in the view) expands the hierarchy one level at a time, adding the next field while keeping the current one visible. This is exactly what the analyst needs here — Product Sub-Category revealed alongside Product Category, without going all the way to Product Name. Starting from Product Category on Rows, clicking the + drill-down control once drops you exactly one level deeper, displaying both Product Category and Product Sub-Category together. That's choice A, and it perfectly matches the requirement. Choice B is tempting if you misread the hierarchy depth, but drilling down twice would expose Product Name as well — one click lands on Sub-Category, the second click lands on Product Name — overshooting the desired level of detail. Choice C describes replacing Product Category with Product Sub-Category by dragging from the Data pane. This gives you Sub-Category alone on Rows, losing Product Category entirely — the opposite of "retaining" the higher level. Choice D misrepresents what expanding a hierarchy in the Data pane does. Expanding it there simply reveals its members for easier dragging; it doesn't automatically add anything to the view. Study tip: On hierarchy questions, always track two things: (1) where you're starting in the hierarchy and (2) how many drill-down clicks map to how many levels. One click = one level deeper. Confusing "expand in Data pane" with "drill down in view" is a classic distractor Tableau questions use to test whether you understand the distinction between the Data pane and the active view.