Select Two (Multi-Select) Questions

Data Mining

Why it fails: Data mining refers to the process of discovering patterns in large data sets. It is not a feature in Tableau for combining data sources. While you can perform data analysis, 'Data Mining' is a broad industry term and not a specific functional mechanism for connecting and integrating datasets.

Data Sorting

Why it fails: Sorting is a visualization technique used to order data in a view. It has nothing to do with combining multiple data sources or integrating datasets. It is an operation performed on existing data, not a method for managing data connections or creating a combined data source model.

Extracting

Why it fails: Extracting is the process of creating a local copy of data to improve performance. It is a format, not a method for combining disparate data sources. While you can extract combined data, extracting itself does not provide the logic to merge or relate data from two different sources.

Convert all dimensions to measures

Why it fails: Converting dimensions to measures is a data modeling error that changes how fields are aggregated. It does not improve query performance and will likely cause incorrect calculations, as categorical data should remain as dimensions to ensure proper partitioning of visual views during the analysis.

Increase the number of dashboard worksheets

Why it fails: Increasing the number of worksheets on a dashboard generally degrades performance. Each worksheet initiates its own query to the data source. Adding excessive sheets forces Tableau to handle simultaneous requests, which can lead to longer load times and a sluggish user experience during exploration.

Use live connections for all data sources

Why it fails: Live connections depend entirely on the performance of the underlying database. If the source is slow or unoptimized, Tableau will be slow. Extracts are usually preferred for performance as they use Tableau’s optimized Hyper engine, which is specifically designed for high-speed analytical processing.

They allow users to change the underlying data source connection type.

Why it fails: Parameters are meant for interacting with fields and calculations within the workbook. They do not have the capability to alter the connection type (e.g., changing from a live connection to an extract) of the data source, as that is a fundamental configuration set during data preparation.

They automatically refresh the data from the database.

Why it fails: Parameters handle user input, not data refresh schedules. Refreshing data is managed through extract schedules or live connection settings. A parameter cannot trigger a database refresh or update the data snapshot; its purpose is solely to pass a user-selected value into the analytical logic of the workbook.

They can be used to permanently delete data from the server.

Why it fails: Parameters are purely for UI interactivity and cannot perform administrative actions like deleting data. Any attempt to use parameters to modify, delete, or write data back to the source database is not supported, as Tableau is designed as a read-only analytical platform for data exploration and reporting.

Drag Sub-Category to the Filters shelf and select 'Wildcard match'.

Why it fails: While wildcard filters are useful for searching within large string lists, a standard multi-select list is more intuitive for categorical filtering in dashboards. Using wildcards can lead to user confusion if they are not familiar with the exact naming conventions of the sub-categories, hindering the overall dashboard usability.

Create a parameter to control the background color of the view.

Why it fails: Parameters are useful for dynamic calculations or changing measure selection, but they do not inherently filter data in the way required by the prompt. Using parameters for styling tasks like background colors is inefficient and does not address the core need for interactive data exploration across categories.

Add a dashboard action to highlight marks on click.

Why it fails: Highlight actions draw attention to specific data points but do not remove or exclude data from the view. Since the requirement is to filter based on thresholds and categories, a highlight action alone will not provide the level of granular data reduction that traditional filter controls offer.

Use as many quick filters as possible.

Why it fails: Excessive use of quick filters can severely degrade performance. Every quick filter added requires a separate query to the data source to populate its values. Limiting the number of active filters is a key strategy for keeping dashboard load times within acceptable thresholds.

Increase the number of dashboard sheets.

Why it fails: Adding more sheets to a dashboard increases the complexity and the number of queries fired upon loading. This directly negatively impacts performance. Best practices suggest keeping the number of sheets in a single dashboard limited to ensure the fastest possible user experience.

A parameter used as a filter on the store dimension

Why it fails: Parameters supply user-controlled values that can drive calculations or filters, but they do not change the granularity at which a measure is aggregated. Filtering stores with a parameter still leaves the aggregation tied to the dimensions on the shelves, so this does not deliver an independent level of detail.

A bin created from the sales measure

Why it fails: Binning groups numeric values into ranges and creates a new discrete dimension. It changes how values are bucketed for display rather than computing an aggregate at a different level of detail, so it cannot produce store-level and category-level totals independent of the view's existing dimensions.

A group combining several product categories

Why it fails: Grouping merges related dimension members into a single category, which simplifies a dimension but does not alter the aggregation level of a measure. The totals would still be computed according to the dimensions on the shelves, so a group does not provide the independent granularity the analyst needs for the two required views.

Create a calculated field to join the columns.

Why it fails: Calculated fields cannot reshape the underlying table structure in the way a pivot does. Attempting to concatenate or join values via calculations is inefficient and does not result in the proper long-format structure required for effective multi-measure analysis in Tableau visualizations.

Drag 'Measure Names' to the filter shelf.

Why it fails: Dragging Measure Names to the filter shelf allows you to select which measures appear in the view, but it does not change the physical structure of your data source. It is an analytical step, not a data preparation or reshaping step.

Use the Split function on the 'Date' column.

Why it fails: The Split function is intended for extracting parts of a string or parsing delimited text. It has no relevance to the task of pivoting measures or reshaping the data format. Applying it to a date field would not assist in achieving the desired wide-to-long transformation.

It automatically joins multiple data sources into a single logical model.

Why it fails: Data Interpreter focuses on cleaning and structuring individual spreadsheet files. It does not perform joins or relationships between separate data sources. Logical modeling is handled in the Data Source page via relationships or joins, which are distinct operations from the automated cleanup processes performed by the interpreter.

It permanently alters the original source file on the user's hard drive.

Why it fails: Data Interpreter only modifies how Tableau interprets the data during the import process. It does not touch or change the original source file. Any cleaning performed is strictly within the Tableau environment, keeping the original data safe and accessible in its raw form for other applications.

It is only available for data sources connected via a live connection.

Why it fails: Data Interpreter is independent of connection types. Whether you are creating an extract or maintaining a live connection to a file, the interpreter is available as an option. Its primary function is to interpret the structure of the incoming data, not the mode of communication used.