MENU
There is a need to relate two entities in the data structure: Employee and Skill.
Employees can have multiple skills, and a single skill can relate to multiple employees.
What kind of relationship would these entities have, and what is the minimum number of tables required to implement the design, according to Appian best practices? (Choose the best answer.)
Suggested Answer: C
Get Premium ACD200 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
DY
Dyan
10 months ago
Hmm, I thought one-to-many was a possibility too.
SH
Shawnna
11 months ago
Totally agree, many-to-many is the way to go!
ED
Edward
11 months ago
Wait, are we sure it’s not just 2 tables?
AJ
Aja
11 months ago
I think it requires 3 tables for proper normalization.
SH
Shawna
11 months ago
It's definitely a many-to-many relationship!
LE
Lenita
12 months ago
I feel like it’s definitely many-to-many, but I’m confused about the number of tables. I thought it was always 3 for that kind of relationship.
BR
Britt
12 months ago
I practiced a similar question, and I believe the answer is many-to-many with 2 tables, but I might be mixing it up with one-to-many scenarios.
AL
Alaine
12 months ago
I’m not entirely sure, but I remember something about needing a junction table for many-to-many relationships. Does that mean we need 3 tables?
AD
Adrianna
1 year ago
I think the relationship is many-to-many since an employee can have multiple skills and a skill can belong to multiple employees.
LA
Lashawnda
1 year ago
The key here is understanding the relationship between Employees and Skills. Since each employee can have multiple skills, and each skill can be associated with multiple employees, the answer must be B, many-to-many with 2 tables.
DE
Desirae
1 year ago
I'm leaning towards D, many-to-many with 3 tables. That would allow us to store additional metadata about the relationship between Employees and Skills, like the proficiency level or date acquired. But I'm not 100% sure if that's the Appian best practice.
MA
Maira
1 year ago
Okay, I think I've got it. Since each employee can have multiple skills, and each skill can be associated with multiple employees, the relationship must be many-to-many. So the answer is B, 2 tables.
ER
Ernestine
1 year ago
Hmm, I'm a bit unsure here. I know we need to model the relationship between Employees and Skills, but I'm not sure if it's one-to-many or many-to-many. Let me think this through carefully.
LI
Lizbeth
1 year ago
This seems like a classic many-to-many relationship between Employees and Skills. I'm pretty confident the answer is B.
MI
Miss
1 year ago
Option B all the way! It's the most efficient way to handle this scenario. Plus, who needs more than 2 tables anyway? One-stop shopping, baby!
AU
Augustine
1 year ago
Definitely! Who needs more than 2 tables anyway? Option B is the way to go.
LE
Leontine
1 year ago
Agreed! It's the most efficient way to handle the scenario with Employee and Skill entities.
MO
Mozell
1 year ago
I think option B is the way to go. Many-to-many relationship with 2 tables is efficient.
ME
Meghann
1 year ago
Wow, this is a classic database design question. I'm confident option B is the right answer. Gotta love those many-to-many relationships!
EL
Elden
1 year ago
Definitely, having a clear understanding of the relationship helps in structuring the data effectively.
MA
Magdalene
1 year ago
I agree, it's important to properly model the relationship between entities in the database design.
GO
Golda
1 year ago
Yeah, it makes sense to have 2 tables for a many-to-many relationship between employees and skills.
VI
Virgie
1 year ago
I think option B is correct too. Many-to-many relationships are common in database design.
AU
Audria
1 year ago
Haha, I bet the exam writer is trying to trick us with these options. But I'm going with B, it's the simplest and most straightforward solution.
MI
Mila
1 year ago
User1: Definitely, keeping it simple with just 2 tables is the way to go.
AS
Asha
1 year ago
User2: Yeah, I agree. It's the most efficient way to represent the relationship between employees and skills.
CA
Carmen
1 year ago
User1: I think B is the answer too, it makes sense for multiple skills and employees to be connected.
GE
Gerardo
1 year ago
I think option D is the best answer. A many-to-many relationship requires 3 tables to properly implement it.
ZA
Zana
1 year ago
Yes, you are correct. Option D is the best answer for a many-to-many relationship.
ZA
Zana
1 year ago
I agree, option D is correct. Many-to-many relationships typically require 3 tables.
DO
Dominga
1 year ago
The relationship between Employee and Skill is many-to-many, so option B is the correct answer. We need 2 tables to implement this design according to Appian best practices.
AZ
Azzie
2 years ago
But wouldn't we need 3 tables for many-to-many relationship?
RE
Rebeca
2 years ago
I agree with Rikki, many-to-many makes sense for this scenario.
RI
Rikki
2 years ago
I think the relationship would be many-to-many.