New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Qlik QSBA2024 Exam - Topic 2 Question 1 Discussion

Actual exam question for Qlik's QSBA2024 exam
Question #: 1
Topic #: 2
[All QSBA2024 Questions]

Refer to the exhibit.

Refer to the exhibits.

A business analyst must add a list of temporary employees (interns) to the current sales app. The app contains an existing employees table. When the business analyst profiles the data, the association view displays possible associations as shown.

Which action should the business analyst take in Data manager to meet the requirements?

Show Suggested Answer Hide Answer
Suggested Answer: D

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 the EmpID in the InternEmp table and the EmployeeID in the Employees table. 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 linking EmpID from InternEmp with EmployeeID from 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 between EmpID and EmployeeID is the best approach, making D the correct answer.


Contribute your Thoughts:

0/2000 characters
Jennie
3 months ago
Why not just concatenate the tables? Seems easier!
upvoted 0 times
...
Alita
3 months ago
Totally agree with D, it’s the most straightforward approach.
upvoted 0 times
...
Jess
3 months ago
Wait, can you really force an association like that? Sounds risky.
upvoted 0 times
...
Jesusita
4 months ago
I think A makes more sense for a clean association.
upvoted 0 times
...
Luis
4 months ago
Looks like option D is the way to go!
upvoted 0 times
...
Luis
4 months ago
I feel like creating a concatenated key could work, but I don't recall if that's necessary in this case. Maybe we should focus on the existing fields instead.
upvoted 0 times
...
Belen
4 months ago
I'm a bit confused about whether we should concatenate the tables or just create an association. I guess it depends on how the data is structured.
upvoted 0 times
...
Rebbeca
4 months ago
I remember practicing a similar question where we had to link different tables. I feel like option D makes the most sense here.
upvoted 0 times
...
Marla
5 months ago
I think we might need to create an association between the EmpID and EmployeeID fields, but I'm not entirely sure if that's the best approach.
upvoted 0 times
...
Verona
5 months ago
This seems straightforward. I'll just create an association between the EmpID and EmployeeID fields to tie the interns into the existing system. Simple solution!
upvoted 0 times
...
Cecilia
5 months ago
I'm a bit confused by the association view - not sure I fully understand how the tables are currently linked. I'll need to spend some time analyzing that before choosing an action.
upvoted 0 times
...
Lucia
5 months ago
Okay, I've got a plan. I think creating a concatenated key to link the two tables is the best approach here. Let me double-check the details.
upvoted 0 times
...
Farrah
5 months ago
Hmm, the key seems to be finding the right way to associate the InternEmp table with the existing Employees table. I'll need to think through the options carefully.
upvoted 0 times
...
Alex
5 months ago
This looks like a tricky one. I'll need to carefully review the association view to understand the existing relationships before deciding how to add the interns.
upvoted 0 times
...
Meaghan
1 year ago
I'm voting for D, the good old-fashioned association. Although, I do have to wonder - who comes up with these wacky multiple-choice options, anyway? Surely they could use a little more real-world experience!
upvoted 0 times
...
Gwenn
1 year ago
D is the way to go, for sure. Maybe the other options would work in a different scenario, but this one clearly calls for associating the relevant fields.
upvoted 0 times
Margot
1 year ago
D) Create an association between the EmpID and EmployeelD fields
upvoted 0 times
...
Skye
1 year ago
C) Force an association between the InternEmp and the Orders tables
upvoted 0 times
...
Brittney
1 year ago
B) Concatenate the InternEmp table to the Employees tables within Data manager
upvoted 0 times
...
Maryln
1 year ago
A) Create a concatenated key to associate the Employees and InternEmp tables
upvoted 0 times
...
...
Raymon
1 year ago
Hmm, D looks good to me. Can't imagine why anyone would choose to concatenate tables or force associations - that just sounds like a mess waiting to happen.
upvoted 0 times
...
Shayne
1 year ago
I'm going with D as well. Concatenating tables or forcing associations doesn't seem like the right approach here. Let's keep it simple!
upvoted 0 times
Stephanie
1 year ago
Yeah, D seems like the most straightforward solution. Let's create that association.
upvoted 0 times
...
Emiko
1 year ago
I agree, keeping it simple is usually the best approach. Let's go with D.
upvoted 0 times
...
Jani
1 year ago
I think D is the best option. It makes sense to create an association between the EmpID and EmployeeID fields.
upvoted 0 times
...
...
Lizbeth
1 year ago
I disagree, I believe the correct answer is D) Create an association between the EmpID and EmployeelD fields.
upvoted 0 times
...
Shad
1 year ago
The correct answer is D. Creating an association between the EmpID and EmployeeID fields is the way to go. Seems straightforward enough.
upvoted 0 times
Wayne
1 year ago
I agree with you, D is the correct answer. Creating an association between the EmpID and EmployeeID fields is the way to go.
upvoted 0 times
...
Rocco
1 year ago
I disagree, I believe the correct answer is B. Concatenating the tables within Data manager makes more sense.
upvoted 0 times
...
Jannette
1 year ago
I think the answer is A. Creating a concatenated key seems like the best option.
upvoted 0 times
...
...
Noble
1 year ago
I think the answer is A) Create a concatenated key to associate the Employees and InternEmp tables.
upvoted 0 times
...

Save Cancel