Free Salesforce-Tableau-Data-Analyst Practice Test Questions (2026)

Explanations:

A. Add Math Score to the Rows shelf and History Score to the Columns shelf.

Why it's correct: To create a scatter plot in Tableau, you need a measure on the Rows shelf and a measure on the Columns shelf. In this exhibit, the vertical Y-axis represents the Math Score and the horizontal X-axis represents the History Score. Therefore, Math Score must go on Rows and History Score on Columns. This creates the basic two-dimensional plot structure.

C. Drag Student ID to Detail on the Marks card.

Why it's correct: When you place two measures on Rows and Columns, Tableau defaults to aggregating them (usually as a SUM or AVG), resulting in only one single dot on the view. To see a distinct dot for each student (as shown in the exhibit), you must disaggregate the data. Dragging the unique identifier (Student ID) to the Detail property on the Marks card tells Tableau to plot one mark per student row in the dataset, creating the scatter plot.

E. Drag in a Trend Line from the Analytics pane.

Why it's correct: The exhibit displays a solid diagonal line passing through the data points. This is a linear trend line (regression line) used to analyze the correlation between the two variables. In Tableau, you create this by navigating to the Analytics pane (next to the Data pane), expanding the Model section, and dragging Trend Line onto the view (dropping it on the "Linear" option).

❌ Why the other options are incorrect:

B. Right-click the y-axis, and then select Add Reference Line.

Why it's incorrect: While adding reference lines to an axis is a valid Tableau feature, it is not the correct method to create the diagonal trend line shown in the exhibit. Right-clicking the axis allows you to add horizontal or vertical reference lines (like averages or constants), not a dynamic regression/trend line that angles across the plot. To get the line shown, you must use the Analytics pane (Option E).

D. Add History Score and Math Score to the Marks card.

Why it's incorrect: If you add measures directly to the Marks card (like the Color, Size, or Label properties), you are modifying how the marks look or are aggregated, but you are not defining the X and Y axes. The axes are defined by the Rows and Columns shelves (Option A). Simply adding them to the Marks card without putting them on Rows/Columns will not generate the scatter plot shown.

🔗 References:

Tableau Help: Build a Scatter Plot (Confirms Measures on Rows/Columns and Dimension on Detail).

Explanation

The correct answer is A. [Event Date] <= TODAY() AND DATETRUNC("year", [Event Date]) = DATETRUNC("year", TODAY()). Year-to-date (YTD) means including all events from the beginning of the current year up to and including today's date. This formula has two required conditions. First, [Event Date] <= TODAY() ensures that no future dates beyond today are included. Second, DATETRUNC("year", [Event Date]) = DATETRUNC("year", TODAY()) ensures that the event's year matches the current year by truncating both dates to the first day of their respective years and comparing them. Together, these conditions correctly return only events that occurred between January 1 of the current year and today. This makes option A the correct answer.

Why the other options are incorrect:

B. [Event Date] <= DATETRUNC("year", [Event Date])
– This formula compares the event date to the first day of its own year. Since any date is greater than or equal to the start of its own year, this condition effectively includes all dates and does not restrict the data to the current year or to the present day. It does not accomplish year-to-date filtering.

C. DATETRUNC("year", [Event Date]) = DATETRUNC("year", TODAY())
– This formula only checks that the event occurred in the current calendar year. It does not exclude future dates within the current year, so events scheduled later this year would incorrectly be included. It is missing the [Event Date] <= TODAY() condition.

D. [Event Date] > TODAY() AND DATETRUNC("year", [Event Date]) = DATETRUNC("year", TODAY())
– This formula uses > instead of <=, which returns only future events in the current year. This is the exact opposite of year-to-date filtering, which requires past and present events.

Reference:

Tableau Desktop Specialist and Tableau Data Analyst content areas on Calculations and Date Functions — specifically using TODAY(), DATETRUNC(), and logical operators (AND) to create dynamic year-to-date filters.

Explanation

The Edit Data Source Filters dialog box is designed to manage filters that are applied to the entire data connection before any worksheet processing occurs. These filters are global and affect all worksheets using that data source. When you choose to apply a dimension filter from the Filters shelf to "All Using This Data Source," Tableau promotes this filter to the data source level, and it is subsequently listed in the Edit Data Source Filters dialog box.

Options Analysis

✔️ Correct Option: [D] A dimension filter on all the sheets
When an analyst applies a dimension filter on the Filters shelf of a worksheet and changes its scope to "All Using This Data Source," it is automatically recognized and listed in the Edit Data Source Filters dialog box. This is because a filter applied to all sheets using the same source functions as a data source filter, limiting the underlying data before it reaches any view.

❌ Incorrect Option: [A] A table calculation filter used on Sheet
Table calculation filters operate at the very last step of Tableau's Order of Operations, long after the data has been loaded and the view table has been created. They filter what is displayed based on aggregated results, but they do not filter the underlying data source. Therefore, a table calculation filter would never appear in the Edit Data Source Filters dialog.

❌ Incorrect Option: [B] A top N condition filter on a dimension in Sheet 1 and Sheet2
A Top N filter is a type of Dimension filter applied on the Filters shelf. However, it is fundamentally a worksheet-level filter unless its scope is explicitly set to "All Using This Data Source." Even when applied to a select set of sheets like Sheet 1 and Sheet 2, it remains a global filter, which is a separate scope from a true data source filter that applies to all sheets and is listed in the dedicated dialog.

❌ Incorrect Option: [C] A context filter on a dimension in Sheet3
A Context Filter is executed early in the query pipeline, but it is still a worksheet-level filter (or set of filters) designed to work within the confines of a single worksheet's data table before dimension filters are applied. It is not a global filter that applies to all worksheets equally and therefore does not get listed or managed in the Data Source Filters dialog box.

Reference 🔗
Tableau Help: Filter Data from Your Data Source: The official documentation states that when you create a data source filter, any global filters that use that data source are displayed automatically in the Edit Data Source Filters dialog box.

Explanation

The correct answer is D. Select Sheet 3 on the dashboard and click the Swap Sheet button next to Sheet 2. In Tableau Desktop, when a dashboard contains a worksheet that needs to be replaced, the analyst can select the existing sheet on the dashboard (Sheet 3) and then locate the desired replacement sheet (Sheet 2) in the Sheets list on the left side of the Dashboard pane. A "Swap Sheet" button will appear next to Sheet 2. Clicking this button replaces Sheet 3 with Sheet 2 while preserving the position and layout within the tiled container. This makes option D the correct answer.

Why the other options are incorrect:

A. Select Remove Dashboard Item from the context menu of Sheet 3
– This removes Sheet 3 from the dashboard but leaves an empty space. It does not insert Sheet 2 in its place, requiring the analyst to manually add Sheet 2 afterward and reconfigure the layout.

B. Right-click Sheet 2 and select Add to Dashboard
– This adds Sheet 2 as a new tiled item, potentially creating a second container or disrupting the existing layout. It does not replace Sheet 3; both sheets would appear on the dashboard.

C. Select Deselect from the context menu of Sheet 3
– The "Deselect" option is unrelated to replacing a sheet. It simply removes the current selection from the sheet and has no effect on swapping worksheets.

Reference:

Tableau Desktop Specialist and Tableau Data Analyst content areas on Dashboards — specifically replacing worksheets using the Swap Sheet button, managing tiled dashboard layouts, and preserving container structure when substituting sheets.

Explanation

The correct answer is D. Connect to the Excel file using Tableau Desktop and publish the data source to the Tableau site, then schedule it to refresh. Create a new workbook and connect to both the revenue and goals data sources. Since the revenue data is already published to the corporate Tableau site, the analyst should connect to it directly. The goals data, however, is stored in an Excel file that must be updated regularly by sales managers. To ensure the dashboard stays current and accessible to others, the analyst should publish the Excel-based data source to Tableau Server/Cloud and set up a scheduled refresh (or configure it to be refreshed manually/on a schedule). This allows the sales managers to update the Excel file, and the published data source can then be refreshed on a schedule so the workbook always reflects the latest goals. The analyst then creates a new workbook that connects to both the published revenue data source and the newly published goals data source. This makes option D the correct answer.

Why the other options are incorrect:

A. Log in to the Tableau site and create a new workbook. Upload the Excel file and connect to the published revenue data source
– While web authoring allows connecting to published data sources, uploading the Excel file directly into a workbook does not establish a managed, refreshable data source for the goals. The workbook would rely on static data that cannot be easily scheduled for refresh or reused across workbooks.

B. Ask the Enterprise Resource Planning (ERP) developers to add new fields to the employee records to store the sales rep goals. Update the existing revenue data source to include the new fields
– This approach is overly complex, time-consuming, and outside the analyst's control. It also assumes the ERP system is the right place to store sales goals, which may not be accurate or feasible. The requirement is to use the existing Excel file updated by sales managers.

C. Create a new workbook in Tableau Desktop and connect to both the published revenue data and an extract of the Excel file. Publish the new workbook to the Tableau site
– While this creates a working workbook, using an extract of the Excel file means the goals data becomes static and will not automatically reflect updates made by sales managers. It does not establish a refreshable, shared data source, so the goals data would become stale over time.

Reference:

Tableau Desktop Specialist and Tableau Data Analyst content areas on Data Sources and Publishing — specifically publishing data sources to Tableau Server/Cloud, scheduling extract refreshes, connecting to published data sources, and combining multiple data sources for dashboard creation.

Explanation

The correct answer is D. Add All Subtotals. The desired result shows a "Total" row appearing after each Category group (Furniture, Office Supplies, Technology), summarizing the Sales values for the Sub-Categories within each Category. This is a subtotal, which aggregates data at an intermediate level of a hierarchy. In Tableau, the "Add All Subtotals" option under the Totals submenu of the Analysis menu automatically generates subtotal rows for every dimension in the view (in this case, for the Category dimension), producing the exact layout shown in the desired visualization. This makes option D the correct answer.

Why the other options are incorrect:

A. Show Column Grand Totals
– Column Grand Totals add a single total row at the very bottom of the entire table, summarizing all Categories combined. This would not produce the per-Category "Total" rows shown in the desired result.

B. Show Row Grand Totals
– Row Grand Totals add a total column at the far right of the table, summarizing all measures across rows. This does not create the "Total" rows displayed in the desired result and is unrelated to the required output.

C. Column Totals to Top
– This option simply moves existing column grand totals from the bottom to the top of the table. It does not create the per-Category subtotal rows required for the desired result.

Reference:

Tableau Desktop Specialist and Tableau Data Analyst content areas on Totals and Subtotals :— specifically using the Analysis menu to add subtotals, the distinction between grand totals and subtotals, and applying "Add All Subtotals" to generate per-dimension summary rows in a hierarchical view.

Explanation

The workbook uses a live SQL Server connection that only your department can access. When you publish it to a Tableau Server site (Public) where everyone can view it, users who don’t have database access will not be able to see the data unless you either extract the data or embed credentials so Tableau authenticates on their behalf.

🟩 Correct Option A: Change the data source to an extract before you publish
Using an extract copies the data into Tableau Server instead of relying on the live SQL Server connection. Since the extract no longer requires direct database access, all users who can access the workbook can view the data. This removes dependency on SQL Server permissions and ensures wide access while maintaining performance benefits of extracts.

🟩 Correct Option B: Embed the credentials when you publish the workbook
When you embed credentials, Tableau Server uses those credentials to connect to the SQL Server database, even if users do not have database access. This allows every user to view the workbook without requiring access privileges to the underlying database. It keeps the live connection functional and secure while providing shared access to the visualizations.

❌ Incorrect Option C: Remove all the data source filters before publishing
Removing filters does not affect database security or connectivity. Users still wouldn’t be able to see the data without access to SQL Server. Filters only control data visibility on Tableau, not access to the underlying source, so this does not solve the permission issue.

❌ Incorrect Option D: Export the data to a .csv before publishing
Exporting to a CSV breaks the connection and workflow, requiring new data imports for every update. It also removes the advantages of using Tableau Server data refreshes, automation, and secure handling of data. This is not a recommended or scalable way to share data on Tableau Server.

❌ Incorrect Option E: Configure the local file permissions to the workbook
Changing file permissions on the local workbook before publishing does not control data access once it is hosted on Tableau Server. Tableau Server permissions and data source credentials determine access, so modifying local file access has no impact on server access to the database.

📝 Summary
To ensure everyone can view the workbook on Tableau Server Public, you must either embed database credentials or convert the live connection to an extract. These choices enable access even for users who cannot connect to SQL Server.

🔗 Reference
Tableau Server Data Authentication (Official Documentation):
https://help.tableau.com/current/server/en-us/datasource_permissions.htm

Explanation

The correct answer is D. Modify the XML tags in the Preferences.tps file in My Tableau Repository. To add a custom color palette that can be used across multiple workbooks in Tableau Desktop, the analyst must edit the `Preferences.tps` file located in the My Tableau Repository folder. This XML file allows users to define custom color palettes by adding specific `` tags with a name and a list of hex color codes. Once the file is saved and Tableau is restarted, the custom palette becomes available in the color legend menu for any workbook, ensuring consistent company branding across all visualizations. This makes option D the correct answer.

Why the other options are incorrect:

A. Define new shapes for the colors of the custom color palette and copy the shapes to the Shapes folder in My Tableau Repository
– The Shapes folder is used for custom shape palettes (images used as marks), not for color palettes. Copying shape files has no effect on defining custom colors.

B. Select the colors from the color picker and click Add to Custom Colors
– The "Add to Custom Colors" feature in the color picker only saves a color temporarily for the current session or workbook. It does not create a reusable, named palette that persists across multiple workbooks.

C. Select Worksheet Formatting from the Format menu for the worksheet. From the color picker, select Shading, and then select the colors
– This approach only applies formatting to a specific worksheet or view. It does not create a global custom color palette that can be reused across different workbooks.

Reference:

Tableau Desktop Specialist and Tableau Data Analyst content areas on Formatting and Customization — specifically creating custom color palettes by editing the Preferences.tps file, using XML `` tags, and making branded palettes available across all workbooks.

Explanation

The file extension .tds stands for Tableau Data Source. This is a proprietary Tableau file type designed to save the connection information to data, without saving the actual data itself. A .tds file stores details like the database server name (e.g., SQL Server), port, credentials (or prompt for them), and any customized settings, folders, calculations, or hierarchies applied within Tableau. This file type is specifically used to share and reuse a standardized connection setup.

✅ Correct Option: B. Sales.tds
The .tds (Tableau Data Source) file is an XML file created by Tableau Desktop. Its primary function is to store the full definition of a data connection, including the type of database (e.g., SQL Server), server address, authentication requirements, and any metadata customizations specific to Tableau. It acts as a shortcut or template, allowing an analyst to easily reconnect to the external data source without having to rebuild the connection from scratch.

❌ Incorrect Option: A. Sales.csv
A .csv (Comma Separated Values) file is a plain text file that contains the raw, delimited data itself. It does not contain any connection information to an external, live data source like an SQL Server database. The data within a CSV is already static and local to the file, and it is not designed to maintain a dynamic connection.

❌ Incorrect Option: C. Export.mdb
A .mdb file is a file format used by Microsoft Access Database. While it is a database that contains both data and database objects, it is a local, file-based database. It does not contain the connection instructions for a separate, external SQL Server database, which is typically accessed via an ODBC/JDBC driver and a .tds or similar connection file.

❌ Incorrect Option: D. Book1.json
A .json (JavaScript Object Notation) file is a standard text-based format for transmitting and storing data, often used by web applications. Similar to a CSV, a JSON file contains the raw data itself, structured in key-value pairs. It does not contain the necessary connection instructions, drivers, or metadata to establish a live connection to an external SQL Server database.

📚 Reference
You can find the official documentation for Tableau file types:
Tableau Help: Tableau File Types and Folders

Explanation

The correct answer is B. Add Invoice Number to the Marks card Detail shelf. The current result shows only one aggregated mark per Vendor because Tableau is aggregating the Discount values (using AVG by default) at the Vendor level. To create a proper box plot, Tableau needs access to the individual, disaggregated data points for each Vendor. Adding a unique identifier, such as Invoice Number, to the Detail shelf of the Marks card disaggregates the data, allowing Tableau to plot every individual Discount value. Once the individual marks are visible, the Box Plot reference line can accurately calculate and display the distribution (median, quartiles, and whiskers) for each Vendor, as shown in the desired result. This makes option B the correct answer.

Why the other options are incorrect:

A. Allow whiskers to extend to the maximum extent of the data
– This configuration setting only changes how the whiskers of the box plot are drawn (e.g., to the 1.5 IQR or the full data range). It does not resolve the underlying issue that the data is currently aggregated into a single mark per Vendor. The box plot cannot be generated correctly without individual data points.

C. Change AVG(Discount) field aggregation to Count Distinct
– Changing the aggregation to Count Distinct would count the number of unique discount values per Vendor. This would still result in a single aggregated mark per Vendor and would not provide the individual discount values needed to draw the box plot.

D. Convert AVG(Discount) field to Discrete
– Converting the measure to discrete would change how the values are displayed on the axis (as individual headers rather than a continuous range). It does not disaggregate the data or provide the individual points required for the box plot distribution.

Reference:

Tableau Desktop Specialist and Tableau Data Analyst content areas on Visualizations — specifically creating box plots, the requirement of disaggregated data using a dimension on the Detail shelf, and configuring reference lines for distribution analysis.