Refer to the exhibits.

The InternEmp table contains information about temporary employees (interns), and the Employees table contains regular employee data. To properly link these two tables, the business analyst needs to create an association between theEmpIDin theInternEmptable and theEmployeeIDin theEmployeestable. This will ensure that the two tables are correctly associated based on the employee identifiers, allowing the system to relate both tables in the data model.

Key Concepts:

Association: Qlik Sense automatically suggests associations between tables based on field names. By linkingEmpIDfrom InternEmp withEmployeeIDfrom Employees, the tables can be properly related in the data model.

Association View: The association view in Data Manager helps visualize how tables are connected and suggests appropriate links between tables based on common fields.

Why the Other Options Are Less Suitable:

A. Create a concatenated key: Concatenation is unnecessary for this scenario since the data model relies on direct associations between keys.

B. Concatenate the tables: Concatenating the InternEmp table into the Employees table would combine the records, but it’s not appropriate since the two tables should remain separate entities.

C. Force an association between InternEmp and Orders: There’s no need to associate InternEmp with Orders directly since the focus is on employees and interns.

References for Qlik Sense Business Analyst:

Field Associations in Qlik Sense: Properly associating fields between tables is crucial for building a clean and efficient data model in Qlik Sense.

Thus, creating an association betweenEmpIDandEmployeeIDis the best approach, makingDthe correct answer.