In this scenario, the data architect needs to replace the SupplierID in the Orders table with the corresponding SupplierName from the Suppliers table, and the desired output should be a single table that includes all the order details along with the SupplierName instead of the SupplierID.

Analyzing the Options:

Option A:

Uses a MAPPING LOAD followed by an APPLYMAP to replace SupplierID with SupplierName in the Orders table. However, the table is dropped afterward, which means it won’t produce the required output.

The MAPPING LOAD approach is generally used to map values but is not necessary in this context as we are combining data from two tables directly.

Option B:

This option attempts to LEFT JOIN the Products table with the Suppliers table, but it does not directly address replacing SupplierID with SupplierName in the Orders table.

Additionally, it does not remove the SupplierID after the join, which is essential for the correct output.

Option C:

This option uses a LEFT JOIN with the DISTINCT keyword on the SupplierID field to avoid duplicates. The SupplierName is correctly joined to the Orders table, replacing the SupplierID.

This approach is the most appropriate because it results in a single table containing all order details with the SupplierName instead of the SupplierID.

Option D:

Similar to Option A, but it also introduces an unnecessary renaming step with MAPPING LOAD. It’s redundant and does not improve the solution over Option C.

Correct Script Choice:

Option Cis the correct script because:

It ensures that SupplierName replaces SupplierID in the Orders table using a LEFT JOIN.

The DISTINCT keyword is applied to the SupplierID field to prevent duplicate rows during the join.

The result is a single table containing the required information with SupplierName in place of SupplierID.

References:

Qlik Sense Join Operations: Using the correct JOIN type and ensuring proper deduplication (with DISTINCT if necessary) is key to merging tables in Qlik Sense.