Tableau-Desktop-Found Connecting to and Preparing Data — 10 Questions

Question 1

You are creating a data source that combines a large Sales table with a smaller Regions table. You need to ensure that the data remains at the lowest level of detail for the Sales table without duplicating records when joined. Which join type should you prioritize?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Left Join. A Left Join ensures that all rows from the primary Sales table are preserved, while matching rows from the Regions table are appended. This approach maintains the granularity of the Sales table, preventing row duplication that often occurs with Many-to-Many joins or Cartesian products. Understanding join behavior is critical for data integrity and ensuring that calculated fields, such as sums and averages, produce accurate results for business stakeholders.

Answer

Inner Join

Answer

Full Outer Join

Answer

Right Join

Question 2

Which TWO of the following statements regarding the 'Relationship' model in Tableau are true?

Accepted Answer

Relationships preserve the grain of each table. Relationships represent a modern approach to data modeling in Tableau that avoids the pitfalls of static joins. By preserving the individual grain of each table and calculating aggregations dynamically, relationships ensure data accuracy and improve performance. This is critical for users working with complex, multi-table datasets, as it significantly reduces the risk of incorrect calculations resulting from accidental data duplication during the data preparation phase.

Answer

Relationships perform a join at the time of query execution

Answer

Relationships always produce a Cartesian product

Answer

Relationships are only available for Excel files

Question 3

When cleaning data, you need to group similar strings that have slight variations (e.g., 'California', 'Calif.', 'CA'). Which feature should you use to handle this efficiently in the Data Source tab?

Accepted Answer

Group and Replace. Data Interpreter or the 'Group' feature in the Data Source tab is designed to handle messy text data. 'Group and Replace' is a powerful tool for cleaning inconsistent entries without complex formulas. It allows users to consolidate variations into a single, standardized value, ensuring that visualizations are not fragmented by typographical errors or inconsistent naming conventions in the source dataset.

Answer

Data Interpreter

Answer

Split Column

Answer

Change Data Type

Question 4

Which THREE of the following are benefits of creating a Tableau Extract (.hyper) instead of using a Live connection?

Accepted Answer

Improved query performance for large datasets. Extracts are a vital part of the Tableau architecture, offering performance and scalability. Understanding the trade-offs between extracts and live connections is essential for designing efficient data strategies. Extracts are generally preferred for heavy analytical workloads to ensure speed and offload processing from production systems, while live connections are reserved for scenarios where data freshness is the absolute priority over dashboard performance.

Answer

Always reflects the most real-time data possible

Answer

Automatic encryption of all data at rest

Question 5

Refer to the exhibit. You are attempting a cross-database join between an SQL Server table and a CSV file. Given the policy, why might the performance be slower than expected?

Accepted Answer

Data must be pulled into a single engine for processing. Cross-database joins force Tableau to pull data from both sources into a local memory buffer to perform the join. Even with a high-performance engine like Hyper, this requires moving data across the network, which is the primary bottleneck. Recognizing this limitation is crucial for architects when deciding whether to use physical joins or the more performant Relationship model, which optimizes how data is queried from different systems.

Answer

The JSON policy forces the use of a legacy driver

Answer

The Hyper engine cannot process CSV files

Answer

Cross-database joins are restricted by the policy

Question 6

You are connected to a database and need to see the underlying SQL that Tableau generates for your current view. Which feature allows you to view this?

Accepted Answer

View Data window. Viewing the underlying SQL is crucial for debugging complex data connections and optimizing performance. By using the 'View Data' window or the Tableau log files, you can inspect the exact queries sent to the database. This is essential for understanding how your filters, joins, and calculations are being translated into SQL and for working with your DBA to tune the database for better query performance.

Answer

Performance Recorder

Answer

Data Source Page

Answer

Calculated Field Editor

Question 7

When connecting to a live data source, you notice the performance is sluggish. What is the most effective way to improve performance without switching to an extract?

Accepted Answer

Add a data source filter.. Optimizing live connections often involves reducing the amount of data sent to the database or simplifying the query complexity. Context filters are particularly powerful because they create a temporary table, effectively reducing the scope of subsequent queries. This is a critical skill for balancing the need for real-time data against the constraints of database performance in enterprise-grade analytics environments where extract-based workflows might be prohibited by security or latency requirements.

Answer

Switch the data connection to legacy mode.

Answer

Create a group from the existing fields.

Answer

Increase the join complexity.

Question 8

Refer to the exhibit. Why is the 'Pivot' option unavailable for your data source?

Accepted Answer

Live relational databases do not support pivoting in Tableau.. Tableau's pivot functionality is natively supported for file-based data sources (like Excel, CSV) and some specific extracts. However, for live connections to relational databases (like SQL Server), Tableau cannot physically reorder columns into rows because it relies on the database's underlying schema. Understanding these limitations is critical for data architects who must decide between performing structural transformations in the database layer versus using Tableau's internal data preparation capabilities.

Answer

The data source requires a custom SQL query first.

Answer

The user lacks database administrator permissions.

Answer

The date field prevents pivoting of other columns.

Question 9

You are cleaning a dataset and need to replace 'USA', 'U.S.A.', and 'United States' with a single value, 'US'. What is the most efficient feature to use?

Accepted Answer

Use the Alias feature.. The Alias feature is the standard tool for renaming specific members of a dimension without altering the underlying data source. It is ideal for cleaning up inconsistent data entry, like variations in country names. By creating aliases, you standardize the visualization output while keeping the original data values intact, which is critical for maintaining data lineage and auditing purposes in professional reporting environments.

Answer

Use a calculated field with an IF statement.

Answer

Use the Data Interpreter to merge values.

Answer

Use a data source filter to remove the variations.

Question 10

When preparing data, which THREE actions can be performed directly within the Tableau Data Source page? (Choose three)

Accepted Answer

Renaming fields.. The Data Source page acts as a visual interface for managing your data pipeline before it enters the sheet level. Users can perform essential data grooming tasks, such as changing data types, hiding unnecessary columns, and adding filters, directly within this interface. These actions are fundamental to maintaining a clean, performant data model, as they allow for early-stage optimization before complex visualizations are even created, reducing the risk of errors and performance lag in dashboards.

Answer

Writing complex Python scripts.

Answer

Creating dashboard actions.