Tableau Quiz: Map Layers
10 questions · exam conditions
0:00
Map LayersQuestion 1 of 10

A single data source contains state geography, city geography, state profitability, and city sales. One worksheet must display states as filled polygons colored by profitability and cities as sized circles colored by sales.

Which approach provides the required independent mark types and encodings in one map?

Create separate marks layers for state and city geography, then configure each layer's Marks card independently.
Place both geographic fields on Detail in one marks layer, then assign one shared mark type and color scale.
Place city sales on Size and state profitability on Color in one marks layer, then enable map washout.
Use a background demographic layer for states and place city geography on the worksheet's only Marks card.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Map Layers

Practice Map Layers 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 Map Layers, 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 single data source contains state geography, city geography, state profitability, and city sales. One worksheet must display states as filled polygons colored by profitability and cities as sized circles colored by sales.

Which approach provides the required independent mark types and encodings in one map?

  1. Create separate marks layers for state and city geography, then configure each layer's Marks card independently. (correct answer)
  2. Place both geographic fields on Detail in one marks layer, then assign one shared mark type and color scale.
  3. Place city sales on Size and state profitability on Color in one marks layer, then enable map washout.
  4. Use a background demographic layer for states and place city geography on the worksheet's only Marks card.
Explanation: When a single map needs to display two different geographic levels with completely different mark types and independent encodings, you should immediately think about Marks layers — Tableau's mechanism for stacking multiple independent visualization layers on one map sheet. Marks layers let you add separate entries to the Marks card panel, each with its own mark type, color, size, and detail configuration. This is exactly what the scenario requires: filled polygons (a "Map" mark type) for states colored by profitability, and circles for cities sized by sales volume. Answer A is correct because creating separate Marks layers gives each geography its own independent card, so state profitability drives one color scale and city sales drives an entirely separate size and color encoding — no compromise required. Answer B fails because placing both fields on Detail in a single marks layer forces you to choose one shared mark type and one shared encoding channel. You cannot have polygons and circles simultaneously, nor two independent color scales, within the same layer. Answer C is a creative misread of Tableau's architecture. Color and Size are separate channels on one Marks card, but they still apply to a single mark type. You cannot render states as filled polygons and cities as circles using one mark type, and "map washout" is a background map styling option — it doesn't resolve the encoding conflict. Answer D confuses demographic background layers (static reference imagery from Tableau's map service) with actual data-driven mark layers. A demographic layer cannot encode your state profitability data dynamically. Study tip: Whenever a question describes two geographic levels needing different mark types on one sheet, that's your signal that Marks layers are the intended solution — not workarounds within a single Marks card.

Question 2

A map contains a primary layer of store circles and a second marks layer used only to display regional text labels. Users should be able to select stores, but clicking the regional labels must not select marks or interfere with selecting stores beneath them.

Which layer configuration best meets these requirements?

  1. Hide the regional-label layer and add the same text to the background map's place-name layer.
  2. Disable selection for the store layer while keeping selection enabled for the regional-label layer.
  3. Move the regional-label layer below the background map and leave both marks layers selectable.
  4. Disable selection for the regional-label layer while keeping the store layer visible and selectable. (correct answer)
Explanation: When working with dual-layer maps in Tableau, the key question is always: which layer needs interaction, and which layer is purely visual? Tableau allows you to control selection behavior independently per marks layer, so you never have to sacrifice visibility to prevent unwanted click interference. Here, the regional labels exist solely for context — users should be able to click through them to select store circles underneath. The cleanest solution is D: disable selection on the regional-label layer while leaving the store layer fully selectable. This way, clicks on label areas pass through to the stores below, and the labels remain visible without interrupting the user's workflow. A is a workaround that sidesteps the actual feature entirely. Background map place-name labels are not marks layers — they can't be styled or controlled the same way, and you'd lose the flexibility that a dedicated marks layer provides. This answer misunderstands the architecture. B inverts the logic completely. Disabling selection on the store layer defeats the entire purpose — users can no longer select stores, which is the primary interaction requirement. Keeping the label layer selectable only adds confusion. C is a red herring about layer ordering. Moving the regional-label layer below the background map would likely hide it entirely, and layer stacking order doesn't control whether clicks register on a marks layer — the selection toggle does. As a study tip, remember that Tableau's dual-axis and multi-marks-layer setups often involve tradeoffs between visibility and interactivity. When a question describes a "display-only" layer, your instinct should immediately be: disable selection on that layer, not the functional one.

Question 3

For a minimalist presentation, an author wants to display only geocoded customer marks on a blank canvas. The marks and their geographic positions must remain intact, but no streets, borders, land shading, or place names should appear.

Which change most directly produces this result?

  1. Select None as the background map while retaining the customer marks layer. (correct answer)
  2. Remove the customer geography from the view and retain the current background map.
  3. Set background washout to its minimum and hide the customer marks layer.
  4. Disable selection on every map layer while retaining the current background style.
Explanation: When working with maps in Tableau, it helps to distinguish between two independent layers: the background map (the cartographic tiles providing streets, borders, labels, and shading) and the data layer (your plotted marks). The question asks you to eliminate everything from the background while keeping geocoded marks visible — so you need to control these two layers separately. Selecting None as the background map style (answer A) does exactly this. In Tableau's Map menu under Background Maps, choosing "None" strips away all cartographic content — streets, country borders, land coloring, place names — leaving a blank canvas. Your customer marks remain plotted at their correct geographic coordinates because the data layer is untouched. This is the most direct path to the described result. Answer B gets it completely backwards: removing the customer geography discards your marks while the map background remains, which is the opposite of what's needed. Answer C introduces a common misconception about the washout slider. Washout controls the opacity of the background map — setting it to minimum fades the map to white but doesn't truly remove it, and hiding the marks layer defeats the entire purpose of keeping customers visible. Answer D is a distractor that conflates layer interactivity (selection behavior) with layer visibility. Disabling selection on map layers changes how users interact with features, not whether background cartography appears. A useful rule of thumb: when a question asks you to remove something from a Tableau view, look for explicit hide, remove, or "None" options — adjusting sliders or interactivity settings rarely produces a clean removal.

Question 4

A hiking-access map uses pale orange trailhead circles. The current Light background style lacks terrain and outdoor context, but the author must preserve the trailhead layer's calculations, colors, sizes, and labels.

Which modification best addresses the issue?

  1. Convert the trailhead circles to density marks so terrain is inferred from concentrations of trailheads.
  2. Replace the trailhead marks layer with a terrain demographic layer and reuse its existing labels.
  3. Increase washout on the Light background style and disable all terrain-related map layers.
  4. Change to an outdoor-oriented background style and enable appropriate terrain reference layers. (correct answer)
Explanation: When working with Tableau maps, you need to distinguish between two independent layers: the background style (the base map tile that provides geographic context) and mark layers (your data-driven visualizations plotted on top). The key insight is that changing the background style never affects your marks — their calculations, colors, sizes, and labels are completely preserved. Here, the problem is a mismatch between the background style and the map's purpose: a hiking-access map needs terrain context, but the Light style is too plain. The fix is to swap the background to something like the Outdoors style, then enable terrain reference layers (contours, hillshading, parks) through the Map Layers dialog. This directly solves both problems — you gain terrain context while every property of the trailhead circles remains untouched. That makes D the correct answer. A is wrong because converting marks to density/heatmap style would destroy the individual trailhead circles and their associated properties. Density marks also don't generate terrain information — they only visualize data concentration. B is wrong because replacing the trailhead layer with a demographic layer discards exactly what the question says must be preserved: the trailhead calculations, colors, sizes, and labels. You'd lose the core data. C is the sneakiest distractor — increasing washout actually reduces background detail, making terrain context worse, not better. Disabling terrain layers compounds the problem rather than solving it. A reliable strategy: when a Tableau map question mentions preserving mark properties, look for the answer that changes background settings only. Background and mark layers are independent — changing one never touches the other.

Question 5

A workbook author is troubleshooting a map with three marks layers. The author wants to temporarily stop displaying a service-area polygon layer while preserving its fields, formatting, and layer configuration for later reuse.

Which action should the author take?

  1. Remove the service-area marks layer and use Undo whenever the layer must be restored.
  2. Hide the service-area marks layer, then show it again when the troubleshooting is complete. (correct answer)
  3. Set the background map to None and retain all three visible data-mark layers.
  4. Disable selection on the service-area layer while leaving its polygon marks displayed.
Explanation: When working with multi-layer maps in Tableau, a key distinction to understand is the difference between removing something and hiding it. This question tests whether you know how to temporarily suppress a marks layer without losing any of its configuration. Tableau's Maps with multiple marks layers let you toggle individual layers on or off using the visibility (eye) icon in the Marks card. Hiding the service-area layer — answer B — does exactly what the scenario requires: the layer disappears from the view, but all its fields, formatting, mark type settings, and layer-specific configurations remain fully intact. When troubleshooting is complete, you simply show it again with one click. Answer A is a destructive workaround. Removing the layer permanently deletes its configuration, and relying on Undo is fragile — close the workbook, publish it, or perform too many actions, and that undo history is gone. This approach risks losing exactly what the author wants to preserve. Answer C addresses the background map tiles, not the marks layers themselves. Setting the background to None would remove geographic context (streets, borders, terrain), but all three data-driven marks layers — including the service-area polygons — would still render on top. This doesn't hide the polygon layer at all. Answer D controls interactivity, not visibility. Disabling selection simply prevents users from clicking that layer's marks; the polygons remain fully visible on the map, which contradicts the goal of temporarily hiding them. The study tip here: on Tableau exam questions involving "preserving" layer settings, the answer almost always involves a non-destructive toggle like hide/show rather than delete-and-redo.

Question 6

A map uses a Tableau background map. The author must retain state borders and city names but remove road lines because they resemble line marks representing delivery routes.

What should the author do?

  1. Set the background map to None, then reproduce state borders and city names using mark labels.
  2. Increase background-map washout until roads disappear while borders and city names remain unchanged.
  3. Select a different map projection that suppresses roads but preserves borders and place names.
  4. Open Map Layers, clear the roads-related layer, and leave borders and place names enabled. (correct answer)
Explanation: When working with Tableau background maps, it helps to know that map content is organized into discrete, toggleable layers — not a single monolithic image. This means you have granular control over what geographic elements appear, which is exactly what this question is testing. The right move here is D: open the Map Layers pane (via the Map menu) and simply uncheck the roads layer while leaving state borders and city names enabled. Each layer operates independently, so removing roads has zero effect on the other elements. This is the precise, surgical solution the scenario demands. Here's why the other options fall short. A is impractical because setting the background to None strips everything — you'd then have to manually reconstruct borders and city labels using marks and labels, which is a cumbersome workaround when a built-in tool already solves the problem cleanly. B misunderstands what washout does: it fades the entire map uniformly, so roads, borders, and city names all become lighter together. You cannot selectively washout one layer while keeping others vivid. C reflects a common misconception — map projections control how the earth's curvature is translated onto a flat surface (Mercator, Robinson, etc.), not which content layers are visible. No projection suppresses roads while preserving other elements. The study tip here is to memorize the Map Layers pane as your go-to tool anytime a Tableau question involves selectively showing or hiding geographic content. If the question says "remove X but keep Y" on a background map, that's your signal — Map Layers, not projections, not washout, not rebuilding from scratch.

Question 7

A map displays company locations as circles across the United States. Tableau's built-in U.S. demographic data layers are available. The analyst wants county-level population density as contextual shading behind the locations but does not need to filter or select counties and does not want to add population records to the company data source.

What should the analyst do?

  1. Place company population on Color and change the company-location marks from circles to filled maps.
  2. Add a county-level population-density data layer from the Map Layers pane behind the location marks. (correct answer)
  3. Enable the county-borders background layer and use washout to generate population-density shading.
  4. Duplicate the location marks layer and aggregate the duplicated circles to the county geographic role.
Explanation: When a question asks about adding contextual geographic shading without touching your data source or filtering behavior, you're being tested on Tableau's Map Layers feature — a tool specifically designed to overlay built-in demographic and reference data behind your marks. Tableau ships with U.S. demographic data layers (population density, median income, etc.) accessible through the Map Layers pane (Map menu → Map Layers). You simply check the desired layer — such as county-level population density — and it renders as background shading behind your existing marks. It requires no additional data source, no new calculated fields, and no changes to mark types. This is exactly what option B describes, making it the correct choice. Option A fails on two fronts: it requires population data to already exist in the company data source (which the analyst explicitly wants to avoid), and switching to filled maps replaces the circle marks entirely rather than adding shading behind them. Option C sounds plausible, but county-borders is a reference layer that draws boundary lines only — it has no shading or density-encoding capability, and "washout" is a map style setting that fades the basemap, not a way to generate data-driven shading. Option D misunderstands how geographic roles work; duplicating a marks layer and reassigning a geographic role doesn't aggregate or pull in external demographic data — it would just attempt to re-plot your existing records differently. A useful pattern to remember: whenever a scenario involves adding external geographic context (demographics, census data, reference boundaries) without modifying your data source, think Map Layers pane first.

Question 8

An organization hosts an approved Web Map Service containing current parcel imagery. A Tableau worksheet already displays inspection points, and the author wants the hosted service to replace the standard Tableau basemap without converting the imagery into inspection records.

Which workflow is appropriate?

  1. Connect to the Web Map Service as a relational data source and place its URL on Detail.
  2. Import the service as a spatial file and join each image tile to an inspection record.
  3. Add the WMS server as a background map, select it, and retain inspections as data marks. (correct answer)
  4. Add the service URL as a dashboard web object positioned beneath the inspection worksheet.
Explanation: Whenever you see a question about external map services in Tableau, ask yourself two things: Where does the imagery belong in the Tableau architecture, and should it behave as data or as a visual backdrop? A Web Map Service (WMS) provides tiled imagery meant to serve as a reference layer — not as rows in a dataset — so it belongs in Tableau's background map layer, not in a data source connection. That reasoning points directly to C. Tableau's Map menu lets you add a WMS server as a background map, replacing or supplementing the default basemap with your organization's hosted imagery. Your inspection points remain as marks driven by the actual data source, sitting visually on top of the imagery — exactly what the scenario requires. A is wrong because WMS is not a relational database. You cannot create a meaningful SQL-style connection to it, and placing a URL on Detail would add a text field to your marks, not render map tiles as a background layer. B is wrong because WMS tiles are not spatial files (like Shapefiles or GeoJSON). Even if you could import them, joining image tiles to inspection records would be architecturally nonsensical — image tiles have no row-level relationship to point data. D is wrong because a dashboard web object is an embedded browser panel, not an integrated map canvas. It cannot interact with Tableau's coordinate system, so inspection marks would not align geographically with the imagery beneath them. The study tip here: on Tableau exam questions involving external imagery or custom maps, distinguish between background maps (visual, geographic context) and data sources (records you analyze). WMS always means background map.

Question 9

A worksheet contains dark blue proportional-symbol marks over a detailed Tableau background map. The analyst wants roads, boundaries, and place names to remain visible as geographic context, but the background currently competes with the data marks.

Which action best satisfies the requirement without changing the marks' color or opacity?

  1. Change the background map to None, leaving only the data marks and geographic axes in the view.
  2. Increase Washout in the Map Layers pane while retaining the required background-map layers. (correct answer)
  3. Reduce opacity on the marks layer and keep the background map at its current intensity.
  4. Change the marks to a lighter color and disable the background map's place-name layer.
Explanation: Whenever you see a Tableau question about a busy background map competing with data marks, think about the Map Layers pane — specifically the tools it gives you to reduce visual noise without touching the marks themselves. The constraint here is critical: you cannot change the marks' color or opacity, so the solution must come from adjusting the map, not the data layer. The Washout slider in Map Layers fades the background map toward white, making it less visually dominant while keeping all selected layers — roads, boundaries, place names — intact and readable. This is exactly what the analyst needs: geographic context preserved, background quieted, marks untouched. That makes B the correct answer. A fails because removing the background entirely eliminates the roads, boundaries, and place names the analyst specifically wants to retain. You'd have data marks floating over blank space. C directly violates the stated constraint — reducing mark opacity is exactly what the question forbids, and it also makes the dark blue marks harder to read rather than clarifying the map underneath. D is a double violation: it changes the marks' color and disables the place-name layer, both of which the requirement explicitly rules out. A useful rule of thumb for the Tableau exam: when a question involves background map visibility, your first instinct should be the Map Layers pane. It controls which layers appear (terrain, coastlines, streets, labels) and the Washout slider independently controls overall map intensity — a clean separation between what appears and how prominently it appears.

Question 10

A map has a filled county-polygon marks layer and a circle layer for facilities. Both layers are visible, but some facility circles are obscured by opaque county polygons. The facility coordinates and filters are correct.

What is the most direct correction?

  1. Move Facility Name to Label so Tableau renders each facility after drawing all polygon marks.
  2. Increase background-map washout so the facility circles are drawn above the county polygons.
  3. Reorder the marks layers so the facility layer is above the county-polygon layer. (correct answer)
  4. Disable selection on the county layer so its polygons no longer cover facility circles.
Explanation: When working with dual-layer maps in Tableau, think of marks layers like transparent sheets stacked on top of each other — whatever is on top visually covers what's below. This question tests your understanding of how Tableau's marks layer ordering controls rendering sequence on a map. The root problem here is straightforward: the county polygons are opaque and rendering on top of the facility circles, hiding them. The most direct fix is to reorder the layers so the facility circle layer sits above the county-polygon layer in the Marks card stack. Tableau draws layers from bottom to top, so placing facilities higher in the order ensures they render last and remain visible. That's exactly what C does — directly resolving the visual overlap at its source. A is wrong because moving Facility Name to the Label shelf controls text labels, not the rendering order of circle marks themselves. Labels appear on top of marks, but this does nothing to make the underlying circle marks visible through opaque polygons. B is a common trap — background map washout adjusts the basemap's brightness, not the stacking order of your own marks layers. Washing out the background won't move county polygons below facility circles. D is wrong because disabling selection is a interactivity setting; it has no effect on how or where marks are drawn visually. As a study tip: whenever a Tableau question describes one marks layer covering another, your first instinct should be layer order in the Marks card — it's almost always the most direct lever for controlling what appears on top.