• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Tableau Data Analyst

Tableau Data Analyst

Checklist progress

0/304Learned

Tableau Data Analyst

Study Checklist

  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect

Checklist progress

0/304Learned

1.1.1. Identify data source

0/6

  • Connecting Tableau Desktop to a cloud database, a local flat file, and a published data source within the same workbook — which native connection methods apply to each source type.
  • Given a business requirement to report on data stored in a Salesforce org, which Tableau data source connector is appropriate.
  • Authentication requirements when connecting Tableau Desktop to a Salesforce org data source.
  • Identifying when a data source type (file, relational database, cloud service, published source) is the correct choice given a described data architecture.
  • When Tableau Cloud needs to connect to an on-premises database behind a firewall, identifying which Tableau component (Tableau Bridge) bridges this network boundary and what it requires to be installed and configured.
  • When no native Tableau connector exists for a web-based or REST API data source, identifying Web Data Connector (WDC) as the appropriate fallback and what a WDC does.

1.1.2. Determine live connection vs. extract

0/4

  • A stakeholder requires up-to-the-minute dashboard data but the underlying database is on a slow WAN connection. Which trade-offs determine whether a live connection or extract is the better choice.
  • When a data source contains row-level security enforced at the database level, choosing between live connection and extract and how each option affects security enforcement.
  • Performance and cost trade-offs of live connection vs. extract when querying a cloud data warehouse (e.g., Snowflake or BigQuery) with per-query charges.
  • Identifying which capabilities are available only with an extract (e.g., offline access, certain optimizations) versus only with a live connection.

1.1.3. Connect to extracts

0/3

  • A workbook was built against a .hyper extract. The analyst wants to share it with a colleague who does not have database access. Which packaging approach preserves the extract data.
  • How extract filters affect the data included in a Hyper extract and when applying an extract filter is preferable to filtering at the view level.
  • Appending new rows to an existing Tableau Hyper extract using the 'Append data from file' option — schema requirements for the source to match the extract and when append is preferable to a full refresh.

1.1.4. Connect to files

0/4

  • An analyst receives a multi-tab Excel file where each tab represents a region. How to connect Tableau Desktop to all tabs simultaneously and which technique merges them into a single logical table.
  • Supported flat file formats in Tableau Desktop (CSV, Excel, JSON, PDF, spatial files) and when each format type is the appropriate choice.
  • Known limitations of Tableau flat file connectors (e.g., Excel multi-tab handling, JSON nesting, PDF table extraction).
  • When connecting to a CSV file with an inconsistent header row, which Tableau tool correctly detects and removes the extraneous rows before analysis.

1.1.5. Connect to relational databases

0/5

  • When connecting Tableau Desktop to a relational database via custom SQL or an Initial SQL statement is required.
  • Performance implications of using custom SQL or Initial SQL instead of selecting tables directly in Tableau.
  • A company needs Tableau to access a proprietary database for which no native connector exists. Which connection method supports this and what is required.
  • How database authentication options (Windows authentication vs. username/password) in Tableau differ and when each is appropriate for publishing.
  • The Initial SQL field when connecting to a relational database — what types of statements it executes (DDL, session variables, temp tables) and when it runs (each time a connection opens).

1.1.6. Connect to published data sources from a Tableau Server or Tableau Cloud site

0/3

  • An analyst wants all team members to use the same curated dataset. Which approach — embedding a data source in the workbook vs. publishing the data source separately — achieves this goal and why.
  • How certified data sources on Tableau Server/Cloud differ from non-certified published data sources in terms of discoverability and governance.
  • A published data source uses a live connection to a database. When a workbook connects to this published source, determining where query execution occurs and who controls refresh.

1.1.7. Replace the connected data source with another data source for an existing chart or sheet

0/2

  • An analyst built 15 sheets against a development database and must now point them at the production database with identical schema. The fastest technique to remap all sheets at once.
  • When replacing a data source with one that has different field names, how Tableau handles unmatched fields and what steps the analyst must take to restore broken references.

1.2.1. Assess data quality

0/3

  • Identifying null values, blank strings, and outliers in a connected dataset using Tableau's built-in profile and data pane indicators.
  • A dataset has a date field stored as a string with inconsistent formats (MM/DD/YYYY and YYYY-MM-DD). How to identify this inconsistency in Tableau and which approach resolves it.
  • When reviewing a measure field that shows unexpected values (negatives where only positives are expected), which Tableau pane features help isolate the problem rows.

1.2.2. Perform cleaning operations

0/6

  • Using Tableau Prep Builder vs. calculated fields in Tableau Desktop to clean data — when each tool is the correct choice given organizational constraints.
  • Using ZN() and IFNULL() to substitute null values in a measure field via calculated fields in Tableau.
  • Trade-offs of handling null measures via calculation substitution vs. data source filtering in Tableau.
  • Trimming whitespace and standardizing case in a string dimension field using Tableau calculated fields so that 'New York' and ' new york' are treated as the same member.
  • Tableau Prep Builder's Group and Replace feature — how it clusters similar string values using pronunciation, common characters, or spelling.
  • How accepted Group and Replace suggestions in Tableau Prep become persistent cleaning steps that reapply on flow refresh.

1.2.3. Organize data fields into folders

0/2

  • What organizing data fields into folders in Tableau accomplishes and what it does not change about the underlying data or calculations.
  • A team has 40 calculated fields in a published data source. How folders help consumers of that source navigate the data pane efficiently.

1.2.4. Use multiple data sources

0/12

  • When to use a Tableau relationship vs. a join — key behavioral differences in row granularity and how each handles unmatched rows.
  • How Tableau relationships vs. joins affect Level of Detail (LOD) calculations differently.
  • A company has orders in one table and returns in another. The analyst needs each order row to appear regardless of whether a return exists. Which join type and relationship model achieves this.
  • How Tableau relationships differ from traditional joins in how they handle duplicate rows and unmatched data — and when this difference changes analysis results.
  • When a union is the correct operation to combine tables versus a join or a relationship, given that the tables have identical schemas but represent different time periods.
  • Tableau's two-layer data model — the logical layer where tables connect via relationships and the physical layer where joins and unions are defined.
  • Why dragging a second table onto the logical canvas creates a relationship by default rather than a join in modern Tableau.
  • Data blending in Tableau — the primary and secondary data source model and how each source's role affects query execution.
  • How linking fields work in data blending — the blue tick on the primary source and orange tick on the secondary source.
  • What an orange tick mark on a field in the secondary data source signifies in the view when data blending is active.
  • When data blending is required instead of a join or relationship — scenarios where data sources reside in different database systems or require pre-aggregation before combining.
  • Data blending's aggregate-level join limitation — why row-level fields from the secondary source are unavailable in the primary view.

1.2.5. Prepare data by using Data Interpreter, pivot, and split

0/3

  • When Tableau's Data Interpreter is appropriate and what types of spreadsheet formatting issues it resolves automatically.
  • An Excel file has monthly sales as separate columns (Jan, Feb, Mar...). The analyst needs a single 'Month' dimension and a 'Sales' measure. Which Tableau operation transforms the data into this shape.
  • Using the Split function to extract components from a delimited string field (e.g., 'City, State') — the difference between automatic split and custom split and when each is appropriate.

1.2.6. Create extract and data source filters

0/3

  • How a data source filter differs from an extract filter in terms of scope, performance impact, and who can override it.
  • An extract contains 5 years of data but analysts only need the current year. Adding an extract filter to reduce extract size — effect on historical views already built against the extract.
  • When a data source filter that excludes certain customer segments is applied, determining which Tableau objects (views, LOD calcs, table calcs) are affected vs. unaffected.

1.3.1. Choose which data transformation to perform based on a business scenario

0/2

  • Given a business requirement to compare current-year sales against prior-year for the same period, determining which data transformation (pivot, union, calculation, LOD) most directly solves the problem.
  • A company receives daily sales files with identical schemas. The analyst must analyze trends across all days. Selecting the correct transformation (union vs. join vs. blend) and explaining why.

1.3.2. Combine data by using unions

0/3

  • Requirements for a wildcard union in Tableau — when it applies and how new files matching the wildcard pattern are automatically included.
  • When unioning tables with mismatched columns, how Tableau handles the mismatch and what appears in the resulting dataset for rows from each source.
  • The [Sheet] and [Table Name] generated fields automatically added to a unioned dataset — how to use them to identify which source table each row originated from and a use case for filtering by source in downstream analysis.

1.3.3. Combine data by using joins

0/5

  • INNER and LEFT join behavior in Tableau — which rows from each table are preserved and how unmatched rows appear.
  • RIGHT and FULL OUTER join behavior in Tableau — when each is appropriate and which table's rows are fully preserved.
  • A many-to-many join between two tables causes row duplication, inflating SUM measures. Why this happens and the preferred alternative in modern Tableau (relationships).
  • Cross-database joins in Tableau — when they are available, and what limitations apply compared to same-database joins.
  • Using a join calculation to create a custom join expression when key fields do not match directly (e.g., joining on a truncated date or a type-cast integer) — how to define the expression in the join clause editor and its performance considerations.

1.3.4. Shape data by using aggregations

0/2

  • When aggregating at the data source level via a custom SQL or initial SQL is preferable to aggregating in the Tableau view, given performance and governance requirements.
  • How the 'Aggregate Measures' setting in Tableau affects view-level calculations and when toggling it off is appropriate.

1.3.5. Perform filtering

0/4

  • The Tableau filter order of operations (extract → data source → context → fixed LOD → dimension → measure → table calc) and how it determines which filters can see which data.
  • A FIXED LOD calculation produces unexpected totals when a dimension filter is applied. The analyst suspects the filter is not affecting the LOD. Explaining why and the correct fix.
  • Relative date filter options in Tableau — 'Last N days/weeks/months' and how the filter automatically recomputes as time progresses.
  • Relative date filter anchor configuration — anchoring to today vs. a specific date and how this differs from a fixed date range filter.

1.3.6. Shape data by using pivots

0/2

  • When pivoting columns to rows is required for correct analysis — the structural difference between wide (crosstab) and tall (normalized) data and which shape Tableau prefers.
  • An analyst needs to pivot multiple measure columns into a single measure/category pair. How the pivot operation in Tableau Desktop's Data Source page works and what the resulting schema looks like.

1.3.7. Determine which output type to use

0/3

  • When to publish a data source separately to Tableau Server vs. embed the data source in a workbook — criteria for shared governance vs. workbook portability.
  • When a Tableau Packaged Workbook (.twbx) with an embedded extract is the correct distribution output vs. a published shared data source.
  • When a Tableau Packaged Workbook (.twbx) is the correct output type for distribution versus a plain workbook (.twb) and the implications for data portability.

1.4.1. Change default field properties

0/2

  • Changing the default aggregation of a measure field from SUM to AVG in the data pane — how this affects all existing and future views using that field.
  • Setting a default sort order on a dimension field in the data pane vs. sorting in the view — which is persistent across all sheets using the field.

1.4.2. Rename columns

0/2

  • Renaming a field in Tableau's data pane (display alias) vs. renaming it in the underlying data source — which affects calculated fields that reference the original name.
  • A published data source has a poorly named field that consumers find confusing. The analyst renames the field in Tableau. Whether downstream workbooks using the published source need updating.

1.4.3. Choose when to convert between discrete and continuous

0/3

  • The visual and behavioral difference between a discrete (blue) date pill and a continuous (green) date pill on the Columns shelf — what each produces on the axis.
  • An analyst wants a line chart showing monthly trends with an unbroken X-axis even for months with no data. Which pill type (discrete or continuous) achieves this and why.
  • When converting a measure to discrete creates a row header instead of an axis — use cases where discrete measures are preferable in visualization.

1.4.4. Choose when to convert between dimension and measure

0/2

A numeric field (e.g., Zip Code, Employee ID) is automatically classified as a measure. Explaining why converting it to a dimension is correct and how it affects aggregation behavior.

Learn this concept
Unseen

When treating a string dimension as a measure makes sense — and what aggregation options are available for string fields converted to measures.

Learn this concept
Unseen

1.4.5. Create aliases

0/2

  • Creating member aliases for a dimension field — what aliases change (display value), what they do not change (underlying data value), and how this affects filters and calculations.
  • An analyst aliases 'NY' to 'New York' in a published data source. A downstream workbook has a filter hardcoded to 'NY'. Whether the filter still works after the alias is applied.
  • The behavioral difference between RANK and RANK_DENSE when there are tied values — shared ranks vs. consecutive ranks with no gaps.
  • The behavioral difference between RANK_MODIFIED and RANK_UNIQUE when there are tied values in Tableau.
  • An analyst wants to show rank within each product category independently. Setting up RANK partitioned by Category to restart numbering for each category pane.
  • Matching Tableau quick table calculations (Running Total, Difference, Percent Difference, Percent of Total, Rank, Percentile, Moving Average) to their business use cases.
  • After applying a quick table calculation, the analyst drags the field off the view and back — whether the quick calc persists and how to permanently convert it to a calculated field.
  • Customizing a table calculation's compute using 'Specific Dimensions' — how selecting specific dimensions for addressing vs. partitioning changes the scope of the calculation.
  • The FIRST(), LAST(), and SIZE() table calculation functions — FIRST() returns the offset from the first row, LAST() from the last row, SIZE() returns the partition row count.
  • How filtering a dimension (categorical filter) differs from filtering a measure (quantitative filter) in Tableau's filter dialog — available options for each.
  • A view aggregates sales by region. The analyst adds a measure filter for SUM(Sales) > 100000. Explaining where in the filter order of operations this filter applies and what it excludes.
  • Using DATEDIFF to calculate the number of business days between two date fields — and why DATEDIFF does not natively exclude weekends, requiring additional logic.
  • Using DATEADD to compute a future or past date relative to a record's date field — syntax, date part options, and how the result changes with different date_part arguments.
  • A dashboard must show YTD sales. Writing a Boolean calculated field using DATEPART or DATETRUNC to isolate records in the current year up to today.
  • DATETRUNC behavior with different date parts — how truncating to 'month' vs. 'quarter' vs. 'year' affects grouping of date fields in a view.
  • Handling fiscal year date calculations in Tableau when the fiscal year starts in a non-January month — how DATEPART's fiscal_year option or manual offset logic works.
  • The difference between TODAY() and NOW() in Tableau — TODAY() returns the current date with no time component while NOW() returns a datetime.
  • When to use TODAY() vs. NOW() depending on whether the underlying date field includes a time portion and whether the data source is live or an extract.
  • Behavioral differences between CONTAINS, STARTSWITH, and FIND when filtering or flagging string fields in Tableau.
  • Case sensitivity behavior of CONTAINS, STARTSWITH, and FIND string functions in Tableau.
  • Extracting a substring from a product code field using MID, LEFT, or RIGHT — selecting the correct function when the extraction position is fixed vs. variable.
  • A calculated field needs to concatenate a string and a number (e.g., 'Order #' + [Order ID]). The correct Tableau syntax and why type conversion is required.
  • Using REGEXP_MATCH, REGEXP_EXTRACT, and REGEXP_REPLACE to handle complex string patterns in Tableau calculated fields.
  • Which Tableau data source connection types support regular expression functions.
  • Choosing between IF/ELSEIF/ELSE and CASE/WHEN expressions for categorizing a dimension — when CASE is more appropriate and its limitation with complex conditions.
  • How NULL propagates through logical expressions in Tableau — why NULL compared with any value returns NULL and how IIF handles the unknown third state.
  • How ISNULL() detects null values in Tableau calculated fields and what it returns.
  • The difference between IFNULL() and ZN() for replacing or converting null measure values in Tableau.
  • Writing a multi-condition Boolean expression using AND/OR operators to classify records — operator precedence rules and use of parentheses in Tableau calculation syntax.
  • The three calculation execution contexts in Tableau — row-level (computed per row before aggregation in the database), aggregate (computed after aggregation), and table calculation (computed in Tableau after the query returns).
  • Why calculation execution context determines where a field can be used — e.g., table calculations cannot be used in data source filters.
  • Differentiating ROUND, FLOOR, and CEILING in financial rounding scenarios — which to use when always rounding up, always rounding down, or rounding to nearest.
  • Using the MOD function to identify even/odd records or create cyclical groupings — syntax and practical use case in Tableau calculated fields.
  • Calculating percent change using Tableau number functions vs. table calculations — trade-offs for each approach when the analyst needs row-level percent change.
  • Using ABS(), SQRT(), and POWER() in Tableau row-level calculated fields — practical use cases for deviation and variance-related metrics.
  • Using STR(), INT(), FLOAT(), and DATE() for explicit type conversion — which function to apply when a date stored as integer (YYYYMMDD) must be converted to a date type.
  • Using DATEPARSE to convert a string with a custom date format into a Tableau date — syntax and supported format tokens.
  • The behavioral difference between COUNT and COUNTD in Tableau — when COUNTD is required and its performance cost compared to COUNT.
  • Using ATTR() in a calculated field — what it returns when all values in the partition are the same vs. when they differ, and why it appears as a '*' in certain views.
  • A calculated field mixes aggregated (SUM) and non-aggregated references. Tableau throws an 'Cannot mix aggregate and non-aggregate' error. Diagnosing the cause and correcting the formula.
  • How MIN() and MAX() aggregate functions behave on string fields (alphabetical), date fields (earliest/latest), and numeric fields in Tableau.
  • Using MIN([Order Date]) in a FIXED LOD calculation to find each customer's first purchase date.
  • How the TOTAL() table calculation function computes the table-level total of an aggregate expression across the entire partition.
  • How TOTAL() differs from WINDOW_SUM with unlimited range when showing each row's share of a grand total without changing view granularity.
  • Using MAKEPOINT to create a spatial point from latitude and longitude fields — requirements for the fields and how the result is used in a map visualization.
  • Using DISTANCE to compute the straight-line distance between two spatial points — required inputs, unit specification, and use case for delivery route analysis.
  • How WINDOW_AVG syntax works — specifying the start and end offsets relative to current row to create a trailing 3-month moving average.
  • A table calculation's addressing vs. partitioning determines how WINDOW_AVG scopes its window. Choosing 'Table (across)' vs. 'Pane (down)' for a given chart layout.
  • Two approaches to percent of total: SUM([Sales])/WINDOW_SUM(SUM([Sales])) vs. Tableau's quick table calculation. When the manual approach is required for correct scoping.
  • A percent-of-total calculation produces 100% for each sub-category within a partition. Diagnosing the addressing scope error and correcting the partitioning to compute percent of grand total.
  • The difference between RUNNING_SUM and WINDOW_SUM — which is cumulative across the view and which sums a fixed window, and when each is appropriate.
  • A running total chart resets to zero each quarter instead of continuing. Diagnosing the partitioning setting causing the restart and correcting it.
  • Using LOOKUP(SUM([Sales]), -1) to compute period-over-period difference vs. using the 'Difference From' quick table calculation — which is more flexible for custom offsets.
  • A percent-of-difference table calc shows an error for the first period where there is no prior period. How Tableau handles this and how to suppress or replace the NULL.
  • How PERCENTILE aggregate and WINDOW_PERCENTILE table calculation differ — when each is appropriate for showing the 90th percentile of a distribution.
  • How INDEX() assigns row numbers within a partition — its typical use for creating rank-based filters, alternating row colors, or custom orderings.
  • Using INDEX() with a filter to show 'Top 5 only' within each category pane — why a context filter or RANK is sometimes needed instead of INDEX for this use case.
  • How the 'Top N' filter uses a parameter to dynamically control how many members appear — wiring a parameter to the Top N value field.
  • The difference between a wildcard filter using 'contains' vs. 'starts with' vs. 'matches regex' — when each is appropriate and whether regex is supported for all data sources.
  • A conditional filter on a dimension includes members where SUM(Profit) > 0. How this conditional filter interacts with the view's current aggregation context.
  • Relative date filter anchor options — anchoring to 'Today', a specific fixed date, or a field value.
  • How changing a relative date filter anchor from today to a specific date affects visible data when the workbook is opened at different points in time.
  • What a context filter does in Tableau's filter order of operations — why adding a dimension filter to context makes dependent filters (Top N, FIXED LOD) compute against the filtered data.
  • A Top N filter shows the wrong top products because it is computed before the region filter restricts the data. Fixing this by promoting the region filter to context.
  • Performance trade-offs of context filters — why they trigger a separate query pass and when overuse of context filters degrades dashboard performance.
  • How a dashboard filter applied to 'All Using Related Data Sources' works and when it fails to filter sheets connected to a different primary key.
  • Using a single filter control on a dashboard to filter sheets from two different data sources — the requirement that the filter field must be a shared dimension linked by relationship or data blending.
  • The difference between applying a filter to 'Selected Worksheets', 'All Using This Data Source', and 'All Using Related Data Sources' in the context of a multi-datasource dashboard.
  • Creating a parameter and referencing it inside a calculated field — how changing the parameter value changes the calculation result dynamically without re-authoring.
  • A parameter allows users to switch the measure displayed (Sales vs. Profit vs. Quantity) by using a CASE statement in a calculated field. Building this pattern and its limitations.
  • Tableau parameter data types (integer, float, string, Boolean, date, date-time) and how data type constrains what calculated fields can reference.
  • Configuring parameter allowable values as a fixed list (including from a data source field), a range with step size, or all values.
  • Adding a reference line whose value is driven by a parameter — wiring a float parameter to a constant reference line and the effect of parameter type (float, integer, string) on available line positions.
  • A dashboard requires a target line on a bar chart that users can adjust interactively. Building this using a parameter and a reference line, specifying how the parameter control is exposed.
  • Configuring a parameter to refresh its list of allowable values from a published data source on Tableau Cloud — the 'When workbook opens' option and its behavior.
  • The limitation of parameter values not automatically updating when new members are added to the underlying data — how dynamic parameters address this gap and what is required to enable them.
  • The difference between a fixed set and a dynamic (computed) set in Tableau — which updates automatically when data changes and which is locked to specific members.
  • Using a set to highlight the top 10 customers by revenue and comparing them to the rest — how the IN/OUT membership is used in calculations and color encoding.
  • Combining two Tableau sets with Union, Intersection, or Difference — the resulting membership in each case.
  • Set actions on a dashboard — how clicking a mark updates a set's membership and propagates the selection to other sheets using the set in their calculations.
  • Creating bins from a continuous measure — how to set bin size and how the bins appear as a new dimension in the data pane.
  • Building a histogram from a measure using bins — the correct chart type configuration and why histograms require bins rather than just a raw measure on Columns.
  • Choosing an appropriate bin size for a distribution analysis — trade-offs between too few bins (loss of detail) and too many bins (noise) given the data range.
  • Creating a custom hierarchy in Tableau (e.g., Country > Region > State > City) — how drill-down behavior works in a view when the hierarchy is expanded.
  • When to use date hierarchies vs. manual date level selection — how Tableau's built-in date hierarchy differs from a custom dimension hierarchy in drill behavior.
  • Expanding and collapsing hierarchy levels using + and - drill indicators — how drilling inserts or removes child dimensions and changes mark count.
  • How hierarchy drill-down interacts with existing filters and aggregations in the current view.
  • Group vs. set for answering the question 'Which customers are in my VIP segment?' — when a group is simpler and when a set (especially dynamic or action-driven) is required.
  • Building a symbol map using latitude/longitude fields vs. Tableau's built-in geographic role — when to assign a geographic role vs. use custom coordinates.
  • Encoding multiple measures on a symbol map using size and color simultaneously — chart configuration steps and visual perception trade-offs.
  • When a density (heatmap) map is more appropriate than a symbol map — the volume of data points required for density maps to be meaningful.
  • Configuring density map intensity and radius in Tableau — how these settings interact with zoom level.
  • Assigning a geographic role (State, Country, Postal Code) to a dimension field to enable a filled map — requirements for Tableau to recognize the geographic role.
  • A filled map shows unknown locations for several dimension members. Diagnosing the cause (unrecognized geographic values) and resolving it using the Edit Locations dialog.
  • Choosing between a filled map and a symbol map for displaying regional sales data — which better communicates distribution across irregular geographic polygons.
  • Adding a second mark layer to a map using dual-axis — combining a filled map (polygon) with a symbol layer to show both regional color and point-level detail.
  • How to synchronize axes on a dual-axis map to ensure both layers share the same geographic extent and projection.
  • Adding grand totals to rows and columns in a crosstab — how Tableau computes the total (re-aggregating from source vs. summing visible cells) and when they differ.
  • A row total for a ratio measure (e.g., Profit Ratio = SUM(Profit)/SUM(Sales)) shows an incorrect value because Tableau averages the ratio instead of re-aggregating. How to fix the total aggregation.
  • How subtotals appear at each level of a multi-level dimension hierarchy in a Tableau crosstab.
  • Controlling subtotal position (above or below detail rows) and how Tableau re-aggregates for subtotals vs. summing visible cells.
  • Adding a constant reference line vs. a computed reference line (e.g., Average) to an axis — how each is configured and when a computed line is preferred.
  • Configuring a reference line to display per-pane vs. per-cell vs. entire view — what changes when the scope is set to 'Per Pane' in a view with multiple category panes.
  • Creating a reference band between two computed values (e.g., between Q1 and Q3 to shade the interquartile range) — configuration steps in the Reference Lines dialog.
  • Using a reference band to highlight a target range (e.g., 80–120% of target) on a performance chart — how the band's fill color communicates the acceptable zone.
  • Interpreting an average line on a bar chart — whether it represents the mean of the visible marks or a re-aggregated mean from the underlying data, and when these differ.
  • Analytics pane categories in Tableau — Summarize (constant/average/median/95% CI lines), Model (trend line, forecast), and Custom (reference line/band/distribution).
  • How dragging analytics objects from the Analytics pane differs from adding them via the Analysis menu.
  • Tableau's linear, logarithmic, and exponential trend line model types — when each is appropriate based on data shape.
  • Tableau's polynomial and power trend line model types — when each is appropriate and what R-squared indicates about model fit.
  • A trend line on a scatter plot shows a p-value of 0.42 in the Describe Trend Line dialog. Interpreting what this means for the relationship between the plotted variables.
  • When trend lines are appropriate vs. misleading — scenarios where adding a trend line to a non-time series or non-continuous axis creates an incorrect statistical impression.
  • Adding distribution bands (standard deviation or percentile-based) to a view — what each band option communicates and how many standard deviations are common for outlier identification.
  • How Tableau's built-in forecasting algorithm (exponential smoothing) determines trend and seasonality — requirements for a minimum number of data points before forecasting is enabled.
  • What the forecast confidence interval represents in a Tableau forecast visualization and how to interpret a widening confidence band over the forecast horizon.
  • Customizing forecast length, seasonality period, and ignoring last N periods in Tableau's forecast model options — when each customization improves forecast accuracy.
  • Selecting between additive and multiplicative trend and seasonality models in Tableau forecasting — when multiplicative is preferred for data with increasing seasonal amplitude.
  • The syntax of a FIXED LOD calculation and how it bypasses the view's current level of detail to compute at a specified granularity.
  • A FIXED LOD {FIXED [Customer ID] : MAX([Order Date])} computes each customer's most recent order date. How this value can be used in a view broken down by Product Category without re-aggregating per category.
  • Why a FIXED LOD calculation ignores dimension filters but respects context filters — and how to use this behavior intentionally vs. how to work around it when it causes incorrect results.
  • Using a FIXED LOD to compute customer lifetime value at the customer level and then aggregate those values at the segment level in the view.
  • How INCLUDE adds a dimension to the computation that is not in the current view — use case: computing average order value per customer (INCLUDE [Customer ID]) when the view is at the Product level.
  • The difference in granularity between {INCLUDE [Customer ID] : SUM([Sales])} and SUM([Sales]) in a view at the Region level — why INCLUDE produces a higher result in this case.
  • How EXCLUDE removes a dimension from the computation — use case: computing the ratio of each product's sales to the overall category total, removing Product from the LOD.
  • An analyst uses {EXCLUDE [Region] : SUM([Sales])} to compute national total in a view broken down by Region. Why the EXCLUDE LOD returns the same value in every row of the Region dimension.
  • Why nesting one LOD expression inside another is sometimes required — example: finding the average of a per-customer sum, requiring FIXED at customer level nested inside an AVG aggregation.
  • A nested LOD that first computes per-order revenue at the order line level, then finds the maximum order revenue per customer — the syntax and evaluation order.
  • Selecting between a bar chart and a line chart for a time-series dataset — when lines imply continuous change and when bars are more appropriate for discrete categorical comparison.
  • Building a dual-axis chart combining a bar and a line measure — steps to synchronize the secondary axis and why axis synchronization matters for accurate visual comparison.
  • Building a Gantt chart to visualize project timelines — which fields map to Columns (start date), Rows (task), and Size (duration), and how duration is calculated.
  • Creating a box plot in Tableau — what the five-number summary components (min, Q1, median, Q3, max) map to in the chart and how to configure whisker extent.
  • When a pie chart is appropriate vs. misleading — the maximum number of slices for readability and when to switch to a bar chart for the same data.
  • Building a scatter plot to analyze correlation between two measures — which shelves each measure occupies and how to add a third dimension via color or size.
  • Creating a highlight table (heat map crosstab) — the correct mark type, the field on Color, and how this differs from a standard crosstab with text values.
  • A tree map is requested to show sales by subcategory. Identifying which measure controls rectangle size, which controls color, and when a tree map is preferred over a bar chart.
  • Stacked area chart vs. individual (overlapping) area chart in Tableau — which mark type and shelf configuration produces each.
  • When stacked vs. individual area charts are semantically appropriate for communicating part-to-whole vs. independent trends.
  • Creating a packed bubbles (circle view) chart in Tableau — which fields control bubble size and color, when packed bubbles communicate part-to-whole proportions, and how it compares to a tree map for the same data.
  • Building a text table (crosstab / data table) in Tableau — placing dimensions on Rows and Columns, placing a measure on the Text mark, and when to use Show Me's 'Text Tables' option versus manually configuring the shelves for a custom crosstab layout.
  • How the Show Me panel recommends chart types based on the count and types of fields currently selected (e.g., two dimensions + one measure recommends a heat map).
  • How selecting a chart type from Show Me automatically rearranges pills on the Rows, Columns, and Marks shelves.
  • Adding a dimension to the Detail mark shelf to increase mark granularity without adding a visible encoding — how Detail increases the number of marks in a view and when this is needed to reveal disaggregated data (e.g., showing individual order lines on a chart aggregated by region).
  • Using the Pages shelf to animate a view across dimension members or date periods — how it creates a playable sequence, what Player controls appear, and a use case for reviewing how sales by region change month by month without building a dashboard action.
  • Sorting a bar chart by measure descending vs. by dimension alphabetically — which sort is applied in the view and whether it persists when the view is published.
  • Creating a custom (manual) sort order for a dimension (e.g., a non-alphabetical priority list) — how to configure it in the Sort dialog and its behavior when new members are added.
  • Nested sort: sorting Sub-Category within each Category independently by sales — the correct Sort configuration to achieve independent sorting within each outer dimension.
  • In-view sort buttons (toolbar and axis headers) vs. field-level Sort dialog — ad-hoc view sort that resets when the field is removed vs. persistent default sort.
  • How to clear all sorts on a view to return fields to their default order.
  • The difference between tiled and floating objects on a dashboard — use cases for each layout mode and why mixing them can complicate responsive design.
  • Using horizontal and vertical containers to control the layout of multiple sheets — how nested containers create grid-like arrangements and the effect of resizing one panel.
  • Fixed vs. automatic dashboard sizing — when automatic sizing is appropriate and the risk of chart distortion when the fixed size does not match the viewer's screen resolution.
  • Adding a text object to a dashboard for a title or annotation — how text object formatting differs from sheet title formatting.
  • Embedding a web page object in a Tableau dashboard — use cases and security considerations (X-Frame-Options headers that can block embedding).
  • Placing an image object on a dashboard for branding — supported image formats, URL vs. local file options, and fit options (fit image, center image, etc.).
  • How a Tableau story differs from a dashboard — when to use a story to walk stakeholders through a sequential analytical narrative.
  • Story point types in Tableau — blank, captured (snapshot), and duplicate — and which preserves the current state of a dashboard as a static image.
  • A story point based on a dashboard with a filter applied — whether viewers can change filters on the story point and how to lock the state for a presenter-led walkthrough.
  • Adding a filter control to a dashboard and configuring which sheets it applies to ('All Using This Data Source' vs. 'Selected Worksheets') — choosing the right scope.
  • Using a sheet on a dashboard as a filter (clicking a bar filters other sheets) vs. using an explicit filter action — the default behavior difference and how to configure each.
  • The difference between a filter action, a URL action, and a highlight action — which alters data shown in target sheets vs. which only visually emphasizes marks.
  • Configuring a filter action's 'Run action on' trigger (Hover, Select, Menu) and 'Clearing the selection will' behavior — when 'Show all values' vs. 'Exclude all values' is appropriate.
  • A URL action that passes the selected mark's field value as a URL parameter to open a CRM record — how to insert field values dynamically into the URL template.
  • How dynamic zone visibility works in Tableau — tying a container's visibility to a Boolean parameter or field so it appears or disappears based on user selection.
  • A dashboard shows different chart types based on a user's selection in a single-value filter. Implementing this with dynamic zone visibility and a Boolean calculated field.
  • Adding a navigation button to a dashboard that links to a different sheet, dashboard, or story page — available navigation targets and how to configure button appearance.
  • When navigation buttons are preferable to URL actions for moving between dashboard pages — and the limitation that navigation buttons cannot pass field values to the target.
  • A parameter action that changes a parameter's value when the user clicks a mark — configuring the source field, target parameter, and aggregation for the value passed.
  • A set action that adds clicked marks to a set — configuring 'Add to', 'Remove from', and 'Assign to' behaviors and when 'Assign' replaces previous selection.
  • Using a parameter action on a scatter plot to drill into a selected data point — showing detail for the selected customer in a secondary sheet driven by the parameter.
  • Using show/hide buttons to reveal a legend panel or filter panel on demand — how this approach improves dashboard real estate while preserving interactivity.
  • Applying a diverging color palette to a measure — when diverging palettes are semantically appropriate vs. when a sequential palette is better for the data.
  • The Tableau formatting hierarchy: workbook-level defaults, worksheet-level formats, and field-level formats — which level overrides which and how to reset to the default.
  • The Marks card encoding channels — Color, Size, Label, Detail, Tooltip, and Shape — and what visual variable each controls (hue, area, text, granularity, hover content, symbol).
  • Which dimension and measure field types can be assigned to each Marks card encoding channel in Tableau.
  • Configuring mark opacity (transparency) via the Color mark card — how reducing opacity below 100% reveals overlapping marks in a dense scatter plot and the interaction between opacity and the active color palette.
  • Installing custom shapes in Tableau by placing image files in the Repository/Shapes folder — the supported file types and how to make shapes available in the mark card.
  • Creating a custom color palette by editing the Preferences.tps file — the XML structure required and how to reload preferences in Tableau Desktop.
  • The three annotation types in Tableau (Point, Mark, Area) — what each anchors to and when each is the correct choice for calling out a specific value or region.
  • Adding a Mark annotation to the highest sales bar in a chart — what field values are automatically available in the annotation text template.
  • Adding a Viz in Tooltip — embedding a secondary sheet that renders based on the hovered mark's dimension values, and how to configure the tooltip sheet's view.
  • Customizing tooltip text to include calculated values, formatted numbers, and explanatory copy — what field reference tokens are available in the tooltip editor.
  • Configuring inner vs. outer padding on dashboard objects — how inner padding affects the content margin inside an object and outer padding affects spacing between objects.
  • Enabling alternating row banding in a Tableau crosstab to improve readability — where in the Format pane to configure band color and the band level granularity.
  • Removing gridlines from a view to create a cleaner aesthetic — the format pane location for zero lines, grid lines, and axis rulers, and the visual difference between them.
  • Creating a phone-optimized layout for a published dashboard — how device-specific layouts allow independent arrangement of objects vs. inheriting the default layout.
  • A dashboard has a complex layout that becomes unusable on a mobile device. The analyst creates a separate phone layout with simplified charts. Which objects are available in the phone layout and which are excluded.
  • The Tableau Server/Cloud site role hierarchy (Viewer, Explorer, Creator) — what each role can and cannot do regarding connecting to data, publishing, and editing content.
  • Permissions on a published workbook (View, Download, Filter, etc.) interact with site roles — why a user with 'Creator' site role can be denied Download Full Data by a project permission rule.
  • How Tableau Server row-level security can be implemented using user filters or entitlement tables joined to data — the high-level pattern and when each is appropriate.
  • Project-level permission locking — the effect of locking a project's permissions and how it prevents content owners from overriding permissions on individual items.
  • Assigning permissions to groups vs. individual users on Tableau Server/Cloud and how group memberships combine with individual permission rules.
  • Tableau permission conflict resolution — the most permissive capability applies unless an explicit Deny overrides any Allow.
  • Creating a subscription to email a published view on a schedule — the available delivery formats (PNG vs. PDF), who can be subscribed, and whether external users can receive subscriptions.
  • A manager wants the team to receive a weekly PDF of the sales dashboard every Monday morning. Configuring the subscription schedule, format, and scope — including whether filters in the view apply to the emailed snapshot.
  • What a custom view saves in Tableau Server/Cloud (filter selections, sort order, parameter values) and what it does not save (data or workbook structure changes).
  • An analyst saves a custom view with a specific Region filter applied and marks it as the default. What other users see when they first open the workbook vs. what they see before the default was set.
  • Publishing a workbook to Tableau Server — the available options during publish (project, permissions, views to show as tabs, embedding credentials) and what each controls.
  • A workbook uses an embedded data source. The analyst publishes the workbook without extracting. Who can access the data and what credential behavior applies to viewers.
  • Overwriting an existing published workbook vs. publishing as a new workbook — what the overwrite option preserves (subscription, custom views) vs. what it replaces.
  • Publishing a data source from Tableau Desktop vs. from Tableau Prep Builder — how the resulting published data source differs and when each publishing path is appropriate.
  • Certifying a data source on Tableau Server — who can certify, what the certification badge communicates to data consumers, and whether certification affects refresh scheduling.
  • Credential handling when publishing a data source — embedding database credentials, prompting users at connect time, and OAuth for supported cloud databases.
  • Security and usability trade-offs of embedded credentials vs. prompting vs. OAuth on published data sources.
  • Export format options for a Tableau view (PDF, PNG, CSV, Tableau Packaged Workbook, PowerPoint, Crosstab) — which formats preserve interactivity and which are static.
  • An executive wants a PowerPoint file with each dashboard page as a slide. Exporting to PowerPoint from Tableau Server — what renders in the file and what interactivity is lost.
  • Exporting a Tableau view's underlying data as a CSV — the difference between 'Summarized' (view-level aggregation) and 'Full data' (row-level) export and which requires Creator permission.
  • Publishing a Tableau Prep flow to Tableau Server or Tableau Cloud — requirements (Prep Builder license, server version compatibility) and what options are available for scheduling the flow.
  • A published Prep flow outputs a Hyper extract to a published data source. The extract is scheduled to refresh daily. Identifying whether the downstream workbook needs a separate refresh schedule.
  • The difference between a full refresh and an incremental refresh for a Tableau extract — requirements for incremental refresh (the data source must have an incrementing column) and its limitations.
  • A business requires hourly data but the extract refresh is scheduled only once per day. Determining whether live connection, more frequent refresh scheduling, or a different architecture solves this.
  • Who can schedule an extract refresh on Tableau Server — the minimum site role required and where in the Server interface schedules are managed.
  • Tableau Bridge for on-premises extract refreshes on Tableau Cloud — where Bridge is installed and how it maintains an outbound connection to Tableau Cloud.
  • Which on-premises data source types Tableau Bridge supports for scheduled extract refreshes on Tableau Cloud.
  • Setting up a data-driven alert on Tableau Server — the condition types available (above, below, has data, is null), trigger frequency, and who receives notification.
  • A view uses a live connection and an analyst sets an alert to fire when SUM(Revenue) drops below $1M. On which event does Tableau Server check the alert condition.
  • The available distribution methods for a published workbook (share link, embed code, PDF export, subscription, download) and what each requires from the recipient in terms of Tableau license.
  • Embedding a published view in an external web page using the embed code — what the Tableau JavaScript API provides vs. a simple iframe embed, and the authentication implications of each.
  • An analyst wants to share a filtered version of a dashboard with an external partner without giving them a Tableau license. The trade-offs between guest access, published view embedding, and PDF export.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Tableau Data Analyst studiers.

Go to Discord

When treating a string dimension as a measure makes sense — and what aggregation options are available for string fields converted to measures.

Explainer

Learn More

Practice Question

Keep going

Next conceptCreating member aliases for a dimension field — what aliases change (display value), what they do not change (underlying data value), and how this affects filters and calculations.

Checklist progress

0/304 (0%)

0 of 304 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Tableau Data Analyst studiers.

Go to Discord

Explainer

Tableau distinguishes dimensions as qualitative groupers and measures as quantitative aggregators, but you can convert a dimension to a measure by applying an aggregation function. Treating a string dimension as a measure makes sense when you need to count occurrences, count unique values, or satisfy the requirement for an aggregate expression in table calculations, effectively generating a temporary numeric column from text data. This conversion allows qualitative fields to participate in numeric analysis without altering the field's original data type.

Core information
  • Aggregating a dimension creates a temporary measure column in the view, allowing the dimension to take on measure characteristics without changing its underlying type.
More details and nuances
  • Count (Distinct) is unavailable in legacy workbooks, Microsoft Access data sources, and Excel or Text file sources where it requires an extract.