Sign in
Home/Tableau/Tableau Certified Data Analyst (TDA-C01)/Free questions

Tableau Certified Data Analyst (TDA-C01) — Free Practice Questions

10 free sample questions from a bank of 175, with the correct answers and explanations. No signup required — start practising right now.

1You are the owner of an alert. You receive an email notification that the alert was suspended. From where can you resume the suspended alert?
  • The My Content area of Tableau web pages
  • The Data Source page of Tableau Desktop
  • The Notifications area of Tableau Prep
  • The Shared with Me page
Answer: A

The short version

A — Resume a suspended alert from My Content on the web. Ownership plus scheduling lives on Server and Cloud, not Desktop or Prep. My Content lists your alerts for restart.

Key concepts in this question

  • Alert ownership: creator owns thresholds and recipients for a view-based data trigger.
  • Suspension cause: failures or config changes pause alerts with email notice to the owner.
  • My Content home: web area showing owned workbooks, alerts and subscriptions with actions.
  • Desktop contrast: authoring tool builds views, it does not manage server alert state.
  • Prep and Shared contrast: data prep flows and shared-with-me views lack alert controls.

Why A is correct

A is correct because Tableau schedules alerts from Server and Cloud, and the owner restarts them from the My Content area of web pages. That view exposes the suspended alert with a resume control tied to the underlying view and schedule. Data Source pages in Desktop cannot touch server schedules, Prep notifications cover flows, and Shared with Me shows others content without ownership actions. Only My Content gives the resume path.

Why the others are wrong

  • B. Desktop data page authors extracts, it does not host server alert lifecycle controls.
  • C. Prep notifications track flow runs, not view alert suspension and resume.
  • D. Shared with Me lists content others shared, lacking owner alert management.

TDA-C01 exam tip

Suspended alert equals My Content resume. Desktop, Prep and Shared never manage alerts.

2A colleague provides you with access to a folder that contains the following files: Sales.csv - Book1.twb - Sales.hyper - Export.mdb - Which file contains an extract?
  • Export.mdb
  • Sales.hyper
  • Book1.twb
  • Sales.csv
Answer: B

The short version

B — Sales dot hyper holds the extract. Hyper is the current extract engine file. CSV is raw, TWB is XML without data, MDB is Access.

Key concepts in this question

  • Hyper format: high-performance columnar extract created by Tableau Desktop for offline snapshots.
  • CSV role: plain text source that can feed an extract but is not one itself.
  • TWB role: workbook XML with connection logic and visuals, no embedded rows.
  • MDB role: Access database file, a possible source yet not a Tableau extract.
  • Repository habit: extracts default to My Tableau Repository with hyper or legacy tde suffix.

Why B is correct

B is correct because when Desktop creates an extract it materializes a local hyper file containing compressed columnar data for fast querying. Sales dot hyper therefore is the only extract among the folder mates. Sales dot csv remains source text, Book1 dot twb remains instructions without data, Export dot mdb remains a foreign database. Recognizing the hyper suffix is the direct file-type test.

Why the others are wrong

  • A. Access MDB can be read as source, but it is not a Tableau extract artifact.
  • C. TWB stores definitions and layout, it needs live or extract data to render.
  • D. CSV is ingestable source text, not the built extract snapshot.

TDA-C01 exam tip

Extract equals hyper or tde. TWB equals no data, CSV equals source, MDB equals Access.

3You have a workbook that uses an extracted data source. You publish the workbook to Tableau Server. Which three actions can you perform from the Extract Refresh page in Tableau Server? (Choose three.)
  • Run a refresh.
  • Change the refresh from full to incremental.
  • Change the priority of the refresh.
  • Delete the refresh.
  • Modify the frequency of the refresh.
Answer: A, C, E

The short version

ACE — Run refresh, change priority and modify frequency from the Extract Refresh page. Published extracts expose scheduling operations there. Type changes and deletion live elsewhere.

Key concepts in this question

  • Refresh run: on-demand execution to pull fresh source rows into the published extract.
  • Priority control: ordering of refresh jobs when resources contend on Server.
  • Frequency control: cadence such as daily or weekly for automatic updates.
  • Full versus incremental: refresh mode is set at publish or data source config, not on the status page.
  • Delete path: removing a schedule uses data source or admin controls, not the refresh card action set.

Why ACE is correct

ACE is correct because the Extract Refresh page for a Server workbook with an extract lets owners run a refresh now, adjust its queue priority and modify its frequency. Those three are scheduling operations tied to the published refresh task. Changing from full to incremental alters extract logic defined in Desktop or source settings, and deleting the refresh is handled through broader data source management. The settled trio matches the page capability scope.

Why the others are wrong

  • B. changing full to incremental edits extract definition, not a refresh page scheduling tweak.
  • D. deleting the refresh removes the task itself, outside the run plus tune actions of ACE.

TDA-C01 exam tip

Refresh page equals run plus priority plus frequency. Mode change and delete live elsewhere.

4A Data Analyst has a data source with row data for service calls and their activity log. Which calculation allows the analyst to count the calls that have never had a technician assigned to them?
Tableau Certified Data Analyst (TDA-C01) question 4
  • SUM( {INCLUDE [Activity Name]: COUNT(IF [Activity Name] <> 'Assign Technician’ THEN 1 END) } )
  • COUNTD( IF {INCLUDE [Activity Name]: NOT ’Assign Technician' } THEN [Call ID] END )
  • SUN( {FIXED [Call ID]: IF MAX( [Activity Name] = 'Assign Technician') THEN 0 ELSE 1 END } )
  • COUNT( {FIXED [Call ID]: IF [Activity Name] <> ’Assign Technician' THEN 1 ELSE 0 END } )
Answer: C

The short version

C — FIXED per Call ID with MAX check finds never assigned calls. Row level test rolled to call grain flags absence across the whole activity log in the settled key.

Key concepts in this question

  • FIXED LOD: computes at stated dimensionality regardless of view layout, ideal for per call lifetime checks.
  • MAX boolean test: MAX of a condition returns true if any row in the group matches, revealing at least one assignment.
  • Call grain: grouping by Call ID collapses many activity rows into one verdict per service case.
  • INCLUDE and COUNTD contrast: view dependent or distinct counting that can double count or miss absence logic.
  • Row wise inequality trap: testing each row for not equal counts partial matches rather than proving no assignment ever occurred.

Why C is correct

C is correct because FIXED at Call ID evaluates all activity rows for that call together. If MAX of assigned equals true, the call had a technician at least once and scores zero, otherwise one. Summing or counting those ones yields exactly calls never assigned, which row level filters cannot isolate.

Why the others are wrong

  • A. INCLUDE plus COUNT of non matching rows inflates when one call has many other activities.
  • B. malformed INCLUDE inside COUNTD does not test whole call history for absence.
  • D. row level not equal marks every non assign row, so assigned calls still contribute counts.

TDA-C01 exam tip

Never assigned means FIXED at ID plus MAX check, not row level not equal.

5You have the following dataset. Which Level of Detail (LOD) expression should you use to calculate the grand total of all the regions?
Tableau Certified Data Analyst (TDA-C01) question 5
  • { FIXED [Region]: SUM(Sales) }
  • { FIXED : SUM(Sales) }
  • { FIXED [Region]: TOTAL(Sales) }
  • { FIXED : TOTAL(Sales) }
Answer: B

The short version

B — empty FIXED gives the grand total. Removing Region from the address collapses all rows into one sum in the settled key.

Key concepts in this question

  • FIXED LOD: sets aggregation grain explicitly, overriding view dimensions when the field list is empty or partial.
  • Empty scope: FIXED with no dimension aggregates the entire dataset to a single value repeated as needed.
  • Region scoped contrast: FIXED with Region returns per region subtotals, preserving breakdown rather than grand total.
  • TOTAL contrast: table calculation dependent on view layout, fragile when filters or paging change.
  • SUM versus TOTAL: SUM aggregates source rows while TOTAL aggregates displayed marks, with different refresh behavior.

Why B is correct

B is correct because FIXED with no dimension instructs Tableau to sum Sales across all regions before view partitioning. The result is a true grand total immune to Region pills on rows or columns. Region scoped or TOTAL variants would return partitioned or layout dependent numbers instead.

Why the others are wrong

  • A. FIXED Region yields one total per region, not the overall grand sum.
  • C. Region plus TOTAL mixes LOD with table calc and stays partitioned.
  • D. empty FIXED with TOTAL misuses aggregation and layout dependence.

TDA-C01 exam tip

Grand total across all means FIXED with nothing before the colon.

6You have the following sets in a Tableau workbook: Top N Customers - Customers of 2020 - Top N Products - Sellers of 2020 - Which two sets can you combine? (Choose two.)
  • Top N Customers
  • Sellers of 2020
  • Customers of 2020
  • Top N Products
Answer: A, C

The short version

AC — Top N Customers plus Customers of 2020 combine because both use Customers. Sets need the same dimension to intersect or unite. Products and sellers use different fields.

Key concepts in this question

  • Set rule: Tableau combines only sets built on an identical dimension.
  • Customer pair: both Top N and 2020 sets slice the Customer dimension, so union and intersect work.
  • Product isolation: Top N Products slices Product, incompatible with customer sets.
  • Seller isolation: Sellers of 2020 slices a seller field, not the customer field.
  • Use case: combining finds loyal high-value buyers present in both customer sets.

Why AC is correct

AC is correct because Top N Customers and Customers of 2020 share the Customers dimension, satisfying the combine prerequisite. Tableau can then union, intersect or subtract them to isolate overlapping cohorts. Top N Products uses Products, Sellers of 2020 uses sellers, neither shares the customer key, so any mix with them is blocked. Dimension equality is the gate, and only A with C passes.

Why the others are wrong

  • B. sellers set uses a different dimension, so it cannot merge with customer sets.
  • D. products set uses Products, incompatible with customer-based logic.

TDA-C01 exam tip

Combine needs same dimension. Customers with customers works, customers with products never does.

7You subscribe to a view that delivers a daily email to your inbox. You want to make the subscription available to other stakeholders. What should you do?
  • From the worksheet, modify the subscription.
  • From the My Content overview page, modify the subscription.
  • From the My Content overview page, modify the alert.
  • From the dashboard overview page, modify the subscription.
Answer: A

The short version

A — Modify the subscription from the worksheet to share it. Worksheet context carries the view plus schedule that others need. Other pages manage ownership or alerts, not this share flow.

Key concepts in this question

  • Subscription scope: tied to a specific view or workbook with cadence and recipients.
  • Worksheet path: opening the subscribed view exposes subscription settings for extension.
  • Sharing intent: adding stakeholders keeps the same snapshot while widening distribution.
  • Content page contrast: My Content overview manages owned items broadly, not this worksheet share edit.
  • Alert contrast: alerts trigger on thresholds, subscriptions deliver snapshots on schedule.

Why A is correct

A is correct because the settled workflow resumes sharing by opening the worksheet and modifying the subscription to include other stakeholders. That keeps the subscribed view, schedule and format intact while adding recipients in one edit. My Content overview edits ownership views generically, alert edits change condition logic, and dashboard overview paths do not match the view-level share. The worksheet modify preserves context and is the keyed answer.

Why the others are wrong

  • B. My Content modify manages owned items broadly, not the worksheet subscription share in this key.
  • C. alert modify changes threshold triggers, unrelated to scheduled email sharing.
  • D. dashboard overview modify misses the worksheet context tied to this subscription.

TDA-C01 exam tip

Share a view subscription from its worksheet. Alerts equal thresholds, content pages equal ownership.

8A Data Analyst is frequently asked to report on events that have a single row per day but may have missing days in the dataset. The analyst needs to fill the gaps in the data between two dates. What should the analyst use to do this in Tableau Prep?
  • Union
  • Pivot
  • Aggregate
  • Now Rows
Answer: D

The short version

D — add New Rows to fill missing dates in Prep. The gap filling step generates calendar rows between min and max dates in the settled key.

Key concepts in this question

  • Missing days problem: single row per day datasets skip holidays or outages, breaking running totals and trend lines.
  • New Rows: Tableau Prep operation that inserts scaffold rows for absent dimension values within a range.
  • Union contrast: stacks additional tables vertically but does not invent absent dates from thin air.
  • Pivot contrast: rotates columns to rows for reshaping, unrelated to calendar completion.
  • Aggregate contrast: summarizes existing rows to coarser grain, which cannot restore dates that never existed.

Why D is correct

D is correct because the analyst needs continuous dates for accurate daily reporting. New Rows builds the full interval between the two boundary dates and leaves measures null for imputation or zero fill. No other listed Prep step synthesizes absent calendar members automatically.

Why the others are wrong

  • A. Union appends present data but never creates missing calendar entries.
  • B. Pivot reshapes fields without generating new date members.
  • C. Aggregate rolls up what exists and preserves gaps.

TDA-C01 exam tip

Gaps between dates in Prep always means New Rows scaffolding.

9When using Tableau Desktop to connect to a published data source on Tableau Cloud or Tableau Server, which data sources will be displayed to the user?
  • Only certified data sources
  • Only the data sources the user has created themselves previously
  • Only the data sources the user has the Connect permission to
  • Only data sources in the user’s home directory
Answer: C

The short version

C — only Connect allowed sources appear. Server permission filters the list to what the user may actually query in the settled key.

Key concepts in this question

  • Connect capability: Tableau permission that authorizes running queries against a published source.
  • Server browsing: Desktop lists sources from Cloud or Server after auth, scoped by effective permissions.
  • Certified contrast: quality endorsement badge that aids discovery but does not gate visibility.
  • Ownership contrast: personal authorship is one path to access, not the rule for enterprise discovery.
  • Home directory contrast: personal folder location for organization, unrelated to cross project source rights.

Why C is correct

C is correct because Tableau enforces content permissions before showing connection targets. Without Connect on a source or its project, the user cannot execute queries, so hiding it avoids dead ends. Certified status, ownership, or home location never override that access check.

Why the others are wrong

  • A. certified marks trusted content but uncertified allowed sources still appear.
  • B. shared team sources appear even when another author created them.
  • D. home directory organizes favorites, not permission scoped discovery.

TDA-C01 exam tip

Published source visibility equals Connect permission, nothing else.

10You have a data source that contains the following columns. You have the following FIXED Level of Detail (LOD) expression. [Region Sales] = {FIXED [Region] : SUM [Sales]} You have a view that has a dimension filter on the State column to exclude five states. What should you do to ensure that the five states are also excluded from the LOD expression?
Tableau Certified Data Analyst (TDA-C01) question 10
  • Right-click the State dimension filter, and then click Add to Context.
  • Right-click the State dimension filter, and then click Attribute.
  • Change the LOD expression to [Region Sales] = {FIXED [Region], [State]: SUM [Sales]}.
  • Drag the LOD expression to the Filters shelf.
Answer: A

The short version

A — Add the State filter to context so FIXED LOD respects it. FIXED computes before dimension filters unless promoted. Context makes the filter apply first.

Key concepts in this question

  • FIXED order: FIXED LOD runs before regular dimension filters in the pipeline.
  • Context power: context filters execute early and constrain both LOD and base queries.
  • State exclusion: removing five states must filter the Region Sales sum, not just the view rows.
  • Attribute contrast: attribute aggregation changes display, not filter precedence.
  • Shelf contrast: dragging LOD to filters does not change its early evaluation.

Why A is correct

A is correct because the Region Sales FIXED expression sums Sales per Region independent of the State dimension filter, so excluded states still inflate totals. Right-clicking State and adding to context promotes it to a context filter that runs before FIXED, forcing the LOD to sum only included states. Changing dimensions in the expression or toggling attribute would not fix ordering. Context promotion is the documented fix for FIXED plus filter interaction.

Why the others are wrong

  • B. attribute changes aggregation display, it does not move filter order before FIXED.
  • C. adding State to FIXED alters granularity rather than enforcing the exclusion cleanly.
  • D. placing LOD on filters controls view inclusion, not the internal LOD computation order.

TDA-C01 exam tip

FIXED ignores normal filters. Add to context to make filters apply first.

Want the full bank of 175 questions for Tableau Certified Data Analyst (TDA-C01)? See all practice exams.