Tableau Quiz: Creating Maps
10 questions · exam conditions
0:00
Creating MapsQuestion 1 of 10

A field named Region Name contains the values Georgia, Jordan, France, and Japan. It was mistakenly assigned the State/Province geographic role. On the resulting map, Georgia is plotted as a U.S. state while the other values are unknown.

Which correction should be made to create one symbol for each intended nation?

Retain the State/Province role and add United States to Detail so all four values receive geographic context.
Change Region Name to the Country/Region geographic role and use the field to define the map's level of detail.
Change Region Name to the City geographic role and use generated Latitude as the map's level of detail.
Remove the geographic role and convert Region Name to a measure before placing it on the Marks card.
← Back to quizzes

Tableau Quiz

Tableau Quiz: Creating Maps

Practice Creating Maps 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 Creating Maps, 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 field named Region Name contains the values Georgia, Jordan, France, and Japan. It was mistakenly assigned the State/Province geographic role. On the resulting map, Georgia is plotted as a U.S. state while the other values are unknown.

Which correction should be made to create one symbol for each intended nation?

  1. Retain the State/Province role and add United States to Detail so all four values receive geographic context.
  2. Change Region Name to the Country/Region geographic role and use the field to define the map's level of detail. (correct answer)
  3. Change Region Name to the City geographic role and use generated Latitude as the map's level of detail.
  4. Remove the geographic role and convert Region Name to a measure before placing it on the Marks card.
Explanation: When working with geographic roles in Tableau, the role you assign tells Tableau what kind of geographic entity each value represents. Mismatched roles cause plotting errors — Tableau looks in the wrong geographic layer and either misidentifies values or marks them unknown. Here, the field contains country names, but the State/Province role forces Tableau to search a state-level database. Georgia matches a U.S. state, so it gets plotted — incorrectly — as one. Jordan, France, and Japan have no state-level matches, so they go unrecognized entirely. The fix is straightforward: assign the Country/Region geographic role to Region Name. This tells Tableau to look in its country-level database, where all four values resolve correctly. Placing Region Name on the Marks card (via Detail, for example) then gives each country its own symbol on the map — exactly the intended result. B is correct. A is wrong because adding United States to Detail doesn't fix the underlying mismatch. The State/Province role still causes Tableau to interpret values as states, not nations. Jordan, France, and Japan would remain unknown regardless. C is wrong because the City role is even more granular than State/Province — it would make the mismatch worse, not better. Cities named Georgia, Jordan, France, and Japan may or may not exist, and the results would be unreliable and incorrect. D is wrong because converting a geographic field to a measure strips away its geographic meaning entirely. Measures represent quantitative values; doing this would make mapping impossible. Study tip: On geographic role questions, always ask two things: What does the data actually represent? and Does the assigned role match that level? Mismatches between role and content are a classic Tableau troubleshooting scenario.

Question 2

A symbol map should display one circle per state, sized by total Sales. State has the correct State/Province geographic role. After Order ID is added to Detail for a tooltip requirement, the map displays many overlapping circles within each state.

What is the best way to restore one mark per state while preserving total Sales as the size encoding?

  1. Keep both dimensions on Detail, change Circle marks to Map marks, and place Sales on Color.
  2. Keep Order ID on Detail, convert Sales to a dimension, and change the aggregation from SUM to ATTR.
  3. Remove State from Detail, keep Order ID as the geographic level, and leave aggregated Sales on Size.
  4. Remove Order ID from Detail, keep State as the geographic detail, and leave aggregated Sales on Size. (correct answer)
Explanation: Whenever a Tableau map shows unexpected duplicate or overlapping marks, the root cause is almost always the level of detail — specifically, a dimension on the view that's breaking aggregation at a finer grain than you want. Here, adding Order ID to Detail tells Tableau to draw one mark per unique Order ID within each state, which destroys the one-circle-per-state behavior you need. The fix is straightforward: remove Order ID from Detail. With only State driving the level of detail, Tableau aggregates Sales back to the state level, SUM(Sales) sizes one circle per state correctly, and your map is restored. That's exactly what D does — and it works without touching Sales or any mark type. If you still need Order ID in a tooltip, you can reference it via a calculated field or LOD expression without placing it directly on the Marks card. Looking at the wrong answers: A changes the mark type to Map and moves Sales to Color, which doesn't address the real problem — Order ID still fragments the view into order-level marks. B is doubly flawed: converting Sales to a dimension loses the aggregation you need for sizing, and ATTR is an aggregation for dimensions, not a meaningful fix here. C removes State from Detail instead of Order ID, which eliminates your geographic grouping entirely — Tableau would then treat Order ID as the geographic anchor, which makes no geographic sense and breaks the state-level map. A quick rule of thumb: every dimension on the Marks card increases mark granularity. When your map shows too many marks, audit Detail first and remove any field that's fragmenting beyond your intended level of detail.

Question 3

A filled county map contains many unknown locations because the County field includes names such as Washington and Jefferson that occur in multiple states. A separate State field is available, but neither field has yet been assigned a geographic role.

Which approach is most likely to resolve the locations and preserve county-level filled polygons?

  1. Assign County the State/Province role and State the Country/Region role, then place County on Color.
  2. Assign both County and State the County role, then place only State on Detail to select the county polygons.
  3. Assign County the County role and State the State/Province role, then include both in the view with State providing geographic context. (correct answer)
  4. Concatenate County and State into a numeric measure, remove both geographic roles, and use that measure on Detail.
Explanation: When Tableau encounters ambiguous geographic names like "Washington" or "Jefferson," it needs additional context to resolve them to unique locations. The key concept here is geographic role hierarchy: Tableau uses higher-level geographic fields to disambiguate lower-level ones, but only when both fields are properly configured and present in the view. Assigning County the County geographic role and State the State/Province role — then including both in the view — gives Tableau exactly what it needs. State acts as the disambiguating context, allowing Tableau to distinguish "Washington County, PA" from "Washington County, TX." The county-level filled polygons are preserved because the County field still drives the map marks. This is why C is correct. A is wrong because swapping the roles inverts the geographic hierarchy. Assigning County as State/Province means Tableau treats county names as states, which produces the wrong polygon type and worsens ambiguity rather than resolving it. B is wrong because assigning both fields the same County role gives Tableau no hierarchical context. Two County-role fields don't tell Tableau which state a county belongs to — they just create redundancy. State must carry the State/Province role to function as a parent geography. D is wrong on multiple levels. Concatenating fields into a numeric measure strips away all geographic meaning. Tableau cannot resolve a number to a map polygon — geographic roles require string-based geographic fields, not measures. A useful pattern to remember: whenever you see ambiguous place names on the Tableau exam, the fix almost always involves assigning the correct role to a parent geography and including it in the view to provide context.

Question 4

Country and State are assigned the Country/Region and State/Province geographic roles and are arranged in a Country-to-State hierarchy. A filled map currently displays country polygons colored by Sales. The analyst now needs state polygons while retaining country context for geocoding.

Which action best changes the geographic level without discarding the hierarchy context?

  1. Expand the Country level to State in the hierarchy and keep Sales on Color with the Map mark type. (correct answer)
  2. Move State to Size while leaving Country as the only geographic field defining the marks.
  3. Change Country to the State/Province role and keep State hidden from the map worksheet.
  4. Convert State to a continuous measure and replace Sales on Color with the State values.
Explanation: When working with geographic hierarchies in Tableau, the core principle is that expanding a hierarchy drills down to a more granular level while preserving the parent-level context that enables accurate geocoding. This is exactly what the question is testing. Expanding the Country level to reveal State within an established Country-to-State hierarchy — as described in A — is the correct approach. Tableau uses the parent Country field to disambiguate states that share names across countries (for example, "Georgia" the U.S. state vs. "Georgia" the country). Keeping the Map mark type with Sales on Color means the view simply transitions from country polygons to state polygons without losing any geographic or analytical context. The hierarchy does the heavy lifting. B is wrong because moving State to Size while leaving Country as the active geographic mark doesn't change which polygons are rendered — you'd still see country-level shapes, just sized by a state-level field, which is a mismatch that produces unreliable results. C is a trap: reassigning Country's geographic role to State/Province corrupts the original field's meaning and breaks the hierarchy. Hidden fields don't contribute geocoding context either, so states would lose their disambiguation anchor. D confuses dimension-based mapping with measure behavior. Converting State to a continuous measure removes its geographic role entirely, so Tableau can no longer render it as a polygon layer. Replacing Sales on Color with numeric state values also defeats the original analytical goal. Study tip: On Tableau exam questions involving maps and hierarchies, always ask yourself whether the proposed action preserves the geographic role and hierarchy structure. Drilling down through a hierarchy is almost always safer than reassigning roles or converting field types.

Question 5

A store data source contains numeric fields Store Latitude and Store Longitude, plus Store ID and Sales. The analyst needs one proportional symbol at each store's exact recorded coordinates rather than at Tableau's built-in city centroid.

Which configuration will create the intended symbol map?

  1. Assign both coordinate fields the City geographic role, place Store Latitude on Rows and Store Longitude on Columns, add Store ID to Detail, and use the Map mark type.
  2. Assign the Latitude and Longitude roles, place Store Latitude on Columns and Store Longitude on Rows, add Store ID to Detail, and place Sales on Color.
  3. Assign the Latitude and Longitude roles, place Store Longitude on Columns and Store Latitude on Rows, add Store ID to Detail, and place Sales on Size. (correct answer)
  4. Leave both coordinate fields without geographic roles, place their discrete values on the Rows and Columns shelves, add Store ID to Color, and use Polygon marks.
Explanation: When mapping custom coordinates in Tableau, the critical details are geographic role assignment, shelf placement, and mark type. Tableau's convention is strict: Longitude goes on Columns (the horizontal axis) and Latitude goes on Rows (the vertical axis), mirroring how an x/y coordinate plane works on a map. Option C follows this exactly — Store Longitude on Columns, Store Latitude on Rows, both fields assigned the proper Latitude/Longitude geographic roles, Store ID on Detail to generate one mark per store, and Sales on Size to create the proportional symbol effect. This bypasses Tableau's built-in geocoding entirely, plotting marks at the precise recorded coordinates rather than estimated city centroids. Option A fails on two counts: assigning coordinate fields the City role tells Tableau to snap points to city centroids (exactly what the question wants to avoid), and the Map mark type doesn't create proportional symbols — Circle or automatic marks do. Option B assigns the correct geographic roles and places Sales on Color rather than Size — a meaningful distinction because "proportional symbol map" specifically means symbol size encodes the measure. Color encodes a different dimension entirely and wouldn't produce proportional symbols. Option D leaves the fields without geographic roles, which means Tableau treats them as plain numbers rather than spatial coordinates. Discrete values on shelves produce a table-like grid, and Polygon marks require a specific path/polygon structure — neither produces a symbol map. A good rule of thumb: memorize Longitude → Columns, Latitude → Rows as a locked pairing. Exam questions frequently swap these to test whether you know the convention cold.

Question 6

A data source contains a text field named State and a measure named Sales. State currently has a data type of String and no geographic role. An analyst wants each U.S. state polygon shaded according to total Sales.

Which sequence of actions will create the intended view?

  1. Assign State the State/Province geographic role, add State to the view, change the mark type to Map, and place Sales on Color. (correct answer)
  2. Assign State the State/Province geographic role, add State to the view, retain Circle marks, and place Sales on Size.
  3. Assign State the City geographic role, add State to the view, change the mark type to Map, and place Sales on Color.
  4. Convert State to a measure, add it to the view, change the mark type to Polygon, and place Sales on Detail.
Explanation: When you want to shade U.S. state polygons by a measure in Tableau, two things must be true: the dimension needs the right geographic role so Tableau can match it to map polygons, and the mark type must be set to Map (filled polygons) rather than any point-based mark. Answer A gets both right. Assigning State the State/Province geographic role tells Tableau to look up U.S. state boundaries, placing State on the view generates the filled-polygon map, switching to Map marks renders those polygons, and putting Sales on Color shades each state by its total Sales value — exactly what the analyst wants. Answer B fails because it retains Circle marks and puts Sales on Size. Circle marks plot a single dot per state, not a filled polygon, and sizing those circles is a bubble map, not a choropleth. The intent is shading (color), not sizing. Answer C assigns the City geographic role instead of State/Province. Tableau would try to match state names to city coordinates, causing most records to fail geocoding or plot incorrectly. The geographic role must match the actual granularity of the data. Answer D converts State to a measure, which strips its geographic meaning entirely. Numeric measures can't trigger polygon map rendering by themselves, and placing Sales on Detail rather than Color wouldn't produce the shaded view regardless. A quick study tip: on Tableau exam questions about maps, always check two things — the correct geographic role for the field's granularity, and whether the mark type matches the intended visual (Map for filled polygons, not Circle or Polygon drawn manually).

Question 7

An orders data source includes City, State, Country, and Sales. It contains cities with repeated names, including Portland in multiple states and countries. The required view is one symbol for each distinct city-state-country combination, with symbol size representing Sales.

Which configuration most reliably creates the required symbol map?

  1. Assign City a City role, place City on Detail, place Sales on Size, and leave State and Country out of the view.
  2. Assign geographic roles to City, State, and Country; place all three on Detail; and place Sales on Size. (correct answer)
  3. Assign State a City role, place State and Country on Detail, and place the unassigned City field on Size.
  4. Assign geographic roles to City and Country, place Country on Detail, and place both City and Sales on Color.
Explanation: When building a symbol map with repeated city names, Tableau needs enough geographic context to distinguish between identically named places — and enough dimensional detail to plot one mark per unique combination. This question tests whether you understand how geographic roles, LOD (level of detail), and mark encoding work together. The reliable solution is B: assign geographic roles to City, State, and Country, then place all three on Detail with Sales on Size. By putting all three fields on Detail, you define the granularity of the view as the city-state-country combination, so Portland, Oregon, USA and Portland, Maine, USA each get their own mark. The geographic roles let Tableau geocode each city correctly within its state and country context, and Size encodes Sales as intended. A fails because placing only City on Detail means Tableau sees "Portland" as a single location — it can't distinguish between Portlands in different states or countries, collapsing multiple cities into one mark or geocoding ambiguously. C is nonsensical: assigning a City geographic role to the State field forces Tableau to misinterpret state names as city coordinates. Putting City on Size also makes no sense — Size should encode a measure, not a dimension. D partially works but misuses Color. Placing City on Color creates one color per city name, not one mark per city-state-country combination. With duplicate city names, you still won't reliably get distinct marks, and using Color for geographic differentiation instead of Detail is the wrong tool. Your study tip: on symbol map questions, always ask yourself two things — what defines a unique mark? (Detail shelf) and what provides geocoding accuracy? (geographic roles on all relevant fields). Granularity and roles must align.

Question 8

A field named Customer ZIP was imported as a whole number. After the field is assigned the Postal Code geographic role, many locations in the northeastern United States remain unknown. Inspection shows that values such as 02108 were imported as 2108.

What should the analyst do before rebuilding the map?

  1. Convert Customer ZIP to String, restore leading zeros to five characters, and retain the Postal Code geographic role. (correct answer)
  2. Convert Customer ZIP to String without changing its values, and assign the field the County geographic role.
  3. Keep Customer ZIP numeric, format it to display five digits, and retain the Postal Code geographic role.
  4. Keep Customer ZIP numeric, place it on Detail as a continuous measure, and use generated map coordinates.
Explanation: When Tableau geocodes postal codes, it compares field values against a built-in reference database of five-digit strings. This question tests whether you understand that geographic matching is string-based, not numeric — so data type and formatting both matter. The root problem is that importing ZIP codes as whole numbers silently dropped leading zeros. Massachusetts ZIPs like 02108 became 2108, a four-digit value that will never match Tableau's five-digit postal code reference. The fix has two parts: change the data type to String (so Tableau treats values as text, not quantities), then pad the values back to five characters by restoring the leading zero. Once the values correctly read "02108" as a string, the existing Postal Code geographic role will match them successfully. That's exactly what A describes, making it the correct answer. B is wrong because simply converting to String without fixing the values leaves you with "2108" — still a four-digit string that won't geocode. Assigning the County role makes no sense here; you have ZIP codes, not county names. C is a common trap. Numeric formatting in Tableau only changes how a number displays on screen — the underlying value stored and passed to geocoding is still 2108, not 02108. The map will remain broken. D is wrong because continuous numeric measures placed on Detail don't trigger geographic matching at all. Generated coordinates rely on other geographic fields already resolving correctly, which they aren't. Study tip: Whenever you see ZIP or postal code data imported as a number, immediately suspect truncated leading zeros — always convert to String and verify character length before geocoding.

Question 9

An analyst selects City and Profit and attempts to use Show Me to create a filled map. City has the City geographic role, but the required result is a map with geographic areas shaded by Profit rather than circles positioned at city centers.

Which change is most appropriate when the data also contains a State field?

  1. Aggregate Profit by State, assign State the State/Province role, and use State polygons with Profit on Color. (correct answer)
  2. Keep City as the geographic level, change the mark type to Circle, and place Profit on Size instead of Color.
  3. Assign City the State/Province role, keep city names unchanged, and use Map marks with Profit on Color.
  4. Convert Profit to a geographic dimension, retain City on Detail, and use Polygon marks for city boundaries.
Explanation: When building filled maps in Tableau, the key distinction is between point-based geography (like cities, which plot as circles at a coordinate) and polygon-based geography (like states or countries, which render as shaded regions). A filled map requires polygon boundaries, and Tableau can only shade areas it has polygon data for — city boundaries aren't natively available, but state boundaries are. That's why A is correct. By aggregating Profit to the State level and assigning State the State/Province geographic role, you give Tableau both the polygon boundaries it needs and a meaningful measure to shade them. Placing Profit on Color then produces exactly the filled map described — geographic areas shaded by Profit value. B misses the point entirely. Switching to Circle marks and putting Profit on Size gives you a proportional symbol map, not a filled map. You'd see bubbles over city centers, not shaded regions. C is a geographic role mismatch. Assigning City the State/Province role tells Tableau to treat city names as state names, which will either produce mapping errors or incorrectly geocode your data. You can't rename a role and expect city-level data to behave like state polygons. D introduces a fundamental misunderstanding. Profit is a quantitative measure — converting it to a geographic dimension is not a valid operation, and city boundaries aren't available as native polygon data in Tableau anyway. As a study tip: whenever a Tableau question mentions "filled map" or "shaded areas," immediately ask yourself what polygon geography is available in the data. Filled maps require polygon-capable roles — State/Province, Country, ZIP code — not point-level roles like City.

Question 10

A worksheet contains one mark per state. State has the State/Province geographic role, and the analyst must create a symbol map in which larger circles represent higher Sales while color distinguishes profitable from unprofitable states.

Which Marks card configuration meets both requirements without converting the view to a filled map?

  1. Use Map marks, place Sales on Detail, and place State on Color while leaving Profit out of the view.
  2. Use Map marks, place Sales on Color, and place Profit on Size using an appropriate continuous scale.
  3. Use Circle marks, place State on Size, and place both Sales and Profit together on the Detail property.
  4. Use Circle marks, place Sales on Size, and place Profit on Color using an appropriate diverging color treatment. (correct answer)
Explanation: When building a symbol map in Tableau, you need to keep two goals distinct: size encodes a measure (Sales), and color encodes a dimension or calculated field (profitability). The marks type must also stay as circles or symbols — not filled polygons — to avoid a filled map. Option D is the correct configuration. Using Circle marks preserves the symbol map format. Placing Sales on Size makes circles scale with revenue, directly satisfying the first requirement. Placing Profit on Color with a diverging palette (e.g., orange-blue) naturally separates profitable states (positive values) from unprofitable ones (negative values), satisfying the second requirement cleanly and intuitively. Option A fails on multiple counts: Map marks produce filled maps, not symbol maps, and placing Sales on Detail gives it no visual encoding — circles won't vary in size at all. Profit is also excluded entirely, so neither requirement is actually met. Option B also uses Map marks, which again risks a filled map view. More critically, it swaps the encodings: Sales goes on Color and Profit goes on Size. This is backwards — you want size to reflect Sales magnitude, not color, and you want color to distinguish profitability, not size. Option C uses the correct Circle marks type, but places State on Size, which makes no sense — State is a dimension with no inherent magnitude, so Tableau can't meaningfully size circles by it. Bundling both Sales and Profit onto Detail encodes neither visually. A useful rule of thumb: Size = quantitative magnitude; Color = categorical or directional distinction. Match your shelf assignments to that principle, and symbol map questions become straightforward.