Question 11
You are developing a data source in Tableau Prep.
You have two tables named Orders and Employees.
The Orders table was created in 2019 and contains the following columns.

The Employees table contains all the employee information for the various sales teams in the sales department and contains the following columns

You want to prepare the data so that you can analyze sales trends over time for every sales team. Which three actions should you perform in order? (Place the three correct options in order. Use the arrows to move Options to Answer Area. Use Answer Area arrows to re-order the options.)

You have two tables named Orders and Employees.
The Orders table was created in 2019 and contains the following columns.

The Employees table contains all the employee information for the various sales teams in the sales department and contains the following columns

You want to prepare the data so that you can analyze sales trends over time for every sales team. Which three actions should you perform in order? (Place the three correct options in order. Use the arrows to move Options to Answer Area. Use Answer Area arrows to re-order the options.)


Explanation:
To successfully combine the Orders and Employees tables using a horizontal join in Tableau Prep Builder, the matching keys from both sources must share the exact same data type signature.
Action 1 (Fixing the Data Type Mismatch):Looking at the source tables, the ID column in the Orders table is currently stored as a text string (indicated by the Abc icon in image_c08ba9.png), whereas Employee ID in the Employees table is stored as an integer (indicated by the # icon in image_c08bae.png). Attempting to join a string field directly to an integer field will cause an error or result in zero matched records. Therefore, you must add a Clean step first to cast the ID field into a Whole number.
Action 2 (Renaming for Alignment): In the same Clean step, renaming the ID column to match the target field name (Employee ID) ensures data clarity and allows Tableau Prep to automatically recognize and pair the join keys.
Action 3 (Executing the Join): With data types aligned, dragging the Orders flow branch and dropping it on top of the Employees block to select Join creates the relational link needed to bring Sales Team information into the orders stream.
Why Other Options Are Incorrect:
Creating a Union: A Union appends data vertically (stacking rows). Because these tables represent entirely different entity attributes (transactional orders vs. staff directories), a union is fundamentally incorrect.
Filtering out null rows:
While filtering nulls can be useful for cleanup, it does not address the fundamental structural data type mismatch preventing the table join from running.
References:
Tableau Prep Documentation (Join Data): "To join tables, the fields that make up the join clause must have the same data type. If the data types are different, you must convert them in a Clean step before joining."






