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

Explanation

If the data is already visible in a table on a webpage, the absolute fastest way to get it into Tableau is by selecting the table, copying it (Ctrl+C), and pasting directly into Tableau. No files, no drivers, no coding – it just works instantly.

✅ Correct Option: B. Clipboard
Tableau treats anything copied from an HTML table as structured data. Simply open Tableau → click in the Connect pane → press Ctrl+V (or Data → Paste Data). In seconds you have a ready-to-use dataset. Perfect for quick exploration with zero setup.

❌ Incorrect Option: A. ODBC connector
ODBC is a database protocol that requires a compatible driver, server address, port, authentication, and often IT/admin approval. Public websites almost never expose their front-end tables via ODBC, so this approach is either impossible or requires building a whole backend extraction pipeline — completely opposite of “least effort.”

❌ Incorrect Option: C. Web data connector
A Web Data Connector needs either a pre-built connector from the Tableau community or custom JavaScript development (HTML parsing, authentication handling, pagination, etc.). Even if a connector exists, you still have to discover, install, configure, and refresh it — far more steps and technical overhead than a simple copy-paste.

❌ Incorrect Option: D. CSV file
Using a CSV forces an extra workflow: the website must offer a download button (many don’t), you wait for the file to save, locate it on your computer, then drag it into Tableau. If no export exists, you’d have to manually copy into Excel first and save — multiple slow, error-prone steps compared to instant clipboard import.

Reference:
https://help.tableau.com/current/pro/desktop/en-us/examples_paste.htm

Explanation:

When you create a subscription in Tableau, you are scheduling a view or dashboard to be automatically sent to one or more users on a regular basis. These subscriptions can be delivered via email, and the content is sent in a non-editable, snapshot format that ensures users see the same version of the data, regardless of their Tableau access level.
As of current Tableau Server and Tableau Cloud functionality:

✅ A. PDF
Tableau supports sending dashboards or views as PDF attachments in subscriptions. This is commonly used for sharing static, printable reports. The PDF preserves formatting and is widely accessible.
➡️ Ideal for executives or stakeholders who prefer printable versions.
➡️ Subscription setup allows choosing PDF as the output format.

🔗 Reference:
Tableau Docs – Subscribe to Views
“When you subscribe to a view, Tableau can send you an image or a PDF of that view.”

✅ B. Image
You can also subscribe users to receive an inline image (PNG) of the view in the email body. This allows users to get a quick glance at the dashboard without opening any attachments.
➡️ Very useful for quick updates.
➡️ The image is generated based on the view as it looks at the time the subscription is triggered.

❌ C. Microsoft Excel
Excel export is not supported as a subscription format. While users can manually export data from a view into Excel (using "Export Crosstab"), this cannot be automated through subscriptions. Excel export is reserved for interactive sessions and on-demand use, not for scheduled delivery.

❌ D. Microsoft PowerPoint
PowerPoint is not a supported subscription format either. While Tableau supports exporting dashboards to PowerPoint manually (via the “Export as PowerPoint” option), it does not allow scheduled delivery of dashboards in PowerPoint format through subscriptions.

Explanation

To filter a published dashboard so that each user only sees the data relevant to them (known as user-based filtering or row-level security), the analyst must create a Boolean calculated field that compares the currently logged-in user's name against a unique identifier field in the data. The Tableau function $\text{USERNAME()}$ returns the username of the user viewing the dashboard on Tableau Server/Cloud. Comparing this result directly to the Tableau_User_Name field will yield $\text{TRUE}$ only for the rows that belong to that user, correctly creating the necessary security filter.

✅ Correct Option: [D] USERNAME()=(Tableau_USER_NAME)
This formula is the standard and correct syntax for implementing row-level security based on usernames in Tableau. $\text{USERNAME()}$ returns the string of the authenticated user (e.g., kh@email.com). The formula evaluates to $\text{TRUE}$ when the logged-in user's username matches the value in the $\text{Tableau\_User\_Name}$ field for that specific row, allowing only those rows to pass the filter for the current viewer.

❌ Incorrect Option: [A] NAMEUSERNAME()
This syntax is invalid in Tableau. There is no standard function named $\text{NAMEUSERNAME()}$. The correct function to retrieve the logged-in user's ID is simply $\text{USERNAME()}$. Since this option is not a valid Tableau function, it would produce an error and cannot be used to filter the data source.

❌ Incorrect Option: [B] ISFULLNAMETableu_USER_NAME))=USERNAME()
This syntax is also invalid. There is a function called $\text{ISFULLNAME()}$ in Tableau, but it is a Boolean function used to test if a string matches the full name of the user, not a function that returns the full name. It is not designed to return a value to be compared against a data column, nor is it correctly structured for comparison.

❌ Incorrect Option: [C] NAME Tableau_USER_NAME)
This syntax is invalid. While $\text{NAME}$ is not a standalone function, the expression structure itself is incorrect for what is required. To establish a filter, an equality check (comparison) must be made between the user's login ID and the data field containing the corresponding login ID, which this option fails to do.

Reference 🔗
Tableau Help: Restrict Access to a Data Source on Tableau Server

Explanation

When preparing data in Tableau Prep for colleagues to use in dashboards on Tableau Cloud or Server, the output must be accessible in the shared Tableau ecosystem. The solution should enable seamless collaboration, automatic refreshes, and centralized management while maintaining data security and governance standards across the organization.

✅ Correct Option

D. A published data source ✅
Publishing the data source directly to Tableau Cloud/Server creates a centralized, managed data asset that multiple users can securely access. This enables automatic refresh schedules, maintains data lineage, and allows your colleague to build multiple workbooks from the same certified source. It provides the best combination of governance, performance, and collaboration for enterprise dashboard development.

❌ Incorrect Options

A. CRM Analytics ❌
CRM Analytics is a specialized platform for AI-powered predictions and relationship analytics, not general dashboard data preparation. This would create unnecessary complexity and wouldn't efficiently serve the straightforward need of building a Tableau dashboard.

B. Salesforce Data Cloud ❌
While integrated with Tableau, Data Cloud is designed for unifying customer data across multiple systems at massive scale. This is over-engineered for a simple prepared dataset meant for colleague dashboard building and adds unnecessary implementation overhead.

C. A Tableau data extract file ❌
While a .hyper extract file provides excellent performance, it creates distribution challenges as colleagues would need manual file sharing. This approach lacks centralized management, automatic refresh capabilities, and the collaborative features needed for team dashboard development.

📝 Summary
A published data source provides the ideal balance of centralized management, automatic refresh capabilities, and secure collaboration for team dashboard development on Tableau Cloud/Server.

📚 Reference
Tableau Help: Publish Data Sources from Tableau Prep - Official documentation on publishing prepared data directly to Tableau Server/Cloud for organizational consumption.

Explanation

Tableau’s built-in Device Layouts feature lets you design once and then create tailored versions of the same dashboard (Desktop, Tablet, Phone) under a single published URL. Tableau Server/Online automatically detects the device and serves the correct layout — no extra work for users.

✅ Correct Option: B. Add device layouts for the dashboard so that appropriate layouts are shown based on the device.
This is the official, recommended way. In Tableau Desktop, go to Dashboard → Device Layouts → Add layouts for Tablet and Phone. Customize each one (reposition, hide, resize objects) while keeping one URL. When published, Tableau automatically delivers the right experience on laptop, iPad, or phone.

❌ Incorrect Option: A. Use floating containers on the dashboard so that the content shifts responsively to adjust for each device.
Tableau does not have true responsive design like a website. Floating objects can be manually rearranged, but they do not automatically reflow or resize intelligently across devices. You still end up with poor mobile experiences without device-specific layouts.

❌ Incorrect Option: C. Create a workbook for each device type and let the users know which one to open on which device.
This works technically but is a terrible user experience. Users must remember and bookmark multiple URLs (or be redirected manually). It also triples maintenance effort — every change has to be copied into three separate workbooks.

❌ Incorrect Option: D. Set the dashboard size to Automatic and let Tableau adjust the layout automatically for each device size.
“Automatic” sizing only scales the entire dashboard up/down like an image — it squishes or stretches content and almost always breaks readability on phones (tiny text, overlapping objects). It is not true device-specific formatting and is strongly discouraged for mobile use.

Reference:
Tableau Official – "Create Device-Specific Dashboards"

Explanation

The Worksheet menu in Tableau Desktop is designed for exporting the visualization itself or its direct data representation. The three primary and direct export functions available through this menu (and the closely linked File menu for PowerPoint) are as an Image (.png), as a Crosstab to Excel (.xlsx), and as a PowerPoint Slide (.pptx). These options allow a user to quickly reuse the worksheet in reports, presentations, or for further data analysis without publishing the entire workbook.

🟢 Correct Options

A. .png: ✔️
This is the standard method for creating a static image of your visualization. Accessed via Worksheet > Export > Image, it opens a dialog box allowing you to include features like legends, titles, and filters in the exported image, making it perfect for embedding in documents or emails.

C. .xlsx: ✔️
This option exports the underlying data that makes up the current view as an Excel crosstab. Found under Worksheet > Export > Crosstab, it generates a new .xlsx file where the data is structured in a tabular format, mirroring the aggregation and layout seen in the worksheet's view.

E. .pptx: ✔️
While initiated from the File menu (File > Export As PowerPoint), this function exports the selected worksheet as a key component. It creates a new PowerPoint presentation where the active worksheet is placed as an image on a single slide, facilitating quick presentation building.

🔴 Incorrect Options

B. .html: ❌
Exporting a single worksheet as a standalone .html file is not a native function of the Worksheet menu. While entire workbooks can be saved to the web, the menu in question does not offer a direct HTML export for a single sheet.

D. .txt: ❌
Tableau does not provide an option to export the worksheet view to a plain text file (.txt) from this menu. The system is focused on visual or structured data exports, not unstructured text.

F. .csv: ❌
The Worksheet > Export > Data command is often confused with a direct CSV export. However, its default behavior is to create a Tableau Data Extract file (.tde or .hyper), not a CSV. To get a CSV, one typically uses the "View Data" feature and copies the data, making it an indirect process, not a direct menu export.

📚 Reference
Tableau Help: Export a View, Data, or Workbook

Explanation

To find the first Tuesday of each month, the standard and most reliable approach in Tableau is to:
Go to the first day of the month using DATETRUNC('month', [Date])
Determine what weekday that day is
Add the correct number of days using DATEADD to reach the first Tuesday
Only one option contains exactly the two functions needed for this logic.

Correct Option:

✅ A. DATETRUNC, DATEADD
This is the officially recommended combination.
Typical formula:
DATEADD('day', (3 + (7 - DATEPART('weekday', DATETRUNC('month', [Order Date]))) % 7 ) % 7 , DATETRUNC('month', [Order Date]) )
It first truncates to the 1st of the month, finds the weekday, calculates how many days to add, then adds them — always landing on the first Tuesday.

Incorrect Options:

❌ B. DATEADD, DATENAME
DATENAME returns text like “Tuesday” instead of a number, so you cannot perform arithmetic with it to add the correct number of days. It is useful for labels, but not for calculating the exact date of the first Tuesday.

❌ C. DATETRUNC, DATEPART
These two functions together can get you to the 1st of the month and tell you its weekday number, but they cannot add days — you remain stuck on the 1st and cannot reach the actual first Tuesday without DATEADD.

❌ D. DATEDIFF, DATEPART
DATEDIFF calculates the difference between two dates and DATEPART extracts parts, but neither can construct or return a new date that falls on the first Tuesday. This pair is completely insufficient for the required result.

Reference:
Tableau Official Functions Reference – DATETRUNC
Tableau Training Videos (2024+) – “First Tuesday of the Month” example uses exactly DATETRUNC + DATEADD

Explanation

Cleaning text fields is an important step in data preparation. When a field such as Name contains characters that do not add value, those characters should be removed without breaking the text into multiple pieces. Tableau provides functions that can test, locate, split, or substitute characters, but only one of these functions can directly replace unwanted symbols with blank values, ensuring the data remains clean and readable.

✔️ Correct Option: D. REPLACE
The REPLACE() function directly replaces selected characters with another value. By using REPLACE([Name], ";", ""), semicolons are completely removed from the text. This function is ideal for cleaning string data because it modifies the text while keeping the original field structure intact, without splitting or returning only a Boolean output.

❌ Incorrect Options

CONTAINS
This function checks whether a text string contains a particular value and returns TRUE or FALSE. Since it only identifies the presence of characters and does not modify the text, it cannot be used to remove or clean unwanted characters such as semicolons.

SPLIT
The SPLIT function divides text into separate segments based on a specified delimiter. Using SPLIT with semicolons would break the Name field into multiple fields, which is unnecessary and undesired when the goal is only to clean a string by removing characters.

FIND
FIND returns the position of a substring within a string. While it can help identify where an unwanted character appears, it does not alter or remove any characters. It is useful for locating text, not modifying or cleaning it.

📎 Reference
🔗 Tableau String Functions: “REPLACE(string, substring, replacement)” https://help.tableau.com/current/pro/desktop/en-us/calculations_calculatedfields_string_functions.htm

Explanation

In Tableau, two or more sets can be combined (using operations like Union, Intersect, or Difference) only if they are derived from the same dimension. Combining sets from different dimensions (e.g., combining a Customer set with a Product set) is logically impossible, as the resulting set would contain incompatible member types. Therefore, the analyst must identify the sets based on the same underlying field.

✅ Correct Option: B
Top N Customers
This set is based on the Customer dimension. Because it shares the same base dimension with the Customers of 2024 set, it can be combined using Tableau's set combination features (e.g., to find customers who are both a Top N Customer and were a Customer of 2024).

✅ Correct Option: C
Customers of 2024
This set is also based on the Customer dimension. Since it is derived from the same dimension as the Top N Customers set, they can be successfully combined. The combination allows for advanced analysis, such as identifying the intersection (customers present in both sets) or the union (all unique customers from both sets).

❌ Incorrect Options

A. Sellers of 2024
This set is based on the Seller dimension (or employee dimension). This dimension is different from the Customer dimension used for options B and C, and the Product dimension used for option D. Therefore, it cannot be combined with the sets based on Customers or Products.

D. Top N Products
This set is based on the Product dimension. This dimension is different from the Customer dimension used for options B and C, and the Seller dimension used for option A. Consequently, it cannot be combined with the sets based on Customers or Sellers.

📖 Reference
Tableau Official Documentation: Combine Sets
Source: Tableau Help: Combine Sets (Search for "Tableau combine sets same dimension" on the official Tableau website)

Note: The official Tableau documentation clearly states that "You can only combine sets if they are based on the same dimension." This rule is fundamental to performing set operations in Tableau.

Explanation

The question asks for a dynamic filter using the City dimension to show only cities with populations greater than 1 million. Since the condition depends on a measure value, the correct approach is applying a rule-based filter that evaluates the population numerically, not by text or ranking.

🟩 Correct Option: Condition Filter
A Condition filter is used when you need to keep dimension members based on a numerical condition from a measure. For example, applying Population > 1000000 while filtering the City dimension ensures that only cities whose population exceeds one million are displayed. It also updates dynamically as population values change in the data.

❌ Incorrect Option: General Filter
A General filter only allows selecting dimension members manually from a list. It does not evaluate numeric rules, so you would have to manually choose each city. When population values change or more cities exceed one million, the filter wouldn’t update automatically.

❌ Incorrect Option: Wildcard Filter
A Wildcard filter is text-based. It filters values using patterns like letters or characters (e.g., cities starting with “S”). Because it cannot compare numbers or measures, it cannot filter based on population size, making it unsuitable for this task.

❌ Incorrect Option: Top Filter
A Top filter ranks dimension members based on a measure (e.g., Top 10 cities by population). It cannot filter based on a specific threshold like population > 1 million. It restricts results based on ranking, not on a numeric condition.

📝 Summary
To show only cities with populations above one million, a Condition filter must be used. It applies a numerical rule to the population measure, unlike general, wildcard, and top filters, which cannot evaluate numeric thresholds.

🔗 Reference
Official Tableau Filter Documentation:
Filter Data from Your Views