Qlik Exam QSBA2021 Topic 2 Question 40 Discussion

Actual exam question for Qlik's QSBA2021 exam

Question #: 40
Topic #: 2

[All QSBA2021 Questions]

Refer to the exhibit.

A business analyst must add a list of interns to the current sates app. The app contains an existing employees table When the business analyst profiles the data the association vow displays possible associations as shown.

Which action should the business analyst take to meet the requirements?

ACreate a concatenated key to associate the Employees and internEmp tables

BForce an association between the InternEmp and the Orders tables

CCreate an association between the EmpID and EmployeelD fields

DConcatenate the InternEmp table to the Employees tables within data manager

Show Suggested Answer

Suggested Answer: D

by Jesusita at Apr 14, 2024, 12:18 AM

Limited Time Offer

25%

Off

Get Premium QSBA2021 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Tammi

6 months ago

I'm not sure, but forcing an association between the InternEmp and the Orders tables could also work.

upvoted 0 times

...

Dominic

6 months ago

But wouldn't it be better to concatenate the InternEmp table to the Employees tables within data manager?

upvoted 0 times

...

Glen

7 months ago

I agree, it seems like the most logical step to meet the requirements.

upvoted 0 times

...

Rene

7 months ago

I think we should create an association between the EmpID and EmployeelD fields.

upvoted 0 times

...

Mozell

7 months ago

Okay, let's think this through step-by-step. The business analyst needs to add interns to the current sales app, which has an existing Employees table. The 'association vow' seems to be showing possible associations between the tables. Based on that, I think option C is the best choice - creating a direct association between the EmpID and EmployeeID fields.

upvoted 0 times

...

Ahmed

7 months ago

I'm a bit confused by the wording of this question too. What exactly is the 'association vow'? Is that some kind of database jargon I'm not familiar with? Anyway, I'm leaning towards option C as well, since that seems to be the most direct way to associate the Employees and InternEmp tables.

upvoted 0 times

...

Anglea

7 months ago

Ha! 'Association vow'? Sounds like someone's getting married to their database. In all seriousness though, I think option C is the way to go. Linking the EmpID and EmployeeID fields makes the most sense to me based on the information provided.

upvoted 0 times

...

Lourdes

7 months ago

I agree with Florinda, option C does seem like the logical choice here. Trying to force an association between the InternEmp and Orders tables (option B) doesn't seem relevant to the given requirement. And concatenating the tables (options A and D) also doesn't seem like the best approach.

upvoted 0 times

Natalie

6 months ago

I agree, linking the tables using EmpID and EmployeeID seems like the right approach.

upvoted 0 times

...

Johnna

6 months ago

I think option C makes the most sense.

upvoted 0 times

...

Florinda

7 months ago

Hmm, this is a tricky one. Based on the information provided, it sounds like we need to associate the Employees and InternEmp tables in some way. I'm leaning towards option C, creating an association between the EmpID and EmployeeID fields, as that seems like the most straightforward approach.

upvoted 0 times

...

Kayleigh

8 months ago

I'm not really sure about this question. The options seem a bit confusing, and I'm not sure what the 'association vow' is referring to. I think I'll need to carefully review the exhibit images to try to understand the context better.

upvoted 0 times

...