Tableau Quiz: Dual Axis Charts
10 questions · exam conditions
0:00
Dual Axis ChartsQuestion 1 of 10

An analyst is overlaying monthly Revenue in dollars with Profit Margin as a percentage. The purpose is to compare the timing of increases and decreases, not to imply that a dollar value is numerically equivalent to a percentage.

How should the analyst configure the axes?

Use a dual-axis chart, synchronize both axes, and format each axis independently with its original unit.
Use a dual-axis chart, retain independent scales, and format one axis as currency and the other as a percentage.
Use a combined axis, retain a single scale, and format individual marks according to their underlying measure.
Use a dual-axis chart, convert Profit Margin to currency, and synchronize it with the Revenue axis.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Dual Axis Charts

Practice Dual Axis Charts 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 Dual Axis Charts, giving you a quick way to practice the rules, question types, and explanations that matter most for Tableau.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

An analyst is overlaying monthly Revenue in dollars with Profit Margin as a percentage. The purpose is to compare the timing of increases and decreases, not to imply that a dollar value is numerically equivalent to a percentage.

How should the analyst configure the axes?

  1. Use a dual-axis chart, synchronize both axes, and format each axis independently with its original unit.
  2. Use a dual-axis chart, retain independent scales, and format one axis as currency and the other as a percentage. (correct answer)
  3. Use a combined axis, retain a single scale, and format individual marks according to their underlying measure.
  4. Use a dual-axis chart, convert Profit Margin to currency, and synchronize it with the Revenue axis.
Explanation: When you need to plot two measures with fundamentally different units on the same chart, the central question is: should the scales be shared or independent? Sharing a scale only makes sense when the units are comparable — Revenue in dollars and Profit Margin as a percentage are not, so they need their own axes. A dual-axis chart is the right tool here because it places two independent y-axes on opposite sides of the view, allowing each measure to scale naturally within its own range. This preserves the visual integrity of both trends without distorting either. You then format the left axis as currency and the right axis as a percentage, making the units immediately clear to the viewer. That's exactly what B describes, and it's the correct approach. A fails because synchronizing both axes forces them to share the same numeric range. That would compress or distort one measure to match the other — defeating the entire purpose of showing each trend on its own terms. C is wrong because a combined axis merges both measures onto a single scale, which numerically equates dollars to percentages — precisely what the passage says you want to avoid. D converts Profit Margin into currency before plotting, which fundamentally changes the meaning of the data and misrepresents the metric; you'd no longer be showing a true margin percentage at all. A useful rule of thumb: whenever two measures have different units, reach for a dual-axis chart with independent scales. Reserve synchronization only for when both axes share the same unit and a direct numeric comparison is intentional.

Question 2

In a dual-axis chart, the primary Sales axis has a fixed range from zero to a positive upper limit. Profit includes several negative values. The analyst synchronizes the Profit axis to the fixed Sales axis and then notices that the negative Profit marks are no longer visible.

What is the most appropriate correction if equal currency values must still align?

  1. Keep the fixed primary range, convert Profit to discrete, and display negative values as headers beside the bars.
  2. Keep the fixed primary range, disable synchronization, and rely on matching currency formats to align equal values.
  3. Keep synchronization, reverse the secondary axis, and preserve the fixed positive range on the primary axis.
  4. Keep synchronization, revise the primary range to include the negative values, and allow the synchronized secondary scale to follow it. (correct answer)
Explanation: Whenever you see a dual-axis chart question involving synchronization, your core concern should be axis alignment: synchronized axes share the same scale, meaning if one axis changes, the other must follow to preserve value-to-value alignment on screen. Here, the problem is that the fixed Sales axis starts at zero, so after synchronization the Profit axis also starts at zero — clipping any negative Profit values below the visible area. The fix must accomplish two things simultaneously: reveal negative values and maintain the equal-currency alignment that synchronization provides. Answer D does exactly this. By expanding the primary axis range to include the negative values (e.g., setting the minimum below zero), the synchronized secondary axis stretches to match, keeping every currency unit visually aligned while making all Profit marks visible. Answer A fails because converting Profit to discrete and displaying negative values as headers is a formatting workaround that destroys the spatial alignment between the two axes — equal currency values will no longer sit at the same vertical position. Answer B breaks synchronization entirely. Without synchronization, the two axes scale independently, so "matching currency formats" only makes the tick labels look similar — the actual positions of equal values will diverge, misleading the reader. Answer C reverses the secondary axis, which flips Profit so negative values appear above zero. This distorts the visual relationship between Sales and Profit and misrepresents the data direction entirely. Study tip: On Tableau exam questions about dual-axis charts, always ask whether a proposed fix preserves both visibility and scale alignment — those two requirements often eliminate most distractors immediately.

Question 3

A worksheet compares SUM(Orders) with AVG(Shipping Days) over continuous month. A developer claims a dual-axis chart cannot be created unless both measures use the same aggregation.

Which evaluation of the claim is most accurate?

  1. The claim is correct because dual axes require both measures to use identical aggregation functions and scale ranges.
  2. The claim is incorrect because each axis can use a different aggregation, although synchronization should be judged by unit and meaning. (correct answer)
  3. The claim is correct because AVG can appear on a secondary axis only after it is converted to SUM.
  4. The claim is incorrect because Tableau automatically converts both aggregations to ATTR when Dual Axis is selected.
Explanation: When you see a question about dual-axis charts in Tableau, the core concept being tested is whether the two axes share requirements around aggregation. The key insight is that a dual-axis chart is fundamentally about displaying two independent measures on separate scales — the axes operate independently of each other. Tableau allows each measure on a dual-axis chart to use a completely different aggregation function. In this scenario, SUM(Orders) and AVG(Shipping Days) coexist perfectly on a dual-axis chart because each axis maintains its own scale and aggregation logic. The choice of aggregation should be driven by analytical meaning — SUM makes sense for counting orders, while AVG makes sense for measuring shipping performance — not by any technical requirement that they match. This confirms B as correct: dual axes support mixed aggregations, and synchronization decisions should be based on unit and interpretive meaning, not forced uniformity. A is wrong on both counts — axes don't require identical aggregation functions, and synchronized scales are an optional setting you control manually, not a prerequisite for creating the chart. C invents a rule that doesn't exist; AVG can appear on a secondary axis without any conversion, and Tableau would never require you to distort a measure's meaning just to place it on an axis. D is entirely fabricated — Tableau does not convert aggregations to ATTR upon selecting Dual Axis. ATTR is a specific aggregation used to display a dimension-like field as a measure when values are uniform, and it plays no automatic role in dual-axis creation. As a study tip, remember that in Tableau, dual axes are about independent visualization — think of them as two separate charts sharing a single view, each free to have its own aggregation, mark type, and scale.

Question 4

An author created a dual-axis chart and then cleared Show Header for the secondary measure to simplify the presentation. Later, the author discovers that the axes were never synchronized and cannot right-click the hidden secondary axis in the view.

Which procedure most directly resolves the issue?

  1. Duplicate the primary measure, replace the hidden secondary pill, and select a shared Measure Values scale.
  2. Show the primary header, right-click the primary axis, select Edit Alias, and then hide both axis headers.
  3. Restore Show Header from the secondary measure pill, right-click the displayed secondary axis, select Synchronize Axis, and optionally hide it again. (correct answer)
  4. Expose the secondary Marks card, select Synchronize Axis from Color, and then remove the secondary header.
Explanation: Whenever you see a question about dual-axis charts in Tableau, remember that axis options like Synchronize Axis are only accessible by right-clicking the axis itself in the view — not through any menu, pill dropdown, or marks card. This means the axis must be visible before you can interact with it. The root problem here is a chicken-and-egg situation: the secondary axis was hidden before it was synchronized, and now it can't be right-clicked. The fix in C breaks the deadlock cleanly — restore the secondary axis header by re-enabling Show Header on the secondary measure pill, right-click the now-visible axis to select Synchronize Axis, then optionally hide it again if you want a cleaner presentation. This is the direct, intended workflow Tableau provides. A is a workaround that misunderstands the architecture — duplicating a measure and routing through Measure Values doesn't replicate a true dual-axis setup and won't resolve the synchronization issue in any meaningful way. B conflates the primary axis with the secondary one; right-clicking the primary axis gives you options for the primary scale only — Synchronize Axis acts on the secondary axis relative to the primary, so you must access it from the secondary side. D is fabricated logic — the Marks card controls encoding (color, size, shape) and has no Synchronize Axis option at all; synchronization is strictly an axis-level operation. The key study tip: in Tableau, you can only right-click what you can see. If an axis interaction is unavailable, your first instinct should be to check whether the axis is hidden — show it, act on it, then hide it again.

Question 5

A worksheet displays monthly Sales as bars in one pane and monthly Profit as a line in a second pane. Both measures are currency values, and the analyst wants equal dollar values to appear at the same vertical position while retaining different mark types.

Which sequence best produces the requested view?

  1. Select Dual Axis for Profit, synchronize the secondary axis, and assign Bar and Line on the two measure Marks cards. (correct answer)
  2. Select Combined Axis for Profit, synchronize the shared axis, and assign Bar and Line from the All Marks card.
  3. Move both measures to Measure Values, hide Measure Names, and assign Bar and Line from the worksheet Marks card.
  4. Select Dual Axis for Profit, leave both axes independent, and assign Bar and Line on the two measure Marks cards.
Explanation: When Tableau questions describe two measures shown as different mark types (bars and lines) with the requirement that equal dollar values align vertically, you're being tested on the difference between Dual Axis and Combined Axis — and critically, on axis synchronization. Dual Axis places two independent axes (one left, one right) on the same pane, giving each measure its own Marks card so you can assign different mark types independently. Synchronizing the secondary axis forces both axes to share the same scale and origin, meaning equal dollar values truly appear at the same vertical position. That's exactly what the question demands — separate mark types, two panes collapsed into one, with aligned scales. This makes A the correct sequence. B is wrong because Combined Axis merges both measures onto a single shared axis with one blended Marks card (the "All" card). You cannot assign different mark types per measure through the All card alone — both marks would be the same type, which contradicts the requirement. C is wrong because using Measure Values places both measures on a single axis controlled by one Marks card. Like B, this prevents per-measure mark type assignment, and hiding Measure Names doesn't solve that structural limitation. D is wrong because it correctly uses Dual Axis and assigns mark types per Marks card, but leaving the axes independent means the left and right scales can differ. A $1,000 profit bar and a $1,000 sales bar would not align vertically — which directly violates the stated requirement. A useful rule of thumb: whenever you need both independent mark types and aligned scales, the answer involves Dual Axis plus synchronization. If only one of those two steps appears, keep looking.

Question 6

A view contains continuous Month on Columns and two measures on Rows. One measure is continuous and produces an axis; the other was changed to discrete and produces headers. The Dual Axis option is unavailable for the discrete measure.

What should the author do first to enable a standard dual-axis overlay?

  1. Convert Month to discrete so each month has a header, then synchronize the two measure headers.
  2. Convert the continuous measure to discrete so that both measures provide headers, then select Dual Axis.
  3. Convert the discrete measure to continuous so that both measures provide continuous axes, then select Dual Axis. (correct answer)
  4. Move the discrete measure to Filters, show the filter, and select Dual Axis from the filter menu.
Explanation: Whenever you see a question about dual axis in Tableau, the core rule to remember is this: Dual Axis requires two continuous measures, each producing its own axis. If either measure is discrete, it produces headers instead of an axis, and the Dual Axis option becomes grayed out entirely. In this scenario, you have one continuous measure (good — it has an axis) and one discrete measure (problem — it only has headers). The fix is straightforward: convert that discrete measure back to continuous so it generates an axis. Once both measures are continuous, Dual Axis becomes available, and you can overlay the two into a combined view. That's exactly what C describes, making it the correct answer. A is wrong because converting Month to discrete addresses the dimension on Columns, not the measures on Rows. Changing Month doesn't resolve the incompatibility between your two measures, and "synchronizing headers" isn't a real Tableau workflow for dual axis. B goes in the opposite direction — converting the continuous measure to discrete would leave you with two discrete measures, meaning zero axes. You'd now have no axis at all, making Dual Axis even less accessible than before. D is a nonsense option in this context. Moving a measure to Filters removes it from the view entirely, and there is no "Dual Axis" option within a filter menu. This choice misrepresents how Tableau's interface works. As a study tip: when Dual Axis is unavailable, your first diagnostic question should always be "do I have two continuous measures on Rows?" If not, that's your fix.

Question 7

A dual-axis chart uses circles for Sales and a line for Profit. An analyst changes the mark type from the All Marks card to Line and unexpectedly turns both layers into lines.

How should the analyst restore the intended mark types without rebuilding the axes?

  1. Select the SUM(Sales) Marks card and choose Circle, then select the SUM(Profit) Marks card and choose Line. (correct answer)
  2. Select the primary axis and choose Circle, then select the secondary axis header and choose Line.
  3. Select the All Marks card and choose Automatic, then synchronize the axes a second time.
  4. Select Measure Names on the Data pane and assign Circle to Sales and Line to Profit aliases.
Explanation: When working with dual-axis charts in Tableau, the key concept to understand is the Marks card hierarchy. Every dual-axis chart has three Marks cards: one labeled "All," one for the first measure, and one for the second measure. The "All" card acts as a global override — changes there cascade to both layers simultaneously, which is exactly what caused the analyst's problem. To fix mismatched mark types independently, you need to target each measure's individual Marks card. Selecting the SUM(Sales) card and setting it to Circle, then selecting the SUM(Profit) card and setting it to Line, restores each layer separately without touching the axes or rebuilding anything. That's why A is correct — it leverages the individual Marks cards to assign distinct mark types to each axis layer. B is wrong because you don't assign mark types by clicking on axis headers. Axis headers control formatting, reference lines, and axis ranges — not mark types. Tableau simply doesn't offer mark-type selection through the axis itself. C is wrong on two counts: setting the "All" card to Automatic won't restore previously customized individual mark types, and synchronizing axes is about aligning scale ranges — it has no effect on mark types whatsoever. D is wrong because Measure Names is a dimension used in blended charts — it doesn't have aliases that control mark types, and mark assignments aren't made through the Data pane at all. A useful rule of thumb: whenever a dual-axis chart needs different mark types per layer, always work from the individual Marks cards, never the "All" card.

Question 8

Order Date is on Columns as a continuous month. SUM(Sales) and SUM(Return Amount) are on Rows, producing two vertically stacked panes. The analyst wants to overlay the existing marks without replacing the measures with Measure Values.

Which action directly changes the view to the requested structure?

  1. Right-click the second measure pill or its axis, select Dual Axis, and then configure the two measure Marks cards. (correct answer)
  2. Right-click the first measure pill, select Discrete, and then place both measures on the All Marks card.
  3. Drag Measure Names to Rows, remove both measure pills, and select a single continuous Measure Values axis.
  4. Right-click the date axis, select Dual Axis, and then assign each measure to a separate date level.
Explanation: When you have two separate measure pills on Rows producing stacked panes and want to overlay them into a single shared space, you're working with Tableau's Dual Axis feature — not Measure Values, which is a different blending mechanism entirely. The key move is what answer A describes: right-clicking the second measure pill (or its axis) and selecting Dual Axis. This collapses the two stacked panes into one synchronized view where both measures share the same plot area. You then get independent Marks cards for each measure, letting you configure mark types, colors, and sizes separately — exactly what "overlay without replacing" means. This is the direct, purpose-built path Tableau provides for this scenario. Answer B goes off track because switching a pill to Discrete changes axis behavior (producing headers instead of a continuous axis) and doesn't overlay anything — stacking and blending are still separate issues. Answer C describes the Measure Names/Measure Values approach, which the question explicitly rules out; dragging Measure Names to Rows replaces individual measure pills with a combined field, losing granular Marks card control. Answer D misidentifies where Dual Axis lives — you right-click a measure axis, not the date axis. Date axes don't offer Dual Axis because that option is about synchronizing two measure scales, not time levels. Study tip: Memorize that Dual Axis is triggered from the second measure pill or its vertical axis — right-click, select Dual Axis. If a question mentions overlaying measures while keeping independent mark control, that's your signal. Measure Values is the other multi-measure technique, but it merges control rather than preserving it.

Question 9

A designer wants Revenue to determine the primary scale and Cost to appear on the secondary axis. Both are continuous currency measures. The final chart must use a synchronized scale.

Which setup most reliably preserves the intended primary-secondary relationship?

  1. Place both measures in Measure Values, apply Dual Axis to Measure Names, and set Revenue as the default format.
  2. Place Cost before Revenue on the same shelf, apply Dual Axis to Revenue, and synchronize the Revenue axis to Cost.
  3. Place Revenue on Rows and Cost on Columns, apply Dual Axis to Revenue, and synchronize both worksheet directions.
  4. Place Revenue before Cost on the same shelf, apply Dual Axis to Cost, and synchronize the Cost axis to Revenue. (correct answer)
Explanation: When building a dual-axis chart in Tableau, order and direction matter enormously. The key rule to internalize: whichever measure receives the Dual Axis command becomes the secondary axis, and the synchronization always anchors the secondary axis to the primary one — not the other way around. With that framework in mind, D is the correct setup. Placing Revenue before Cost on the same shelf establishes Revenue as the primary measure. Applying Dual Axis to Cost promotes it to the secondary axis. Synchronizing the Cost axis to Revenue then locks both scales together while respecting Revenue as the scale authority — exactly what the designer intended. Here's why the other options fail. A uses Measure Values and Measure Names, which consolidates both measures onto a single axis rather than creating two independent axes — dual axis functionality is lost entirely, and there's no meaningful primary-secondary distinction. B places Cost before Revenue, which makes Cost the primary axis by default; applying Dual Axis to Revenue then inverts the intended relationship, making Revenue secondary when it should be primary. Synchronizing Revenue to Cost compounds the error. C places the measures on different shelves (Rows and Columns), which creates a scatterplot layout, not a dual-axis chart — Dual Axis requires both measures to live on the same shelf. The strategy tip to carry forward: on dual-axis questions, always trace two things — which measure appears first (that's your primary) and which measure receives the Dual Axis command (that's your secondary). The synchronization always flows from secondary toward primary.

Question 10

A synchronized dual-axis view contains SUM(Sales) as bars and SUM(Profit) as a line. The analyst wants Region to color both layers, but wants labels to appear only on the Profit line.

Which Marks card configuration meets both requirements with the least duplication?

  1. Place Region on Color on the All Marks card, and place the label field only on the SUM(Profit) Marks card. (correct answer)
  2. Place Region on Color on the SUM(Sales) card, and place the label field on the All Marks card.
  3. Place Region on Color and the label field on the All Marks card, then hide labels from the primary axis.
  4. Place Region on Color on the SUM(Profit) card, and place the label field only on the SUM(Sales) Marks card.
Explanation: When working with dual-axis views in Tableau, the Marks card hierarchy is essential to understand: the All Marks card acts as a shared layer that applies formatting to both mark types simultaneously, while each individual Marks card (SUM(Sales) and SUM(Profit)) controls only its own layer. The challenge here is applying color globally but labels selectively. Answer A is correct because placing Region on Color on the All Marks card efficiently colors both the bar and line layers without repeating the configuration on each individual card. Then, placing the label field only on the SUM(Profit) Marks card restricts labels to just the line — exactly what's needed. This is the minimum number of steps with zero redundancy. Answer B fails because placing Region on Color only on the SUM(Sales) card colors the bars but leaves the Profit line uncolored by Region. Moving the label to All Marks would then apply labels to both layers, violating the label-only-on-Profit requirement. Answer C adds unnecessary work. Placing labels on the All Marks card applies them to both layers, and then manually hiding labels from one axis is a workaround that creates maintenance overhead — not a clean configuration. Answer D is essentially backwards: Region on Color only on the SUM(Profit) card leaves Sales uncolored, and placing labels on the SUM(Sales) card puts labels on the wrong mark type entirely. Study tip: Think of the All Marks card as a "broadcast" channel — use it when you want something applied universally, and use individual Marks cards for layer-specific exceptions. This hierarchy question pattern appears frequently on the Tableau exam.