Sign in
Home/Tableau/Tableau Desktop Specialist (TDS-C01)/Free questions

Tableau Desktop Specialist (TDS-C01) — Free Practice Questions

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

1What are two methods for renaming a field in a visualization? (Choose two.)
  • From the Data pane, use the field’s drop-down menu and select Rename.
  • From the Data pane, right-click the field and select Replace References.
  • From the Data pane, click and hold on the field until the name is editable.
  • From the Format menu, select Field Labels.
Answer: A, C

The short version

AC — Rename from the Data pane with menu or slow click. Both paths edit the field caption used in the view without changing the underlying data source field name.

Key concepts in this question

  • Data pane rename: edits the display name for the field in the workbook while preserving the remote column name for queries.
  • Drop-down Rename: right-side affordance on each Data pane field that opens an inline rename control for precise edits.
  • Click and hold: slow-click gesture that makes the Data pane label editable directly, matching finder-style rename behaviour.
  • Replace References versus Rename: Replace References remaps field references after a source change, while Rename only changes the label.
  • Format menu scope: controls fonts, shading, borders and number formatting for view elements, not field identity.

Why AC is correct

Tableau documents two Data pane rename paths as standard. Using the field drop-down menu and choosing Rename opens the editable name box for that field. Clicking and holding on the field name until it becomes editable performs the same operation through a direct gesture. Both change only the workbook display name, so visual headers, shelves and tooltips update while extracts and live queries still resolve to the original column.

Why the others are wrong

  • B. Replace References swaps one field for another after data source edits and does not rename the label.
  • D. Format menu Field Labels controls label appearance and position, not the field name itself.

TDS-C01 exam tip

Remember Data pane for identity tasks and Format menu for appearance tasks, since the exam often swaps those scopes to build distractors.

2Which statement accurately describes aliases?
  • You can assign an alias to a field member before creating a visualization.
  • When you assign an alias, the name changes in the database.
  • You can create an alias for a discrete measure.
  • You can create an alias for a continuous dimension.
Answer: A

The short version

A — Aliases relabel members only and can be set before viz building. An alias changes display text in views while the database value and field name stay unchanged.

Key concepts in this question

  • Alias scope: applies to individual members of a discrete field, such as renaming New York to NYC in headers and tooltips.
  • Pre-visualization setup: aliases can be defined from the Data pane or dimension member list before dragging fields to shelves.
  • Database independence: aliasing never writes back to the source system, so extracts, live connections and refreshes keep original values.
  • Dimension member eligibility: aliases require discrete members with distinct labels, not aggregated continuous values.
  • Discrete versus continuous: discrete dimension members form headers that can be relabeled, while continuous values form axes.

Why A is correct

Tableau allows an author to assign aliases to dimension members at any time, including before any view exists, by editing aliases from the Data pane field menu. The alias is stored in the workbook metadata and surfaces wherever that member appears, including filters, legends and tooltips. Because it is presentation metadata, it does not require a view, a calculation or a database write, so statement A is the only accurate description of alias behaviour.

Why the others are wrong

  • B. Aliases never change database values, they only change workbook display text.
  • C. Discrete measures aggregate to numbers and do not expose named members to alias.
  • D. Continuous dimensions produce a quantitative axis without discrete member labels to alias.

TDS-C01 exam tip

Link alias to member relabel and rename to field relabel, since mixing member-level and field-level wording is a classic TDS-C01 trap.

3You need to invert the color intensity of a quantitative range. Which option should you use?
  • Border
  • Reversed
  • Opacity
  • Stepped Color
Answer: B

The short version

B — Reversed inverts the intensity mapping. For a continuous measure on Color, Tableau assigns progressively darker or more saturated shades to larger values by default, and ticking Reversed flips that ramp so larger values receive lighter shades instead.

Key concepts in this question

  • Quantitative color ramp: a continuous gradient where position encodes magnitude, with intensity increasing toward one end.
  • Edit Colors dialog: the Color legend control for palette, stepped treatment, opacity, and direction of the range.
  • Reversed option: a checkbox that flips the low-to-high assignment of colors without changing the field, aggregation, or mark type in the view.
  • Opacity versus direction: opacity controls transparency of all marks uniformly, while direction controls which end of the data range receives the strongest visual weight.
  • Stepped Color: stepped mode bins the range into discrete bands instead of reversing order.

Why B is correct

Reversed is the documented control for flipping assignment of the quantitative palette. When it is selected, the color that previously encoded the minimum now encodes the maximum and vice versa, so darker shades move to the opposite end of the range. That inverts intensity immediately without recoding data.

Why the others are wrong

  • A. Border controls the outline drawn around marks and has no effect on interior fill ramp direction.
  • C. Opacity makes every color more transparent and washes the view out, but it preserves which values are darkest versus lightest.
  • D. Stepped Color converts a smooth gradient into a fixed number of discrete color bands and does not flip the low-to-high order by itself.

TDS-C01 exam tip

Think ramp flip equals Reversed, fade equals Opacity, bands equals Stepped — only Reversed answers invert intensity.

4You need to display the complete list of potential data connections when you connect to a server. What action should you perform?
  • Select Connecting to Data.
  • Select More under To a File.
  • Select More under To a Server.
  • Select File on the menu, and then select New.
Answer: C

The short version

C — More under To a Server reveals the full connector list. The Connect pane on the Start page shows only recently used and common server types at first, and the More link expands that section to every installed server connector.

Key concepts in this question

  • Connect pane: the left-hand panel on the Tableau Desktop Start page where file, server, and saved data source entry points are organized for new connections.
  • To a Server section: the grouping that lists Tableau Server, Tableau Cloud, and common databases such as SQL Server, MySQL, and cloud warehouses.
  • More link pattern: progressive disclosure used separately under To a File and To a Server so the initial screen stays compact.
  • Search for Data and Tableau Server integration: the path for governed content, distinct from creating a direct database connection from the connector catalog.
  • File versus New menu paths: File and New actions manage workbook lifecycle, not enumeration of available connection types for servers.

Why C is correct

Tableau documentation describes the Start page as showing file types first, then common or recent server types, with a More option to see the complete list. Selecting More under To a Server therefore exposes connectors hidden from the abbreviated view. That matches the task wording exactly, which asks for the complete list of potential server connections rather than a single recent or featured connector.

Why the others are wrong

  • A. Connecting to Data language is not the Start page control that expands the catalog of server connectors.
  • B. More under To a File expands flat-file types such as Excel, Text, JSON, and spatial files, not server-based databases and platforms.
  • D. File then New creates a new workbook context and does not enumerate the server connector library.

TDS-C01 exam tip

Remember File equals files, Server More equals servers — match the More link to the section you want to expand.

5When creating a data source, how can you add additional connections to different databases?
  • From the drop-down menu of the current connection, select Edit Connection.
  • From the Connections pane, select Add.
  • From the Data menu, select New Data Source.
  • From the File menu, select New.
Answer: B

The short version

B — Add in the Connections pane adds another connection to the same data source. That keeps both connections inside one data source so tables from different databases can be combined with joins, unions, or logical relationships.

Key concepts in this question

  • Connections pane: the upper area of the Data Source page that lists each active connection contributing tables to the current data source.
  • Add action: the control that introduces a second connection, even cross-database, without discarding the existing connection.
  • Single data source with multiple connections: the structure that enables cross-database joins and federated logic inside one logical model on Desktop.
  • New Data Source versus Add connection: a new data source creates an isolated container with its own canvas, while Add extends the current container.
  • Edit Connection scope: editing changes server, database, credentials, or options for the selected existing connection rather than appending a new one.

Why B is correct

Adding from the Connections pane is the documented way to bring tables from a different database into the data source you are already building. Because both connections remain in the same data source, you can then define joins, unions, or relationships across them. Creating a separate data source would prevent that unified modeling and would instead require blending.

Why the others are wrong

  • A. Edit Connection modifies the parameters of the current connection and does not append an additional database connection.
  • C. New Data Source from the Data menu starts a separate independent source instead of extending the one being created.
  • D. New from the File menu starts a new workbook or clears context and does not add a connection to the active data source.

TDS-C01 exam tip

Extend equals Add, isolate equals New Data Source — choose Add when tables must live and join in one source.

6What are two characteristics of relationships? (Choose two.)
  • Relationships will query every table in a data model regardless of whether the fields are in the visualization.
  • Relationships will query only the tables and fields needed to create a visualization.
  • Relationships are only supported when using extracts.
  • Relationships are aware automatically of the native level of detail of logical tables.
Answer: B, D

The short version

BD — Relationships query only needed tables and respect native granularity. They defer joins to query time and preserve each logical table level of detail automatically.

Key concepts in this question

  • Logical layer relationships: flexible links between logical tables defined by matching fields without merging into one physical table.
  • Query pruning: Tableau generates SQL that touches only tables whose fields are actually used in the current view.
  • Native level of detail: each logical table keeps its own row grain, so orders, customers and returns do not duplicate prematurely.
  • Joins versus relationships: joins fix row grain at data source time, while relationships resolve grain dynamically per view.
  • Extract compatibility: relationships work with live connections and extracts, not extracts alone.

Why BD is correct

Relationships were designed to avoid the over-querying and fan-out of premature physical joins. When a view uses only two of five related tables, Tableau queries only those tables and joins on the fly at the correct aggregation level. Each logical table also retains awareness of its own native granularity, so counts and sums stay correct when fields from different grains combine. Those two behaviours together define the modern data model and make B and D correct.

Why the others are wrong

  • A. Relationships specifically avoid querying every table, querying only what the view needs.
  • C. Relationships are fully supported for live connections as well as extracts.

TDS-C01 exam tip

Picture relationships as lazy and grain-aware and joins as eager and fixed, then choose relationship answers when the question mentions differing aggregation levels.

7What are two examples of a date value? (Choose two.)
  • January 1, 1995
  • December
  • Wednesday
  • 2020-05-01
Answer: A, D

The short version

AD — Full calendar dates count as date values, parts alone do not. January 1, 1995 and 2020-05-01 resolve to specific points on the calendar accepted by Tableau date parsing.

Key concepts in this question

  • Date value definition: a complete year plus month plus day that maps to one calendar position and supports date arithmetic.
  • Date part versus date value: December or Wednesday names a recurring part used for grouping, not a unique storable value.
  • ISO date literal: 2020-05-01 follows year-month-day order and parses unambiguously across locales.
  • Locale long form: January 1, 1995 includes month name, day and year and converts to a true date type.
  • String versus date type: text that looks date-like stays a string until Tableau casts it to a date domain.

Why AD is correct

Tableau treats a date value as any literal that identifies one exact day, which can then be drilled to year, quarter, month or day parts or placed on a continuous axis. January 1, 1995 supplies all three components in long form and 2020-05-01 supplies them in ISO form, so both cast cleanly to Date. By contrast December lacks year and day and Wednesday lacks month and year, making them parts for partitioning rather than values for the date domain.

Why the others are wrong

  • B. December alone is a month part that recurs every year and cannot anchor a timeline.
  • C. Wednesday alone is a weekday part used for cyclic grouping, not a unique date.

TDS-C01 exam tip

Ask whether the literal pins one calendar day, and if year, month or day is missing, treat it as a part rather than a value.

8What are three reasons to use joins instead of relationships? (Choose three.)
  • You need to use a specific join type.
  • You need to create an extract that will have multiple tables.
  • You need to use row-level security.
  • You need to use a data model that supports shared dimensions.
  • You need to connect to multiple databases.
Answer: A, C, D

The short version

ACD — Explicit join type, row-level security, and shared dimensions still favor joins. Relationships are the modern flexible default, but physical joins remain required when you must fix join logic, filter physically, or reuse one dimension across multiple fact tables.

Key concepts in this question

  • Logical versus physical layer: relationships define flexible logical links resolved per view, while joins materialize one combined physical table with fixed row logic.
  • Explicit join type control: inner, left, right, and full outer semantics enforced at the table level before analysis begins.
  • Row-level security with joins: entitlement filters that depend on a physically joined user table so unauthorized rows never enter the extract or view.
  • Shared dimensions in a star pattern: one conformed dimension table joined to several fact tables to guarantee consistent definitions across measures.
  • Cross-database and multi-table extracts: capabilities that both models can support in modern versions, so they do not by themselves force a join.

Why ACD is correct

Tableau help on data model migration states to use relationships by default and to use joins only when absolutely needed, then lists explicit join type, shared-dimension modeling, and row-level security as valid exceptions. Physical joins also support entitlement designs where security is baked into the table, plus classic star schemas with shared dimensions. Those three conditions together define the settled key.

Why the others are wrong

  • B. Multi-table extracts can be built from logical tables and relationships, so extracts alone do not require physical joins.
  • E. Both joins and relationships can span multiple databases through cross-database combinations, so that capability does not decide between them.

TDS-C01 exam tip

Default to relationships, switch to joins for fixed type, security, shared dimensions — memorize type, security, shared.

9What are three benefits of using an extract as compared to a live connection to a data source? (Choose three.)
  • A live connection to a data source provides the best performance for data connections.
  • Calculated fields perform better in workbooks connected to extracts than in workbooks with live connections to a data source.
  • Extracts are stored in memory (RAM), resulting in faster query performance as compared with live data connections.
  • An extract reduces the amount of data stored on a client computer as compared to a live data connection.
  • A live connection to a data source can be slow due to network and user traffic, whereas a connection to an extract improves performance.
Answer: B, C, E

The short version

BCE — Extracts cache data locally for faster calc and query speed. In-memory Hyper storage avoids network and source load that slow live connections.

Key concepts in this question

  • Hyper extract: compressed columnar snapshot stored locally that answers queries from RAM and disk without round trips.
  • Calculated field speed: extracts pre-materialize and optimize many row-level and aggregate evaluations inside Hyper.
  • Network overhead: live queries pay database compute plus transfer time and contend with other users and traffic.
  • Client storage trade-off: extracts add a local .hyper file, so they use more client disk rather than less.
  • Live connection strength: live gives real-time freshness, not best performance under load.

Why BCE is correct

Extracts move query execution from a remote database to a local Hyper file tuned for analytics, so filtering, aggregation and calculated fields evaluate faster. Because data sits in memory-optimized structures, query latency drops and interactive exploration stays responsive. Live connections must instead send SQL over the network, wait for source execution and compete with production traffic, which is why avoiding that path improves performance and makes B, C and E correct characterizations of extract benefits.

Why the others are wrong

  • A. Live connections are valued for freshness, not for best performance.
  • D. Extracts increase local storage with a .hyper file rather than reducing stored data.

TDS-C01 exam tip

Pair extract with speed and offline snapshot and live with freshness and governance, then check whether the stem asks about performance or currency.

10How can you access options to apply bold formatting to an axis in the view?
  • Select Text on the Marks card.
  • Select Field Labels on the Format menu.
  • Right-click on the Field and select Format.
  • Right-click on the axis.
Answer: D

The short version

D — Right-click the axis itself to reach its font controls. The axis context menu opens Format with axis scope for bold and other type settings.

Key concepts in this question

  • Axis context scope: right-clicking an axis selects that axis as the formatting target for tick labels and title.
  • Format pane scoping: the Format pane follows the selected sheet element, so axis, header, title and pane each expose different options.
  • Marks card scope: Text on the Marks card edits mark labels inside the plot, not surrounding axis labels.
  • Field-level Format: formatting a field from Rows or Columns edits default number or font for that field broadly.
  • Direct manipulation: Tableau favours right-clicking the visual element you want to change for fastest access.

Why D is correct

Axis type styling lives with the axis object, so the documented gesture is to right-click directly on the axis tick labels or axis line and choose Format or Font settings. That action scopes the Format pane to the selected axis, exposing bold, italic, size and colour for ticks and title without affecting mark text or other sheet chrome. Because the requirement is axis-specific bolding in the view, the direct axis menu is the precise and minimal path.

Why the others are wrong

  • A. Text on the Marks card formats labels on marks inside the chart, not axis labels.
  • B. Field Labels on the Format menu styles table headers and totals labels, not continuous axes.
  • C. Formatting the field changes default field formatting rather than the specific view axis instance.

TDS-C01 exam tip

When the stem names a view element, right-click that element first, since Format scope follows selection and generic menus often miss the target.

Want the full bank of 117 questions for Tableau Desktop Specialist (TDS-C01)? See all practice exams.